March 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Assigned: (JBESB-199) Message Store Repository bootstrap

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-199?page=all ] Mark Little reassigned JBESB-199: --------------------------------- Assignee: Mark Little (was: Daniel Brum) > Message Store Repository bootstrap > ---------------------------------- > > Key: JBESB-199 > URL: http://jira.jboss.com/jira/browse/JBESB-199 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Reporter: Daniel Brum > Assigned To: Mark Little > Priority: Optional > Fix For: 5.0 > > > Create a bootstrap process for the message store, same design to be used by service registry -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-453) Dead letter Service - Message Store implementation

by Kurt Stam (JIRA)

Dead letter Service - Message Store implementation -------------------------------------------------- Key: JBESB-453 URL: http://jira.jboss.com/jira/browse/JBESB-453 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Daniel Brum Fix For: 4.0 Beta 1 Maintenance Pack 1 For the message-store implementation, you need to define what you want to store, and how you want to retrieve, and i guess clean-up redelivered messages. -- 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, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-447) Make JBossESB 1.2.0GA the default JMS

by Mark Little (JIRA)

Make JBossESB 1.2.0GA the default JMS ------------------------------------- Key: JBESB-447 URL: http://jira.jboss.com/jira/browse/JBESB-447 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Transports Affects Versions: 4.0 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.0 Maintenance Pack 1 Now that JBoss Messaging has gone GA we should make it our default JMS provider. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-475) SmooksTransformer can no longer maintain a static ref to a StandaloneSmooks instance

by Tom Fennelly (JIRA)

SmooksTransformer can no longer maintain a static ref to a StandaloneSmooks instance ------------------------------------------------------------------------------------ Key: JBESB-475 URL: http://jira.jboss.com/jira/browse/JBESB-475 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.0 Maintenance Pack 1 Because of the new deploy, this is no longer an option. It's OK though, because Kev is providing a singleton action processor mechanism, at which point, there'll be no need to use a static ref. (a static ref was used because of the overhead in loading and working through smooks configs + actions were not singleton) -- 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, 1 month

1
1
0 / 0

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

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-401?page=all ] Mark Little updated JBESB-401: ------------------------------ Fix Version/s: 4.2 (was: 4.0 Maintenance Pack 1) Assignee: Kevin Conner (was: Daniel Brum) > 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: Kevin Conner > Fix For: 4.2 > > > 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

19 years, 1 month

1
0
0 / 0

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

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-400?page=all ] Mark Little updated JBESB-400: ------------------------------ Fix Version/s: 4.2 (was: 4.0 Maintenance Pack 1) Assignee: Tom Fennelly (was: Daniel Brum) > 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: Tom Fennelly > Fix For: 4.2 > > > 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-312) StandaloneBootStrapper Messages

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-312?page=all ] Mark Little updated JBESB-312: ------------------------------ Fix Version/s: 4.2 (was: 4.0 Maintenance Pack 1) > StandaloneBootStrapper Messages > ------------------------------- > > Key: JBESB-312 > URL: http://jira.jboss.com/jira/browse/JBESB-312 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Burr Sutter > Assigned To: Kevin Conner > Priority: Minor > Fix For: 4.2 > > > When the application server is restarted out from under a live running listener (via the Standalonebootstrapper) it does appear to work once the app server is brought back to life. However, it produces a long stacktrace. Even after it redeploys the services (even though it shouldn't hav redeployed the servcies because their config file was untouched) it continues to complain and throw up errors/warnings until freshly restarted. > [java] 19:15:14,465 WARN [Connection Monitor Thread][Connection] Connectio > n 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(Cloc > kDaemon.java:364) > [java] at java.lang.Thread.run(Thread.java:595) > [java] Caused by: java.io.IOException: ping timeout. > [java] ... 3 more > [java] 19:15:18,027 WARN [Connection Monitor Thread][Connection] Connectio > n 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(Cloc > kDaemon.java:364) > [java] at java.lang.Thread.run(Thread.java:595) > [java] Caused by: java.io.IOException: ping timeout. > [java] ... 3 more > [java] 19:15:18,027 WARN [Connection Monitor Thread][Connection] Connectio > n 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(Cloc > kDaemon.java:364) > [java] at java.lang.Thread.run(Thread.java:595) > [java] Caused by: java.io.IOException: ping timeout. > [java] ... 3 more > [java] 19:15:18,183 WARN [Connection Monitor Thread][Connection] Connectio > n 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(Cloc > kDaemon.java:364) > [java] at java.lang.Thread.run(Thread.java:595) > [java] Caused by: java.io.IOException: ping timeout. > [java] ... 3 more > [java] 19:15:18,308 WARN [Connection Monitor Thread][Connection] Connectio > n 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(Cloc > kDaemon.java:364) > [java] at java.lang.Thread.run(Thread.java:595) > [java] Caused by: java.io.IOException: ping timeout. > [java] ... 3 more > [java] 19:15:20,043 WARN [Connection Monitor Thread][Connection] Connectio > n 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(Cloc -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-442) Profile the code base

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-442?page=all ] Kurt Stam closed JBESB-442. --------------------------- Resolution: Done We found some issues with JMS. For MP1 this is been good. This is ongoing work though. Closing this one, we'll continue this work for the next release: http://jira.jboss.com/jira/browse/JBESB-472 > Profile the code base > --------------------- > > Key: JBESB-442 > URL: http://jira.jboss.com/jira/browse/JBESB-442 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.0 > Reporter: Kurt Stam > Assigned To: Kurt Stam > Fix For: 4.0 Maintenance Pack 1 > > > We need a good performance profile of the current codebase. > Look for memory and thread leaks, caching opportunities and other optimization opportunities. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-446) getTemporaryReplyTo broken

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-446?page=all ] Mark Little updated JBESB-446: ------------------------------ Fix Version/s: 4.2 (was: 4.0 Maintenance Pack 1) > getTemporaryReplyTo broken > -------------------------- > > Key: JBESB-446 > URL: http://jira.jboss.com/jira/browse/JBESB-446 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Esteban Schifman > Priority: Critical > Fix For: 4.2 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > In some circumstances getTemporaryReplyTo can generate an EPR that will be functionally identical to the original To EPR. If the client and service share the same transport mechanism (e.g., JMS queue) then it's possible that replies to the client may be lost because they get picked up by the service again. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-418) Catch-All/Otherwise/Default for CBR

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-418?page=all ] Mark Little updated JBESB-418: ------------------------------ Fix Version/s: 4.2 (was: 4.0 Maintenance Pack 1) > Catch-All/Otherwise/Default for CBR > ----------------------------------- > > Key: JBESB-418 > URL: http://jira.jboss.com/jira/browse/JBESB-418 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kurt Stam > Priority: Critical > Fix For: 4.2 > > > For CBR, it currently has no exception handling. -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2007