We have mediation module is responsible for:
Receiving the Request XML message from SCA destination.
Perform validations of the input request
Persist the input message to a JMS queue
We have another mediation module is responsible for:
Receiving the XML message from persistent JMS queue
Invoke the EIS-FTP import component (FTP adapter) and places the file in dealer specific input folder of DMSI FTP server.
We have noticed that second mediation module not process the XML message from persistent JMS queue that had failed earlier which has unlocked state.
Mediation module process the XML message from persistent JMS queue that had failed earlier which has locked. Why mediation modules not process the unlocked state messages? Please find attached Unlocked state.doc
How we can fix this problem? Can you please help?
This topic has been locked.
2 replies Latest Post - 2012-04-23T21:48:44Z by SystemAdmin
Pinned topic Not process the XML message from persistent JMS queue
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-04-23T21:48:44Z at 2012-04-23T21:48:44Z by SystemAdmin
mmalc 10000036A9231 Posts
SystemAdmin 110000D4XK3556 PostsACCEPTED ANSWER
Re: Not process the XML message from persistent JMS queue2012-04-23T21:48:44Z in response to mmalcRegarding the the technote
We have below version.
WebSphere Application Server 188.8.131.52
WebSphere Process Server 184.108.40.206
references APAR iFixes for PK73716 and JR30708...
We do have the APAR fix for PK73716 since it first went into WebSphere
AppServer 220.127.116.11 and you have ND 18.104.22.168 cf311015.02.
The APAR iFix for JR30708 was included in WPS 22.214.171.124 per this link
and we have WBI 126.96.36.199 of1024.07.
So we do have both the iFixes referenced in the suggestion from
technote, so that is not relevant to our situation.