geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Closed: (GERONIMO-482) Servlet lifecycle doesn't work well with connection lifecycle
Date Wed, 08 Dec 2004 19:43:10 GMT
     [ http://nagoya.apache.org/jira/browse/GERONIMO-482?page=history ]
     
David Jencks closed GERONIMO-482:
---------------------------------

     Resolution: Fixed
    Fix Version: 1.0-M4

I don't have a test case but this should be fixed with the "interceptor" stack for enter/leave
scope.

> Servlet lifecycle doesn't work well with connection lifecycle
> -------------------------------------------------------------
>
>          Key: GERONIMO-482
>          URL: http://nagoya.apache.org/jira/browse/GERONIMO-482
>      Project: Apache Geronimo
>         Type: Bug
>   Components: connector
>     Versions: 1.0-M3
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0-M4

>
> If a servlet opens a connection in init, it might get this exception in destroy when
trying to close it.
> java.lang.NullPointerException
>         at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTrackingCoordinator.handleReleased(Connec
> tionTrackingCoordinator.java:131)
>         at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTrackingCoordinator$$FastClassByCGLIB$$5d
> 33aabf.invoke(<generated>)
>         at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:87)
>         at org.apache.geronimo.gbean.jmx.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>         at org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
>         at org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:823)
>         at org.apache.geronimo.gbean.jmx.RawInvoker.invoke(RawInvoker.java:89)
>         at org.apache.geronimo.gbean.jmx.RawOperationInvoker.invoke(RawOperationInvoker.java:34)
>         at org.apache.geronimo.gbean.jmx.CGLibMethodInterceptor.intercept(CGLibMethodInterceptor.java:112)
>         at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$1850a2fe.handle
> Released(<generated>)
>         at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.returnConnection(ConnectionTrackingInter
> ceptor.java:81)
>         at org.apache.geronimo.connector.outbound.GeronimoConnectionEventListener.connectionClosed(GeronimoConnectionEve
> ntListener.java:68)
>         at org.codehaus.activemq.ra.ActiveMQManagedConnection.proxyClosedEvent(ActiveMQManagedConnection.java:454)
>         at org.codehaus.activemq.ra.JMSConnectionProxy.close(JMSConnectionProxy.java:67)
>         at com.gluecode.samples.jms.servlet.SubscriberServlet.destroy(SubscriberServlet.java:87)
>         at org.mortbay.jetty.servlet.ServletHolder.stop(ServletHolder.java:270)
>         at org.mortbay.jetty.servlet.ServletHandler.doStop(ServletHandler.java:470)
> Probably the servlet init method isn't properly setting the connection tracking context.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message