Exception In Weblogic Server Log When A Work Order is Executed With Runjmsclient Script

(Doc ID 755912.1)

Last updated on AUGUST 28, 2017

Applies to:

Oracle Communications ASAP - Version 4.7.1 to 5.2.4 [Release 4.7 to 5.2]
Oracle WebLogic Server - Version 11.1.1.7.0 to 11.1.1.7.0 [Release 11g]
Information in this document applies to any platform.
***Checked for relevance on 22-OCT-2012***



Symptoms


The following exception was displayed in the weblogic server log when a WorkOrder is executed with the runJMSClient script in ASAP. (The Workorder is fired successfully)

<Nov 24, 2008 9:28:19 AM BRST> <Error> <JDBC> <BEA-001112> <Test "ping"
set up for pool
"System.AS52.ApplicationType.ServiceActivation.Application.1-0;5-2;ASAP.Comp.RPC
ConnectionPool" failed with exception: "java.sql.SQLException: JZ0S2: Statement
object has already been closed.".>

refresh xa conn with {url=jdbc:sybase:Tds:osm-des:40170, serverName=osm-des,
dataSourceName=System.AS52.ApplicationType.ServiceActivation.Application.1-0;5-2
;ASAP.Comp.RPCConnectionPool, user=sarmAS52, networkProto =Tds,
DISABLE_UNPROCESSED_PARAM_WARNINGS=true, databaseName=SARMAS52,
password=sarmAS52, portNumber=40170, USE_METADATA=false,
IS_CLOSED_TEST=ping}



Steps To Reproduce:
Send a Work Order through the JSRP interface and monitor the BEA WLS server logs.


Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms