[JBoss JIRA] (WFLY-1172) mechanism to load tag libraries from module
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-1172?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-1172:
-----------------------------------
Assignee: Remy Maucherat (was: Brian Stansberry)
> mechanism to load tag libraries from module
> -------------------------------------------
>
> Key: WFLY-1172
> URL: https://issues.jboss.org/browse/WFLY-1172
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (JBoss Web)
> Reporter: Ivica Loncar
> Assignee: Remy Maucherat
> Priority: Critical
> Labels: modules, tag, taglib, tld
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> tag libraries are scanned only if they appear in jar inside WEB-INF/lib or are defined in tld under WEB-INF.
> The simplest scenario to explain why this is a problem: portlet 2 defines standard portlet taglib, but the classes in this file come from concrete implementations. Currently I see no way to use 2 different portals in a portable way.
> Please provide a way to notify a relevant subsystem for web applications that specific module contains a .tld.
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-405) Patching system
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-405?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated WFLY-405:
----------------------------------
Assignee: Emanuel Muckenhuber (was: Brian Stansberry)
> Patching system
> ---------------
>
> Key: WFLY-405
> URL: https://issues.jboss.org/browse/WFLY-405
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Emanuel Muckenhuber
> Priority: Blocker
> Labels: rhq
> Fix For: 8.0.0.Beta1
>
>
> "Server" side of the patching system. Server not in the sense of the domain model Server, but rather client-server where the client is whatever tool (JON) determines there are patches available and asks the server to apply them.
> This does not need to implemented until M2 but thinking about it during the design of the InstalledImage is good.
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-16) Intermittent failure in RemoteOutboundConnectionReconnectTestCase
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-16?page=com.atlassian.jira.plugin.sy... ]
Brian Stansberry updated WFLY-16:
---------------------------------
Assignee: jaikiran pai (was: Brian Stansberry)
> 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.Alpha1
>
>
> 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
11 years, 8 months
[JBoss JIRA] (WFLY-156) Unable to start jboss AS on windows if installed on path containig non-ascii characters
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-156?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated WFLY-156:
----------------------------------
Assignee: Tomaz Cerar (was: Brian Stansberry)
> Unable to start jboss AS on windows if installed on path containig non-ascii characters
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-156
> URL: https://issues.jboss.org/browse/WFLY-156
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Environment: windows 2008 x64
> Reporter: Ales Kolenc
> Assignee: Tomaz Cerar
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
>
> 1.) Install jboss into a folder containing non-ascii characters. (i.e. "C:\Testチ").
> 2.) run standalone.bat
> C:\Test?\jboss-as-7.1.1.Final\bin>set JAVA_HOME=C:\Program Files\Java\jre7
> C:\Test?\jboss-as-7.1.1.Final\bin>standalone.bat
> Calling "C:\Test?\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: C:\Test?\jboss-as-7.1.1.Final
> JAVA: C:\Program Files\Java\jre7\bin\java
> JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb
> oss.server.default.config=standalone.xml
> ===============================================================================
> Error: Unable to access jarfile C:\Test?\jboss-as-7.1.1.Final\jboss-modules.jar
> Press any key to continue . . .
> C:\Test?\jboss-as-7.1.1.Final\bin>
> 3.) pleas note that: "Testチ" used in path -> 'チ' does not bellong to system locale code page. E.g.: char 'チ' is in CP 932, system locale code page used 437/1252,..
> 4.) i would also like to add that jboss does not start if it installed in "normal" folder, but JBOSS_CONFIG_DIR && JBOSS_LOG_DIR are set to folder with non-ascii characters:
> c:\test\jboss-as-7.1.1.Final\bin>set JBOSS_LOG_DIR=c:\Test?
> c:\test\jboss-as-7.1.1.Final\bin>set JBOSS_CONFIG_DIR=c:\Test?\configuration
> c:\test\jboss-as-7.1.1.Final\bin>dir %JBOSS_CONFIG_DIR%
> Volume in drive C has no label.
> Volume Serial Number is 2C2F-FA6F
> Directory of c:\Test?\configuration
> 01/04/2013 02:34 AM <DIR> .
> 01/04/2013 02:34 AM <DIR> ..
> 01/04/2013 01:42 AM 634 application-roles.properties
> 01/04/2013 01:42 AM 812 application-users.properties
> 01/04/2013 01:42 AM 2,042 logging.properties
> 01/04/2013 01:42 AM 836 mgmt-users.properties
> 01/04/2013 01:42 AM 27,024 standalone-full-ha.xml
> 01/04/2013 01:42 AM 20,794 standalone-full.xml
> 01/04/2013 01:42 AM 20,358 standalone-ha.xml
> 01/04/2013 01:42 AM 15,372 standalone.xml
> 01/04/2013 02:34 AM <DIR> standalone_xml_history
> 8 File(s) 87,872 bytes
> 3 Dir(s) 20,185,866,240 bytes free
> c:\test\jboss-as-7.1.1.Final\bin>standalone.bat -Djboss.server.config.dir=%JBOSS_CONFIG_DIR%
> Calling "c:\test\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: c:\test\jboss-as-7.1.1.Final
> JAVA: C:\Program Files\Java\jre7\bin\java
> JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb
> oss.server.default.config=standalone.xml
> ===============================================================================
> Unable to read the logging configuration from 'file:c:\Test?\configuration/logging.properties' (java.io.FileNotFoundException: c:\Test?\configuration\logging.properties (The filename, directory name, or volume label syntax is incorrect))
> java.lang.IllegalStateException: JBAS018701: Configuration directory does not exist: c:\Test?\configuration
> at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:371)
> at org.jboss.as.server.Main.determineEnvironment(Main.java:242)
> at org.jboss.as.server.Main.main(Main.java:83)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:260)
> at org.jboss.modules.Main.main(Main.java:291)
> Press any key to continue . . .
> c:\test\jboss-as-7.1.1.Final\bin>
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-1189) java:properties element in SAR deployments are no longer supported
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-1189?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-1189:
--------------------------------
Assignee: (was: James Perkins)
> java:properties element in SAR deployments are no longer supported
> ------------------------------------------------------------------
>
> Key: WFLY-1189
> URL: https://issues.jboss.org/browse/WFLY-1189
> Project: WildFly
> Issue Type: Feature Request
> Components: JMX
> Reporter: John Mazzitelli
> Labels: rhq
>
> I have a SAR deployment that works in AS 4.2.3. It no longer deploys in AS 7.1.1.Final. The problem is due to the fact that the java:properties element is no longer supported in AS 7 whereas it was supported in AS 4.2.3.
> Here's what my jboss-service.xml looks like that FAILS to parse in AS 7 (this works in AS 4.2.3):
> <?xml version="1.0" encoding="UTF-8"?>
> <server xmlns="urn:jboss:service:7.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="urn:jboss:service:7.0 jboss-service_7_0.xsd">
> <mbean code="org.rhq.enterprise.server.core.comm.ServerCommunicationsService"
> name="rhq:service=ServerCommunications">
> <attribute name="ConfigurationOverrides" serialDataType="jbxb">
> <java:properties xmlns:java="urn:jboss:java-properties"
> xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
> xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
> <java:property>
> <java:key>foo</java:key>
> <java:value>bar</java:value>
> </java:property>
> </java:properties>
> </attribute>
> </mbean>
> </server>
> Notice the <attribute> has a child "java:properties" because the MBean uses Properties as the attribute type.
> Here's the AS7 error I see in the log when that SAR attempts to be deployed:
> 22:30:31,921 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."rhq-enterprise-server-services.sar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."rhq-enterprise-server-services.sar".PARSE: Failed to process phase PARSE of deployment "rhq-enterprise-server-services.sar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> 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]
> 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: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017224: Failed to parse service xml ["/home/mazz/source/rhq/dev-container/jbossas/standalone/deployments/rhq-enterprise-server-services.sar/META-INF/jboss-service.xml"]
> at org.jboss.as.service.ServiceDeploymentParsingProcessor.deploy(ServiceDeploymentParsingProcessor.java:95)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> ... 5 more
> Caused by: java.lang.IllegalStateException: Not a textual event (START_ELEMENT)
> at com.ctc.wstx.sr.BasicStreamReader.throwNotTextual(BasicStreamReader.java:5444)
> at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:833)
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.getText(XMLExtendedStreamReaderImpl.java:275) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.unexpectedContent(JBossServiceXmlDescriptorParser.java:622)
> at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.parseAttribute(JBossServiceXmlDescriptorParser.java:346)
> at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.parseMBean(JBossServiceXmlDescriptorParser.java:257)
> at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.readElement(JBossServiceXmlDescriptorParser.java:183)
> at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.readElement(JBossServiceXmlDescriptorParser.java:46)
> 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.service.ServiceDeploymentParsingProcessor.deploy(ServiceDeploymentParsingProcessor.java:88)
> ... 6 more
> If I were to completely remove the <attribute> XML and the child elements, this SAR deploys in AS7 without that error. I can only assume the source of the problem is because <java:properties> type is no longer supported.
> I don't know if this means anything but I looked in <as7-install-dir>/docs/schema and I do not see any java-properties_1_0.xsd (this file that is hosted on jboss.org: http://www.jboss.org/j2ee/schema/java-properties_1_0.xsd )
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-1198) Arq: @CleanContainerDataDirsAfterTest - Delete data/ and /tmp after test is run.
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-1198?page=com.atlassian.jira.plugin.... ]
Kabir Khan reassigned WFLY-1198:
--------------------------------
Assignee: Aslak Knutsen (was: Kabir Khan)
> Arq: @CleanContainerDataDirsAfterTest - Delete data/ and /tmp after test is run.
> --------------------------------------------------------------------------------
>
> Key: WFLY-1198
> URL: https://issues.jboss.org/browse/WFLY-1198
> Project: WildFly
> Issue Type: Feature Request
> Components: Test Suite
> Reporter: Ondrej Zizka
> Assignee: Aslak Knutsen
>
> Some tests leave files in AS /data dir.
> And the tested modules bypass their configuration from standalone.xml and rather rely on these data.
> This prevents running multiple tests within a single AS instance run; therefore, multiple AS instances, Surefire executions or Maven modules are needed.
> Having something like {{@CleanContainerDataDirsAfterTest}} per method would make writing these tests much easier and faster to run.
> Further, sometimes these tests run with multiple instances (clustering, messaging, ...).
> Not all of them may loose data in some scenarios - some of them must keep the data (e.g. for failover testing).
> Therefore, the annotation should have parameters - a list of container config names (matching arquillian.xml). Only those instances would be cleaned.
> {code:java}
> @CleanContainerDataDirsAfterTest({"InstanceFoo", "InstanceBar"})
> {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
11 years, 8 months
[JBoss JIRA] (WFLY-157) Stale session data received when using DIST SYNC on node shutdown
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-157?page=com.atlassian.jira.plugin.s... ]
Jason Greene reassigned WFLY-157:
---------------------------------
Assignee: Paul Ferraro (was: Jason Greene)
fix invalid assign
> Stale session data received when using DIST SYNC on node shutdown
> -----------------------------------------------------------------
>
> Key: WFLY-157
> URL: https://issues.jboss.org/browse/WFLY-157
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Critical
> Labels: as713tracking
> Fix For: 8.0.0.Alpha1
>
>
> There are few occurrences when client received older data even when using DIST SYNC.
> http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x...
> {noformat}
> ./perf17.log:2012/05/13 17:11:47:416 EDT [DEBUG][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned: hAzyrOe0KxA51coCNbSMUsrZ
> ./perf17.log:2012/05/13 17:11:47:416 EDT [DEBUG][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JvmRoute assigned: perf18
> ./perf17.log:2012/05/13 17:14:11:542 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf18 -> perf21
> ./perf17.log:2012/05/13 17:14:15:546 EDT [WARN ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 37, received 36, Runner: 968>
> ./perf17.log:2012/05/13 17:14:15:546 EDT [WARN ][Runner - 968] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 37, received 36, Runner: 968>
> ./perf17.log:2012/05/13 17:21:20:224 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf21 -> perf19
> ./perf17.log:2012/05/13 17:23:01:507 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf19 -> perf21
> {noformat}
> No logging about the session (hAzyrOe0KxA51coCNbSMUsrZ) in the logs.
--
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
11 years, 8 months