[JBoss JIRA] (WFLY-29) An ear file with modules in subfolders can not deploy under AS 7.0
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-29?page=com.atlassian.jira.plugin.sy... ]
Jason Greene updated WFLY-29:
-----------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.Alpha3)
> An ear file with modules in subfolders can not deploy under AS 7.0
> ------------------------------------------------------------------
>
> Key: WFLY-29
> URL: https://issues.jboss.org/browse/WFLY-29
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Reporter: Adrian Zuo
> Assignee: David Lloyd
> Fix For: 8.0.0.Beta1
>
> Attachments: migrate.ear, migrate.ear
>
>
> I have an ear file names migrate.ear which contains one ejb jar (ejb.jar) and one war file (war.war), if I put the ejb jar to a ejb folder and war file to war folder, the ear can not be depoyed.
> If I move the ejb jar and war file out, it can be deployed.
> Below structuer can be deployed:
> ejb.jar
> lib/
> lib/util-1.0-SNAPSHOT.jar
> lib/version.jar
> META-INF/
> META-INF/application.xml
> META-INF/MANIFEST.MF
> war.war
>
> Below structure can not be deployed:
> ejb/
> ejb/ejb.jar
> lib/
> lib/util-1.0-SNAPSHOT.jar
> lib/version.jar
> META-INF/
> META-INF/application.xml
> META-INF/MANIFEST.MF
> war/
> war/war.war
> Below is the error:
> http://community.jboss.org/message/630869#630869
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-16) Intermittent failure in RemoteOutboundConnectionReconnectTestCase
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-16?page=com.atlassian.jira.plugin.sy... ]
Jason Greene updated WFLY-16:
-----------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.Alpha3)
> Intermittent failure in RemoteOutboundConnectionReconnectTestCase
> -----------------------------------------------------------------
>
> Key: WFLY-16
> URL: https://issues.jboss.org/browse/WFLY-16
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Kabir Khan
> Assignee: jaikiran pai
> Priority: Critical
> Fix For: 8.0.0.Beta1
>
>
> Assigning to Jaikiran since I think this is ejb client
> This happened for IPv6 but I don't know if that has any relevance.
> The test has not been disabled
> {code}
> org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerRestarts
> Failing for the past 1 build (Since #3674 )
> Took 8.7 sec.
> add description
> Error Message
> Cannot deploy: server-two-module.jar
> Stacktrace
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: server-two-module.jar
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
> at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
> at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:145)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.deployment.ClientDeployer.deploy(ClientDeployer.java:93)
> at org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerRestarts(RemoteOutboundConnectionReconnectTestCase.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270)
> at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
> at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
> at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: java.lang.Exception: {"JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.naming.context.java.app.server-two-module.server-two-module.EchoOnServerTwo Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.naming.context.java.global.server-two-module.\"EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho\" Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.deployment.unit.\"server-two-module.jar\".component.EchoOnServerTwo.VIEW.\"org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho\".REMOTE Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.deployment.unit.\"server-two-module.jar\".deploymentCompleteService Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.naming.context.java.module.server-two-module.server-two-module.\"EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho\" Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.deployment.unit.\"server-two-module.jar\".component.EchoOnServerTwo.START Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.deployment.unit.\"server-two-module.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.naming.context.java.module.server-two-module.server-two-module.EchoOnServerTwo Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.naming.context.java.app.server-two-module.server-two-module.\"EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho\" Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.deployment.unit.\"server-two-module.jar\".jndiDependencyService Missing[JBAS014861: <one or more transitive dependencies>]",
> "jboss.naming.context.java.global.server-two-module.EchoOnServerTwo Missing[JBAS014861: <one or more transitive dependencies>]"
> ]}
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:52)
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
> ... 123 more
> Standard Output
> 02:31:11,030 INFO [org.jboss.arquillian.container.test.impl.client.container.ClientContainerController] (main) Manual starting of a server instance
> 02:31:11,053 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/opt/jdk1.6.0_29/bin/java, -Xmx512m, -XX:MaxPermSize=256m, -Djboss.dist=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/../../../build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT, -Djava.net.preferIPv4Stack=false, -Djava.net.preferIPv6Addresses=true, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=fccc::2, -Dmcast=ff01::1, -Djbossas.ts.submodule.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode, -Djbossas.ts.integ.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/.., -Djbossas.ts.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/../.., -Djbossas.project.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/../../.., -Djboss.dist=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/../../../build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT, -Djboss.inst=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/target/jbossas, -Djboss.node.name=default-jbossas, -ea, -Djboss.home.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/target/jbossas, -Dorg.jboss.boot.log.file=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/target/jbossas/standalone/log/boot.log, -Dlogging.configuration=file:/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/target/jbossas/standalone/configuration/logging.properties, -Djboss.bundles.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/../../../build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/bundles, -jar, /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/target/jbossas/jboss-modules.jar, -mp, /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/../../../build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules:/home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/target/modules, -jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config, standalone-ha.xml]
> 02:31:11,906 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA
> 02:31:12,166 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
> 02:31:12,257 INFO [org.jboss.as] JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
> 02:31:14,791 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
> 02:31:14,798 INFO [org.xnio] XNIO Version 3.0.5.GA
> 02:31:14,827 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.5.GA
> 02:31:14,848 INFO [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem
> 02:31:14,849 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
> [0m02:31:14,889 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.8.GA
> [0m[0m02:31:14,916 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) JBAS010280: Activating Infinispan subsystem.
> [0m[0m02:31:14,979 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 38) JBAS010260: Activating JGroups subsystem.
> [0m[0m02:31:14,991 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 45) JBAS011906: Activating OSGi Subsystem
> [0m[0m02:31:15,009 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 44) JBAS011800: Activating Naming Subsystem
> [0m[0m02:31:15,015 INFO [org.jboss.as.security] (ServerService Thread Pool -- 50) JBAS013171: Activating Security Subsystem
> [0m[0m02:31:15,047 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.13.Final
> [0m[0m02:31:15,161 INFO [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.12.Final)
> [0m[0m02:31:15,164 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
> [0m[0m02:31:15,332 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
> [0m[0m02:31:15,371 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]
> [0m[31m02:31:15,331 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.remoting.endpoint.subsystem: org.jboss.msc.service.StartException in service jboss.remoting.endpoint.subsystem: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
> Caused by: java.lang.NullPointerException
> at sun.nio.ch.Util.atBugLevel(Util.java:448) [rt.jar:1.6.0_29]
> at sun.nio.ch.SelectorImpl.<init>(SelectorImpl.java:40) [rt.jar:1.6.0_29]
> at sun.nio.ch.EPollSelectorImpl.<init>(EPollSelectorImpl.java:47) [rt.jar:1.6.0_29]
> at sun.nio.ch.EPollSelectorProvider.openSelector(EPollSelectorProvider.java:18) [rt.jar:1.6.0_29]
> at java.nio.channels.Selector.open(Selector.java:209) [rt.jar:1.6.0_29]
> at org.xnio.nio.NioXnioWorker.<init>(NioXnioWorker.java:112)
> at org.xnio.nio.NioXnio.createWorker(NioXnio.java:126)
> at org.jboss.remoting3.EndpointImpl.construct(EndpointImpl.java:137)
> at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:60)
> at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:73)
> at org.jboss.as.remoting.EndpointService.start(EndpointService.java:71)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> [0m[0m02:31:15,747 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> [0m[0m02:31:16,070 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.1.0.Beta2
> [0m[0m02:31:16,117 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-4) Starting Coyote AJP/1.3 on ajp-/0:0:0:0:0:0:0:1%1:8009
> [0m[0m02:31:16,117 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http-/0:0:0:0:0:0:0:1%1:8080
> [0m[0m02:31:16,357 INFO [org.jboss.modcluster.ModClusterService] (ServerService Thread Pool -- 56) Initializing mod_cluster 1.2.1.Final
> [0m[0m02:31:16,437 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (ServerService Thread Pool -- 56) Listening to proxy advertisements on ff01:0:0:0:0:0:0:3:23,364
> [0m[0m02:31:16,718 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 34) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> [0m[0m02:31:16,742 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 34) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
> [0m[0m02:31:16,908 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/target/jbossas/standalone/deployments
> [0m[0m02:31:16,927 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "dep1.jar"
> [0m[0m02:31:16,960 INFO [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on [::1]:9999
> [0m[0m02:31:16,977 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> [0m[0m02:31:17,615 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ShutdownBean in deployment unit deployment "dep1.jar" are as follows:
> java:global/dep1/ShutdownBean!org.jboss.as.test.manualmode.ejb.shutdown.RemoteEcho
> java:app/dep1/ShutdownBean!org.jboss.as.test.manualmode.ejb.shutdown.RemoteEcho
> java:module/ShutdownBean!org.jboss.as.test.manualmode.ejb.shutdown.RemoteEcho
> java:jboss/exported/dep1/ShutdownBean!org.jboss.as.test.manualmode.ejb.shutdown.RemoteEcho
> java:global/dep1/ShutdownBean
> java:app/dep1/ShutdownBean
> java:module/ShutdownBean
> [0m[0m02:31:17,617 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named LatchBean in deployment unit deployment "dep1.jar" are as follows:
> java:global/dep1/LatchBean!org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch
> java:app/dep1/LatchBean!org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch
> java:module/LatchBean!org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch
> java:jboss/exported/dep1/LatchBean!org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch
> java:global/dep1/LatchBean
> java:app/dep1/LatchBean
> java:module/LatchBean
> [0m[0m02:31:17,619 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named RealEcho in deployment unit deployment "dep1.jar" are as follows:
> java:global/dep1/RealEcho!org.jboss.as.test.manualmode.ejb.shutdown.RemoteEcho
> java:app/dep1/RealEcho!org.jboss.as.test.manualmode.ejb.shutdown.RemoteEcho
> java:module/RealEcho!org.jboss.as.test.manualmode.ejb.shutdown.RemoteEcho
> java:jboss/exported/dep1/RealEcho!org.jboss.as.test.manualmode.ejb.shutdown.RemoteEcho
> java:global/dep1/RealEcho
> java:app/dep1/RealEcho
> java:module/RealEcho
> [0m[0m02:31:18,940 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "dep1.jar"
> [0m[0m02:31:18,951 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.remoting.endpoint.subsystem: org.jboss.msc.service.StartException in service jboss.remoting.endpoint.subsystem: Failed to start service
> [0m[0m02:31:18,992 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://::1:9990/management
> [0m[0m02:31:18,994 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://::1:9990
> [0m[31m02:31:18,996 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started (with errors) in 7657ms - Started 185 of 364 services (34 services failed or missing dependencies, 144 services are passive or on-demand)
> [0m[0m02:31:19,141 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/manualmode/target/jbossas/standalone/data/content/34/cf5c1cb3656c84a2615763b9f95b3a16536c40/content
> [0m[0m02:31:19,164 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "server-two-module.jar"
> [0m[0m02:31:19,227 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named EchoOnServerTwo in deployment unit deployment "server-two-module.jar" are as follows:
> java:global/server-two-module/EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho
> java:app/server-two-module/EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho
> java:module/EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho
> java:jboss/exported/server-two-module/EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho
> java:global/server-two-module/EchoOnServerTwo
> java:app/server-two-module/EchoOnServerTwo
> java:module/EchoOnServerTwo
> [0m[0m02:31:19,578 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS015870: Deploy of deployment "server-two-module.jar" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.app.server-two-module.server-two-module.EchoOnServerTwo Missing[JBAS014861: <one or more transitive dependencies>]","jboss.naming.context.java.global.server-two-module.\"EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho\" Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"server-two-module.jar\".component.EchoOnServerTwo.VIEW.\"org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho\".REMOTE Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"server-two-module.jar\".deploymentCompleteService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.naming.context.java.module.server-two-module.server-two-module.\"EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho\" Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"server-two-module.jar\".component.EchoOnServerTwo.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"server-two-module.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.naming.context.java.module.server-two-module.server-two-module.EchoOnServerTwo Missing[JBAS014861: <one or more transitive dependencies>]","jboss.naming.context.java.app.server-two-module.server-two-module.\"EchoOnServerTwo!org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteEcho\" Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"server-two-module.jar\".jndiDependencyService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.naming.context.java.global.server-two-module.EchoOnServerTwo Missing[JBAS014861: <one or more transitive dependencies>]"]}
> [0m[0m02:31:19,652 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment server-two-module.jar in 97ms
> [0m
> Help us localize this page Page generated: Aug 31, 2012 7:20:23 AMJenkins ver. 1.473
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-8) [PassivateTask] null: java.lang.NullPointerException
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-8?page=com.atlassian.jira.plugin.sys... ]
Jason Greene updated WFLY-8:
----------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.Alpha3)
> [PassivateTask] null: java.lang.NullPointerException
> ----------------------------------------------------
>
> Key: WFLY-8
> URL: https://issues.jboss.org/browse/WFLY-8
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Beta1
>
> Attachments: server.log
>
>
> Going through the server logs from clustering testsuite suspicious NPE on INFO caught my eye. Seems like an edge case not being covered.
> Affected version: master 8a6aac3c8eb6bc94b7eddfa4d090c9ac05c7e37b
> {code}
> 15:10:57,385 INFO [org.jboss.as.ejb3.cache.spi.impl.PassivateTask] (pool-17-thread-1) null: java.lang.NullPointerException
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.prePassivate(StatefulSessionComponent.java:157) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.prePassivate(StatefulSessionComponent.java:73) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.prePassivate(SerializationGroupMemberContainer.java:165) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.prePassivate(SerializationGroupMemberContainer.java:51) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.passivate(PassivatingBackingCacheImpl.java:189) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.passivate(PassivatingBackingCacheImpl.java:60) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.cache.spi.impl.PassivateTask.run(PassivateTask.java:46) [jboss-as-ejb3-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_17]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_17]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_17]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) [rt.jar:1.7.0_17]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-11) Bundle path for Embedded server still not working properly
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-11?page=com.atlassian.jira.plugin.sy... ]
Jason Greene updated WFLY-11:
-----------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.Alpha3)
> Bundle path for Embedded server still not working properly
> ----------------------------------------------------------
>
> Key: WFLY-11
> URL: https://issues.jboss.org/browse/WFLY-11
> Project: WildFly
> Issue Type: Bug
> Reporter: Galder Zamarreño
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.Beta1
>
>
> Error is:
> {code} io.escalante.test.artifact.ArtifactInstallTest: bundlesDir not a directory{code}
> The problem is that the check is done in an 'assert' block and that only happens when assertions have been enabled by the user :(
> The problem comes cos bundlesDir is set to "null/bundles", even if I have not set any bundlesDir.
> Seems like bundlesDir is pre-computed too early in EmbeddedContainerConfiguration where it expects a system property, but that might not be set, it might come from arquillian.xml. So better delay until EmbeddedServerFactory.create.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-19) JMX over remoting pollutes query results with ModelController objects
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-19?page=com.atlassian.jira.plugin.sy... ]
Jason Greene updated WFLY-19:
-----------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.Alpha3)
> JMX over remoting pollutes query results with ModelController objects
> ---------------------------------------------------------------------
>
> Key: WFLY-19
> URL: https://issues.jboss.org/browse/WFLY-19
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JMX
> Reporter: Tristan Tarrant
> Assignee: Kabir Khan
> Fix For: 8.0.0.Beta1
>
>
> When issuing MBean queries over JMX remoting, the AS is returning a list of org.jboss.as.controller.ModelController objects in addition to those matching the query.
> This is a transcript of a chat we had about it on IRC:
> Oct 15 14:51:46 <ttarrant> darranl, if I issue a jmx query over jmx-remoting I get many more objects than expected
> Oct 15 14:51:55 <ttarrant> darranl, i.e. ones that do not match the query
> Oct 15 14:52:09 <ttarrant> darranl, this is with 7.1.x
> Oct 15 14:52:57 <ttarrant> darranl, this works if I use the standard JMX over RMI
> Oct 15 14:53:08 --> fnasser (~fnasser(a)CPE602ad07ab726-CM602ad07ab723.cpe.net.cable.rogers.com) has joined #jboss-as7
> Oct 15 14:53:09 <-- fnasser has quit (Changing host)
> Oct 15 14:53:09 --> fnasser (~fnasser@redhat/jboss/fnasser) has joined #jboss-as7
> Oct 15 14:53:09 --- ChanServ gives voice to fnasser
> Oct 15 14:53:16 <ttarrant> darranl, do you just pass the query the the mbeanserver ?
> Oct 15 14:53:39 <darranl> ttarrant: what kind of objects? within AS7 I think there are two things that could affec
> t this 1 - The Remoting JMX protocol, 2 - The domain management representation over JMX
> Oct 15 14:53:54 <darranl> For #1 yes we just pass it to the MBEanServer and return whatever it returns
> Oct 15 14:54:04 <darranl> if it was a Remoting JMX bug maybe we are messing up the query
> Oct 15 14:54:16 <ttarrant> darranl, the query is as follows: *:type=CacheManager,component=Interpreter,name=*
> Oct 15 14:54:16 <darranl> But not sure if #2 could be the reason more is getting added
> Oct 15 14:54:32 <ttarrant> darranl, wait a sec
> Oct 15 14:54:57 <darranl> ttarrant: I would suggest getting a Jira raised and assigned to me, I can verify if it i
> s a remoting jmx issue or pass over if it is a domain management integration issue
> Oct 15 14:55:20 <darranl> regardless of where it is happenign it sounds like you may have discovered a bug
> Oct 15 14:56:23 <ttarrant> darranl, let me get the objects it's returning
> Oct 15 14:56:39 <darranl> ttarrant: when you enable the RMI approach you bypass both Remoting JMX AND the domain m
> anagement integration
> Oct 15 14:56:42 <darranl> ok
> Oct 15 15:26:08 <ttarrant> darranl, ok, my query actually returns the object I queried for and a bunch of org.jboss.as.controller.ModelController (one for each subsystem)
> Oct 15 15:51:24 <darranl> ttarrant: ok that does then sound like it is the domain management integration that is 'poluting' the query results
> Oct 15 15:51:53 <darranl> ttarrant: going RMI was just bypassing that as well
> Oct 15 15:52:05 <ttarrant> darranl, shall I open a Jira ?
> Oct 15 15:52:34 <ttarrant> darranl, I work around the issue by manually filtering the returned objects based on class name
> Oct 15 15:53:23 <darranl> ttarrant: it would probably be one for kkhan to look into, think he is just back today so may be worth the Jira so he can have a look once he has caught back up ;-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years