You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2017/12/08 22:12:08 UTC
[Bug 61880] New: Tomcat server 5: java process crashing
https://bz.apache.org/bugzilla/show_bug.cgi?id=61880
Bug ID: 61880
Summary: Tomcat server 5: java process crashing
Product: Tomcat 7
Version: unspecified
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: saanchi@gmail.com
Target Milestone: ---
Java process crashing multiple time on Tomcat
Problem Summary
---------------------------------------------------
Java process crashing multiple time on Tomcat
Problem Description
---------------------------------------------------
We see below exception being logged when the issue occur and this we suspect
is causing Java process to crash frequently.
OJDBC 5 : Implementation-Version: 11.2.0.1.0
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Tomcat version is 5
2017-12-03 09:49:26,454|ERROR|Log Runner Thread|149766653|
BasicConnectionFactory: Error while destroying a connection
java.sql.SQLException: Protocol violation
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4C7Ocommoncall.doOLOGOFF(T4C7Ocommoncall.java:61)
at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:491)
at oracle.jdbc.driver.PhysicalConnection.close(PhysicalConnection.java:3754)
at
org.apache.commons.dbcp.DelegatingConnection.close(DelegatingConnection.java:151)
at
org.apache.commons.dbcp.PoolableConnection.reallyClose(PoolableConnection.java:95)
at
org.apache.commons.dbcp.PoolableConnectionFactory.destroyObject(PoolableConnectionFactory.java:301)
at
com.capula.connectionPool.BasicConnectionFactory.access$001(BasicConnectionFactory.java:17)
at
com.capula.connectionPool.BasicConnectionFactory$Destroyer.call(BasicConnectionFactory.java:40)
at
com.capula.connectionPool.BasicConnectionFactory$Destroyer.call(BasicConnectionFactory.java:30)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 61880] Tomcat server 5: java process crashing
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61880
San <sa...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #2 from San <sa...@gmail.com> ---
Hi,
Thank you for responding to the bug.
I understand Tomcat 5 is desupported.
We are having an issue in production env where the tomcat server is crashing.
We see below OOM errors,
Would you be able to comment as what area needs investigation?
Is it the jdbc driver which is causing the issue? We have upgrade to jdbc
driver 7 but still haivng below issue. Any comment/guideline much appreciated.
Thanks.
2017-12-01 08:20:38,943|ERROR|TP-Processor1|42286971|
Exception [Java heap space] in action [class
org.apache.struts.action.ActionMapping]
com.capula.eoasis.EoasisException: Java heap space
at
com.capula.eoasis.actions.EoasisDispatchAction.execute(EoasisDispatchAction.java:46)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at sun.reflect.GeneratedMethodAccessor681.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.capula.eoasis.actions.EoasisDispatchAction.execute(EoasisDispatchAction.java:40)
... 42 more
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.lang.reflect.Array.newInstance(Array.java:70)
at oracle.jdbc.driver.BufferCache.get(BufferCache.java:226)
at
oracle.jdbc.driver.PhysicalConnection.getCharBuffer(PhysicalConnection.java:7422)
at
oracle.jdbc.driver.OracleStatement.prepareAccessors(OracleStatement.java:983)
at oracle.jdbc.driver.T4CTTIdcb.receiveCommon(T4CTTIdcb.java:273)
at
oracle.jdbc.driver.T4CTTIdcb.receiveFromRefCursor(T4CTTIdcb.java:157)
at
oracle.jdbc.driver.T4CResultSetAccessor.unmarshalOneRow(T4CResultSetAccessor.java:197)
at oracle.jdbc.driver.T4CTTIrxd.unmarshal(T4CTTIrxd.java:916)
at oracle.jdbc.driver.T4CTTIrxd.unmarshal(T4CTTIrxd.java:835)
at oracle.jdbc.driver.T4C8Oall.readRXD(T4C8Oall.java:658)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:328)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
at
oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:202)
at
oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1005)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
at
oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3550)
at
oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4693)
at
oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1086)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:168)
at
com.capula.eoasis.model.dao.PatientDAO.getPatientDetails(PatientDAO.java:215)
at
com.capula.eoasis.model.dao.TheatreDAO.getAppointmentNew(TheatreDAO.java:2023)
at
com.capula.eoasis.model.dao.TheatreDAO.getMicroSessionAppointmentsNew(TheatreDAO.java:1915)
at
com.capula.eoasis.model.theatre.TheatreViewManagerImpl.getMicroSessionsNew(TheatreViewManagerImpl.java:309)
at
com.capula.eoasis.model.theatre.TheatreViewManagerImpl.getMicroSessions(TheatreViewManagerImpl.java:88)
at
com.capula.eoasis.model.theatre.TheatreViewManagerImpl.getMicroSessions(TheatreViewManagerImpl.java:81)
at
com.capula.eoasis.model.theatre.TheatreViewManagerImpl.getMicroSessions(TheatreViewManagerImpl.java:77)
at
com.capula.eoasis.model.theatre.TheatreViewManagerImpl.getMicroSessions(TheatreViewManagerImpl.java:73)
at sun.reflect.GeneratedMethodAccessor662.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 61880] Tomcat server 5: java process crashing
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61880
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
Tomcat 5 is no longer supported - and hasn't been for over 5 years.
Even if it were, Bugzilla is not a support forum. You want the Apache Tomcat
users mailing list.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 61880] Tomcat server 5: java process crashing
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61880
Christopher Schultz <ch...@christopherschultz.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
OS| |All
--- Comment #1 from Christopher Schultz <ch...@christopherschultz.net> ---
Invalid because:
1. This error is occurring in Oracle's JDBC driver, not Tomcat. Note that this
is a Java exception being thrown, and should not result in a JVM shutdown or
process termination.
2. Tomcat 5 is no longer supported[1]
[1] https://tomcat.apache.org/tomcat-55-eol.html
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org