[infinispan-issues] [JBoss JIRA] (ISPN-2330) JBossMarshaller uses wrong class resolver after stop/start
[
https://issues.jboss.org/browse/ISPN-2330?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2330:
----------------------------------------
The root cause appears to be the use of the old cache marshaller instance after cache
restart. Indirectly, Dan has fixed this issue in ISPN-2297 (2nd issue), and I've added
a patch on top of it so that it works as expected for cache restarts. So, can you please
give it a shot to the latest of my branch in
https://github.com/galderz/infinispan/tree/t_2330_5 and see if the issue is gone?
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: anotherAS7clusteringtestServerLogs.zip,
AS7clusteringtestServerLogs.zip, moreAS7clusteringtestServerLogs.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