[
http://jira.jboss.com/jira/browse/JBCLUSTER-56?page=all ]
Brian Stansberry resolved JBCLUSTER-56.
---------------------------------------
Fix Version/s: Q3Y6
Resolution: Done
In Branch_3_2 an UnmarshalException will no longer lead to failover or removal of a target
from the FamilyClusterInfo. Don't know for sure if that resolves your issue, but it
should and is as far as I'll go in Branch_3_2.
After 1st UnmarshallException all following client calls fail:
Serivce unavailable
----------------------------------------------------------------------------------
Key: JBCLUSTER-56
URL:
http://jira.jboss.com/jira/browse/JBCLUSTER-56
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: Solaris 9, Linux, java 1.4.2_07 and higher
Reporter: kleibl
Assigned To: Brian Stansberry
Fix For: Q3Y6
Attachments: failtest.zip
Original Estimate: 3 days
Remaining Estimate: 3 days
when called a method on a session bean that returns non serializable object in clustered
deployment this throws java.rmi.UnmarshallException (this is correct). all subsequent
calls from that client fail and throw:
Service unavailable.
org.jboss.invocation.ServiceUnavailableException: Service unavailable.
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxyHA.invoke(JRMPInvokerProxyHA.java:287)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:163)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:103)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:100)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
at $Proxy2.echo(Unknown Source)
at failtest.client.Tester$TestThread.run(Tester.java:184)
there is no additional communication between client and server. the calls end at the
JRMPInvokerProxyHA.
this behviour doesn't occure in non clustered deployment. in that case the following
client calls are working.
i tested it on jboss 3.2.5, 3.2.6, 3.2.7
in 4.0.2 this error doesn't occure
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira