-
1. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
tadayosi Jan 15, 2013 7:28 AM (in response to samawarad)1 of 1 people found this helpfulHello,
The DeadLetterService you've commented out is hard-wired in the mechanism of action pipeline processing in JBoss ESB. When something wrong happens in the ESB's action pipeline and the ESB message becomes undeliverable, the ESB sends it to DeadLetterService unless you've designated the FaultTo address on the message.
That's the reason why you see MissingServiceException even though you don't invoke DeadLetterService explicitly.
Best regards,
Tadayoshi
-
2. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
samawarad Jan 15, 2013 7:52 AM (in response to tadayosi)Hi Sato,
Thanks for your response.
Could you let me know few more details regarding DeadLetterService.
1) Does Performance of the Application will be low if we uncomment DeadLetterService in jboss-esb.xml?
2) Can you please let me know, (When something wrong happens in the ESB's action pipeline and the ESB message becomes undeliverable, the ESB sends it to DeadLetterService unless you've designated the FaultTo address on the message) What wrong might have happened(any examples) in ESB's action pipeline, is it at our application level or at jboss level?
3)What would you suggest?
a) uncommenting the DeadLetterService in jboss-esb.xml?
b) Handling "MissingServiceException" in our application?
-
3. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
tadayosi Jan 15, 2013 8:23 AM (in response to samawarad)1 of 1 people found this helpfulHello,
> 1) Does Performance of the Application will be low if we uncomment DeadLetterService in jboss-esb.xml?
I don't think so. DeadLetterService is invoked only in exceptional cases, so it wouldn't add anything to performance of the application in most cases.
> 2) Can you please let me know, ... What wrong might have happened(any examples) in ESB's action pipeline, is it at our application level or at jboss level?
When an action in the pipeline throws an exception (either checked or runtime).
> 3)What would you suggest?
"a) uncommenting the DeadLetterService in jboss-esb.xml." If you're still concerned about performance, you can comment out actions inside the service's <actions ...> to effectively disable the service.
Best regards,
Tadayoshi
-
4. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
samawarad Jan 16, 2013 5:17 AM (in response to tadayosi)Hi,
Thank you so much
-
5. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
samawarad Jan 21, 2013 1:04 AM (in response to tadayosi)Hi,
When service is invoked, it is taking 5 minutes to send responses back.
Can you please let me know why the delay of 5 minutes might occur?Is there any configuration available to configure this time?
Jboss SOA Platform version : JBoss Enterprise SOA Platform 5.0.2
And also please teach us where and how to set the fault-to address?
Please help us for the above question.
-
6. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
tadayosi Jan 21, 2013 2:02 AM (in response to samawarad)Hello,
Not sure exactly why it takes 5 mins in your application, but the default interval of the redelivery service for ESB's DLQ messages is 5 mins. You can confirm and reconfigure this setting in $PROFILE/deploy/jbossesb.esb/META-INF/jboss-esb.xml.
<providers>
...
<schedule-provider name="schedule">
<simple-schedule scheduleid="5-min-trigger" frequency="300" execCount="-1"/>
</schedule-provider>
</providers>
HTH.
-
7. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
samawarad Jan 22, 2013 5:31 AM (in response to tadayosi)Hi,
Thanks for the reply.
Please let us know how Fault-to address is related with this issue,Does setting Fault-to address may resolve the issue?
-
8. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
tadayosi Jan 22, 2013 8:26 AM (in response to samawarad)Hello,
For how to set the FaultTo address, please refer to:
https://community.jboss.org/message/506312
http://docs.jboss.org/jbossesb/docs/4.11/manuals/html/Programmers_Guide/index.html#d0e443
If you set the FaultTo address to an ESB message and it causes an exception during the pipeline processing, the ESB routes this undeliverable message to the FaultTo address instead of the default DeadLetterService.
-
9. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
tadayosi Jan 22, 2013 8:41 AM (in response to tadayosi)This is also a good reference on how message redelivery works in JBoss ESB:
http://docs.jboss.org/jbossesb/docs/4.11/manuals/html/Programmers_Guide/index.html#d0e1764
-
10. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
samawarad Feb 5, 2013 4:07 AM (in response to tadayosi)Hi,
I am getting the below exception while deploying the service after commenting "invmScope="GLOBAL" in jboss-esb.xml.
org.jboss.soa.esb.ConfigurationException: Service configuration for Service 'service:test' doesn't define a Message-Aware Listener (i.e. is-gateway='false').
Please correct me to resolve this issue.
-
11. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
tadayosi Feb 5, 2013 7:21 AM (in response to samawarad)You need at least one message-aware listener for each ESB service. Setting invmScope="GLOBAL" registers the inVM transport (message-aware listener) to the service implicitly. So if you'd like to comment out invmScope="GLOBAL" you have to define a message-aware listener such as JMS listener explicitly.
-
12. Re: org.jboss.soa.esb.listeners.message.MissingServiceException: Registry details for service
samawarad Feb 7, 2013 3:54 AM (in response to tadayosi)Hi,
I am upgrading Jboss SOA 5.0.1 to Jboss 5.0.3 server. while starting up the server the following error is coming:
2013-02-07 12:46:26,562 WARN [org.jgroups.protocols.pbcast.GMS] (main) join(16.121.237.34:56200) sent to 16.121.234.116:55200 timed out (after 3000 ms), retrying
2013-02-07 12:46:29,564 WARN [org.jgroups.protocols.pbcast.GMS] (main) join(16.121.237.34:56200) sent to 16.121.234.116:55200 timed out (after 3000 ms), retrying
2013-02-07 12:46:32,565 WARN [org.jgroups.protocols.pbcast.GMS] (main) join(16.121.237.34:56200) sent to 16.121.234.116:55200 timed out (after 3000 ms), retrying
I have changed the jgroups ports under "JBOSS_HOME/server/production/deploy/cluster/jgroups-channelfactory.sar/META-INF" in the file "jgroups-channelfactory-stacks.xml".
Server is not coming up.Please guide me.