Re: Re: Using JDBC Connection Pooling via Websphere JDBC Provider using a DataSournce Name
Hi,
can you share your solution with me, i'm getting the same problem.
Thanx.
Quote:
Originally posted by anthony
Please ignore this message. There was a WebShpere setting I didn't know
I had to set.
Thanks.
anthony wrote:
> *I am trying to conncect to a SQL Server 2000 DB via a Websphere JDBC
> Provider. SQL Server 2000 and Websphere are on different machines.
> I performed the following steps:
>
> 1. Installed the SQL Server 2000 Driver for JDBC on the server where
> Websphere is located.
> 2. Installed the Stored Procedures for JTA on the machine where SQL
> Server 2000 is installed.
> 3. Created a JDBC Provider using the SQL Server 2000 Driver for JDBC:
> com.microsoft.jdbcx.sqlserver.SQLServerDataSource
> 4.Tried connecting to the DB via the DataSource Name.
> 5. Received the following error on the first try:
>
> CONM7007I: Mapping the following SQLException, with ErrorCode 0 and
> SQLState 08S01, to a StaleConnectionException: java.sql.SQLException:
> [Microsoft][SQLServer 2000 Driver for JDBC]There is no process to
> read data written to a pipe.
> at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.sub mitRequest(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest. openCursor(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.execute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeQuery Internal(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.executeQuery (Unknown
> Source)
> at
> com.microsoft.jdbcx.base.BaseStatementWrapper.exec uteQuery(Unknown
> Source)
> at
> com.ibm.ejs.cm.proxy.StatementProxy.executeQueryCo mmon(StatementProxy.java:306)
> at
> com.ibm.ejs.cm.proxy.StatementProxy.executeQuery(S tatementProxy.java:271)
> at
> mckhboc.utils._sqlcommand_jsp_2._jspService(_sqlco mmand_jsp_2.java:267)
> at
> org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:142)
> at javax.servlet.http.HttpServlet.service(HttpServlet .java:853)
> at
> org.apache.jasper.runtime.JspServlet$JspServletWra pper.service(JspServlet.java:323)
> at
> org.apache.jasper.runtime.JspServlet.serviceJspFil e(JspServlet.java:503)
> at
> org.apache.jasper.runtime.JspServlet.service(JspSe rvlet.java:636)
> at javax.servlet.http.HttpServlet.service(HttpServlet .java:853)
> at
> com.ibm.servlet.engine.webapp.StrictServletInstanc e.doService(ServletManager.java:827)
> at
> com.ibm.servlet.engine.webapp.StrictLifecycleServl et._service(StrictLifecycleServlet.java:167)
> at
> com.ibm.servlet.engine.webapp.IdleServletState.ser vice(StrictLifecycleServlet.java:297)
> at
> com.ibm.servlet.engine.webapp.StrictLifecycleServl et.service(StrictLifecycleServlet.java:110)
> at
> com.ibm.servlet.engine.webapp.ServletInstance.serv ice(ServletManager.java:472)
> at
> com.ibm.servlet.engine.webapp.ValidServletReferenc eState.dispatch(ServletManager.java:1012)
> at
> com.ibm.servlet.engine.webapp.ServletInstanceRefer ence.dispatch(ServletManager.java:913)
> at
> com.ibm.servlet.engine.webapp.WebAppRequestDispatc her.handleWebAppDispatch(WebAppRequestDispatcher.j ava:721)
> at
> com.ibm.servlet.engine.webapp.WebAppRequestDispatc her.dispatch(WebAppRequestDispatcher.java:374)
> at
> com.ibm.servlet.engine.webapp.WebAppRequestDispatc her.forward(WebAppRequestDispatcher.java:118)
> at
> com.ibm.servlet.engine.srt.WebAppInvoker.doForward (WebAppInvoker.java:134)
> at
> com.ibm.servlet.engine.srt.WebAppInvoker.handleInv ocationHook(WebAppInvoker.java:239)
> at
> com.ibm.servlet.engine.invocation.CachedInvocation .handleInvocation(CachedInvocation.java:67)
> at
> com.ibm.servlet.engine.invocation.CacheableInvocat ionContext.invoke(CacheableInvocationContext.java: 106)
> at
> com.ibm.servlet.engine.srp.ServletRequestProcessor .dispatchByURI(ServletRequestProcessor.java:154)
> at
> com.ibm.servlet.engine.oselistener.OSEListenerDisp atcher.service(OSEListener.java:315)
> at
> com.ibm.servlet.engine.http11.HttpConnection.handl eRequest(HttpConnection.java:60)
> at
> com.ibm.ws.http.HttpConnection.readAndHandleReques t(HttpConnection.java(Compiled
> Code))
> at com.ibm.ws.http.HttpConnection.run(HttpConnection. java(Compiled
> Code))
> at com.ibm.ws.util.CachedThread.run(ThreadPool.java:1 38)
>
> 6. Tried connecting again and recveived this error:
>
> Servlet Error: Outstanding work on this connection which was not
> comitted or rolledback by the user has been rolledback.:
> com.ibm.ejs.cm.exception.WorkRolledbackException: Outstanding work on
> this connection which was not comitted or rolledback by the user has
> been rolledback.
> at com.ibm.ejs.cm.pool.ConnectO.decRef(ConnectO.java: 366)
> at
> com.ibm.ejs.cm.pool.ConnectionPool.freeConnection( ConnectionPool.java:166)
> at
> com.ibm.ejs.cm.proxy.ConnectionProxy.close(Connect ionProxy.java:821)
> at
> mckhboc.utils._sqlcommand_jsp_2._jspService(_sqlco mmand_jsp_2.java:453)
> at
> org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:142)
> at javax.servlet.http.HttpServlet.service(HttpServlet .java:853)
> at
> org.apache.jasper.runtime.JspServlet$JspServletWra pper.service(JspServlet.java:323)
> at
> org.apache.jasper.runtime.JspServlet.serviceJspFil e(JspServlet.java:503)
> at
> org.apache.jasper.runtime.JspServlet.service(JspSe rvlet.java:636)
> at javax.servlet.http.HttpServlet.service(HttpServlet .java:853)
> at
> com.ibm.servlet.engine.webapp.StrictServletInstanc e.doService(ServletManager.java:827)
> at
> com.ibm.servlet.engine.webapp.StrictLifecycleServl et._service(StrictLifecycleServlet.java:167)
> at
> com.ibm.servlet.engine.webapp.IdleServletState.ser vice(StrictLifecycleServlet.java:297)
> at
> com.ibm.servlet.engine.webapp.StrictLifecycleServl et.service(StrictLifecycleServlet.java:110)
> at
> com.ibm.servlet.engine.webapp.ServletInstance.serv ice(ServletManager.java:472)
> at
> com.ibm.servlet.engine.webapp.ValidServletReferenc eState.dispatch(ServletManager.java:1012)
> at
> com.ibm.servlet.engine.webapp.ServletInstanceRefer ence.dispatch(ServletManager.java:913)
> at
> com.ibm.servlet.engine.webapp.WebAppRequestDispatc her.handleWebAppDispatch(WebAppRequestDispatcher.j ava:721)
> at
> com.ibm.servlet.engine.webapp.WebAppRequestDispatc her.dispatch(WebAppRequestDispatcher.java:374)
> at
> com.ibm.servlet.engine.webapp.WebAppRequestDispatc her.forward(WebAppRequestDispatcher.java:118)
> at
> com.ibm.servlet.engine.srt.WebAppInvoker.doForward (WebAppInvoker.java:134)
> at
> com.ibm.servlet.engine.srt.WebAppInvoker.handleInv ocationHook(WebAppInvoker.java:239)
> at
> com.ibm.servlet.engine.invocation.CachedInvocation .handleInvocation(CachedInvocation.java:67)
> at
> com.ibm.servlet.engine.invocation.CacheableInvocat ionContext.invoke(CacheableInvocationContext.java: 106)
> at
> com.ibm.servlet.engine.srp.ServletRequestProcessor .dispatchByURI(ServletRequestProcessor.java:154)
> at
> com.ibm.servlet.engine.oselistener.OSEListenerDisp atcher.service(OSEListener.java:315)
> at
> com.ibm.servlet.engine.http11.HttpConnection.handl eRequest(HttpConnection.java:60)
> at
> com.ibm.ws.http.HttpConnection.readAndHandleReques t(HttpConnection.java(Compiled
> Code))
> at com.ibm.ws.http.HttpConnection.run(HttpConnection. java(Compiled
> Code))
> at com.ibm.ws.util.CachedThread.run(ThreadPool.java:1 38)
>
> Any thoughts to why I am getting the above two exceptions?
>
> Thanks for your help
> Anthony *
--
anthony
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message240982.html
|
Cell Phones reviews
05-30-04, 05:36 PM
Linear Mode
