[infinispan-issues] [JBoss JIRA] (ISPN-2330) JBossMarshaller uses wrong class resolver after stop/start
Scott Marlow (JIRA)
jira-events at lists.jboss.org
Mon Oct 15 17:19:01 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726629#comment-12726629 ]
Scott Marlow commented on ISPN-2330:
------------------------------------
For my issue, stop/start methods don't appear to be involved. http://pastebin.com/QiGV7F3b shows us creating a new ExtendedRiverMarshaller/ContextClassResolver pair which is used right away for marshalling.
I do see some calls to JBossMarshaller.stop() during my testing but that is very early in the test run (well before any of this occurs and well after the failures occur).
I'll copy this same to the infinispan-dev ml and stop commenting on this thread unless it indeed does turn out to be the same issue somehow.
> JBossMarshaller uses wrong class resolver after stop/start
> ----------------------------------------------------------
>
> Key: ISPN-2330
> URL: https://issues.jboss.org/browse/ISPN-2330
> Project: Infinispan
> Issue Type: Bug
> Components: Marshalling
> Affects Versions: 5.1.4.FINAL
> Reporter: Dennis Reed
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: jdg, jdg6
> Fix For: 5.2.0.CR1, 5.2.0.Final
>
> Attachments: AS7clusteringtestServerLogs.zip
>
>
> org.infinispan.marshall.jboss.JBossMarshaller initializes the classResolver in its inject() method and clears it in its stop() method.
> If the cache is stopped and restarted (for example when redeploying a clustered web app in EAP), the wrong class resolver is used.
> Either the classResolver should not be removed in stop() (testing with it removed did not show any class leaking issues), or it should be reset in start().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list