The exception is raised when there is a loss of connection between the two applications. (the exception does not always come)

The only way that I know to avoid this exception is to bounce (a cleaned one will be better : shutdown and start the BC) your BC after the return of SAP.

But if there was no connection problems, could you give us more information about the your environment (SAP vers, …) , event that raised the exception…

Kind Regards,

Simon G.

hi simon,

thanks for the info!

sap version used is 4.6

below r the details of my BC environment:

Server Environment
Java Version 1.3.1_15 (47.0)
Java Vendor Sun Microsystems Inc.
Java Home E:\program files\JavaSoft\JRE\1.3.1_15
Java VM Version 1.3.1_15-b01
Java VM Info Java HotSpot™ Client VM (mixed mode)
Classpath E:\sapbc47\Server\updates\BC47_CoreFix5.jar
E:\sapbc47\Server\lib\classes
E:\sapbc47\Server\lib\client.jar
E:\sapbc47\Server\lib\mail.jar
E:\sapbc47\Server\lib\server.jar
E:\sapbc47\Server\lib\jars\sapdbc.jar
packages\SAP\code\jars\static\inqmyxml.jar
packages\SAP\code\jars\static\jARM.jar
packages\SAP\code\jars\static\sapidoc.jar
packages\SAP\code\jars\static\sapidocjco.jar
packages\SAP\code\jars\static\sapjco.jar
packages\SAP\code\jars\static\sapxmltoolkit.jar
packages\SAP\code\classes
packages\SAPMonitoring\code\jars\static\jmonapi.jar
packages\SAPMonitoring\code\jars\static\logging.jar
packages\SAPMonitoring\code\jars\static\monitordriver.jar
packages\SAPMonitoring\code\classes
packages\WmPartners\code\classes
packages\WmWin32\code\classes

OS Windows 2000
OS Platform x86
OS Version 5.0
Current User SYSTEM
Working Dir E:\sapbc47\Server

let me know wat can be done to resolve this error though we dont get this exception frequently.