October 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1225) simple_cbr QS uses deprecated getByteArray()

by Tom Cunningham (JIRA)

simple_cbr QS uses deprecated getByteArray() -------------------------------------------- Key: JBESB-1225 URL: http://jira.jboss.com/jira/browse/JBESB-1225 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 simple_cbr uses deprecated getByteArray() : compile: [mkdir] Created dir: /Users/tcunning/src/esb/trunk/product/samples/quickstarts/simple_cbr/build/classes [javac] Compiling 6 source files to /Users/tcunning/src/esb/trunk/product/samples/quickstarts/simple_cbr/build/classes [javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/simple_cbr/src/org/jboss/soa/esb/samples/quickstart/simplecbr/MyJMSListenerAction.java:38: warning: [deprecation] getByteArray() in org.jboss.soa.esb.message.Body has been deprecated [javac] System.out.println("Body: " + new String(message.getBody().getByteArray())); [javac] ^ [javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/simple_cbr/src/org/jboss/soa/esb/samples/quickstart/simplecbr/MyJMSListenerAction.java:48: warning: [deprecation] getByteArray() in org.jboss.soa.esb.message.Body has been deprecated [javac] System.out.println(message.getBody().getByteArray()); [javac] ^ [javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/simple_cbr/src/org/jboss/soa/esb/samples/quickstart/simplecbr/ReturnJMSMessage.java:58: warning: [deprecation] getByteArray() in org.jboss.soa.esb.message.Body has been deprecated [javac] String newMsg = new String(esbMessage.getBody().getByteArray()); [javac] ^ [javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/simple_cbr/src/org/jboss/soa/esb/samples/quickstart/simplecbr/RouteExpressShipping.java:39: warning: [deprecation] getByteArray() in org.jboss.soa.esb.message.Body has been deprecated [javac] System.out.println(new String(message.getBody().getByteArray())); [javac] ^ [javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/simple_cbr/src/org/jboss/soa/esb/samples/quickstart/simplecbr/RouteNormalShipping.java:39: warning: [deprecation] getByteArray() in org.jboss.soa.esb.message.Body has been deprecated [javac] System.out.println(new String(message.getBody().getByteArray())); [javac] ^ [javac] 5 warnings config: -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1209) Update messagestore quickstart

by Burr Sutter (JIRA)

Update messagestore quickstart ------------------------------ Key: JBESB-1209 URL: http://jira.jboss.com/jira/browse/JBESB-1209 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 The current messagestore quickstart is difficult to understand and doesn't demonstrate message retrieval via the built-in action (MessagePersister.getMessage()). -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1247) DB Listener does not include reconnect logic

by David Boeren (JIRA)

DB Listener does not include reconnect logic -------------------------------------------- Key: JBESB-1247 URL: http://jira.jboss.com/jira/browse/JBESB-1247 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: David Boeren Assigned To: Mark Little Priority: Minor What's happening is that the DB Listener seems to be getting stuck and no longer picking up new database entries. If the appserver is bounced then it resumes normal functioning. There's a big string of these errors in the log: 2007-10-24 00:56:43,882 DEBUG [org.jboss.soa.esb.helpers.persist.JdbcCleanConn] execQueryWait() FAILED COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0108E Communication link failure. SQLSTATE=40003 at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:254) at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:418) at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:396) at COM.ibm.db2.jdbc.net.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java:1068) at org.jboss.soa.esb.helpers.persist.JdbcCleanConn.execQueryWait(JdbcCleanConn.java:138) at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.pollForCandidates(SqlTableGatewayListener.java:447) at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.doRun(SqlTableGatewayListener.java:149) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:595) 2007-10-24 00:56:43,882 DEBUG [org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener] Some triggers might not have been returned COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0108E Communication link failure. SQLSTATE=40003 at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:254) at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:418) at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:396) at COM.ibm.db2.jdbc.net.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java:1068) at org.jboss.soa.esb.helpers.persist.JdbcCleanConn.execQueryWait(JdbcCleanConn.java:138) at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.pollForCandidates(SqlTableGatewayListener.java:447) at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.doRun(SqlTableGatewayListener.java:149) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:595) 2007-10-24 00:56:43,882 DEBUG [org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener] Returning 0 rows. Looks like the DB connection has gone down, and the code does not contain any reconnect logic so at that point it fails. -- 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, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-1155) Quickstart: transformation_xml2pojo - clean up (remove deprecated stuff)

by Burr Sutter (JIRA)

Quickstart: transformation_xml2pojo - clean up (remove deprecated stuff) ------------------------------------------------------------------------ Key: JBESB-1155 URL: http://jira.jboss.com/jira/browse/JBESB-1155 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Burr Sutter Assigned To: Burr Sutter Fix For: 4.2.1 make corrections for deprecated methods clean up MyJMSListener.java clean up DVDStoreAction.java -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1229) webservice_consumer2 throws exceptions on runtest

by Tom Cunningham (JIRA)

webservice_consumer2 throws exceptions on runtest ------------------------------------------------- Key: JBESB-1229 URL: http://jira.jboss.com/jira/browse/JBESB-1229 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 webservice_consumer2 throws exceptions on runtest: 11:18:21,807 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 11:18:21,808 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_webservice_consumer2_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_webservice_consumer2_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='307eabe4-f5f6-4e05-88f2-5e9115cbb9e7'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-1024 RelatesTo: jms:correlationID#a39faec6-6301-4a01-8fef-4f35b00d42c7 ] org.jboss.soa.esb.actions.ActionProcessingException: No params. SOAP message parameters must either be set as the default message body payload, or set on the body under the key defined in the 'paramsLocation' acton property. at org.jboss.soa.esb.actions.soap.SOAPClient.process(SOAPClient.java:323) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:273) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1237) bpm_orchestration4 - updates to the variables in the jBPM Admin Console doesn't work

by Jaroslaw Kijanowski (JIRA)

bpm_orchestration4 - updates to the variables in the jBPM Admin Console doesn't work ------------------------------------------------------------------------------------ Key: JBESB-1237 URL: http://jira.jboss.com/jira/browse/JBESB-1237 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Jaroslaw Kijanowski Assigned To: Mark Little I changed the Customer Status to 65 (in the jbpm console), but when I clicked on "Save & close", the console showed the previous value: 12:45:50,723 INFO [STDOUT] Platinum Customer - High Priority - Higher discount 12:45:50,724 INFO [STDOUT] Customer Status: 60 12:45:50,724 INFO [STDOUT] Order Total: 64.92 -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1222) messagestore QS throws exceptions during runtest

by Tom Cunningham (JIRA)

messagestore QS throws exceptions during runtest ------------------------------------------------ Key: JBESB-1222 URL: http://jira.jboss.com/jira/browse/JBESB-1222 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 During runtest, messagestore throws an exception while running on a clean ESB server : 10:40:24,173 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 10:40:27,514 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 10:40:27,514 WARN [ActionProcessingPipeline] Unexpected exception notifying processor of pipeline success java.lang.NullPointerException at java.lang.String.<init>(String.java:479) at org.jboss.soa.esb.samples.quickstart.messagestore.CheckMessageStoreAction.processSuccess(CheckMessageStoreAction.java:69) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessingPipeline.java:560) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:334) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) 10:40:27,515 INFO [STDOUT] ConsoleNotifier 2007/10/21 10:40:27.515<Hello MessageStore> -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1250) Test with Tibco JMS

by Kurt Stam (JIRA)

Test with Tibco JMS ------------------- Key: JBESB-1250 URL: http://jira.jboss.com/jira/browse/JBESB-1250 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kurt Stam 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1245) DB Listener Stops Listening

by Tom Cunningham (JIRA)

DB Listener Stops Listening --------------------------- Key: JBESB-1245 URL: http://jira.jboss.com/jira/browse/JBESB-1245 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 If the database that it is connected to goes down and then is brought back up again, the SqlTableGatewayListener never re-establishes the connection. This should be pretty simple to fix inside of the getDbConn() method in SqlTableGatewayListener.java. -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1199) CBR behaves like a message filter on a zero hit

by Jaroslaw Kijanowski (JIRA)

CBR behaves like a message filter on a zero hit ----------------------------------------------- Key: JBESB-1199 URL: http://jira.jboss.com/jira/browse/JBESB-1199 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.2.1 IR2 Reporter: Jaroslaw Kijanowski Assigned To: Mark Little When a message has been parsed and its content didn't allow to specify a destination, for example, the "total amount" equals 50, but rules specify a destination if "total amount" is greater than or less than 50, then there is no difference between the Message Filter and CBR - the message is simply dropped. Shouldn't, in case of using the CBR, such a message goes to the DLQ? -- 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, 11 months

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2007