[
https://issues.jboss.org/browse/ISPN-3589?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-3589:
-------------------------------------
This seems to be caused by an InternalMetadataImpl having set the "actual" field
to itself. Hard to see how this can happen. Do you have any logs for this?
StackOverflow in InternalMetadataImpl.Externalizer
--------------------------------------------------
Key: ISPN-3589
URL:
https://issues.jboss.org/browse/ISPN-3589
Project: Infinispan
Issue Type: Bug
Affects Versions: 6.0.0.CR1
Reporter: Pedro Ruivo
Assignee: Mircea Markus
Fix For: 6.0.0.Final, 6.1.0.Final
the implementation delegates to another metadata some methods. The result is a chain of
InternalMetadataImpl as you can see in:
{code}
metadata=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=Inte
rnalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl
{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=Internal
MetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{act
ual=InternalMetadataImpl [....]
{code}
--
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