XSQL Throwing Null Pointer In OTM 5.5 (Doc ID 749257.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 5.5.04.01
This problem can occur on any platform.

Symptoms

When running a XSQL statement using the URL, a null pointer error similar to the one below is thrown:

Oracle XML Developers Kit 10.1.3.0.0 - Production
XSQL-017: Unexpected Error Occurred
java.lang.NullPointerException
at oracle.xml.xsql.XSQLDocHandler.valueOfConnectionAttr(XSQLDocHandler.java:493)
at oracle.xml.xsql.XSQLDocHandler.(XSQLDocHandler.java:84)
at oracle.xml.xsql.XSQLPageProcessor.process(XSQLPageProcessor.java:109)
at oracle.xml.xsql.XSQLServlet.doGet(XSQLServlet.java:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run()V(Unknown Source)

An XSQL similar to this was used:

=========================================
<?xml version="1.0"?>
<xsql:query connection="TMSTEST" xmlns:xsql="urn:oracle-xsql">
SELECT
SH.SHIPMENT_XID,SH.SERVPROV_GID
FROM
SHIPMENT SH
WHERE
SH.SHIPMENT_XID = '{@SH}'
AND SH.SHIPMENT_GID LIKE 'SLBNSG.%'
AND SH.DOMAIN_NAME='SLBNSG'
</xsql:query>
========================================

If the properties file file is checked, the glog.database.sid looks correct.

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