Basis Errors and Solutions

WS adapter: Incorr. error handling w/ incorr. configuration

July 10, 2009 at 5:50 am

[error handling] [handling] [handling charge] [handling fee]

1. Improved error handling in the memory pipe layerSymptom If you call the command cleanipc while the system is running, this may lead to the following, endlessly repetitive error messages: dev_icm Tracelevel 1 *** ERROR => e=43 semop(17793029,(18,0,0),(18,1,0),2) (43: Identifier...
2. Improved error handling in the memory pipe layerSymptom If you call the command cleanipc while the system is running, this may lead to the following, endlessly repetitive error messages: dev_icm Tracelevel 1 *** ERROR => e=43 semop(17793029,(18,0,0),(18,1,0),2) (43: Identifier...
3. Wrong error handling in the addressSymptom Process messages in the address persist longer on the UI than they should. Other terms BAS_AP Reason and Prerequisites Code error Solution Apply the attached correction isntructions. ...

Symptom

Due to an error in the Web service configuration, an exception in the Web service runtime may not be interpreted as an error in message processing: The message is flagged as “Successfully processed”, even though an error occurred.

Reason and Prerequisites

The incorrect configuration leads to an inconsistency in the Web service adapter. This is not recognized.
Solution

Implement the correction instructions or import the
Support Package specified below. As a result, the inconsistency is recognized and is displayed as an error when it occurs again.

Permalink