June 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBESB-164) Document and refactor command code

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-164?page=all ] Mark Little closed JBESB-164. ----------------------------- Fix Version/s: 4.2 (was: 5.0) Resolution: Done > Document and refactor command code > ---------------------------------- > > Key: JBESB-164 > URL: http://jira.jboss.com/jira/browse/JBESB-164 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 Beta 1 Maintenance Pack 1 > Reporter: Mark Little > Assigned To: Tom Fennelly > Priority: Minor > Fix For: 4.2 > > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > Fully document the command code and move it into an internal package. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-293) When performing a base listener mapping, make sure that the bus and provider are also base types.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-293?page=all ] Mark Little closed JBESB-293. ----------------------------- Fix Version/s: 4.2 (was: 5.0) Resolution: Done > When performing a base listener mapping, make sure that the bus and provider are also base types. > ------------------------------------------------------------------------------------------------- > > Key: JBESB-293 > URL: http://jira.jboss.com/jira/browse/JBESB-293 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-293) When performing a base listener mapping, make sure that the bus and provider are also base types.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-293?page=all ] Mark Little reopened JBESB-293: ------------------------------- > When performing a base listener mapping, make sure that the bus and provider are also base types. > ------------------------------------------------------------------------------------------------- > > Key: JBESB-293 > URL: http://jira.jboss.com/jira/browse/JBESB-293 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-270) JMSQueueListener doesn't manage Thread creation for the ActionProcessingPipeline i.e. can be flooded with messages

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-270?page=all ] Mark Little closed JBESB-270. ----------------------------- Fix Version/s: 4.2 (was: 5.0) Resolution: Done > JMSQueueListener doesn't manage Thread creation for the ActionProcessingPipeline i.e. can be flooded with messages > ------------------------------------------------------------------------------------------------------------------ > > Key: JBESB-270 > URL: http://jira.jboss.com/jira/browse/JBESB-270 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assigned To: Kevin Conner > Fix For: 4.2 > > > This listener receives messages from a JMS queue and spawns a new thread for the ActionProcessingPipeline instance that is created to process the message. If you hammer this listener with messages (e.g 20 concurrent threads continually pumping messages into the in queue), you'll kill the process through running out of threads to process the messages. > The listener should manage the Threads. Use of a Threadpool would probably take care of this for you i.e. can probably get the pool to block while waiting for a free thread to be returned to the pool. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-270) JMSQueueListener doesn't manage Thread creation for the ActionProcessingPipeline i.e. can be flooded with messages

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-270?page=all ] Mark Little reopened JBESB-270: ------------------------------- > JMSQueueListener doesn't manage Thread creation for the ActionProcessingPipeline i.e. can be flooded with messages > ------------------------------------------------------------------------------------------------------------------ > > Key: JBESB-270 > URL: http://jira.jboss.com/jira/browse/JBESB-270 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assigned To: Kevin Conner > Fix For: 4.2 > > > This listener receives messages from a JMS queue and spawns a new thread for the ActionProcessingPipeline instance that is created to process the message. If you hammer this listener with messages (e.g 20 concurrent threads continually pumping messages into the in queue), you'll kill the process through running out of threads to process the messages. > The listener should manage the Threads. Use of a Threadpool would probably take care of this for you i.e. can probably get the pool to block while waiting for a free thread to be returned to the pool. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-182) Web Services support

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-182?page=all ] Mark Little reopened JBESB-182: ------------------------------- > Web Services support > -------------------- > > Key: JBESB-182 > URL: http://jira.jboss.com/jira/browse/JBESB-182 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.0 Beta 1 Maintenance Pack 1 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2 > > > Integrate Web Services. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-164) Document and refactor command code

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-164?page=all ] Mark Little reopened JBESB-164: ------------------------------- > Document and refactor command code > ---------------------------------- > > Key: JBESB-164 > URL: http://jira.jboss.com/jira/browse/JBESB-164 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 Beta 1 Maintenance Pack 1 > Reporter: Mark Little > Assigned To: Tom Fennelly > Priority: Minor > Fix For: 4.2 > > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > Fully document the command code and move it into an internal package. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-182) Web Services support

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-182?page=all ] Mark Little closed JBESB-182. ----------------------------- Fix Version/s: 4.2 (was: 5.0) Resolution: Done > Web Services support > -------------------- > > Key: JBESB-182 > URL: http://jira.jboss.com/jira/browse/JBESB-182 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.0 Beta 1 Maintenance Pack 1 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2 > > > Integrate Web Services. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-229) Add "Update" capability on all Admin Console wizards.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-229?page=all ] Mark Little closed JBESB-229. ----------------------------- Fix Version/s: 4.2 (was: 5.0) Resolution: Done > Add "Update" capability on all Admin Console wizards. > ----------------------------------------------------- > > Key: JBESB-229 > URL: http://jira.jboss.com/jira/browse/JBESB-229 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.0 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > Fix For: 4.2 > > > Currently the wizards only support add and delete so if you make a boo boo, you need to delete and readd. This is a bit of a pain. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-229) Add "Update" capability on all Admin Console wizards.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-229?page=all ] Mark Little reopened JBESB-229: ------------------------------- > Add "Update" capability on all Admin Console wizards. > ----------------------------------------------------- > > Key: JBESB-229 > URL: http://jira.jboss.com/jira/browse/JBESB-229 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.0 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > Fix For: 4.2 > > > Currently the wizards only support add and delete so if you make a boo boo, you need to delete and readd. This is a bit of a pain. -- 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

18 years, 10 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

esb-issues June 2007