March 2007 - esb-issues - Jboss List Archives

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

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-312?page=all ] Mark Little reassigned JBESB-312: --------------------------------- Assignee: Kevin Conner (was: Esteban Schifman) > 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.0 Maintenance Pack 1 > > > 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] Created: (JBESB-455) Please enable download resume.

by Neil Crow (JIRA)

Please enable download resume. ------------------------------ Key: JBESB-455 URL: http://jira.jboss.com/jira/browse/JBESB-455 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Neil Crow Assigned To: Mark Little Priority: Minor I would like to echo the sentiment raised in JBRULES-460. I have been trying to download JBossESB via HTTP for about a week. I have been trying to get the artifact "jbossesb-4.0GA-bundle.zip" (104mb). A resume option on all downloads would be a very useful. -- 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
4
0 / 0

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

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-418?page=all ] Kurt Stam updated JBESB-418: ---------------------------- Fix Version/s: 4.0 Maintenance Pack 1 (was: 4.2) Affects Version/s: 4.0 (was: 4.0 Beta 1 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.0 Maintenance Pack 1 > > > 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

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

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-418?page=all ] Kurt Stam updated JBESB-418: ---------------------------- Affects Version/s: 4.0 Beta 1 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 Beta 1 Maintenance Pack 1 > 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

[JBoss JIRA] Updated: (JBESB-354) Addition of a helloworld_sftp_action in the quickstarts

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-354?page=all ] Mark Little updated JBESB-354: ------------------------------ Fix Version/s: 4.2 (was: 4.0 Maintenance Pack 1) > Addition of a helloworld_sftp_action in the quickstarts > ------------------------------------------------------- > > Key: JBESB-354 > URL: http://jira.jboss.com/jira/browse/JBESB-354 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 CR1 > Reporter: Bruno Georges > Assigned To: Bruno Georges > Priority: Minor > Fix For: 4.2 > > -- 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-451) Some validation errors are output on stdout

by Mark Little (JIRA)

Some validation errors are output on stdout ------------------------------------------- Key: JBESB-451 URL: http://jira.jboss.com/jira/browse/JBESB-451 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.0 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.0 Maintenance Pack 1 Some validation errors (e.g., in XmlValidatorImpl) are output on stdout. Should be using the logger. -- 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
4
0 / 0

[JBoss JIRA] Commented: (JBESB-398) The use of java.net.URL doesnt allow support for protcols such as ftps, sftp. Refactor to use URI instead.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-398?page=comments#action_12354969 ] Mark Little commented on JBESB-398: ----------------------------------- Can you put the whole stack trace here so we can see where it's coming from? > The use of java.net.URL doesnt allow support for protcols such as ftps, sftp. Refactor to use URI instead. > ----------------------------------------------------------------------------------------------------------- > > Key: JBESB-398 > URL: http://jira.jboss.com/jira/browse/JBESB-398 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.0 CR1 > Reporter: Bruno Georges > Assigned To: Bruno Georges > Fix For: 4.0 Maintenance Pack 1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Exception is thrown when using sftp/ftps protocols. > java.net.MalformedURLException: unknown protocol: sftp > Mark: We should really be using URIs everywhere since EPRs are based on WS-A, which is URI/IRI based. -- 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] Assigned: (JBESB-445) Custom Action:Scripting

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-445?page=all ] Mark Little reassigned JBESB-445: --------------------------------- Assignee: Kevin Conner (was: Mark Little) > Custom Action:Scripting > ----------------------- > > Key: JBESB-445 > URL: http://jira.jboss.com/jira/browse/JBESB-445 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 Maintenance Pack 1 > Reporter: Burr Sutter > Assigned To: Kevin Conner > Priority: Optional > Fix For: 4.0 Maintenance Pack 1 > > Attachments: groovy_action.zip > > > Provide an out-of-the-box action that allows for the integration of scripting languages for as ESB actions. An example of a scripting language would be Groovy or Beanshell. A quickstart example should also be created to illustrate the capabilities. > Gregory Pierce provided a quickstart for Groovy. -- 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] Work started: (JBESB-403) Quickstart package hierarchy should be org.jboss...

by Sebastian Cao (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-403?page=all ] Work on JBESB-403 started by Sebastian Cao. > Quickstart package hierarchy should be org.jboss... > --------------------------------------------------- > > Key: JBESB-403 > URL: http://jira.jboss.com/jira/browse/JBESB-403 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Sebastian Cao > Priority: Minor > Fix For: 4.0 Maintenance Pack 1 > > -- 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] Commented: (JBESB-401) During Trailblazer DEMO, JMS doesn't reconnect after a restart of the App Server [JMS Provider]

by Daniel Brum (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-401?page=comments#action_12354918 ] Daniel Brum commented on JBESB-401: ----------------------------------- ant runJMSBank: The Banks code does not re-connect properly. This is a simulated piece of code, it's meant for demo purposes. ant runESB: This uses the ESB JMS listener gateway and ESB aware, and it will rely on the framework to provide reconnection logic. I think a JIRA task is needed to make the listener's responsible for handling JMS reconnects for ESB logic - the banks stuff does not require this, it's purely demoware. > 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: Daniel Brum > 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

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