Now i realize that I havent mentioned that these messages are getting processed correctly when they are restarted. Sorry for that!So I dont think it has to do with the XML.Today morning an inbound message in another queue failed with almost the same error. Only difference was that the “-1” was not present. Last row ended with “null” like below:Caused by: java.lang.ArrayIndexOutOfBoundsException: null
Thanks for your reply!This is an outbound message sent to third party. We use FILE as Transport Connector and the default file sender is used.Its very strange if the XML is not the same for every message. But I will compare when we get the error next time.Any other suggestions?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.