October 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1366) Some failures in DistributedTopicTest on Solaris 9 sparc

by Phillip Thurmond (JIRA)

Some failures in DistributedTopicTest on Solaris 9 sparc -------------------------------------------------------- Key: JBMESSAGING-1366 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1366 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP02 Reporter: Phillip Thurmond Assigned To: Phillip Thurmond Some failures in DistributedTopicTest on Solaris 9 sparc. Postgres DB, reproduceable in lab. Details to follow. -- 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

16 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1365) ReconnectWithRecoveryTest fails on Solaris 9 sparc

by Phillip Thurmond (JIRA)

ReconnectWithRecoveryTest fails on Solaris 9 sparc -------------------------------------------------- Key: JBMESSAGING-1365 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1365 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP02 Reporter: Phillip Thurmond Assigned To: Phillip Thurmond ReconnectWithRecoveryTest fails on Solaris 9 sparc. Reproduceable in the lab, details to follow. -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1363) Several failures in ScheduledDeliveryTest under Solaris 9 and 10

by Phillip Thurmond (JIRA)

Several failures in ScheduledDeliveryTest under Solaris 9 and 10 ---------------------------------------------------------------- Key: JBMESSAGING-1363 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1363 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP02 Reporter: Phillip Thurmond Assigned To: Phillip Thurmond Reproduceable in the lab. DB is postgres. details to follow. -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1364) ReconnectTest is failing on Solaris 10 sparc

by Phillip Thurmond (JIRA)

ReconnectTest is failing on Solaris 10 sparc -------------------------------------------- Key: JBMESSAGING-1364 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1364 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP02 Reporter: Phillip Thurmond Assigned To: Phillip Thurmond ReconnectTest is failing on Solaris 10 sparc. DB is postgres. Can be reproduced in the lab. details to follow... -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1361) ClusterConnectionManagerTest fails under IBM 1.5 JDK on RHEL

by Phillip Thurmond (JIRA)

ClusterConnectionManagerTest fails under IBM 1.5 JDK on RHEL ------------------------------------------------------------ Key: JBMESSAGING-1361 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1361 Project: JBoss Messaging Issue Type: Bug Reporter: Phillip Thurmond Assigned To: Phillip Thurmond Can be reproduced in the QA lab. Details will follow. -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1360) MultipleFailoverTest clustering test fails under IBM 1.5 JDK on RHEL

by Phillip Thurmond (JIRA)

MultipleFailoverTest clustering test fails under IBM 1.5 JDK on RHEL -------------------------------------------------------------------- Key: JBMESSAGING-1360 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1360 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP02 Environment: QA lab. Reporter: Phillip Thurmond Assigned To: Tim Fox MultipleFailoverTest clustering test fails under IBM 1.5 JDK on RHEL. Can be reproduced in the QA lab. Details to follow. -- 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

16 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1355) org.jboss.test.messaging.jms.clustering.ClusterViewUpdateTest hangs on HP-UX

by Phillip Thurmond (JIRA)

org.jboss.test.messaging.jms.clustering.ClusterViewUpdateTest hangs on HP-UX ---------------------------------------------------------------------------- Key: JBMESSAGING-1355 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1355 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP02 Reporter: Phillip Thurmond Assigned To: Phillip Thurmond org.jboss.test.messaging.jms.selector.SelectorTest hangs. [junit] @main 11:28:52,177 INFO [ServerManagement] Attempting to kill server 2 [junit] @main 11:28:52,177 INFO [ServerManagement] server 2 has not been created or has already been killed, so it cannot be killed [junit] @main 11:28:52,178 INFO [ClusterViewUpdateTest] ********** TRYING TO KILL SERVER 1 [junit] @main 11:28:52,178 INFO [ServerManagement] Attempting to kill server 1 [junit] @main 11:28:52,178 INFO [ServerManagement] invoking kill() on server 1 [junit] @main 11:28:52,178 INFO [ServerManagement] Waiting for server to die -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1362) Several failures in XARecoveryTest(Remote-bisocket) under Solaris 9 and 10.

by Phillip Thurmond (JIRA)

Several failures in XARecoveryTest(Remote-bisocket) under Solaris 9 and 10. --------------------------------------------------------------------------- Key: JBMESSAGING-1362 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1362 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP02 Reporter: Phillip Thurmond Assigned To: Phillip Thurmond Several failures in XARecoveryTest(Remote-bisocket) under Solaris 9 and 10. Using postgres as a DB. I can reproduce this in the lab. Details to follow. -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1256) distributed-topic example fails under eap 4.3

by Phillip Thurmond (JIRA)

distributed-topic example fails under eap 4.3 --------------------------------------------- Key: JBMESSAGING-1256 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1256 Project: JBoss Messaging Issue Type: Bug Reporter: Phillip Thurmond Assigned To: Tim Fox Running the distributed-topic example included with eap 4.3 fails. Here is the stack trace from the server logs. java.lang.IllegalStateException: Channel id map for node 1 already contains binding for queue 70 at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBindingInMemory(MessagingPostOffice.java:2375) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalAddBinding(MessagingPostOffice.java:1863) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBinding(MessagingPostOffice.java:444) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegateInternal(ServerSessionEndpoint.java:1885) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionEndpoint.java:252) at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createConsumerDelegate$aop(SessionAdvised.java:94) at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java) at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:123) 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:585) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java) at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java) at org.jboss.jms.server.endpoint.advised.SessionAdvised.createConsumerDelegate(SessionAdvised.java) at org.jboss.jms.wireformat.SessionCreateConsumerDelegateRequest.serverInvoke(SessionCreateConsumerDelegateRequest.java:100) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:795) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Moved: (GPD-241) jBPM plugin doesn't support default replyTo in ESB Node configuration

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-241?page=com.atlassian.jira.plugin... ] Koen Aers moved JBIDE-2830 to GPD-241: -------------------------------------- Project: JBoss jBPM GPD (was: Tools (JBoss Tools)) Key: GPD-241 (was: JBIDE-2830) Component/s: (was: jbpm) Affects Version/s: jBPM jPDL Designer 3.1.5 (was: 2.1.0.GA) > jBPM plugin doesn't support default replyTo in ESB Node configuration > --------------------------------------------------------------------- > > Key: GPD-241 > URL: https://jira.jboss.org/jira/browse/GPD-241 > Project: JBoss jBPM GPD > Issue Type: Feature Request > Affects Versions: jBPM jPDL Designer 3.1.5 > Reporter: Koen Aers > Assignee: Koen Aers > > The jBPM editor in JBoss IDE doesn't support configuration of storing original replyTo message, described here : https://jira.jboss.org/jira/browse/SOA-295 (SOA-295). It's very usefull feature, i'd be glad to have this done without editing xml by hand. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2008