Bug 780216 (SOA-2601) - opensso ear does not deploy
Summary: opensso ear does not deploy
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2601
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Examples
Version: 5.1.0.ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Douglas Palmer
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
: SOA-2602 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-23 13:58 UTC by mvanek
Modified: 2015-09-28 02:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-14 12:51:48 UTC
Type: Bug


Attachments (Terms of Use)
opensso-ear.zip (8.84 KB, application/zip)
2010-11-26 12:51 UTC, Kevin Conner
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2601 0 Major Closed opensso ear does not deploy 2013-05-31 17:04:47 UTC

Description mvanek 2010-11-23 13:58:40 UTC
Workaround: Workaround Exists
Workaround Description: Modify quickstarts/opensso/opensso-ear/src/main/resources/META-INF/application.xml to:
==================================================================
<?xml version="1.0" encoding="UTF-8"?>
<aop xmlns="urn:jboss:aop-beans:1.0">
   <aspect class="org.jboss.internal.soa.esb.opensso.aspect.PresetConfigDirAspect" scope="PER_VM"/>
   <aspect class="org.jboss.internal.soa.esb.opensso.aspect.SystemPropertyAspect" scope="PER_VM"/>
   <aspect class="org.jboss.internal.soa.esb.opensso.aspect.ShutdownHookAspect" scope="PER_VM"/>
   
   <bind pointcut="withincode(* com.sun.identity.setup.AMSetupServlet->getPresetConfigDir(..)) AND call(* java.util.ResourceBundle->getBundle(..))">
      <advice name="getBundle" aspect="org.jboss.internal.soa.esb.opensso.aspect.PresetConfigDirAspect"/>
   </bind>
   <bind pointcut="withincode(* com.sun.identity.setup.AMSetupServlet->getPresetConfigDir(..)) AND call(* java.util.ResourceBundle->getString(..))">
      <advice name="getString" aspect="org.jboss.internal.soa.esb.opensso.aspect.PresetConfigDirAspect"/>
   </bind>

   <bind pointcut="execution(* com.sun.identity.classloader.FAMClassLoader->setSystemProperties(..))">
      <advice name="setSystemProperties" aspect="org.jboss.internal.soa.esb.opensso.aspect.SystemPropertyAspect"/>
   </bind>

   <bind pointcut="execution(* com.sun.identity.common.ShutdownServletContextListener->contextInitialized(..))">
      <advice name="contextInitialized" aspect="org.jboss.internal.soa.esb.opensso.aspect.ShutdownHookAspect"/>
   </bind>
</aop>

project_key: SOA

When trying to deploy opensso-1.0.ear, server logs the following stack trace. Since JBoss 5, jboss-aop.xml must contain namespace def. xmlns="urn:jboss:aop-beans:1.0".
============================================================
14:37:24,793 DEBUG [MainDeployerImpl] Add deployment: vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/
14:37:24,979 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@74c4178a, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
14:37:24,979 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
14:37:24,979 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
14:37:24,979 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
14:37:24,979 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
14:37:24,980 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@74c4178a, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
14:37:25,870 DEBUG [MainDeployerImpl] Scheduling deployment: vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/ parent=null
14:37:25,871 DEBUG [MainDeployerImpl] Scheduling deployment: vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/opensso-aop-1.0.aop/ parent=AbstractVFSDeploymentContext@1749056972{vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/}
14:37:25,871 DEBUG [MainDeployerImpl] Scheduling deployment: vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/opensso.war/ parent=AbstractVFSDeploymentContext@1749056972{vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/}
14:37:25,885 DEBUG [DeployersImpl] Deploying vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/
14:37:25,889 DEBUG [JBossXBHelper] Parsing file: opensso-1.0.ear/opensso-aop-1.0.aop/META-INF/jboss-aop.xml for type: class org.jboss.aop.microcontainer.beans.metadata.AOPDeployment
14:37:25,889 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@7986e192, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
14:37:25,890 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
14:37:25,890 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
14:37:25,890 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/xinclude/fixup-base-uris set to: false
14:37:25,890 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/xinclude/fixup-language set to: false
14:37:25,890 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
14:37:25,890 DEBUG [SaxJBossXBParser] http://apache.org/xml/features/validation/schema set to: true
14:37:25,890 DEBUG [SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
14:37:25,890 DEBUG [SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@7986e192, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
14:37:25,920 DEBUG [SchemaResolverDeployer] Error during deploy: vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/opensso-aop-1.0.aop/
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/opensso-aop-1.0.aop/
	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to parse schema for nsURI=, baseURI=null, schemaLocation=http://labs.jboss.com/portal/jbossaop/dtd/jboss-aop_1_0.dtd
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
	at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
	at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
	at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
	at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
	at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
	at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304)
	at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:269)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:355)
	... 29 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to parse schema for nsURI=, baseURI=null, schemaLocation=http://labs.jboss.com/portal/jbossaop/dtd/jboss-aop_1_0.dtd
	at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:293)
	at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:274)
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
	at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
	at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
	at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
	at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
	... 37 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 3:3 The markup in the document preceding the root element must be well-formed.
	at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40)
	at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source)
	at org.apache.xerces.impl.xs.XSLoaderImpl.load(Unknown Source)
	at org.jboss.xb.binding.Util.loadSchema(Util.java:395)
	at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:176)
	at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:147)
	at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:285)
	... 53 more
14:37:25,928 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/ state=PreParse mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/opensso-aop-1.0.aop/
	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to parse schema for nsURI=, baseURI=null, schemaLocation=http://labs.jboss.com/portal/jbossaop/dtd/jboss-aop_1_0.dtd
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
	at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
	at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
	at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
	at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
	at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
	at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304)
	at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:269)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:355)
	... 29 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to parse schema for nsURI=, baseURI=null, schemaLocation=http://labs.jboss.com/portal/jbossaop/dtd/jboss-aop_1_0.dtd
	at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:293)
	at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:274)
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
	at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
	at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
	at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
	at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
	... 37 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 3:3 The markup in the document preceding the root element must be well-formed.
	at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40)
	at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source)
	at org.apache.xerces.impl.xs.XSLoaderImpl.load(Unknown Source)
	at org.jboss.xb.binding.Util.loadSchema(Util.java:395)
	at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:176)
	at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:147)
	at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:285)
	... 53 more
14:37:25,937 WARN  [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS MISSING DEPLOYERS: Name

vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/

*** DEPLOYMENTS IN ERROR: Name -> Error

vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/ -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/opensso-aop-1.0.aop/


DEPLOYMENTS IN ERROR:
  Deployment "vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 3:3 The markup in the document preceding the root element must be well-formed.

	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1008)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:954)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

Comment 1 Kevin Conner 2010-11-23 14:03:28 UTC
This is a platform quickstart and not one taken from ESB.

Comment 2 Kevin Conner 2010-11-24 09:30:38 UTC
I am going to work through the deployment issues with Julian

Comment 3 Kevin Conner 2010-11-24 09:31:16 UTC
Also included in this is the issue raised in SOA-2602

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Content is not allowed in prolog. @ vfszip:/home/mvanek/work/er4/jboss-as/server/production/deploy/opensso-1.0.ear/META-INF/application.xml[1,1] 

Comment 4 Kevin Conner 2010-11-24 09:31:45 UTC
Link: Added: This issue is duplicated by SOA-2602


Comment 5 Kevin Conner 2010-11-26 12:49:41 UTC
There are four changes to be made

- The identified application.xml change
- The identified jboss-aop.xml change
- Update of the build.xml to use the app server jars
- Update of the war file creation to remove jsr173_api.jar

Comment 6 Kevin Conner 2010-11-26 12:51:49 UTC
New contents

Comment 7 Kevin Conner 2010-11-26 12:51:49 UTC
Attachment: Added: opensso-ear.zip


Comment 8 Kevin Conner 2010-11-26 13:12:06 UTC
I would have attached the generated ear file but the new jira spent 20 mins trying to upload, even before I had pressed the attach button, before telling me that it was larger than 10Mb.

The new ear can be regenerated by removing the opensso-ear directory and replacing it with the current attachment.


Comment 9 Douglas Palmer 2010-11-30 15:26:38 UTC
Repleace ear files

Comment 10 mvanek 2010-12-13 16:27:21 UTC
Works in 5.1.0.ER5.

Comment 12 Dana Mison 2011-01-05 00:14:38 UTC
Writer: Added: dlesage


Comment 13 David Le Sage 2011-02-10 23:16:41 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2601

A stack trace error occurred when opensso-1.0.ear was run.  This was because there was data in the prologue, meaning it could not be parsed. Changes have been made to the configuration files and a JAR has been removed so that it can now run without error.


Comment 14 David Le Sage 2011-02-10 23:17:56 UTC
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2601

A stack trace error occurred when opensso-1.0.ear was run.  This was because there was data in the prologue, meaning it could not be parsed. Changes have been made to the configuration files and a JAR has been removed so that it can now run without error. Added: https://issues.jboss.org/browse/SOA-2601

A stack trace error occurred when opensso-1.0.ear was run.  This was because there was data in the prologue, meaning it could not be parsed. Changes have been made to the configuration files and the jsr173_api.jar file has been removed removed from the WAR archive so that it can now be deployed without error.


Comment 15 Laura Bailey 2011-02-12 12:10:25 UTC
{quote}* Update of the build.xml to use the app server jars
* Update of the war file creation to remove jsr173_api.jar{quote}

Was the build.xml updated in order to use AS JARs instead of jsr173_api.jar, or are these points unrelated and jsr173_api.jar is just not necessary any more? I need a little more information to write the release note for this JIRA.

Comment 16 Laura Bailey 2011-02-12 12:23:53 UTC
Writer: Removed: dlesage Added: laubai
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2601

A stack trace error occurred when opensso-1.0.ear was run.  This was because there was data in the prologue, meaning it could not be parsed. Changes have been made to the configuration files and the jsr173_api.jar file has been removed removed from the WAR archive so that it can now be deployed without error. Added: The opensso-1.0.ear in the opensso ESB quickstart did not deploy. This occurred for several reasons: firstly, because the application.xml file contained a Byte Order Marker (BOM), which could not be parsed by the deployer; and secondly, because jboss-aop.xml contained an incorrect namespace definition. These errors have been removed from the configuration files. Additionally, the jsr173_api.jar is no longer included in the WAR file, and the quickstart now deploys without error.


Comment 17 Kevin Conner 2011-02-14 09:36:36 UTC
Yes, the jsr173 jar is provided by the server and its inclusion in the war file was causing a conflict at runtime.


Note You need to log in before you can comment on or make changes to this bug.