[
https://issues.apache.org/activemq/browse/SM-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41287#action_41287
]
nroe commented on SM-1223:
--------------------------
The attached file, out.txt, is a complete JBoss log from start up to shutdown.
The entire stacktrace is contained in that file.
> Deploying an SU within JBoss
> ----------------------------
>
> Key: SM-1223
> URL: https://issues.apache.org/activemq/browse/SM-1223
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.2.1
> Environment: ServiceMix 3.2.1, Java 1.6 and 1.5, and JBoss 4.0.5
> Reporter: nroe
> Attachments: out.txt
>
>
> I have an SA made up of a single SU based on the wsdl-first example. This SA
> differs from the SA produced by the example as follows:
> 1) I removed the SU that starts Jetty. I did this because I think I want
> JBoss to handle HTTP.
> 2) I removed the WSDL file. This file is apparently unnecessary.
> This modified SA deploys and works with ServiceMix as a stand-alone.
> I used the JBoss Deployer to generate my ServiceMix SAR as per this page:
> http://servicemix.apache.org/jboss-deployer.html
> At first, I received a warning about Woden during JBoss start, but I added
> the Woden JAR to the SAR's lib dir and this went away. I still receive an
> "env not bound" exception, but this is a known issue (
> https://issues.apache.org/activemq/browse/SM-1206 ) and thus is not currently
> fixable. [what does that error affect?]
> When I place the ZIP containing my SA into my JBoss deployment directory,
> ServiceMix picks it up properly. However, there is then an error that I
> don't understand:
> 15:26:25,620 INFO [org.servicemix.jboss.deployment.JBIDeployer] Init
> ServiceMix JBI Component:
> file:/C:/dev/jboss-4.0.5/server/concierge/tmp/deploy/tmp63401wsdl-first-sa-3.2.1.zip-contents/wsdl-first-jsr181-su-3.2.1.zip
> 15:26:25,620 INFO [org.servicemix.jboss.deployment.JBIDeployer] Init Watcher
> 15:26:25,620 INFO [org.servicemix.jboss.deployment.JBIDeployer] Init
> LoaderRepository
> 15:26:25,620 WARN [org.jboss.deployment.DeploymentInfo] Only the root
> deployment can set the loader repository, ignoring
> config=LoaderRepositoryConfig(repositoryName:
> org.servicemix:loader-repository=JBIContainer, repositoryClassName: null,
> configParserClassName: null, repositoryConfig: null)
> 15:26:25,620 DEBUG [org.servicemix.jboss.deployment.JBIDeployer] looking for
> nested deployments in :
> file:/C:/dev/jboss-4.0.5/server/concierge/tmp/deploy/tmp63401wsdl-first-sa-3.2.1.zip-contents/wsdl-first-jsr181-su-3.2.1.zip
> 15:26:25,620 INFO [org.servicemix.jboss.deployment.JBIDeployer] ServiceMix
> deployer passing deployment to JBI container
> [file:/C:/dev/jboss-4.0.5/server/concierge/tmp/deploy/tmp63401wsdl-first-sa-3.2.1.zip-contents/wsdl-first-jsr181-su-3.2.1.zip]
> 15:26:25,979 ERROR [org.apache.servicemix.jbi.framework.ManagementSupport]
> Error
> java.lang.RuntimeException: Could not create DOM document
> at
> org.apache.servicemix.jbi.framework.ManagementSupport.createDocument(ManagementSupport.java:186)
> at
> org.apache.servicemix.jbi.framework.ManagementSupport.createFrameworkMessage(ManagementSupport.java:155)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.failure(AutoDeploymentService.java:373)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.failure(AutoDeploymentService.java:363)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
