November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3894) shutdown.sh script throws java.lang.NoClassDefFoundError

by Michal Mocnak (JIRA)

shutdown.sh script throws java.lang.NoClassDefFoundError -------------------------------------------------------- Key: JBAS-3894 URL: http://jira.jboss.com/jira/browse/JBAS-3894 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-5.0.0.Beta1 Environment: Debian Linux 4.0 (sid) Reporter: Michal Mocnak Assigned To: Dimitris Andreadis Priority: Critical Fix For: JBossAS-5.0.0.Beta2 1. start jboss as 5.0 2. try to shutdown server by command -> shutdown.sh -S -> it is not possible due to java.lang.NoClassDefFoundError exception which is thrown. Only way how to shutdown the server is to kill the server process Error log: Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/system/server/ServerImplMBean at org.jboss.Shutdown.main(Shutdown.java:116) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3481) Error accessing EJB from Servlet: "Unable to activate POA"

by Peter Rasbora (JIRA)

Error accessing EJB from Servlet: "Unable to activate POA" ---------------------------------------------------------- Key: JBAS-3481 URL: http://jira.jboss.com/jira/browse/JBAS-3481 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: IIOP service, Naming, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1, JBossAS-4.0.1 SP1 Environment: JBoss: 4.0.0, 4.0.1SP1, 4.0.3SP1, 4.0.4GA ( each "out of the box") Java: 1.5.0_06 (build 1.5.0_06-b05) OS: Windows XP SP2 Reporter: Peter Rasbora Assigned To: Francisco Reverbel Priority: Minor When trying to access Stateless SessionBean (JNDI: "vfmcontroller/VFMController") from within a Servlet, it's service() throws a "java.lang.Error: POA: not configured!" JBoss Log warns: "(IIOPListener) Address already in use: JVM_Bind", "org.jboss.corba.ORBFactory:87) Unable to activate POA" and "org.omg.CORBA.INITIALIZE: Could not create server socket" Following to netstat no other processes are bound to specific ports (8080, 1098, 1099, 3528). For further Details (Source, DD, Log-Output) please refer to the following ressources: Stateless SessionBean: http://pastebin.ca/118516 Servlet "Test.java": http://pastebin.ca/118535 jboss.xml: http://pastebin.ca/118520 JBoss Log (Console): http://pastebin.ca/118529 (Hint: Log-Level is DEBUG) Caught Exception in Servlet "Test": http://pastebin.ca/118532 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-250) Listeners fail after a lengthy period of being active.

by Mark Little (JIRA)

Listeners fail after a lengthy period of being active. ------------------------------------------------------ Key: JBESB-250 URL: http://jira.jboss.com/jira/browse/JBESB-250 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Reporter: Mark Little Assigned To: Kevin Conner Fix For: 4.0 >From Burr: "It is really simple, when a service is auto-reloaded via its parameterReloadSecs="10" attribute in the esb-config.xml it sometimes fails to properly go through the self-registration process with the registry. Unfortunately it is not consistent. We'll just need to leave a few listeners running some place to see how they behave over time." >From Kurt: "I see this in the logs when it reloads the config (sometimes): [JmsQueueListener] Unregistering this EPR done: creditagency [java] 14:36:10,880 DEBUG [SocketManager] End ReadTask.run [java] 14:36:10,880 DEBUG [UILClientILService] Stopping [java] 14:36:10,880 DEBUG [SocketManager] End WriteTask.run [java] 14:36:10,927 INFO [JmsQueueListener] Unregistering this EPR done: creditagency [java] 14:36:10,942 DEBUG [SocketManager] End ReadTask.run [java] 14:36:10,942 DEBUG [UILClientILService] Stopping [java] 14:36:10,942 DEBUG [SocketManager] End WriteTask.run [java] 14:36:19,348 INFO [JmsQueueListener] Unregistering this EPR, we're going to reload: creditagency so it goes to unregister twice.. the second time we get a stacktrace, since it's already gone. Do we have more then 1 JmsQueueListener thread??" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-861) JDBC tests failing on the packaged distribution

by Rajesh Rajasekaran (JIRA)

JDBC tests failing on the packaged distribution ----------------------------------------------- Key: JBCACHE-861 URL: http://jira.jboss.com/jira/browse/JBCACHE-861 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1 Reporter: Rajesh Rajasekaran Assigned To: Manik Surtani Fix For: 2.0.0.ALPHA1 The following tests which involve Derby database are failing on the packaged distribution. Build JBossCache-all-2.0.0.ALPHA1.zip Unzip and run the following tests. 1.) org.jboss.cache.loader.JDBCCacheLoaderDerbyDSTest java:/DerbyDS not bound junit.framework.AssertionFailedError: java:/DerbyDS not bound at org.jboss.cache.loader.JDBCCacheLoaderDerbyDSTest.configureCache(JDBCCacheLoaderDerbyDSTest.java:49) at org.jboss.cache.loader.CacheLoaderTestsBase.setUp(CacheLoaderTestsBase.java:72) 2.) org.jboss.cache.loader.JDBCCacheLoaderTest org.jboss.cache.passivation.PassivationToJDBCCacheLoaderTest org.jboss.cache.statetransfer.StateTransfer200Test Failed to load driver null: null java.lang.IllegalStateException: Failed to load driver null: null at org.jboss.cache.loader.JDBCCacheLoader.loadDriver(JDBCCacheLoader.java:945) at org.jboss.cache.loader.JDBCCacheLoader.start(JDBCCacheLoader.java:479) at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:328) at org.jboss.cache.TreeCache.start(TreeCache.java:750) at org.jboss.cache.loader.CacheLoaderTestsBase.setUp(CacheLoaderTestsBase.java:73) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-234) Remove dead code

by Mark Little (JIRA)

Remove dead code ---------------- Key: JBESB-234 URL: http://jira.jboss.com/jira/browse/JBESB-234 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Reporter: Mark Little Assigned To: Tom Fennelly Fix For: 4.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-875) Pessimistic lock interceptor does not write-lock parent nodes when creating or deleting children

by Manik Surtani (JIRA)

Pessimistic lock interceptor does not write-lock parent nodes when creating or deleting children ------------------------------------------------------------------------------------------------ Key: JBCACHE-875 URL: http://jira.jboss.com/jira/browse/JBCACHE-875 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP3 Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Critical Fix For: 1.4.1.GA, 2.0.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-871) Calling remove(FQN) inside a transaction destroys the node before the commit phase

by Galder Zamarreno (JIRA)

Calling remove(FQN) inside a transaction destroys the node before the commit phase ---------------------------------------------------------------------------------- Key: JBCACHE-871 URL: http://jira.jboss.com/jira/browse/JBCACHE-871 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1, 1.3.0.SP3 Reporter: Galder Zamarreno Assigned To: Manik Surtani Attachments: Siemens00012761Test.java Removing a node that has been just been put inside a transaction (Pessimistic Locking, READ_COMMITTED) destroys the node without leaving any trace. Remove should not actually destroy until the commit has been executed. This allows for any paralell transactions to get a WL on this node as there's no any locks any more in this node (it was destroyed) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-256) An explicit Thread.sleep should not be required between starting the message aware listeners, and starting the gateway listeners

by Tom Fennelly (JIRA)

An explicit Thread.sleep should not be required between starting the message aware listeners, and starting the gateway listeners -------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-256 URL: http://jira.jboss.com/jira/browse/JBESB-256 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 RC1 Reporter: Tom Fennelly Assigned To: Mark Little Priority: Critical Fix For: 4.0 You have to manually enter a Thread.sleep between launching EsbListenerController in a thread and launching GatewayListenerController. I spent ages trying to work out an error until I was let in on the little secret. If EsbListenerController is this scencitive, it should manage it's startup such that the caller blocks until EsbListenerController is fully up and ready. This would be a piece of * to do. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-177) Add SQLListener to the Trailblazer demo

by Daniel Brum (JIRA)

Add SQLListener to the Trailblazer demo --------------------------------------- Key: JBESB-177 URL: http://jira.jboss.com/jira/browse/JBESB-177 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Daniel Brum Assigned To: Daniel Brum Fix For: 4.0 Add a Bank interaction that uses the SQLTablePoller listener for it's input and output as part of the TB scenario. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-239) tools module

by Mark Little (JIRA)

tools module ------------ Key: JBESB-239 URL: http://jira.jboss.com/jira/browse/JBESB-239 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.1 Add a tools module and move console in to it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 7 months

1
1
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 2006