Have any of you seen this error before? This is not the case with all of our responses. It happens at random. This occurs when a Java client creates a random topic in a session and waits for response on a Topic. This is more or less following the Chat example available in the samples directory.
Thanks,
--Subbu
javax.naming.NameNotFoundException: Failed to find com.XXXXXXXXXXXXXXX in context endpoint - There is no element /xqEndpoints/com.XXXXXXXXXXXXXXX in the Directory Service
Subbu,
not sure what your exact use case is but an esb service cannot use arbitrary jms destinations. You have to configure an esb endpoint that maps to the desired jms dest.
The only exception (up to Sonic7.6) is ReplyTo, which replies to whatever you have in your JMS ReplyTo header.
Thomas
Thanks Thomas.
This happens only when I set the ReplyTo in the JMS header.. The ReplyTo topic is set by my clients which is not being found by the ESB. This happens at random, not in a specific pattern either.
--Subbu
Ok, the replyto esb destination as such is also temporary. In particular of the sender is using a temporary destination. In that case the sender might have gone away and you will not be able to send.
Do you happen to have a full stack trace?
Thomas