[
https://issues.jboss.org/browse/AS7-5718?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-5718:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
Git Pull Request:
https://github.com/jbossas/jboss-remote-naming/pull/10 (was:
https://github.com/jbossas/jboss-remote-naming/pull/10)
Since the remote-naming PR has been merged into that repo, I'm scheduling this for
7.2.0.Alpha1. A remote-naming upgrade will be needed.
Client deserialising objects using wrong classloader
----------------------------------------------------
Key: AS7-5718
URL:
https://issues.jboss.org/browse/AS7-5718
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.3.Final (EAP)
Reporter: James Livingston
Assignee: James Livingston
Fix For: 7.2.0.Alpha1
The commands in org.jboss.naming.remote.protocol.v1.Protocol deserialize objects using
the Unmarshaller from ReadUtil. That does not explicitly set a ClassResolver, so it
defaults to using the TCCL. Since the handle*Message methods are run in a thread pool, the
TCCL could be set to anything, so the commands need to ensure that the correct classloader
(presumably the one calling the Context methods) is used.
--
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