You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2006/05/09 11:10:21 UTC
[jira] Updated: (TUSCANY-333) BigBank intermittently gets
ClassCastException
[ http://issues.apache.org/jira/browse/TUSCANY-333?page=all ]
Jean-Sebastien Delfino updated TUSCANY-333:
-------------------------------------------
Fix Version: M1
Version: M1
This needs to be fixed for M1. At first sight it looks like this problem may be caused by TUSCANY-226.
> 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
> 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