[jboss-jira] [JBoss JIRA] Updated: (JGRP-261) The value returned by the server method is not delivered by RpcDispatcher to client

Bela Ban (JIRA) jira-events at jboss.com
Fri Jul 14 07:44:16 EDT 2006


     [ http://jira.jboss.com/jira/browse/JGRP-261?page=all ]

Bela Ban updated JGRP-261:
--------------------------

    Fix Version/s: 2.4

Fixed. Problem was that IpAddress as return value is Streamable, so it was marshalled using IpAddress.writeTo(). However, Message.getObject() still used ObjectInputStream.readObject(), so that failed.

> The value returned by the server method is not delivered by RpcDispatcher to client
> -----------------------------------------------------------------------------------
>
>                 Key: JGRP-261
>                 URL: http://jira.jboss.com/jira/browse/JGRP-261
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.3 SP1
>         Environment: Windows XP, Sun
>            Reporter: Serhiy Yevtushenko
>         Assigned To: Bela Ban
>             Fix For: 2.4
>
>         Attachments: jgroupsbug.zip
>
>
> This bug was revealed by the unit testing, when trying to update to the version 2.3 SP1 from 2.2.9.1
> The call to the PpcDispatcher in the version 2.2.9.1 works properly.
> When performing the test example, it can be seen, that in version 2.3 SP1 the methods are being called on the server, but the results of the call are not delivered to the client.
> The output of the test example for the version 2.2.9.1 is the following:
> --not significant part skipped
> JGroupsSendingModeTest$ServerASkeleton.getConnectionPoint192.168.33.113:1914
> JGroupsSendingModeTest$ServerBSkeleton.getConnectionPoint111.111.111.111:5000
> rspList = [sender=192.168.33.113:1926, retval=111.111.111.111:5000, received=true, suspected=false]
> [sender=192.168.33.113:1914, retval=192.168.33.113:1914, received=true, suspected=false]
> ipAdressesList = [111.111.111.111:5000, 192.168.33.113:1914]
> --not significant part skipped
> The output of the example for  the version 2.3 SP1 is the following one:
> --not significant part skipped
> JGroupsSendingModeTest$ServerASkeleton.getConnectionPoint192.168.33.113:1956
> JGroupsSendingModeTest$ServerBSkeleton.getConnectionPoint111.111.111.111:5000
> rspList = [sender=192.168.33.113:1959, retval=null, received=true, suspected=false]
> [sender=192.168.33.113:1956, retval=null, received=true, suspected=false]
> ipAdressesList = []
> --not significant part skipped
> The investigation of the logs has shown, that in log for the version 2.3 SP1 the following message is being present :
>  [ERROR] thread [UpHandler (QUEUE)] class [org.jgroups.blocks.GroupRequest] exception=java.lang.IllegalArgumentException: java.io.StreamCorruptedException: invalid stream header
> This exception is thrown in the method  GroupRequest.receiveResponse(Message m) , in the following block of code:
>  if(m.getLength() > 0) {
>             try {
>                 val=m.getObject();
>             }
>             catch(Exception e) {
>                 if(log.isErrorEnabled()) log.error("exception=" + e);
>             }
>         }  

-- 
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

        



More information about the jboss-jira mailing list