-
1. Re: problem in Static routing
vishal12345 Sep 16, 2008 10:21 PM (in response to vishal12345)srry the contenst of the file where not posted properly here are they
"
<jms-listener name="JMS-Gateway"
busidref="TSQueue"
maxThreads="1"
is-gateway="true"
/>
<!-- <jms-listener name="helloWorld"
busidref="quickstartEsbChannel"
maxThreads="1"
/> -->
<jms-listener name="TS-ESB"
busidref="TSEsb"
maxThreads="1"
/>
"
and static routing portion
"
<route-to destination-name="RoutingService"
service-category="TSListener"
service-name="TsListener"/>
" -
2. Re: problem in Static routing
vishal12345 Sep 16, 2008 10:22 PM (in response to vishal12345)
<jms-listener name="JMS-Gateway"
busidref="TSQueue"
maxThreads="1"
is-gateway="true"
/>
<!-- <jms-listener name="helloWorld"
busidref="quickstartEsbChannel"
maxThreads="1"
/> -->
<jms-listener name="TS-ESB"
busidref="TSEsb"
maxThreads="1"
/>
<route-to destination-name="TM" service-category="TMService" service-name="TmListener" />
<route-to destination-name="CM" service-category="CMService" service-name="CmListener" /> -
3. Re: problem in Static routing
vishal12345 Sep 16, 2008 10:23 PM (in response to vishal12345)sorry i m unable to post the contents of the esb configuration file i dont know but some portion doesnt apper here
-
4. Re: problem in Static routing
beve Sep 17, 2008 1:38 AM (in response to vishal12345)Hi,
hard to say what is happening here with out seeing the config. Have you looked at the static_router quickstart?
This is what the static router configuration looks like:<actions mep="OneWay"> <action name="routeAction" class="org.jboss.soa.esb.actions.StaticRouter"> <property name="destinations"> <route-to service-category="category01" service-name="service01" /> <route-to service-category="category02" service-name="service02" /> <route-to service-category="category03" service-name="service03" /> </property> </action> </actions>
When you post configuration or code snippet are you enclosing them with the Code tag. See the menu bar at the top of the Message body area.
Regards,
/Daniel -
5. Re: problem in Static routing
vishal12345 Sep 17, 2008 10:14 AM (in response to vishal12345)here is the complete configuration file
<?xml version = "1.0" encoding = "UTF-8"?> <jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd" parameterReloadSecs="5"> <providers> <jms-provider name="JBossMQ" connection-factory="ConnectionFactory" jndi-URL="jnp://127.0.0.1:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces"> <jms-bus busid="quickstartGwChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/nt_gw" /> </jms-bus> <jms-bus busid="quickstartEsbChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/nt_esb" /> </jms-bus> <jms-bus busid="TSQueue"> <jms-message-filter dest-type="QUEUE" dest-name="queue/nt_ts" /> </jms-bus> <jms-bus busid="TSEsb"> <jms-message-filter dest-type="QUEUE" dest-name="queue/nt_tsesb" /> </jms-bus> <jms-bus busid="TManager"> <jms-message-filter dest-type="QUEUE" dest-name="queue/nt_tmanager" /> </jms-bus> <jms-bus busid="CManager"> <jms-message-filter dest-type="QUEUE" dest-name="queue/nt_cmanager" /> </jms-bus> </jms-provider> </providers> <services> <service category="FirstEclipseServiceESB" name="SimpleListener" description="Hello World"> <listeners> <jms-listener name="JMS-Gateway" busidref="quickstartGwChannel" maxThreads="1" is-gateway="true" /> <jms-listener name="helloWorld" busidref="quickstartEsbChannel" maxThreads="1" /> </listeners> <actions> <action name="action1" class="com.nativetung.soa.esb.actions.MessageParserAction" process="processMessage" /> </actions> </service> <service category="TSService" name="TsListener" description="Translation Server"> <listeners> <jms-listener name="JMS-Gateway" busidref="TSQueue" maxThreads="1" is-gateway="true" /> <!-- <jms-listener name="helloWorld" busidref="quickstartEsbChannel" maxThreads="1" /> --> <jms-listener name="TS-ESB" busidref="TSEsb" maxThreads="1" /> </listeners> <actions mep="OneWay"> <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter"> <property name="ruleSet" value="FunCBRRules-XPath.drl"/> <property name="ruleLanguage" value="XPathLanguage.dsl"/> <property name="ruleReload" value="true"/> <property name="destinations"> <route-to destination-name="TM" service-category="TMService" service-name="TmListener" /> <route-to destination-name="CM" service-category="CMService" service-name="CmListener" /> </property> </action> </actions> </service> <!-- Translation manager service --> <service category="TMService" name="TmListener" description="Translation Manager"> <listeners> <jms-listener name="TManagerListener" busidref="TManager" maxThreads="1" /> </listeners> <actions mep="OneWay"> <action name="Translate Action" class="com.nativetung.soa.esb.actions.TMAction" process="processMessage" /> <action name="transformtopojo" class="org.jboss.soa.esb.actions.converters.SmooksTransformer" > <property name="resource-config" value="/smooks-res.xml" /> <property name="java-output-location" value="$default" /> </action> <action name="convertPOJO2Message" class="com.nativetung.soa.esb.actions.TMPojoToMessage" /> <action name="routeToCBRService" class="org.jboss.soa.esb.actions.StaticRouter"> <property name="destinations"> <route-to destination-name="RoutingService" service-category="TSListener" service-name="TsListener"/> </property> </action> </actions> </service> <!-- Capitalization manager service --> <service category="CMService" name="CmListener" description="Capitalization Manager"> <listeners> <jms-listener name="CManagerListener" busidref="CManager" maxThreads="1" /> </listeners> <actions> <action name="Capatalization Action" class="com.nativetung.soa.esb.actions.CMAction" process="processMessage" /> </actions> </service> </services> </jbossesb>
-
6. Re: problem in Static routing
vishal12345 Sep 17, 2008 10:15 AM (in response to vishal12345)see there is only one static router that i m trying to configure service name is TsListener
-
7. Re: problem in Static routing
beve Sep 17, 2008 10:25 AM (in response to vishal12345)I can't see that you have a service category named 'TSListener'
<route-to destination-name="RoutingService" service-category="TSListener" service-name="TsListener"/>
Did you mean do write 'TSService'? -
8. Re: problem in Static routing
vishal12345 Sep 17, 2008 10:29 AM (in response to vishal12345)hi sorry i made that mistake i also came to know i made the change and now i got this exception
19:55:01,453 WARN [ServiceInvoker] Courier indicated (un)marshal related error org.jboss.soa.esb.couriers.CourierMarshalUnmarshalException: Failed to serialize ESB Message. during delivery to EPR [JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/nt_tsesb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] for Service [TSService:TsListener] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/nt_tsesb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ba81b56c-882b-44fa-936b-d89fb954e7a1 RelatesTo: jms:correlationID#ba81b56c-882b-44fa-936b-d89fb954e7a1 ]]. Failed to serialize ESB Message. 19:55:01,453 INFO [ServiceInvoker] Delivering message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/nt_tmanager/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ba81b56c-882b-44fa-936b-d89fb954e7a1 RelatesTo: jms:correlationID#ba81b56c-882b-44fa-936b-d89fb954e7a1 ]] to RDLVRQ. 19:55:01,453 WARN [ServiceInvoker] Courier indicated (un)marshal related error org.jboss.soa.esb.couriers.CourierMarshalUnmarshalException: Failed to serialize ESB Message. during delivery to EPR [JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] for Service [JBossESB-Internal:DeadLetterService] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ba81b56c-882b-44fa-936b-d89fb954e7a1 RelatesTo: jms:correlationID#ba81b56c-882b-44fa-936b-d89fb954e7a1 ]]. Failed to serialize ESB Message. 19:55:01,468 ERROR [MessageMulticaster] Failed to deliver message to Service 'TSService:TsListener'. Delivering message to Dead Letter Channel. 19:55:01,468 WARN [ServiceInvoker] Courier indicated (un)marshal related error org.jboss.soa.esb.couriers.CourierMarshalUnmarshalException: Failed to serialize ESB Message. during delivery to EPR [JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] for Service [JBossESB-Internal:DeadLetterService] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ba81b56c-882b-44fa-936b-d89fb954e7a1 RelatesTo: jms:correlationID#ba81b56c-882b-44fa-936b-d89fb954e7a1 ]]. Failed to serialize ESB Message. 19:55:01,468 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/nt_tmanager/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ba81b56c-882b-44fa-936b-d89fb954e7a1 RelatesTo: jms:correlationID#ba81b56c-882b-44fa-936b-d89fb954e7a1 ] org.jboss.soa.esb.actions.ActionProcessingException: org.jboss.soa.esb.listeners.message.MessageDeliverException: Caught (un)marshal related exception during attempted send/receive. at org.jboss.soa.esb.actions.StaticWiretap.process(StaticWiretap.java:63) at org.jboss.soa.esb.actions.StaticRouter.process(StaticRouter.java:48) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.jboss.soa.esb.listeners.message.MessageDeliverException: Caught (un)marshal related exception during attempted send/receive. at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:548) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:447) at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:316) at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:225) at org.jboss.soa.esb.client.ServiceInvoker.deliverToDeadLetterService(ServiceInvoker.java:267) at org.jboss.soa.esb.client.MessageMulticaster.sendToSubset(MessageMulticaster.java:147) at org.jboss.soa.esb.client.MessageMulticaster.sendToAll(MessageMulticaster.java:106) at org.jboss.soa.esb.actions.StaticWiretap.process(StaticWiretap.java:58) ... 6 more Caused by: org.jboss.soa.esb.couriers.CourierMarshalUnmarshalException: Failed to serialize ESB Message. at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:201) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:199) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:525) ... 13 more Caused by: java.io.IOException: Util.serialize caught XMLStreamException: at org.jboss.soa.esb.util.Util.serialize(Util.java:194) at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:195) ... 15 more
-
9. Re: problem in Static routing
beve Sep 17, 2008 11:28 AM (in response to vishal12345)Note sure what is wrong here but please check that the message content consists of serializable objects.
<action name="convertPOJO2Message" class="com.nativetung.soa.esb.actions.TMPojoToMessage" />
Is the pojo referenced here added to the message body? Is it serializable?