January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1443) CallbackCommand state checker can fail in case of loops in BPM process

by Jiri Pechanec (JIRA)

CallbackCommand state checker can fail in case of loops in BPM process ---------------------------------------------------------------------- Key: JBESB-1443 URL: http://jira.jboss.com/jira/browse/JBESB-1443 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kurt Stam Priority: Critical Fix For: 4.2.1 CP1 If there is a loop in jBPM process (or more precisely if the same node is invoked more than once) then the CallbackCommand checking of state can fail. The problem is that checking is based on processId and nodeId. But this combination is not unique if the same node is invoked more than once. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1449) SOAPClient cannot handle more than 1 thread in ESB listener

by Martin Vecera (JIRA)

SOAPClient cannot handle more than 1 thread in ESB listener ----------------------------------------------------------- Key: JBESB-1449 URL: http://jira.jboss.com/jira/browse/JBESB-1449 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Environment: SOA-P 4.2.0GA Reporter: Martin Vecera When I tried to increase number of threads in ESB listener in webservice_consumer1 quickstart the server was not able to process more than 2 messages without problems. Steps to reproduce: 1. Change webservice_consumer1 to sent ~10 messages. 2. Change ESB listener thread count in jboss-esb.xml to at least 2. 2. Deploy it. 3. Run it and see the server log. The server show different errors. Usually: Connection reset, Connection closed, Bad chunk size, Unable to parse status code. See attached file. -- 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

16 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1464) Error running jms_topic quickstart

by Jehudi Castro (JIRA)

Error running jms_topic quickstart ---------------------------------- Key: JBESB-1464 URL: http://jira.jboss.com/jira/browse/JBESB-1464 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Environment: Win2k3 JBoss SOA Platform ESB Standalone Server - Version 4.2.0.beta1 Reporter: Jehudi Castro In the first step: 1. In a command terminal window in this folder ("Window1"), type 'ant deploy'. get this error: [javac] /home/jcastros/Projects/SOA/BETA1/standalone-soa-4.2.0/jboss-soa-p-standalone.4.2.0/samples/quickstarts/jms_topic/src/org/jboss/soa/esb/samples/quickstart/jmstopic/MessageAugmentor.java:34: package junit.framework does not exist [javac] import junit.framework.TestCase; This import (line 34) in not needed, can be deleted. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1422) CreateNewProcess does not propagate token/processId

by Jiri Pechanec (JIRA)

CreateNewProcess does not propagate token/processId --------------------------------------------------- Key: JBESB-1422 URL: http://jira.jboss.com/jira/browse/JBESB-1422 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Environment: FC7/PostgreSQL Reporter: Jiri Pechanec When CreateNew Process command is called it does not propagate anywhere processId/tokenId. It means that it is not possible to send signal to created process. -- 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

16 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBESB-1461) SOAPClient throwing back a missleading exception when the MessagePayloadProxy fails to find the payload

by Tom Fennelly (JIRA)

SOAPClient throwing back a missleading exception when the MessagePayloadProxy fails to find the payload ------------------------------------------------------------------------------------------------------- Key: JBESB-1461 URL: http://jira.jboss.com/jira/browse/JBESB-1461 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Tom Fennelly Fix For: 4.2.1 CP1 It's throwing a MessageDeliverException, but the message is bogus (pre MessagePayloadProxy error message). It's also not chaining the cause exception. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1467) Error running webservice_mtom quickstart

by Jehudi Castro (JIRA)

Error running webservice_mtom quickstart ---------------------------------------- Key: JBESB-1467 URL: http://jira.jboss.com/jira/browse/JBESB-1467 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Environment: Win2k3 Reporter: Jehudi Castro This quickstart ask for an old version of jboss-remoting.jar. Output: $ ant deploy ... [echo] JBR Version String: 'JBossRemoting Version 2.2.2.SP4 (Bluto)'. ... BUILD FAILED .../soa-4.2.0/jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:494: Invalid version of JBossRemoting installed on target server. Please install version 2.2.2.SP2: http://repository.jboss.org/jboss/remoting/2.2.2.SP2/lib/jboss-remoting.jar When fixed the documentation (README.html) should be changed "NOTE: This Quickstart requires the JBossRemoting 2.2.2SP2 patch to be applied. This simply involves downloading jboss-remoting.jar and copying it into your "server/<server>/lib" folder. Be sure to restart your JBoss Application/ESB Server instance." -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1465) Update title on fail-over to add "load balancing"

by Mark Little (JIRA)

Update title on fail-over to add "load balancing" ------------------------------------------------- Key: JBESB-1465 URL: http://jira.jboss.com/jira/browse/JBESB-1465 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial Fix For: 4.2.1 CP1 -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1463) Error running transform_XML2POJO quickstart

by Jehudi Castro (JIRA)

Error running transform_XML2POJO quickstart ------------------------------------------- Key: JBESB-1463 URL: http://jira.jboss.com/jira/browse/JBESB-1463 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Environment: Win2k3 JBoss SOA Platform ESB Standalone Server - Version 4.2.0.beta1 Reporter: Jehudi Castro When execute this step: 2. Open another command terminal window in this folder ("Window2"), type 'ant receive'. get this output: [echo] Runs Test JMS Receiver [java] Usage <queue-name> This is the target in the build.xml file: <target name="receive" depends="compile" description="runs Test JMS Receiver"> <echo>Runs Test JMS Receiver</echo> <java fork="no" classname="org.jboss.soa.esb.samples.quickstart.transformxml2pojo.test.ReceiveJMSMessage" failonerror="true"> <classpath refid="exec-classpath"/> </java> </target> I guess that is missing something like <arg value="queue/myQueue"/> -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1441) SqlTableGatewayListener : insertTimestamp seems to be unused

by Tom Cunningham (JIRA)

SqlTableGatewayListener : insertTimestamp seems to be unused ------------------------------------------------------------ Key: JBESB-1441 URL: http://jira.jboss.com/jira/browse/JBESB-1441 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Tom Cunningham Fix For: 4.2.1 CP1 SqlMessageFilter has a "insert-timestamp" field, ostensibly to insert timestamps when the row is modified by the ESB. I don't see it being used anywhere. -- 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

16 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1124) Incorporate Notifier quickstart

by Mark Little (JIRA)

Incorporate Notifier quickstart ------------------------------- Key: JBESB-1124 URL: http://jira.jboss.com/jira/browse/JBESB-1124 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.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

16 years, 4 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008