[jboss-jira] [JBoss JIRA] (AS7-5718) Client deserialising objects using wrong classloader
[
https://issues.jboss.org/browse/AS7-5718?page=com.atlassian.jira.plugin.s...
]
James Livingston commented on AS7-5718:
---------------------------------------
To go with the remote-naming PR, there is a test for the AS testsuite in
https://github.com/doctau/jboss-as/tree/test-remotenaming-multiclient. I haven't
created a PR yet because it's going to fail builds until remote-naming is fixed.
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
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