[jira] Commented: (GERONIMO-3655) Invalid MdbInstanceFactory behaviour

["Manu T George (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GERONIMO-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643963#action_12643963 ] 

Manu T George commented on GERONIMO-3655:
-----------------------------------------

This issue is fixed in trunk i.e. 2.2-SNAPSHOT. The sample application is working perfectly now

> Invalid MdbInstanceFactory behaviour
> ------------------------------------
>
>                 Key: GERONIMO-3655
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3655
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: OpenEJB
>    Affects Versions: 2.0.1, 2.0.2
>         Environment: Microsoft Windows XP, Sun Java 1.5.0_10, Apache Geronimo 2.0.1
>            Reporter: Alexei Akimov
>         Attachments: badmdb.zip
>
>
> org.apache.openejb.core.mdb.MdbInstanceFactory class pass invalid ThreadContext instance to ThreadContext.exit method at line 263 of its constructBean method. This brokes stack-like usage of ThreadContext objects and leads to problems during lazy initialization of ejb components when they called for the first time from the web tier. In particular ClassCastException is thrown in org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.before() at line 49, because ConnectorInstanceContextImpl instance is returned instead of SharedConnectorInstanceContext instance. This error results in that org.apache.geronimo.tomcat.listener.DispatchListener.beforeDispatch method does not put any data into the current context stack so when the afterDispatch method is called the current context stack throws java.util.EmptyStackException.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.