[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jboss-development
Subject:    [JBoss-dev] [ jboss-Bugs-927062 ] Problem with serialization of Stateful SB handle
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2004-03-31 22:05:12
Message-ID: E1B8npg-0003kf-00 () sc8-sf-web1 ! sourceforge ! net
[Download RAW message or body]

Bugs item #927062, was opened at 2004-03-31 22:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=927062&group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Fleet (andyfleet)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problem with serialization of Stateful SB handle

Initial Comment:
JBoss 3.2.3
JDK 1.4.1
Windows XP

Hi,
   the main problem is described here...

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=47688

There are 2 issues (the main one is described above).

Issue 1)

JBoss appears to create a spurious Session Bean when a 
client serializes and deserializes the remote interface.

The attached file demonstrates the issue - you&#039;ll need to
tweak build.xml, but when that has been done, do

ant deploy
ant client

The client creates a statefull session bean, invokes,
stores the remote handle to a file, deserializes it 
and invokes on the bean (with appropriate narrowing). 
The second invokation goes to the correct bean, however
the server output indicates the Session Bean constructor
and setSessionCOntext have been called (in error).


Issue 2)

After having run &#039;ant client&#039; I see the following output
from the server (starting about 15 minutes after the
&#039;ant client&#039; call)

13:25:25,765 WARN  [AbstractInstanceCache] Unable to
 passivate due to ctx lock, id=dshx0pi7-4
13:35:25,765 WARN  [AbstractInstanceCache] Unable to
 passivate due to ctx lock, id=dshx0pi7-4
13:45:25,781 WARN  [AbstractInstanceCache] Unable to
 passivate due to ctx lock, id=dshx0pi7-4
13:55:25,781 WARN  [AbstractInstanceCache] Unable to 
passivate due to ctx lock, id=dshx0pi7-4


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=927062&group_id=22866


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[prev in list] [next in list] [prev in thread] [next in thread]