We have been facing some “intermittent” issue in putting the messages to a queue via the above adapter, and the rejection code that stated in the server log file is “completion code 2 reason 2009”.
Does anyone have any experience on how to resolve this issue?
Appreciate any feedback. Thanx
This error is generic and does not tell much…
Have you checked the standard output of the java virtual machine? Maybe a more detailed stack stack trace would appear there.
Otherwise which version of Is, MQ client jars are you using? And against which version of MQ server?
Also, this error happened in our production server one week before. So I cannot able to get the stack trace from the IS error log now. Do u know if there are any other method for extracting the stack trace?
Either you are still having the issue, in which case you can check the standard output of the JVM, or you don’t and you won’t get any stack because no error occur
Not sure I understand what you mean. You could also enable DEBUG level for following IS components :
As I said before, the error occured in production server and we need to get down time to work on the same for replicating the issue.
But, we are unable to replicate the same in our local server. The same message is processing fine in the local server. webMethods, MQ jars, code everything is same b/w local and prod environment. Therefore not sure why this error is occuring…The same message we tried to processs three times in production server and it failed all the times…