October 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1272) CommandInterpreter.doTheJob does not make sense in error condition

by Mark Little (JIRA)

CommandInterpreter.doTheJob does not make sense in error condition ------------------------------------------------------------------ Key: JBESB-1272 URL: http://jira.jboss.com/jira/browse/JBESB-1272 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 IR2 Reporter: Mark Little Fix For: 4.3 Message response = Helper.commandMessageTemplate(); Body body = response.getBody(); try { Object obj = getJbpmCommandService().execute(command); body.add(Constants.RETURN_CODE, Constants.RETCODE_OK); if (null!=obj) body.add(Constants.JBPM_RETURN_OBJECT, obj); } catch (JbpmException e) { body.add(Constants.RETURN_CODE, Constants.RETCODE_EXCEPTION); body.add(Constants.EXCEPTION, e); throw e; } return response; Why does the code modify the body when the message isn't going to be returned? -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1273) Incorporate PropertyReplacer into SmooksService/JuddRMIService

by Tom Cunningham (JIRA)

Incorporate PropertyReplacer into SmooksService/JuddRMIService -------------------------------------------------------------- Key: JBESB-1273 URL: http://jira.jboss.com/jira/browse/JBESB-1273 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Tom Cunningham Fix For: 4.3 Tom Fennelly created an ESB property replacer but never checked it in - it should be incorporated into SmooksService/JuddiRMIService because it is better than the implementation in there now. -- 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, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-1206) Cannot buld the trailblazer example app - needs the ESB source code

by Trevor Kirby (JIRA)

Cannot buld the trailblazer example app - needs the ESB source code -------------------------------------------------------------------- Key: JBESB-1206 URL: http://jira.jboss.com/jira/browse/JBESB-1206 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.2.1 IR1 Reporter: Trevor Kirby Assigned To: Kevin Conner Fix For: 4.2.1 triage Cannot buld the trailblazer example app in SOA- needs the ESB source code ant compile Buildfile: build.xml esb.built: [echo] Please build the ESB with "ant dist" in the ESB parent [echo] directory in order to run the Trailblazer application. BUILD FAILED /opt/SOA/samples/trailblazer/build.xml:130: Please build ESB first. Description Cannot buld the trailblazer example app - needs the ESB source code ant compile Buildfile: build.xml esb.built: [echo] Please build the ESB with "ant dist" in the ESB parent [echo] directory in order to run the Trailblazer application. BUILD FAILED /opt/SOA/samples/trailblazer/build.xml:130: Please build ESB first. -- 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, 7 months

5
13
0 / 0

[JBoss JIRA] Created: (JBESB-1281) WebService consuming does not work - exception

by Jiri Pechanec (JIRA)

WebService consuming does not work - exception ---------------------------------------------- Key: JBESB-1281 URL: http://jira.jboss.com/jira/browse/JBESB-1281 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 IR2 Reporter: Jiri Pechanec Priority: Critical When trying to consume Web Service, the follwoing exception is thrown java.lang.ClassCastException: java.lang.String at org.jboss.soa.esb.actions.soap.SOAPClient.process(SOAPClient.java:321) 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:595) The problem si wrong condition at SOAPClient.java:518 -- 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, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-746) Potential memory leak in Aggregator

by Jiri Pechanec (JIRA)

Potential memory leak in Aggregator ----------------------------------- Key: JBESB-746 URL: http://jira.jboss.com/jira/browse/JBESB-746 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor There is minor potential memory leak in Aggregator action. 1) The message is in timeout 2) The process method is started by receiveing one part of timeout message 3) Timeout checker checks the same message 4) Regular process creates aggregated message and removes the record in notification HashMap 5) Timout checker sends a notfificaion message and creates the record in notification HashMap 6) Regular process method receives notification message and ignores it as already timed out 7) The record remains in notification map Recommended solution Add _notified.remove(uuId) call to the branch that handles ignoring already timed out messages. -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1204) Aggregator can't collect messages via aggregatorTags

by Jaroslaw Kijanowski (JIRA)

Aggregator can't collect messages via aggregatorTags ---------------------------------------------------- Key: JBESB-1204 URL: http://jira.jboss.com/jira/browse/JBESB-1204 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 The ESB's aggregator relies on 'aggregatorTags' to puzzle the individual messages back together. The aggregatorTag was set in the MessageRouter.deliverAsync() method. MessageRouter is deprecated and the current ServiceInvoker class nor any other class provides this functionality. -- 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, 7 months

6
14
0 / 0

[JBoss JIRA] Created: (JBESB-1201) Aggregator's timeout doesn't work properly

by Jaroslaw Kijanowski (JIRA)

Aggregator's timeout doesn't work properly ------------------------------------------ Key: JBESB-1201 URL: http://jira.jboss.com/jira/browse/JBESB-1201 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 Attachments: aggregator.tar I've modified the aggregator QS: set the aggregator's timeout to 6 seconds and delayed the delivery of messages to the aggregator for 65 seconds (see attached QS). All messages didn't expire: [java] 14:01:31,406 DEBUG [pool-1-thread-1][Aggregator] Current time=2:01:31 PM message expiration=2:01:31 PM [java] 14:01:31,407 DEBUG [pool-1-thread-1][Aggregator] message is alive. You can find the whole aggreator log in listener.log inside the QS. -- 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, 7 months

5
21
0 / 0

[JBoss JIRA] Created: (JBESB-1004) Quickstarts that don't require JMS dest deployment should warn if user tries "ant deploy-jms-dests"

by Tom Fennelly (JIRA)

Quickstarts that don't require JMS dest deployment should warn if user tries "ant deploy-jms-dests" --------------------------------------------------------------------------------------------------- Key: JBESB-1004 URL: http://jira.jboss.com/jira/browse/JBESB-1004 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 Could simply check for the availability of the destination deployment files and <echo> a "not relevant for this quickstart" message if there are none. -- 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, 7 months

3
14
0 / 0

[JBoss JIRA] Created: (JBESB-1226) spring_helloworld QS throws exceptions duriing runtest

by Tom Cunningham (JIRA)

spring_helloworld QS throws exceptions duriing runtest ------------------------------------------------------ Key: JBESB-1226 URL: http://jira.jboss.com/jira/browse/JBESB-1226 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 10:50:42,244 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 10:50:43,773 ERROR [STDERR] [Fatal Error] :1:1: Content is not allowed in prolog. 10:50:43,774 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/B/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-20500 RelatesTo: jms:correlationID#ID:JBM-25600 ] org.drools.RuntimeDroolsException: javax.xml.xpath.XPathExpressionException at org.drools.rule.EvalCondition.isAllowed(EvalCondition.java:76) at org.drools.reteoo.EvalConditionNode.assertTuple(EvalConditionNode.java:145) at org.drools.reteoo.CompositeTupleSinkAdapter.createAndPropagateAssertTuple(CompositeTupleSinkAdapter.java:73) at org.drools.reteoo.LeftInputAdapterNode.assertObject(LeftInputAdapterNode.java:116) at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:22) at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:140) at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:22) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153) at org.drools.reteoo.Rete.assertObject(Rete.java:177) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201) at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659) at org.jboss.internal.soa.esb.services.routing.cbr.JBossRulesRouter.route(JBossRulesRouter.java:172) at org.jboss.soa.esb.actions.ContentBasedWiretap.routeMessage(ContentBasedWiretap.java:135) at org.jboss.soa.esb.actions.ContentBasedWiretap.process(ContentBasedWiretap.java:101) at org.jboss.soa.esb.actions.ContentBasedRouter.process(ContentBasedRouter.java:52) 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) Caused by: javax.xml.xpath.XPathExpressionException at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473) at org.jboss.internal.soa.esb.services.routing.cbr.DslHelper.xmlContentGreaterThan(DslHelper.java:125) at com.jboss.soa.esb.routing.cbr.Rule_Routing_Rule_using_XPATH_0.eval0(Rule_Routing_Rule_using_XPATH_0.java:9) at com.jboss.soa.esb.routing.cbr.Rule_Routing_Rule_using_XPATH_0Eval0Invoker.evaluate(Rule_Routing_Rule_using_XPATH_0Eval0Invoker.java:16) at org.drools.rule.EvalCondition.isAllowed(EvalCondition.java:72) ... 22 more Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468) ... 26 more 10:50:43,775 WARN [ActionProcessingPipeline] No fault address defined for fault message! header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/B/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-20500 RelatesTo: jms:correlationID#ID:JBM-25600 ] -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1125) Possible bug in Notifier processing

by Richard Achmatowicz (JIRA)

Possible bug in Notifier processing ------------------------------------ Key: JBESB-1125 URL: http://jira.jboss.com/jira/browse/JBESB-1125 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 IR1 Reporter: Richard Achmatowicz Assigned To: Kevin Conner Priority: Minor Don't know if this is intended or unintended - but the name of the property used to enclose NotificationList elements in the <action> target is not validated. For example, this list of notifications works perfectly well: <action name="notificationTest" class="org.jboss.soa.esb.actions.Notifier"> <property name="okMethod" value="notifyOK" /> <property name="THIS-NAME-IS-NOT-VALIDATED"> <NotificationList type="OK">  <target class="NotifyConsole" /> </NotificationList> </property> </action> This raises the question of how to document the property name in the documentation. The name "notification-details" is being used in quickstarts, but that string does not exist in the codebase. -- 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, 7 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 October 2007