November 2007 - esb-issues - Jboss List Archives

[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

18 years, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-1330) Aggregator doesn't fail gracefully on invalid/missing required properties

by Tom Fennelly (JIRA)

Aggregator doesn't fail gracefully on invalid/missing required properties ------------------------------------------------------------------------- Key: JBESB-1330 URL: http://jira.jboss.com/jira/browse/JBESB-1330 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1, 4.2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Doesn't perform any checks on the timeout, service-cat and service-name properties. As far as the service-cat and service-name are concerned, this just means that the timeout-checker bombs out immediately, if they're not specified. For backward compatibility, I think I'll just bomb out more gracefully on this and log a big warning to fix the 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

18 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1331) MessageMulticaster not adding aggregation details properly

by Tom Fennelly (JIRA)

MessageMulticaster not adding aggregation details properly ---------------------------------------------------------- Key: JBESB-1331 URL: http://jira.jboss.com/jira/browse/JBESB-1331 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP1 The multicaster sends a single message to 1+ recipients. As it loops over the recipient list delivering the message, it attaches aggregation info for the message for that recipient. At the end of each loop is should remove the aggregation info for the last recipient, but it's not. -- 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, 5 months

1
2
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

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

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

18 years, 5 months

5
21
0 / 0

[JBoss JIRA] Created: (JBESB-1355) Extend quickstart embedded notion to include running in production deployments

by Kevin Conner (JIRA)

Extend quickstart embedded notion to include running in production deployments ------------------------------------------------------------------------------ Key: JBESB-1355 URL: http://jira.jboss.com/jira/browse/JBESB-1355 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner 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

18 years, 5 months

1
1
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

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

18 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1299) QS custom_action fails when sending ESB message

by Jaroslaw Kijanowski (JIRA)

QS custom_action fails when sending ESB message ----------------------------------------------- Key: JBESB-1299 URL: http://jira.jboss.com/jira/browse/JBESB-1299 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Jaroslaw Kijanowski When running the sendesb ant task I get folowing Exception: sendesb: [echo] Runs Test ESB Message Sender [java] Inbound Data: NO Gateway [java] Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message [header: [ To: JMSEpr [ PortReference < . . . <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]] to Service [ActionServices:CustomActionService]. Check for errors. [java] at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:279) [java] at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:155) [java] at org.jboss.soa.esb.samples.quickstart.customaction.test.SendEsbMessage.main(SendEsbMessage.java:60) -- 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, 5 months

4
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2007