April 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBESB-443) Improve XSLT support and performance

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-443?page=comments#action_12360063 ] Mark Little commented on JBESB-443: ----------------------------------- Do you think this is enough for 4.2? Could we push off any more performance improvements to the 5.0 release? > Improve XSLT support and performance > ------------------------------------ > > Key: JBESB-443 > URL: http://jira.jboss.com/jira/browse/JBESB-443 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transformation Service > Reporter: Mark Little > Assigned To: Tom Fennelly > Priority: Critical > Fix For: 4.2 > > > Customers still want XSLT transformation support. Although Smooks supports XSLT, it may impose an overhead on some transformations versus native XSLT support. We need to see what the overhead is (if any) and maybe add native XSLT support within the ESB transformation service (a separate service implementation). -- 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, 2 months

1
0
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_12360062 ] Mark Little commented on JBESB-398: ----------------------------------- Will this make it into the MR2 release? > 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) > Components: Rosetta, Transports > Affects Versions: 4.0 CR1 > Reporter: Bruno Georges > Assigned To: Bruno Georges > Fix For: 4.2 Milestone Release 2 > > Original Estimate: 2 days > Time Spent: 40 minutes > Remaining Estimate: 1 day, 7 hours, 20 minutes > > 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Work logged: (JBESB-361) Added text on what is CBR.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-361?page=worklog#action_12360061 ] Mark Little logged work on JBESB-361: ------------------------------------- Time Spent: 2 hours Remaining Estimate: 0 minutes Time Spent: 2 hours > Added text on what is CBR. > -------------------------- > > Key: JBESB-361 > URL: http://jira.jboss.com/jira/browse/JBESB-361 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 4.0 CR2 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.2 Milestone Release 2 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBESB-415) JCA container support.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-415?page=all ] Mark Little reassigned JBESB-415: --------------------------------- Assignee: Bill Burke (was: Mark Little) > JCA container support. > ---------------------- > > Key: JBESB-415 > URL: http://jira.jboss.com/jira/browse/JBESB-415 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Adapters > Reporter: Mark Little > Assigned To: Bill Burke > Fix For: 4.2 > > > Support of the JBoss JCA Container on the MC and/or a 3rd party JCA container that has been tested with the various adapters technologies. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-361) Added text on what is CBR.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-361?page=all ] Mark Little closed JBESB-361. ----------------------------- Fix Version/s: 4.2 Milestone Release 2 (was: 4.2) Resolution: Done > Added text on what is CBR. > -------------------------- > > Key: JBESB-361 > URL: http://jira.jboss.com/jira/browse/JBESB-361 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 4.0 CR2 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.2 Milestone Release 2 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > -- 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, 2 months

1
0
0 / 0

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

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-312?page=comments#action_12360033 ] Kevin Conner commented on JBESB-312: ------------------------------------ Forgot to mention that it was fixed in revision 11152 > 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 Milestone Release 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

17 years, 2 months

1
0
0 / 0

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

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-312?page=all ] Kevin Conner closed JBESB-312. ------------------------------ Resolution: Done The code has changes somewhat since this was reported. The two main issues in the current codebase were the following - no exception listener in the connection pool, hence reconnect errors - exception logging via high levels, including when propagating or ignoring the exception The exception logging has been changed to log at DEBUG with appropriate additional messages (at higher levels) where appropriate. The log4j.xml has also been changed to restrict the CONSOLE output to INFO. Executing this in standalone mode no longer displays all the stacktraces. > 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 Milestone Release 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-517) JMS connection pool should register an exception listener to clean up on asynchronous errors

by Kevin Conner (JIRA)

JMS connection pool should register an exception listener to clean up on asynchronous errors -------------------------------------------------------------------------------------------- Key: JBESB-517 URL: http://jira.jboss.com/jira/browse/JBESB-517 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Milestone Release 2 The JMS connection pool does not register an exception listener to clean up the connection on asynchronous errors. The underlying connection should be closed to allow reconnect attempts. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-516) Notifier error handler has incorrect signature

by Kevin Conner (JIRA)

Notifier error handler has incorrect signature ---------------------------------------------- Key: JBESB-516 URL: http://jira.jboss.com/jira/browse/JBESB-516 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Milestone Release 2 The signature of the notifyError method does not include the Throwable which caused the error. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBESB-427) Roll-your-own Gateway example and docs

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-427?page=all ] Mark Little updated JBESB-427: ------------------------------ Fix Version/s: 4.2 (was: 5.0) > Roll-your-own Gateway example and docs > -------------------------------------- > > Key: JBESB-427 > URL: http://jira.jboss.com/jira/browse/JBESB-427 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Documentation > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.2 > > > Provide enough infrastructure and documentation so the end-user of our ESB can relatively easily add their own gateway/listener (BC) to a proprietary protocol that they wish to enable. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2007