March 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBESB-410) WS-BPEL support

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-410?page=all ] Mark Little updated JBESB-410: ------------------------------ Fix Version/s: 4.2 Milestone Release 2 (was: 4.2) > WS-BPEL support > --------------- > > Key: JBESB-410 > URL: http://jira.jboss.com/jira/browse/JBESB-410 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BPM > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.2 Milestone Release 2 > > > Adding BPEL support to the ESB, requires that all services have a configuration flag that dynamically renders WSDL from the current endpoint. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-438) Controlled shutdown

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-438?page=all ] Mark Little updated JBESB-438: ------------------------------ Fix Version/s: 5.0 > Controlled shutdown > ------------------- > > Key: JBESB-438 > URL: http://jira.jboss.com/jira/browse/JBESB-438 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0, 4.2 Milestone Release 2 > > > During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (JBESB-438) Controlled shutdown

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-438?page=all ] Mark Little reassigned JBESB-438: --------------------------------- Assignee: Kevin Conner (was: Mark Little) > Controlled shutdown > ------------------- > > Key: JBESB-438 > URL: http://jira.jboss.com/jira/browse/JBESB-438 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0, 4.2 Milestone Release 2 > > > During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-493) No JBossIDE pdf in binary distribution

by Mark Little (JIRA)

No JBossIDE pdf in binary distribution -------------------------------------- Key: JBESB-493 URL: http://jira.jboss.com/jira/browse/JBESB-493 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.2 Milestone Release 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

17 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-492) RegistryConfiguration doc

by Mark Little (JIRA)

RegistryConfiguration doc ------------------------- Key: JBESB-492 URL: http://jira.jboss.com/jira/browse/JBESB-492 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.2 Milestone Release 2 There are RegistryConfiguration and Registry docs in the binary release. Why? -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-491) GettingStartedGuide refers to 4.0GA

by Mark Little (JIRA)

GettingStartedGuide refers to 4.0GA ----------------------------------- Key: JBESB-491 URL: http://jira.jboss.com/jira/browse/JBESB-491 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.2 Milestone Release 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

17 years, 2 months

1
2
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 Milestone Release 2 (was: 4.2) > 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] Updated: (JBESB-443) Improve XSLT support and performance

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-443?page=all ] Mark Little updated JBESB-443: ------------------------------ Fix Version/s: 4.2 Milestone Release 2 (was: 4.2 Milestone Release 1) > 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 Milestone Release 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] Updated: (JBESB-403) Quickstart package hierarchy should be org.jboss...

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-403?page=all ] Mark Little updated JBESB-403: ------------------------------ Fix Version/s: 4.2 Milestone Release 2 (was: 4.2) > 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.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] Updated: (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=all ] Mark Little updated JBESB-398: ------------------------------ Fix Version/s: 4.2 Milestone Release 2 (was: 4.2) > 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: Mark Little > Fix For: 4.2 Milestone Release 2 > > Original Estimate: 2 days > Time Spent: 30 minutes > Remaining Estimate: 1 day, 7 hours, 30 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2007