[ http://issues.apache.org/jira/browse/TUSCANY-333?page=all ]
Jean-Sebastien Delfino updated TUSCANY-333:
-------------------------------------------
Priority: Critical (was: Major)
I'm not sure anymore that this is related to 226 but this is a serious problem.
We need the complete stack trace and also info on which classloaders are
actually used for the business interface for the service and the dataobject
flowing through it. Rick was going to investigate.
> BigBank intermittently gets ClassCastException
> -----------------------------------------------
>
> Key: TUSCANY-333
> URL: http://issues.apache.org/jira/browse/TUSCANY-333
> Project: Tuscany
> Type: Bug
> Components: Java BigBank Scenario
> Versions: M1
> Reporter: Rick Rineholt
> Priority: Critical
> Fix For: M1
>
> I have noticed this behavior but it's really hard to repro. I have debugged
> it once and it occured in the sun proxyy code I think right after
> JDKInvocationHandler.invoke call. The only regular pattern I've been able to
> see if there is a previous un releated exception like an invalid user name is
> entered that generates an expected exception it seems sometimes after this,
> this exception continues to get thrown for any activity. Once this happens it
> seems the only cure is to recycle TC server.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
