[
http://issues.apache.org/jira/browse/TUSCANY-333?page=comments#action_12379105
]
ant elder commented on TUSCANY-333:
-----------------------------------
This is the error i get:
org.osoa.sca.ServiceUnavailableException:
org.apache.tuscany.core.wire.InvocationRuntimeException: Type
'{http://www.bigbank.com/account}getCustomerProfile' not found in registered
SDO types.
bigbank.webclient.services.account.AccountServiceComponentImpl.getCustomerProfile(AccountServiceComponentImpl.java:78)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.apache.tuscany.container.java.invocation.AbstractJavaComponentInvoker.invokeTarget(AbstractJavaComponentInvoker.java:58)
org.apache.tuscany.container.java.invocation.AbstractJavaComponentInvoker.invoke(AbstractJavaComponentInvoker.java:67)
org.apache.tuscany.core.wire.impl.InvokerInterceptor.invoke(InvokerInterceptor.java:39)
org.apache.tuscany.core.wire.jdk.JDKInvocationHandler.invoke(JDKInvocationHandler.java:112)
$Proxy19.getCustomerProfile(Unknown Source)
bigbank.webclient.services.profile.AccountLoginServiceImpl.login(AccountLoginServiceImpl.java:36)
bigbank.webclient.ui.LoginServlet.login(LoginServlet.java:90)
bigbank.webclient.ui.LoginServlet.doPost(LoginServlet.java:65)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache
Tomcat/5.5.17 logs.
> 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: Java-M1
> Reporter: Rick Rineholt
> Assignee: Rick Rineholt
> Priority: Critical
> Fix For: Java-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
