October 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1208) BPM & ESB Quickstart for human task management

by Burr Sutter (JIRA)

BPM & ESB Quickstart for human task management ---------------------------------------------- Key: JBESB-1208 URL: http://jira.jboss.com/jira/browse/JBESB-1208 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Burr Sutter Assigned To: Burr Sutter Priority: Minor Fix For: 4.2.1 bpm_orchestration4 illustrates how to have both ESB service invocation, async bpm signals, business rule services and human task management in a single example. -- 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

12 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1203) Add JCA quickstarts

by Kurt Stam (JIRA)

Add JCA quickstarts ------------------- Key: JBESB-1203 URL: http://jira.jboss.com/jira/browse/JBESB-1203 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Reporter: Kurt Stam Assigned To: Mark Little Priority: Minor Fix For: 4.3 Add in JCA quickstarts. We have one for JMS and Email on the wiki: http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJCAWithJBossESB -- 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

13 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBESB-844) Pull together some developer docs around the lifecycle identity (on the wiki?)

by Tom Fennelly (JIRA)

Pull together some developer docs around the lifecycle identity (on the wiki?) ------------------------------------------------------------------------------ Key: JBESB-844 URL: http://jira.jboss.com/jira/browse/JBESB-844 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Kevin Conner And draw a few pictures while yer at it Kev ;-) -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-880) The ESB is blocked under heavy load when using JMS

by Jiri Pechanec (JIRA)

The ESB is blocked under heavy load when using JMS -------------------------------------------------- Key: JBESB-880 URL: http://jira.jboss.com/jira/browse/JBESB-880 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2 Milestone Release 3 Environment: RHEL 5, PostgreSQL Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Blocker When the ESB is forced to process a huge batch of messages then it blocks completely. The ESB configuration was just one service with one listener and gateway. Both gateway and listener are using JMS. The testing was executed twice using one and then four threads per listener and gateway. The service contains two actions that serves only for message counting. If you try to send 10000 messages sized around 20 KB it will probaly block after few minutes of processing. The ESB do not respond to TERM signal and even JMX console is not available. The only solution is to kill process violently. With the smaller messages the block does not happend or happends after bigger amount of messages. The sender is generating following log messages [Timer-1][BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask@201d592a: detected failure on control connection Thread[control: Socket[addr=/10.34.34.47,port=2660,localport=51957],5,main]: requesting new control connection We can not exclude problem in JBoss Messaging itself but when we tried to use plain JMS without ESB we were able to send/receive 300000 messages without any problem. Moreover the more messages were processed the longer time it takes for the next batch to be processed. -- 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

14 years, 4 months

7
33
0 / 0

[JBoss JIRA] Created: (JBESB-776) Need a Maven ESB Archetype

by Tom Cunningham (JIRA)

Need a Maven ESB Archetype -------------------------- Key: JBESB-776 URL: http://jira.jboss.com/jira/browse/JBESB-776 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 5.0 We have a maven task which compiles an .esb package. We should also have a maven "archetype" which creates the preferred project layout for Maven. See for details on archetypes http://maven.apache.org/plugins/maven-archetype-plugin/ -- 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

14 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (JBESB-1171) Remove usages org.jboss.soa.esb.listeners.message.MockMessageComposer and replace with BasicMessageComposer

by Tom Fennelly (JIRA)

Remove usages org.jboss.soa.esb.listeners.message.MockMessageComposer and replace with BasicMessageComposer ----------------------------------------------------------------------------------------------------------- Key: JBESB-1171 URL: http://jira.jboss.com/jira/browse/JBESB-1171 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 IR1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 Not doing anything extra -- 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

14 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-801) Wiki pages should be create for all JBoss ESB Quickstarts.

by angel asencio (JIRA)

Wiki pages should be create for all JBoss ESB Quickstarts. ---------------------------------------------------------- Key: JBESB-801 URL: http://jira.jboss.com/jira/browse/JBESB-801 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: angel asencio Assigned To: Mark Little Priority: Minor Wiiki pages should be provided like the ones created for the quickstart samples helloworld and simple_cbr that ease the understanding of these concepts. In addition it can provide navigation links to dependent concepts or concepts that the quickstart sample depends on. -- 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

14 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-800) Provide in the documentation the links of the existing wiki pages for the quickstart samples.

by angel asencio (JIRA)

Provide in the documentation the links of the existing wiki pages for the quickstart samples. --------------------------------------------------------------------------------------------- Key: JBESB-800 URL: http://jira.jboss.com/jira/browse/JBESB-800 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: angel asencio Assigned To: Mark Little Priority: Minor To list any existing wiki quickstart sample link under the corresponding quickstart sample listed in the GettingStarted Guide and the readme.txt of that quickstart sample. For examples: There exist a wiki for the Hello World quickstart: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossESBHelloworld This should be listed under the listing of helloworld in the Getting Started Guide and in the readme.txt of the helloworld quickstart sample. -- 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

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1241) test suite execute against server bound to specified local IP

by Aleksandar Kostadinov (JIRA)

test suite execute against server bound to specified local IP ------------------------------------------------------------- Key: JBESB-1241 URL: http://jira.jboss.com/jira/browse/JBESB-1241 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Aleksandar Kostadinov Assigned To: Mark Little Currently test suite can execute only against server bound to "localhost". It makes sense to be able to execute it against a server running on a selected IP probably an ant property supplied. -- 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

14 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-659) 2 JBossAS instances cannot share the same JBossMQ service for JMS gateways if JMS is installed

by James Williams (JIRA)

2 JBossAS instances cannot share the same JBossMQ service for JMS gateways if JMS is installed ---------------------------------------------------------------------------------------------- Key: JBESB-659 URL: http://jira.jboss.com/jira/browse/JBESB-659 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBossAS 4.2GA, JBossESB - Head as of 07/05.2007. Reporter: James Williams Assigned To: Mark Little I am trying to get 2 JBossAS instances to share the same JMS Server for gateways. There's a lot of moving parts, but I'll try to explain the configurations: 1. JBossAS 4.2.0-GA default config with all .ESB archives, minus the quickstart_helloworld.esb. This server is started using the "-b localhost -c node0" startup parameters. 2. JBossAS 4.2.0-GA default config with "jbossesb.sar" and "quickstart_helloworld.esb". All other .ESB archives are removed and my goal is to use the JMS service in server #1 for gateways/listeners. The quickstart_helloworld.esb archive in this server has its own gateway/listener queues. This server is started using the "-b 192.168.200.1 -c node1" startup parameters. 3. JBossAS 4.2-GA default config with "jbossesb.sar" and "quickstart_helloworld.esb". All other .ESB archives are removed and my goal is to use the JMS service in server #1 for gateways/listeners. The quickstart_helloworld.esb archive in this server has its own gateway/listener queues that are different from the gateways/listeners in #2. This server is started using the "-b 192.168.200.2 -c node2" startup parameters. I'm not having any problems with nodes #2 and #3 sharing the JMS service that's running on #1, so long as JBossMQ isn't installed on node #2 or #3. If JMS is installed, quickstart_helloworld.esb archive fails to deploy on both #2 or #3. It complains that the Gateway queue does not exist, but it most certainly does. Worse yet, when I run the SendJMSMessage test class, it cannot find the queue either. It's as if jbossesb.sar is somehow screwing up all jndi lookups for the queue. There are a couple things I've done to try to rule out other potential root causes: 1. I tried running #1, #2, #3 w/out any .ESB archives or jbossesb.sar to verify that a JMS client can indeed drop requests into queues on all servers. To me, this validates that 3 unclustered JBossAS instances can each have their own JMS queues that are all accessible on a single machine, like my test environment, just by having the app servers bootstrapped by unique config and ip address. I was worried that the JMS service might be the culprit, but that doesn't appear to be the case. 2. I removed JMS from #2 and #3 to verify that the queues are setup correctly on #1 and to verify that #2 and #3 can indeed share the same JMS service provided they do not have JMS running themselves. -- 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

14 years, 8 months

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2007