November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5998) Failure in org.jboss.as.test.integration.osgi.stilts.StompletTestCase

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5998: ------------------------------------- Summary: Failure in org.jboss.as.test.integration.osgi.stilts.StompletTestCase Key: AS7-5998 URL: https://issues.jboss.org/browse/AS7-5998 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Brian Stansberry Assignee: Thomas Diesler StompletTestCase failed on http://teamcity.cafe-babe.org/viewLog.html?buildId=1589&tab=buildResultsD... Relevant details from the server log are below. It looks like BundleStateRevision.getModuleClassLoader() can return null if a ModuleLoadException is thrown, resulting in the NPE in the log. 16:45:42,074 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "stomplet-server-provider" 16:45:42,078 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011001: Bundle installed: stomplet-server-provider:0.0.0 16:45:42,090 WARN [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011915: Cannot deploy from management operation, bypassing deployment unit processors: [org.jboss.netty:3.4.5.Final,location=org.jboss.netty:main] 16:45:42,353 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011001: Bundle installed: org.jboss.netty:3.4.5.Final 16:45:42,356 WARN [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011915: Cannot deploy from management operation, bypassing deployment unit processors: [stilts-stomplet-server-bundle:0.1.26,location=org.projectodd.stilts:main] 16:45:42,394 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: stilts-stomplet-server-bundle:0.1.26 16:45:42,424 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) 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_32] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_32] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32] 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 16:45:42,631 INFO [org.jboss.osgi.framework] (MSC service thread 1-7) JBOSGI011005: Bundle uninstalled: stomplet-server-provider:0.0.0 16:45:42,633 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment stomplet-server-provider in 4ms 16:45:42,634 ERROR [org.jboss.as.server] (management-handler-thread - 2) 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"}} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-5993) Drop BARRIER from default JGroups protocol stacks

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-5993: --------------------------------- Summary: Drop BARRIER from default JGroups protocol stacks Key: AS7-5993 URL: https://issues.jboss.org/browse/AS7-5993 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.3.Final (EAP) Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) BARRIER is only useful when a state transfer protocol is used. We dropped this a while ago, and should have dropped BARRIER too. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] (AS7-2177) TS: Check logging

by Ondrej Zizka (Created) (JIRA)

TS: Check logging ----------------- Key: AS7-2177 URL: https://issues.jboss.org/browse/AS7-2177 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Some tests print to System.out, and also ex.printStackTrace(). Turn it to proper logging. Also check logging config. -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] (AS7-5815) Upgrading JBossTS to 4.17.2.Final

by Paul Robinson (JIRA)

Paul Robinson created AS7-5815: ---------------------------------- Summary: Upgrading JBossTS to 4.17.2.Final Key: AS7-5815 URL: https://issues.jboss.org/browse/AS7-5815 Project: Application Server 7 Issue Type: Component Upgrade Components: Transactions Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 7.2.0.Alpha1 Note: this upgrade is for 7.2 branch, not the 7.1 branch. 7.1 branch must stay on JBossTS 4.16.x. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] (AS7-5890) JdrService assumes auth is required if http code !=200

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created AS7-5890: --------------------------------------- Summary: JdrService assumes auth is required if http code !=200 Key: AS7-5890 URL: https://issues.jboss.org/browse/AS7-5890 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.2.0.Alpha1 Reporter: Bartosz Baranowski Assignee: Bartosz Baranowski Priority: Minor https://github.com/jbossas/jboss-as/commit/44ada8238bbe962ffd35cf4bd8216a... JDR service asssumes that if return code is different than 200, it needs to ask user for auth. What if code is 500 ? -- 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, 5 months

4
6
0 / 0

[JBoss JIRA] (AS7-5871) The default redirect port for the 8080 connector is current 8433. Should be 8443 instead.

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-5871: ------------------------------------- Summary: The default redirect port for the 8080 connector is current 8433. Should be 8443 instead. Key: AS7-5871 URL: https://issues.jboss.org/browse/AS7-5871 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.3.Final (EAP) Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink The default redirect port for the 8080 connector is 8433. Seems that this is wrong as socket-bindings use 8443 (and former releases also) [standalone@localhost:9999 /] /subsystem=web/connector=http:read-resource { "outcome" => "success", "result" => { ..., "name" => "http", "protocol" => "HTTP/1.1", "redirect-port" => 8433, "scheme" => "http", "secure" => false, "socket-binding" => "http", "ssl" => undefined, "virtual-server" => undefined } } The pre-configured "https" socket binding conversely is 8443: [standalone@localhost:9999 socket-binding=https] /socket-binding-group=standard-sockets/socket-binding=https:read-resource { "outcome" => "success", "result" => { "client-mappings" => undefined, "fixed-port" => false, "interface" => undefined, "multicast-address" => undefined, "multicast-port" => undefined, "name" => "https", "port" => 8443 } } -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] (AS7-3830) Remote JNDI call does not bind stateful beans

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3830: ------------------------------------- Summary: Remote JNDI call does not bind stateful beans Key: AS7-3830 URL: https://issues.jboss.org/browse/AS7-3830 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Final Reporter: Ondřej Chaloupka Assignee: jaikiran pai It seems that current ejb remote client is not able to find stateful bean. Exception is thrown instead: {code} javax.naming.NamingException: java.lang.IllegalStateException: No EJB client context is available [Root exception is java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:124) at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:70) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:91) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:133) ... 7 more Caused by: java.lang.IllegalStateException: No EJB client context is available at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:233) at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:160) at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:89) ... 8 more {code} Please, check my test whether definition of remote context does not contain a mistake. But finding singleton and stateless beans works fine. https://github.com/ochaloup/jboss-as/blob/ejb-remote-call/testsuite/integ... -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] (AS7-3907) Upgrade Infinispan to 5.1.2.FINAL

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3907: --------------------------------- Summary: Upgrade Infinispan to 5.1.2.FINAL Key: AS7-3907 URL: https://issues.jboss.org/browse/AS7-3907 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.1.Final -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] (AS7-3943) Upgrade JGroups to 3.0.6.Final

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3943: --------------------------------- Summary: Upgrade JGroups to 3.0.6.Final Key: AS7-3943 URL: https://issues.jboss.org/browse/AS7-3943 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.1.Final -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] (AS7-3916) Concurrent access leads to empty domain.xml

by Heiko Braun (JIRA)

Heiko Braun created AS7-3916: -------------------------------- Summary: Concurrent access leads to empty domain.xml Key: AS7-3916 URL: https://issues.jboss.org/browse/AS7-3916 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Priority: Critical Fix For: 7.1.1.Final Hi Red Hat team. We're still trying to narrow down the trigger but there is a very serious bug when using the admin console in AS 7.1 Final that causes the domain.xml file to be wiped of everything other than the extensions section that is at the top. Have not checked yet if this is a known bug or not but wanted to alert you immediately. The potential trigger for this is more than one person using the admin console at the same time. Even if just for monitoring while the other person is making configuration changes. (Fortunately we had backed up the config using the CLI.) We are trying right now to get our QA1 drop out the door but we'll be giving this a closer look tomorrow. Has anyone else reported this though? Thanks, Bill -- 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, 5 months

4
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012