[JBoss JIRA] (AS7-5926) EJB system exceptions not wrapped as EJBException when tx attribute NEVER
by Cheng Fang (JIRA)
Cheng Fang created AS7-5926:
-------------------------------
Summary: EJB system exceptions not wrapped as EJBException when tx attribute NEVER
Key: AS7-5926
URL: https://issues.jboss.org/browse/AS7-5926
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.2.0.CR1
Reporter: Cheng Fang
Assignee: jaikiran pai
EJB spec has requirements that system exceptions be wrapped as EJBException before throwing it to the client.
The problem I'm seeing is, when the ejb business method has tx attribute NEVER, any runtime exceptions thrown from the method currently are directly propagated to the client.
The exception handling should work with all types of tx attributes.
--
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, 4 months
[JBoss JIRA] (LOGTOOL-62) Log filtering tool
by Jesper Pedersen (JIRA)
Jesper Pedersen created LOGTOOL-62:
--------------------------------------
Summary: Log filtering tool
Key: LOGTOOL-62
URL: https://issues.jboss.org/browse/LOGTOOL-62
Project: Log Tool
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Jesper Pedersen
Assignee: James Perkins
It would be nice to have a log filtering tool, which can help to extract / highlight log statements in huge log files.
An idea could be to have a SQL like language in order to limit the number of lines as much as possible
{noformat}
SELECT * FROM server.log WHERE CATEGORY = 'org.jboss.as' AND SEVERITY IN {FATAL OR ERROR OR WARN} AND TIMESTAMP >= '12:42:00,000' AND CONTENT CONTAINS 'Something went wrong'
{noformat}
Having functions to select all / a defined number of lines after each hit, between timestamps, and so on would be 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
13 years, 4 months
[JBoss JIRA] (AS7-5321) support expressions for remote-destination-outbound-socket-binding host attrib
by John Mazzitelli (JIRA)
John Mazzitelli created AS7-5321:
------------------------------------
Summary: support expressions for remote-destination-outbound-socket-binding host attrib
Key: AS7-5321
URL: https://issues.jboss.org/browse/AS7-5321
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.1.Final
Reporter: John Mazzitelli
I appears that remote-destination-outbound-socket-binding resources cannot have attributes that are expressions - at least the host attrtibute. In JBossAS 4.2.3, we used to have a stock email service.xml that people could customize by simply passing in new system properties (rather than editing .xml or going through a CLI to change the values). However, in AS 7.1.1.Final, we can't do this for the mail service because at least the host attribute does not appear to allow for expressions:
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=mail-smtp
My host attribute was set to the expression ${rhq.server.email.smtp-host:localhost} and when I tried to start the server, I got:
Caused by: java.net.UnknownHostException: ${rhq.server.email.smtp-host:localhost}
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) [rt.jar:1.6.0_29]
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:849) [rt.jar:1.6.0_29]
at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1202) [rt.jar:1.6.0_29]
at java.net.InetAddress.getAllByName0(InetAddress.java:1153) [rt.jar:1.6.0_29]
at java.net.InetAddress.getAllByName(InetAddress.java:1083) [rt.jar:1.6.0_29]
at java.net.InetAddress.getAllByName(InetAddress.java:1019) [rt.jar:1.6.0_29]
at java.net.InetAddress.getByName(InetAddress.java:969) [rt.jar:1.6.0_29]
at org.jboss.as.network.OutboundSocketBinding.getDestinationAddress(OutboundSocketBinding.java:146)
at org.jboss.as.mail.extension.MailSessionService.getServerSocketAddress(MailSessionService.java:106)
The weird thing is, the port attribute appears to allow for expressions. When my port is set to this expression: "${rhq.server.email.smtp-port:25}", the server starts up fine (that is, after I set to the host to a legitimate hostname like "localhost")
This JIRA is to request that expressions be supported for the host attribute as it appears to be supported for the port attribute.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-5342) SAR MBean String attributes cannot be longer than about 3650 characters
by John Mazzitelli (JIRA)
John Mazzitelli created AS7-5342:
------------------------------------
Summary: SAR MBean String attributes cannot be longer than about 3650 characters
Key: AS7-5342
URL: https://issues.jboss.org/browse/AS7-5342
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.1.Final
Reporter: John Mazzitelli
I have a SAR. One of the MBean attributes is a String (actually, for my real use-case the value is a Properties object, but due to JIRA AS7-5336, there are other problems, but let's just go with String attribute type, because the same problem I will describe happens with that type, too)
If the string value is longer than around 3650 characters the beginning of the string is stripped (I can't nail it down to a specific value, but its around that number, give or take 10 characters or so)
For example, if I have this in jboss-service.xml:
<attribute name="MyStrAttrib">
This is a really long string.
...[lots of characters here]...
It has more than 3650
characters in it.
</attribute>
What my MBean setter (setMyStrAttrib(String s)) will be passed is something like "aracters in it." The characters at index 0 through ~3650 are missing, I only have the parts after it.
In my real example, the reason why the string is so long is that its a Properties string with lots of name/value pairs. I ended up working around AS7-5336 but then I hit this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6038) Remove DeploymentScanner's bootTimeScan method
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6038:
-------------------------------------
Summary: Remove DeploymentScanner's bootTimeScan method
Key: AS7-6038
URL: https://issues.jboss.org/browse/AS7-6038
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Priority: Minor
Fix For: 7.3.0.Alpha1
The DeploymentScanner interface's bootTimeScan method isn't implemented and isn't used and should be removed.
--
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, 4 months
[JBoss JIRA] (JBLOGGING-88) Support setting the logging provider via a resource file
by Jérôme Delagnes (JIRA)
Jérôme Delagnes created JBLOGGING-88:
----------------------------------------
Summary: Support setting the logging provider via a resource file
Key: JBLOGGING-88
URL: https://issues.jboss.org/browse/JBLOGGING-88
Project: JBoss Logging
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.1.2.GA
Reporter: Jérôme Delagnes
Assignee: David Lloyd
Logging provider can be set via the system property {{org.jboss.logging.provider}}.
It could be nice if the provider could be also set via the resource {{META-INF/services/org.jboss.logging.provider}} or others.
The algorithm used to locate the provider:
# system property
# resource file
# existing logic
--
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, 4 months
[JBoss JIRA] (AS7-6016) Intermittent failure in OSGi StompletTestCase
by jaikiran pai (JIRA)
jaikiran pai created AS7-6016:
---------------------------------
Summary: Intermittent failure in OSGi StompletTestCase
Key: AS7-6016
URL: https://issues.jboss.org/browse/AS7-6016
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Environment: AS7 upstream - November 22 2012
Reporter: jaikiran pai
Assignee: Thomas Diesler
Just saw this NPE on lightning and the StompletTestCase failed:
{code}
Error Message
java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.deployment.unit.stomplet-server-provider.Activate" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0 Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26 Caused by: java.lang.NullPointerException"}}
Stacktrace
org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.deployment.unit.stomplet-server-provider.Activate" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0
Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26
Caused by: java.lang.NullPointerException"}}
at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:56)
at org.jboss.as.test.integration.osgi.stilts.StompletTestCase$StompletTestCaseServerSetup.setup(StompletTestCase.java:90)
at org.jboss.as.arquillian.container.ServerSetupObserver.handleBeforeDeployment(ServerSetupObserver.java:107)
at sun.reflect.GeneratedMethodAccessor13.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.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.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:155)
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.GeneratedMethodAccessor12.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.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
at sun.reflect.GeneratedMethodAccessor11.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.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
at sun.reflect.GeneratedMethodAccessor6.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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
at sun.reflect.GeneratedMethodAccessor5.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.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79)
at sun.reflect.GeneratedMethodAccessor32.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.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.ContainerEventController.execute(ContainerEventController.java:101)
at sun.reflect.GeneratedMethodAccessor29.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.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.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
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: {"JBAS014671: Failed services" => {"jboss.deployment.unit.stomplet-server-provider.Activate" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0
Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26
Caused by: java.lang.NullPointerException"}}
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:50)
... 96 more
Standard Output
[0m03:09:18,898 INFO [org.jboss.web] (ServerService Thread Pool -- 30) JBAS018224: Unregister web context: /simple-endpoint
[0m[0m03:09:18,903 INFO [org.jboss.as.webservices] (MSC service thread 1-6) JBAS015540: Stopping service jboss.ws.endpoint."simple-endpoint.war"."org.jboss.as.test.integration.osgi.jaxws.bundle.EndpointImpl"
[0m[0m03:09:18,903 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022051: Endpoint unregistered: jboss.ws:context=simple-endpoint,endpoint=org.jboss.as.test.integration.osgi.jaxws.bundle.EndpointImpl
[0m[0m03:09:18,910 INFO [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015540: Stopping service jboss.ws.port-component-link
[0m[0m03:09:18,929 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment simple-endpoint.war in 33ms
[0m[0m03:09:18,935 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m03:09:18,936 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m03:09:18,936 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m03:09:18,936 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m03:09:18,937 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m03:09:18,937 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m03:09:18,944 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/osgi/target/jbossas/standalone/data/content/3e/bce80f886395fad32b517fc67a1bbd498b5751/content
[0m[0m03:09:18,944 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "simple-endpoint.war"
[0m[0m03:09:18,956 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011003: Bundle stopped: simple-client.jar:0.0.0
[0m[0m03:09:18,961 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011005: Bundle uninstalled: simple-client.jar:0.0.0
[0m[0m03:09:18,965 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment simple-client.jar in 12ms
[0m[0m03:09:18,971 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 1) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m03:09:18,971 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 1) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m03:09:18,972 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 1) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m03:09:18,972 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 1) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m03:09:18,973 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 1) JBAS014627: Attribute failover-on-server-shutdown is deprecated, and it might be removed in future version!
[0m[0m03:09:18,973 INFO [org.jboss.as.controller.management-deprecated] (management-handler-thread - 1) JBAS014627: Attribute discovery-initial-wait-timeout is deprecated, and it might be removed in future version!
[0m[0m03:09:19,060 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014901: Content removed from location /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/osgi/target/jbossas/standalone/data/content/40/14f8ce31e3e156d06efe22c44318d763587d8b/content
[0m[0m03:09:19,061 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018558: Undeployed "simple-client.jar"
[0m[0m03:09:19,130 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/jenkins/jenkins-work/workspace/as7-master-testsuite-ip6/testsuite/integration/osgi/target/jbossas/standalone/data/content/6e/3c278ae96ddf3a12da4bff9bb6adea4703b7ea/content
[0m[0m03:09:19,132 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "stomplet-server-provider"
[0m[0m03:09:19,150 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011001: Bundle installed: stomplet-server-provider:0.0.0
[0m[33m03:09:19,215 WARN [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011915: Cannot deploy from management operation, bypassing deployment unit processors: [org.jboss.netty:3.4.5.Final,location=org.jboss.netty:main]
[0m[0m03:09:20,040 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.jboss.netty:3.4.5.Final
[0m[33m03:09:20,047 WARN [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011915: Cannot deploy from management operation, bypassing deployment unit processors: [stilts-stomplet-server-bundle:0.1.26,location=org.projectodd.stilts:main]
[0m[0m03:09:20,100 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: stilts-stomplet-server-bundle:0.1.26
[0m[31m03:09:20,226 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit.stomplet-server-provider.Activate: org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0
at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:130)
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.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26
at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:110)
at org.jboss.as.osgi.service.BundleLifecycleIntegration.start(BundleLifecycleIntegration.java:167)
at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:292)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:228)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:516)
at org.jboss.as.test.integration.osgi.stilts.bundle.StompletServerActivator.start(StompletServerActivator.java:41)
at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:84)
at org.jboss.as.osgi.service.BundleLifecycleIntegration.start(BundleLifecycleIntegration.java:174)
at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:292)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:228)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:522)
at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:127)
... 5 more
Caused by: java.lang.NullPointerException
at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:121)
at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:444)
at org.jboss.osgi.framework.internal.HostBundleState.loadClass(HostBundleState.java:102)
at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:76)
... 16 more
[0m[31m03:09:20,447 ERROR [org.jboss.as.server] (management-handler-thread - 4) JBAS015870: Deploy of deployment "stomplet-server-provider" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.stomplet-server-provider.Activate" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.stomplet-server-provider.Activate: JBAS011968: Cannot start bundle: stomplet-server-provider:0.0.0
Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: stilts-stomplet-server-bundle:0.1.26
Caused by: java.lang.NullPointerException"}}
[0m[0m03:09:20,452 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011005: Bundle uninstalled: stomplet-server-provider:0.0.0
[0m[0m03:09:20,455 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment stomplet-server-provider in 9ms
[0m
{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, 4 months