6 Replies Latest reply on Nov 27, 2012 9:16 AM by kcbabo

Install swithyard in JBoss AS7 installation but start failed with configuration error

zhfeng Nov 27, 2012 2:56 AM

Hi,

I just downloand the switchyard-installer and install in as7 with the following step:

1. unzip switchyard-installer-0.6.0.Final.zip
2. cd swithyard-installer-0.6
3. ant -DAS7_PATH=$JBOSS_HOME
4. cd $JBOSS_HOME && bin/standalone.sh

the as7 start failed with the error

=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /home/zhfeng/Downloads/jboss-as-7.1.1.Final

  JAVA: /opt/jdk1.6.0_27/bin/java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

=========================================================================

15:40:11,722 INFO    [org.jboss.modules] JBoss Modules version 1.1.1.GA
15:40:11,866 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
15:40:11,907 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
15:40:12,316 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
    at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[26,5]
Message: JBAS014789: Unexpected element 'extension' encountered
    at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.parsing.ParseUtils.requireNamespace(ParseUtils.java:212) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:107) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:305) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:127) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
    at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
    at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    ... 3 more

15:40:12,330 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:40:12,346 INFO  [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final "Brontes" stopped in 3ms

It looks like the standalone/configuration/standalone.xml with the empty xmlns

 <extension module="org.jboss.as.web"/>
        <extension module="org.jboss.as.webservices"/>
        <extension module="org.jboss.as.weld"/>
    <extension xmlns="" module="org.switchyard"/>
</extensions>

I manually remove all empty "xmlns" in configuration/stadalone-*.xml and modules/org/hibernate/main/module.xml then the as7 works.

so is it possible issue in xslt tranfer or I did something wrong ?

Thanks,

Amos

1. Re: Install swithyard in JBoss AS7 installation but start failed with configuration error

mageshbk Nov 27, 2012 6:02 AM (in response to zhfeng)

I just tried it with the upstream and could not replicate it. Here is what I answered, could you tell me if this is what you did?

download-sy-as7-check:


download-sy-as7:


request-sy-install:
    [input] Would you like to install the SwitchYard distribution to your AS7 installation (y/n)? ([y], n)




get-jboss-path-question:


get-jboss-path:


install:


notAS7:


unzipSwitchyardResources:
    [unzip] Expanding: /home/magesh/Tests/switchyard-installer-0.7/res/switchyard-as7-bundle.zip into /home/magesh/Tests/jboss-as-7.1.1.Final
     [xslt] Transforming into /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration
     [xslt] Processing /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration/standalone-full.xml to /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration/standalone-full.html
     [xslt] Loading stylesheet /home/magesh/Tests/switchyard-installer-0.7/res/standalone.xsl
     [xslt] Processing /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration/standalone-ha.xml to /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration/standalone-ha.html
     [xslt] Processing /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml to /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration/standalone.html
     [move] Moving 1 file to /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration
     [move] Moving 1 file to /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration
     [move] Moving 1 file to /home/magesh/Tests/jboss-as-7.1.1.Final/standalone/configuration


transform-console-module:
     [xslt] Transforming into /home/magesh/Tests/jboss-as-7.1.1.Final/modules/org/jboss/as/console/main
     [xslt] Processing /home/magesh/Tests/jboss-as-7.1.1.Final/modules/org/jboss/as/console/main/module.xml to /home/magesh/Tests/jboss-as-7.1.1.Final/modules/org/jboss/as/console/main/module.html
     [xslt] Loading stylesheet /home/magesh/Tests/switchyard-installer-0.7/res/console_module.xsl
     [move] Moving 1 file to /home/magesh/Tests/jboss-as-7.1.1.Final/modules/org/jboss/as/console/main


unzipQuickstartResources:
    [unzip] Expanding: /home/magesh/Tests/switchyard-installer-0.7/res/switchyard-as7-bundle.zip into /home/magesh/Tests/switchyard-installer-0.7


request-forge-install:
    [input] Would you like to install the SwitchYard Forge Module (y/n)? ([y], n)
n


check-forge-home:


request-forge-home:


set-forge-home:


validate-forge-home-version:


download-sy-forge-module-check:


download-sy-tools-check:


download-sy-tools:


extract-sy-tools-forge:


download-sy-forge-module:


install-forge:


request-sy-console-install:
    [input] Would you like to install the SwitchYard Console (y/n)? ([y], n)
n


download-sy-console-check:


download-sy-tools-check:


download-sy-tools:


extract-sy-tools-console:


download-sy-console:


install-sy-console:


request-bpel-console-install:
    [input] Would you like to install the BPEL Console (y/n)? ([y], n)
n


download-bpel-console-check:


download-sy-tools-check:


download-sy-tools:


extract-sy-tools-bpel-console:


download-bpel-console:


install-bpel-console:


BUILD SUCCESSFUL

2. Re: Install swithyard in JBoss AS7 installation but start failed with configuration error

vrlgohel Nov 27, 2012 8:09 AM (in response to mageshbk)

Hi Magesh,

I also follwed the steps that you have provied and highlighted above.
After doing the same, I start the Jboss AS 7.1.2, i get the below error/exception and the server is not able to start,

18:18:55,896 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
          at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at org.jboss.as.server.ServerService.boot(ServerService.java:270) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[26,5]
Message: JBAS014789: Unexpected element 'extension' encountered
          at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at org.jboss.as.controller.parsing.ParseUtils.requireNamespace(ParseUtils.java:212) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:107) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:306) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:127) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:99) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]
          at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]
          at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
          ... 3 more

18:18:55,929 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

Also, here are the 'null' namespaces we have in standalone.xml

<extension xmlns="" module="org.switchyard"/>
<datasource xmlns="" use-java-context="true" enabled="true" pool-name="jbpmDS" jndi-name="java:jboss/datasources/jbpmDS">
<security-domain xmlns="" cache-type="default" name="bpel-console">
Actions
3. Re: Install swithyard in JBoss AS7 installation but start failed with configuration error

rcernich Nov 27, 2012 8:50 AM (in response to vrlgohel)

Hey all,

I believe the issue is with the null namespace entries (i.e. xmlns=""). Removing those from the configuration (e.g. standalone.xml) should correct the problem.

I believe this has to do with the version of some jar that gets slurped in by ant on some systems. I see this problem myself on my machine.

Hope that helps.

Rob
Actions
4. Re: Install swithyard in JBoss AS7 installation but start failed with configuration error

vrlgohel Nov 27, 2012 9:11 AM (in response to rcernich)

That's really not a good solution though.
And perhaps, when i remove the 'null' namespaces manually, still Jboss is not able to start the cleanly, i get the below stack trace,

19:26:50,014 WARN [org.jboss.modules] (ServerService Thread Pool -- 50) Failed to define class org.jboss.weld.servlet.WeldListener in Module "org.jboss.weld.core:main" from local module loader @7808b9 (roots: /VirtualMachines/Jboss_Servers/jboss-as-7/modules): org.jboss.modules.ModuleLoadError: Module org.jboss.interceptor:main is not found in local module loader @7808b9 (roots: /VirtualMachines/Jboss_Servers/jboss-as-7/modules)
          at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_24]
          at java.lang.ClassLoader.defineClass(ClassLoader.java:634) [rt.jar:1.6.0_24]
          at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [rt.jar:1.6.0_24]
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
          at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
          at org.jboss.threads.JBossThread.run(JBossThread.java:122)

19:26:50,039 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 50) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "weld")]): java.lang.NoClassDefFoundError: org/jboss/weld/servlet/WeldListener
          at org.jboss.as.weld.deployment.processors.WebIntegrationProcessor.<clinit>(WebIntegrationProcessor.java:66)
          at org.jboss.as.weld.WeldSubsystemAdd$1.execute(WeldSubsystemAdd.java:65)
          at org.jboss.as.server.AbstractDeploymentChainStep.execute(AbstractDeploymentChainStep.java:50)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
          at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
          at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-1.jar:2.0.0.GA-redhat-1]
Caused by: java.lang.ClassNotFoundException: org.jboss.weld.servlet.WeldListener from [Module "org.jboss.as.weld:main" from local module loader @7808b9 (roots: /VirtualMachines/Jboss_Servers/jboss-as-7/modules)]
          at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.2.GA-redhat-1]

          ... 11 more

19:26:50,265 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080
19:26:50,417 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
19:26:50,418 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/jbpmDS]
19:26:50,509 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014784: Failed executing subsystem weld boot operations
19:26:50,525 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "switchyard-bpel-console.war"
19:26:50,528 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) JBAS015012: Started FileSystemDeploymentService for directory /VirtualMachines/Jboss_Servers/jboss-as-7/standalone/deployments
19:26:50,528 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "switchyard-bpel-console-server.war"
19:26:50,538 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:4447
19:26:50,540 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on 127.0.0.1:9999
19:26:51,707 WARN [org.jboss.as.dependency.private] (MSC service thread 1-8) JBAS018567: Deployment "deployment.switchyard-bpel-console.war" is using a private module ("org.javassist:main") which may be changed or removed in future versions without notice.
19:26:51,707 WARN [org.jboss.as.dependency.private] (MSC service thread 1-8) JBAS018567: Deployment "deployment.switchyard-bpel-console.war" is using a private module ("org.javassist:main") which may be changed or removed in future versions without notice.
19:26:51,724 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-jaxrs:main") which may be changed or removed in future versions without notice.
19:26:51,724 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-jaxrs:main") which may be changed or removed in future versions without notice.
19:26:51,726 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-jaxb-provider:main") which may be changed or removed in future versions without notice.
19:26:51,726 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-jaxb-provider:main") which may be changed or removed in future versions without notice.
19:26:51,728 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-multipart-provider:main") which may be changed or removed in future versions without notice.
19:26:51,728 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-multipart-provider:main") which may be changed or removed in future versions without notice.
19:26:51,893 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.switchyard-bpel-console-server.war:main" from Service Module Loader
19:26:51,902 INFO [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011907: Register module: Module "deployment.switchyard-bpel-console.war:main" from Service Module Loader
19:26:52,118 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Deploying javax.ws.rs.core.Application: class org.jboss.bpm.console.server.ConsoleServerApplication
19:26:52,123 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.console.server.ProcessMgmtFacade from Application javax.ws.rs.core.Application
19:26:52,124 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.console.server.InfoFacade from Application javax.ws.rs.core.Application
19:26:52,124 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.report.ReportFacade from Application javax.ws.rs.core.Application
19:26:52,124 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.console.server.TaskListFacade from Application javax.ws.rs.core.Application
19:26:52,125 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.console.server.FormProcessingFacade from Application javax.ws.rs.core.Application
19:26:52,125 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.console.server.UserMgmtFacade from Application javax.ws.rs.core.Application
19:26:52,125 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.console.server.EngineFacade from Application javax.ws.rs.core.Application
19:26:52,126 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.console.server.TaskMgmtFacade from Application javax.ws.rs.core.Application
19:26:52,126 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-6) Adding singleton resource org.jboss.bpm.console.server.ProcessHistoryFacade from Application javax.ws.rs.core.Application
19:26:52,225 ERROR [org.reflections.Reflections] (MSC service thread 1-4) could not create Vfs.Dir from url. ignoring the exception and continuing: org.reflections.ReflectionsException: could not create Dir using org.jboss.errai.bus.server.service.metadata.VFSUrlType from url vfs:/content/switchyard-bpel-console.war/WEB-INF/classes/
          at org.reflections.vfs.Vfs.fromURL(Vfs.java:99) [reflections-0.9.5-RC2_jboss-SP1.jar:]
          at org.reflections.vfs.Vfs.fromURL(Vfs.java:89) [reflections-0.9.5-RC2_jboss-SP1.jar:]
          at org.reflections.Reflections.scan(Reflections.java:136) [reflections-0.9.5-RC2_jboss-SP1.jar:]
          at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.<init>(MetaDataScanner.java:83) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.createInstance(MetaDataScanner.java:95) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.createInstance(MetaDataScanner.java:87) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.service.ErraiServiceConfiguratorImpl.<init>(ErraiServiceConfiguratorImpl.java:58) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.service.ErraiServiceConfiguratorImpl$$FastClassByGuice$$b6139751.newInstance(<generated>)
          at com.google.inject.internal.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40) [guice-2.0.jar:]
          at com.google.inject.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60) [guice-2.0.jar:]
          at com.google.inject.ConstructorInjector.construct(ConstructorInjector.java:85) [guice-2.0.jar:]
          at com.google.inject.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:111) [guice-2.0.jar:]
          at com.google.inject.FactoryProxy.get(FactoryProxy.java:56) [guice-2.0.jar:]
          at com.google.inject.SingleParameterInjector.inject(SingleParameterInjector.java:42) [guice-2.0.jar:]
          at com.google.inject.SingleParameterInjector.getAll(SingleParameterInjector.java:66) [guice-2.0.jar:]
          at com.google.inject.ConstructorInjector.construct(ConstructorInjector.java:84) [guice-2.0.jar:]
          at com.google.inject.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:111) [guice-2.0.jar:]
          at com.google.inject.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:45) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl.callInContext(InjectorImpl.java:811) [guice-2.0.jar:]
          at com.google.inject.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:42) [guice-2.0.jar:]
          at com.google.inject.Scopes$1$1.get(Scopes.java:54) [guice-2.0.jar:]
          at com.google.inject.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:48) [guice-2.0.jar:]
          at com.google.inject.FactoryProxy.get(FactoryProxy.java:56) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl$4$1.call(InjectorImpl.java:758) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl.callInContext(InjectorImpl.java:804) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl$4.get(InjectorImpl.java:754) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl.getInstance(InjectorImpl.java:793) [guice-2.0.jar:]
          at org.jboss.errai.bus.server.servlet.AbstractErraiServlet.buildService(AbstractErraiServlet.java:133) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
          at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]

19:26:52,229 ERROR [org.reflections.Reflections] (MSC service thread 1-4) could not create Vfs.Dir from url. ignoring the exception and continuing: org.reflections.ReflectionsException: could not create Dir using org.jboss.errai.bus.server.service.metadata.VFSUrlType from url vfs:/content/switchyard-bpel-console.war/WEB-INF/lib/activity-monitor-ui-lib-1.2.1.Final.jar/
          at org.reflections.vfs.Vfs.fromURL(Vfs.java:99) [reflections-0.9.5-RC2_jboss-SP1.jar:]
          at org.reflections.vfs.Vfs.fromURL(Vfs.java:89) [reflections-0.9.5-RC2_jboss-SP1.jar:]
          at org.reflections.Reflections.scan(Reflections.java:136) [reflections-0.9.5-RC2_jboss-SP1.jar:]
          at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.<init>(MetaDataScanner.java:83) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.createInstance(MetaDataScanner.java:95) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.createInstance(MetaDataScanner.java:87) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.service.ErraiServiceConfiguratorImpl.<init>(ErraiServiceConfiguratorImpl.java:58) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.service.ErraiServiceConfiguratorImpl$$FastClassByGuice$$b6139751.newInstance(<generated>)
          at com.google.inject.internal.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40) [guice-2.0.jar:]
          at com.google.inject.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60) [guice-2.0.jar:]
          at com.google.inject.ConstructorInjector.construct(ConstructorInjector.java:85) [guice-2.0.jar:]
          at com.google.inject.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:111) [guice-2.0.jar:]
          at com.google.inject.FactoryProxy.get(FactoryProxy.java:56) [guice-2.0.jar:]
          at com.google.inject.SingleParameterInjector.inject(SingleParameterInjector.java:42) [guice-2.0.jar:]
          at com.google.inject.SingleParameterInjector.getAll(SingleParameterInjector.java:66) [guice-2.0.jar:]
          at com.google.inject.ConstructorInjector.construct(ConstructorInjector.java:84) [guice-2.0.jar:]
          at com.google.inject.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:111) [guice-2.0.jar:]
          at com.google.inject.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:45) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl.callInContext(InjectorImpl.java:811) [guice-2.0.jar:]
          at com.google.inject.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:42) [guice-2.0.jar:]
          at com.google.inject.Scopes$1$1.get(Scopes.java:54) [guice-2.0.jar:]
          at com.google.inject.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:48) [guice-2.0.jar:]
          at com.google.inject.FactoryProxy.get(FactoryProxy.java:56) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl$4$1.call(InjectorImpl.java:758) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl.callInContext(InjectorImpl.java:804) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl$4.get(InjectorImpl.java:754) [guice-2.0.jar:]
          at com.google.inject.InjectorImpl.getInstance(InjectorImpl.java:793) [guice-2.0.jar:]
          at org.jboss.errai.bus.server.servlet.AbstractErraiServlet.buildService(AbstractErraiServlet.java:133) [errai-bus-1.1-Final.jar:1.1-Final]
          at org.jboss.errai.bus.server.servlet.AbstractErraiServlet.init(AbstractErraiServlet.java:104) [errai-bus-1.1-Final.jar:1.1-Final]


          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
          at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
Actions
5. Re: Install swithyard in JBoss AS7 installation but start failed with configuration error

kcbabo Nov 27, 2012 9:15 AM (in response to vrlgohel)

Try not installing the BPEL console. There are a few issues with BPEL console on startup which are registered as part of this JIRA:
https://issues.jboss.org/browse/SWITCHYARD-719

The Riftsaw team is working on a fix. For now, I would either ignore the error or simply not install the BPEL console if you won't be using it.

BTW, the installer in the project is based on AS 7.1.1 and I noticed you are installing into EAP 6.0 / AS 7.1.2. We had to patch the version of Weld in AS 7.1.1 and that patch is no longer required in AS 7.1.2, so you may end up hitting an issue there as well.
Actions
6. Re: Install swithyard in JBoss AS7 installation but start failed with configuration error

kcbabo Nov 27, 2012 9:16 AM (in response to kcbabo)

I should mention that others in the community and our internal build team have successfully run SwitchYard on top of EAP 6.0. My comment about the AS version above is just to point out that the community installer is targeted at the latest community release of the AS. As soon as a more recent community release of the AS is available we will upgrade the installer to reflect that.
Actions

Go to original post