October 2008 - jboss-jira - Jboss List Archives

[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

17 years, 9 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

17 years, 9 months

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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5963) ClientUserTransaction should log cause exceptions

by Galder Zamarreno (JIRA)

ClientUserTransaction should log cause exceptions ------------------------------------------------- Key: JBAS-5963 URL: https://jira.jboss.org/jira/browse/JBAS-5963 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Manager (JBossTM) Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno When org.jboss.tm.usertx.client.ClientUserTransaction encounters exceptions, it should at least log them at debug level, otherwise important cause exceptions and stacktraces are lost. So, code like this: catch (RemoteException e) { // destroy session gone bad. destroySession(); throw new SystemException(e.toString()); } catch (Exception e) { throw new SystemException(e.toString()); } Should become: catch (RemoteException e) { // destroy session gone bad. destroySession(); log.debug("Remote exception encountered while....", e); throw new SystemException(e.toString()); } catch (Exception e) { log.debug("Exception encountered while...", e); throw new SystemException(e.toString()); } -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-379) Split large messages into fragments

by Tim Fox (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-379?page=com.atlassian.jir... ] Tim Fox commented on JBMESSAGING-379: ------------------------------------- Clebert- Can't you just work on the branch like everyone else? Or create a new branch? Working on patches is not helpful since it's hard for anyone to see what you're doing. > Split large messages into fragments > ----------------------------------- > > Key: JBMESSAGING-379 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-379 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assignee: Clebert Suconic > Priority: Critical > Fix For: 2.0.0 Beta > > Attachments: message-chunk-r5057-v1.patch > > > We need to split large messages into small chunks (say 1K), so the sending or receiving of a large message doesn't stall the entire connection since all traffic is multiplexed over it. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1405) Producer hangs after 20M sent

by Andy Taylor (JIRA)

Producer hangs after 20M sent ----------------------------- Key: JBMESSAGING-1405 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1405 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 2.0.0 Alpha Reporter: Andy Taylor Assignee: Tim Fox Fix For: 2.0.0 Beta If you run the perf sender and set the message size to 64k, the producer stops sending after 32000 messages, if the message size is 32k it stops sending after 64000 messages, and so forth. This is because of Producer flow control. -- 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

17 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBREM-1037) CLONE [JBREM-1006] - SOA MTOM bug points to bug in Remoting codebase

by Ron Sigal (JIRA)

CLONE [JBREM-1006] - SOA MTOM bug points to bug in Remoting codebase --------------------------------------------------------------------- Key: JBREM-1037 URL: https://jira.jboss.org/jira/browse/JBREM-1037 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP7, 2.4.0.GA (Pinto) Environment: SOA 4.3.0 CP02 CR3 Reporter: Ron Sigal Assignee: Ron Sigal Priority: Minor Fix For: 2.4.0.SP1 (Pinto) SOA-568 and JBESB-1803 point to a potential bug in the HttpUnmarshaller code shipped with EAP 4.3.0 CP01. -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-379) Split large messages into fragments

by Clebert Suconic (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-379?page=com.atlassian.jir... ] Clebert Suconic commented on JBMESSAGING-379: --------------------------------------------- For now I'm working with patches instead of branches. (As it is easier to administrate over merges) To generate the same "branch" I have, download the trunk on the revision used on the patch, then: cd /trunk svn udpate -r<revision> patch -p0 < message-chunk-r<revision>-vN.patch > Split large messages into fragments > ----------------------------------- > > Key: JBMESSAGING-379 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-379 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assignee: Clebert Suconic > Priority: Critical > Fix For: 2.0.0 Beta > > Attachments: message-chunk-r5057-v1.patch > > > We need to split large messages into small chunks (say 1K), so the sending or receiving of a large message doesn't stall the entire connection since all traffic is multiplexed over it. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-379) Split large messages into fragments

by Clebert Suconic (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-379?page=com.atlassian.jir... ] Clebert Suconic updated JBMESSAGING-379: ---------------------------------------- Attachment: message-chunk-r5057-v1.patch > Split large messages into fragments > ----------------------------------- > > Key: JBMESSAGING-379 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-379 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assignee: Clebert Suconic > Priority: Critical > Fix For: 2.0.0 Beta > > Attachments: message-chunk-r5057-v1.patch > > > We need to split large messages into small chunks (say 1K), so the sending or receiving of a large message doesn't stall the entire connection since all traffic is multiplexed over it. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-379) Split large messages into fragments

by Clebert Suconic (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-379?page=com.atlassian.jir... ] Clebert Suconic reassigned JBMESSAGING-379: ------------------------------------------- Assignee: Clebert Suconic (was: Tim Fox) > Split large messages into fragments > ----------------------------------- > > Key: JBMESSAGING-379 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-379 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assignee: Clebert Suconic > Priority: Critical > Fix For: 2.0.0 Beta > > Attachments: message-chunk-r5057-v1.patch > > > We need to split large messages into small chunks (say 1K), so the sending or receiving of a large message doesn't stall the entire connection since all traffic is multiplexed over it. -- 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

17 years, 9 months

1
0
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 October 2008