February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-401) During Trailblazer DEMO, JMS doesn't reconnect after a restart of the App Server [JMS Provider]

by Bruno Georges (JIRA)

During Trailblazer DEMO, JMS doesn't reconnect after a restart of the App Server [JMS Provider] ----------------------------------------------------------------------------------------------- Key: JBESB-401 URL: http://jira.jboss.com/jira/browse/JBESB-401 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.0 Environment: JBoss ESB 4.0 GA + JBoss AS 4.0.5GA - Win 2000 - Fedora Core 6 Reporter: Bruno Georges Assigned To: Mark Little Fix For: 4.0 Maintenance Pack 1 During Trailblazer DEMO, JMS doesn't reconnect when App Server restart: ERROR [JmsCourier] JMS error. Attempting JMS reconnect. ant runJMSBank [java] 10:00:01,759 WARN [Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect [java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.) [java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277) [java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364) [java] at java.lang.Thread.run(Thread.java:595) [java] Caused by: java.io.IOException: ping timeout. [java] ... 3 more ant runESB [java] 09:58:52,056 ERROR [JmsCourier] JMS error. Attempting JMS reconnect. [java] javax.jms.IllegalStateException: The consumer is closed [java] at org.jboss.mq.SpyMessageConsumer.checkClosed(SpyMessageConsumer.java:963) [java] at org.jboss.mq.SpyMessageConsumer.receive(SpyMessageConsumer.java:360) [java] at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:349) [java] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:184) [java] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:166) [java] at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:246) [java] at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:228) [java] at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:114) [java] at java.lang.Thread.run(Thread.java:595) [java] 09:59:51,775 WARN [Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect [java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.) [java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277) [java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364) [java] at java.lang.Thread.run(Thread.java:595) [java] Caused by: java.io.IOException: ping timeout. [java] ... 3 more [java] 09:59:52,056 ERROR [JmsCourier] JMS error. Attempting JMS reconnect. -- 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

18 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-802) FailoverTest.testBrowserFailoverSendMessagesPostFailure() fails

by Ovidiu Feodorov (JIRA)

FailoverTest.testBrowserFailoverSendMessagesPostFailure() fails --------------------------------------------------------------- Key: JBMESSAGING-802 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-802 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta2 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Beta2 -- 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

18 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-803) QueueBrowser doesn't refresh the content of its Enumeration on the second getEnumeration() call

by Ovidiu Feodorov (JIRA)

QueueBrowser doesn't refresh the content of its Enumeration on the second getEnumeration() call ----------------------------------------------------------------------------------------------- Key: JBMESSAGING-803 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-803 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.0.1.SP3, 1.2.0.Beta1 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.Beta2, 1.0.1.SP4 Test org.jboss.test.messaging.jms.BrowserTest.testGetEnumeration() (currently failing) Test org.jboss.test.messaging.jms.BrowserTest.testBrowse() is incorrect and has to be fixed. -- 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

18 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-799) org.jboss.test.messaging.jms.DuplicateClientIDTest testDuplicate() and testPreconfiguredDuplicateClientID() fail

by Ovidiu Feodorov (JIRA)

org.jboss.test.messaging.jms.DuplicateClientIDTest testDuplicate() and testPreconfiguredDuplicateClientID() fail ---------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-799 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-799 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Beta2 -- 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

18 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-791) Duplicates clientIDs are not throwing InvalidClientIDException

by Clebert Suconic (JIRA)

Duplicates clientIDs are not throwing InvalidClientIDException -------------------------------------------------------------- Key: JBMESSAGING-791 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-791 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP2, 1.0.1.SP3, 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1, 1.0.1.SP4 -- 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

18 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3784) derby-jdbc2-service.xml not updated to jboss 4.x

by ppc (JIRA)

derby-jdbc2-service.xml not updated to jboss 4.x ------------------------------------------------ Key: JBAS-3784 URL: http://jira.jboss.com/jira/browse/JBAS-3784 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: ppc the file doc/examples/jms/derby-jdbc2-service.xml containt the follow line <depends optional-attribute-name="ConnectionManager">jboss.jca:service=LocalTxCM,name=....</depends> that is applicable to jboss 3.x instead <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=...</depends> according to http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB this errors comes also when form the webstart installer you choose derby as default datasource instead hipersonic. -- 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

18 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3785) Syntax Error in derby-jdbc2-service.xml

by ppc (JIRA)

Syntax Error in derby-jdbc2-service.xml --------------------------------------- Key: JBAS-3785 URL: http://jira.jboss.com/jira/browse/JBAS-3785 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Reporter: ppc Assigned To: Adrian Brock in the line DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE EXITS (SELECT JMS_TRANSACTIONS.TXID FROM JMS_TRANSACTIONS \ WHERE JMS_TRANSACTIONS.TXID = JMS_MESSAGES.TXID) \ AND JMS_MESSAGES.TXOP = ? there's a syntax error on EXITS istead EXISTS -- 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

18 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-797) Deadlock in aop stack deployment

by Tim Fox (JIRA)

Deadlock in aop stack deployment -------------------------------- Key: JBMESSAGING-797 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-797 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.0.1.GA The following deadlock occures in TRUNK: Java stack information for the threads listed above: SERVER 1 STDOUT: =================================================== SERVER 1 STDOUT: "WorkerThread#0[127.0.0.1:54574]": SERVER 1 STDOUT: at org.jboss.aop.AspectManager.findAdvisor(AspectManager.java:518) SERVER 1 STDOUT: - waiting to lock <0x00002b1b28689000> (a java.util.WeakHashMap) SERVER 1 STDOUT: at org.jboss.aop.AspectManager.getAnyAdvisorIfAdvised(AspectManager.java:537) SERVER 1 STDOUT: at org.jboss.aop.ClassAdvisor.populateMethodTables(ClassAdvisor.java:1432) SERVER 1 STDOUT: at org.jboss.aop.ClassAdvisor.createMethodTables(ClassAdvisor.java:1448) SERVER 1 STDOUT: at org.jboss.aop.ClassAdvisor.access$100(ClassAdvisor.java:82) SERVER 1 STDOUT: at org.jboss.aop.ClassAdvisor$1.run(ClassAdvisor.java:288) SERVER 1 STDOUT: at java.security.AccessController.doPrivileged(Native Method) SERVER 1 STDOUT: at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:271) SERVER 1 STDOUT: - locked <0x00002b1b287e7da0> (a org.jboss.aop.ClassAdvisor) SERVER 1 STDOUT: at org.jboss.aop.AspectManager.initialiseClassAdvisor(AspectManager.java:587) SERVER 1 STDOUT: at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:575) SERVER 1 STDOUT: at org.jboss.jms.client.delegate.ClientConnectionDelegate.<clinit>(ClientConnectionDelegate.java) SERVER 1 STDOUT: at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:219) SERVER 1 STDOUT: at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:132) SERVER 1 STDOUT: at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:107) SERVER 1 STDOUT: at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:126) SERVER 1 STDOUT: at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:715) SERVER 1 STDOUT: at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:552) SERVER 1 STDOUT: at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:378) SERVER 1 STDOUT: at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:158) SERVER 1 STDOUT: "Thread-4": SERVER 1 STDOUT: at org.jboss.aop.Advisor.newBindingAdded(Advisor.java:516) SERVER 1 STDOUT: - waiting to lock <0x00002b1b287e7da0> (a org.jboss.aop.ClassAdvisor) SERVER 1 STDOUT: at org.jboss.aop.AspectManager.updateAdvisorsForAddedBinding(AspectManager.java:1472) SERVER 1 STDOUT: - locked <0x00002b1b28689000> (a java.util.WeakHashMap) SERVER 1 STDOUT: at org.jboss.aop.AspectManager.addBinding(AspectManager.java:1441) SERVER 1 STDOUT: - locked <0x00002b1b28689000> (a java.util.WeakHashMap) SERVER 1 STDOUT: - locked <0x00002b1b2868a3d8> (a org.jboss.aop.AspectManager) SERVER 1 STDOUT: at org.jboss.aop.AspectXmlLoader.deployBinding(AspectXmlLoader.java:286) SERVER 1 STDOUT: at org.jboss.aop.AspectXmlLoader.deployTopElements(AspectXmlLoader.java:1038) SERVER 1 STDOUT: at org.jboss.aop.AspectXmlLoader.deployXML(AspectXmlLoader.java:886) SERVER 1 STDOUT: at org.jboss.jms.client.container.JmsClientAspectXMLLoader.deployXML(JmsClientAspectXMLLoader.java:88) SERVER 1 STDOUT: at org.jboss.jms.client.ClientAOPStackLoader.load(ClientAOPStackLoader.java:69) SERVER 1 STDOUT: - locked <0x00002b1b287c7098> (a org.jboss.jms.client.ClientAOPStackLoader) SERVER 1 STDOUT: at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:199) SERVER 1 STDOUT: at org.jboss.jms.client.JBossConnectionFactory.createXAConnection(JBossConnectionFactory.java:129) SERVER 1 STDOUT: at org.jboss.jms.client.JBossConnectionFactory.createXAConnection(JBossConnectionFactory.java:124) SERVER 1 STDOUT: at org.jboss.jms.recovery.BridgeXAResourceRecovery.hasMoreResources(BridgeXAResourceRecovery.java:229) SERVER 1 STDOUT: at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecovery(XARecoveryModule.java:677) SERVER 1 STDOUT: at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:177) SERVER 1 STDOUT: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWork(PeriodicRecovery.java:237) SERVER 1 STDOUT: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:163) SERVER 1 STDOUT: SERVER 1 STDOUT: Found 1 deadlock. and a related one (see forum reference) in 1.0.1.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

18 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-400) Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws

by Daniel Brum (JIRA)

Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws ----------------------------------------------------------------------------------- Key: JBESB-400 URL: http://jira.jboss.com/jira/browse/JBESB-400 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.0 Reporter: Daniel Brum Assigned To: Daniel Brum Fix For: 4.0 Maintenance Pack 1 Add an ANT task to generate the client side ws classes for the JSR-181 pojo used in the trailblazer. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1222) Incorrect behaviour of InstanceContainer.createDefinition in case a definition already exists

by Adam Warski (JIRA)

Incorrect behaviour of InstanceContainer.createDefinition in case a definition already exists --------------------------------------------------------------------------------------------- Key: JBPORTAL-1222 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1222 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha1 Reporter: Adam Warski Assigned To: Julien Viet If an instance already exists, a DuplicateInstanceException exception should be thrown, instead of setting the transaction to rollback. -- 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

18 years, 11 months

2
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 February 2007