Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

WAS AEs 4.0: Invalid column number when running DB2SPSample (SOAP sample)

36 views

Skip to first unread message

Kathy Zhang

unread,

Jul 23, 2001, 12:07:29 PM7/23/01

I followed the instruction in the InfoCenter and also had the DB2 Stored
Procedure sample set up. When I tried to run DB2SPSample, I got the invalid
column number exception. The detail is shown below. Is it caused by the
version of DB2 or what else? Thanks in advance.

Kathy

Environment:
DB2 UDB Personal Develper Edition v7.1
Window 2000 server
WAS 4.0 AEs

Invoking the ALL_DATA_TYPES stored procedure

Ouch, the call failed:
Fault Code = SOAP-ENV:Server
Fault String = WASDB2SPProvider: [IBM][JDBC Driver] CLI0610E Invalid co
lumn number. SQLSTATE=S1002
STACK TRACE:
COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0610E Invalid column
number. SQLSTATE=S1002
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throwColumnIndexErro
r(SQLExceptionGenerator.java:543)
at COM.ibm.db2.jdbc.app.DB2ResultSet.getString(DB2ResultSet.java:4
86)
at com.ibm.ejs.cm.proxy.ResultSetProxy.getString(ResultSetProxy.ja
va:539)
at com.ibm.soap.providers.impl.WASDB2SPProviderImpl.invoke(WASDB2S
PProviderImpl.java:353)
at org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterSe
rvlet.java:286)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(S
ervletManager.java:718)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(S
trictLifecycleServlet.java:160)
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLi
fecycleServlet.java:287)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(St
rictLifecycleServlet.java:105)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletMa
nager.java:428)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispat
ch(ServletManager.java:870)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch
(ServletManager.java:788)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWeb
AppDispatch(WebAppRequestDispatcher.java:439)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(
WebAppRequestDispatcher.java:239)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(W
ebAppRequestDispatcher.java:104)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoke
r.java:61)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(W
ebAppInvoker.java:132)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvoca
tion(CachedInvocation.java:67)
at com.ibm.servlet.engine.invocation.CacheableInvocationContext.in
voke(CacheableInvocationContext.java:106)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByUR
I(ServletRequestProcessor.java:125)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.servic
e(OSEListener.java:271)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(Http
Connection.java:49)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnect
ion.java:303)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:232)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)

Invoking the ONE_RESULT_SET stored procedure

Done

0 new messages