Re: [JBoss-dev] problems with JBossMQ
Uh... Today even worse. Just have checked out cvs and couldn't even start JBoss w/o that exception. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] problems with JBossMQ
BTW, on this topic I have found that MDB's attached to queues will lockup and/or contain messages in limbo after high load over time. I have no idea why this happens. I have only tried to rolling file pm too. Could simply be a pm issue. Anyways, FYI. --jason -Original Message- From: [EMAIL PROTECTED] [mailto:jboss- [EMAIL PROTECTED]] On Behalf Of Alex Loubyansky Sent: Tuesday, July 23, 2002 11:58 PM To: Alex Loubyansky Subject: Re: [JBoss-dev] problems with JBossMQ Uh... Today even worse. Just have checked out cvs and couldn't even start JBoss w/o that exception. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] problems with JBossMQ
Hi, something wrong with jboss.mq in the current cvs version. After building jboss starts and runs fine. But if some message is sent to the topic/testTopic next time jboss starts with the following trace: 2002-07-23 18:46:12,409 WARN [org.jboss.system.ServiceController] Problem starting service jboss.mq:service=PersistenceManager java.lang.IllegalAccessError: try to access class org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener from class org.jboss.resource.connectionmanager.LocalTxConnectionManager at org.jboss.resource.connectionmanager.LocalTxConnectionManager.registerConnectionEventListener(LocalTxConnectionManager.java:229) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:534) at org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManagedConnection(LocalTxConnectionManager.java:224) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:595) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:874) at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalDataSource.java:102) at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:212) at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1088) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:937) at $Proxy10.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:378) at org.jboss.system.ServiceController.start(ServiceController.java:392) at org.jboss.system.ServiceController.start(ServiceController.java:392) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:177) at $Proxy13.start(Unknown Source) at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:220) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:804) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:634) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:599) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy7.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:381) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:576) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:449) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:187) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:254) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:937) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:378) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at
Re: [JBoss-dev] problems with JBossMQ
Hmmm, I was getting similar errors yesterday when JBossManagedConnectionPool tried to access its inner classes. All I could find to to was make the inner classes public. Anyone have any ideas what's going on? Are there 2 copies of these classes loaded which is interfering with package visibility??? david jencks On 2002.07.23 12:04:33 -0400 Alex Loubyansky wrote: Hi, something wrong with jboss.mq in the current cvs version. After building jboss starts and runs fine. But if some message is sent to the topic/testTopic next time jboss starts with the following trace: 2002-07-23 18:46:12,409 WARN [org.jboss.system.ServiceController] Problem starting service jboss.mq:service=PersistenceManager java.lang.IllegalAccessError: try to access class org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener from class org.jboss.resource.connectionmanager.LocalTxConnectionManager at org.jboss.resource.connectionmanager.LocalTxConnectionManager.registerConnectionEventListener(LocalTxConnectionManager.java:229) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:534) at org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManagedConnection(LocalTxConnectionManager.java:224) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:595) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:874) at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalDataSource.java:102) at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:212) at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1088) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:937) at $Proxy10.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:378) at org.jboss.system.ServiceController.start(ServiceController.java:392) at org.jboss.system.ServiceController.start(ServiceController.java:392) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:177) at $Proxy13.start(Unknown Source) at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:220) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:804) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:634) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:599) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy7.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:381) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:576) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:449) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:187) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:254) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at
Re: [JBoss-dev] problems with JBossMQ
It could be a problem with the newer package based class loading index if somehown the inner class is not resolving to the same class loader as the outer class. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: David Jencks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 23, 2002 11:23 AM Subject: Re: [JBoss-dev] problems with JBossMQ Hmmm, I was getting similar errors yesterday when JBossManagedConnectionPool tried to access its inner classes. All I could find to to was make the inner classes public. Anyone have any ideas what's going on? Are there 2 copies of these classes loaded which is interfering with package visibility??? david jencks --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] problems with JBossMQ
Alex Loubyansky wrote: something wrong with jboss.mq in the current cvs version. After building jboss starts and runs fine. But if some message is sent to the topic/testTopic next time jboss starts with the following trace: 2002-07-23 18:46:12,409 WARN [org.jboss.system.ServiceController] Problem starting service jboss.mq:service=PersistenceManager java.lang.IllegalAccessError: try to access class org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener from class org.jboss.resource.connectionmanager.LocalTxConnectionManager Really annoying. It has been bugging me all day, and I still haven't a clue about where the problem is. Also, this makes over half of the HEAD testsuite fail with errors. Best Regards, Ole Husgaard. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] problems with JBossMQ
Scott suggested it might be a problem with one of the recent classloader changes, that sorts classes by package, getting confused by inner class names. I haven't had time to take a look, probably won't till the weekend. david jencks On 2002.07.23 21:09:51 -0400 Ole Husgaard wrote: Alex Loubyansky wrote: something wrong with jboss.mq in the current cvs version. After building jboss starts and runs fine. But if some message is sent to the topic/testTopic next time jboss starts with the following trace: 2002-07-23 18:46:12,409 WARN [org.jboss.system.ServiceController] Problem starting service jboss.mq:service=PersistenceManager java.lang.IllegalAccessError: try to access class org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener from class org.jboss.resource.connectionmanager.LocalTxConnectionManager Really annoying. It has been bugging me all day, and I still haven't a clue about where the problem is. Also, this makes over half of the HEAD testsuite fail with errors. Best Regards, Ole Husgaard. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development