MAPPING errors when using WSA .

Posted by thiago.daniel@dtsconsultoria.com.br on 13-Jan-2014 02:36


Hello friends ,

Good night ,

We have developed a system in progress that communicates with a tomcat 
webservice which in turn talks to the SAP ERP . This side using Progress 
WSA .
We have a routine of talking integration of SAP with the same WSA .
It turns out that due to the size of the structure , eventually our 
technology department to stop these apps servers for maintenance , 
updating software etc. ... routines Spray Technology department.
But here comes the big problem , our SAP continues running , and of 
course it features the integration errors while PROGRESS resource is 
unavailable. Until then normal.

It turns out that when you restart the PROGRESS apps , they remain quiet 
awaiting communication from SAP , but the first transaction that occurs 
arising from integration between SAP and APP Server Progress always , 
without exception fails with errors " MAPPING " .
Checking the world PROGRESS found the following KB dealing with this 
condition :

http://knowledgebase.progress.com/articles/Article/P110855

As the first requisition integration fails , I can end up with major 
pending request processing . From what I understand the KB is as if the 
APP stay hibernating and the first transaction to be used so he could 
wake up. Would that be?
So the gentlemen have any practical solution that can be implemented for 
this App Server to be started was already ready to be used ?

Thank you all .

Thiago .













All Replies

Posted by David Cleary on 14-Jan-2014 10:22

The KB refers to restarting an AppServer with an already running WSA. Restarting both Tomcat and the AppServer would solve that issue. However, I'm confused about the MAPPING error and where that comes from. Are you sure what you are seeing is related to the KB?

This thread is closed