Re: [JBoss-user] Stateful Session Bean problem (newbie?)

2002-09-27 Thread Stephen Coy

How do you know that you are getting the same instance of the SFSB on 
the second call?

Is the second call on the same JSP and responding to the same HTTP 
request?
If not,  how are you caching the instance reference between requests?

Half a second seems like a long time to be processing the same page.


Steve Coy

On Friday, September 27, 2002, at 06:06  PM, wonder sonic wrote:

 Hello,
 I've spent about 4 hours on this but I couldn't find
 the problem.
 I've got a local SFSB with one attribut : an Object
 (that implements the Serializable interface).
 I use it from a JSP (embedded JBOSS+Tomcat):

 -1- call to the SFSB = the attribut receives an
 instance of the Object.
 -2- call (about 500ms after) to the SFSB = the
 attribut is now equals to null!

 The SFSB is configured to be used with XDoclet 1.1.2
 with trans-type:Required.
 I've also a create method:

 public void ejbCreate() {}

 What should I do to make this work?



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Stateful Session Bean problem (newbie?)

2002-09-27 Thread wonder sonic

AFAIK, a stateful session bean means, for a client, it
is the same, in the 1st point, the loginCheck.jsp
create the Object, in the 2nd point, an other JSP try
to retrieves the object... I begin to see where does
the problem comes from. But how to do what I intend
to?

It's not the same HTTP request (2 different business
methods)

half a second because the JSP is being compiled ;)

thanks for the answer :)
Wonder Sonic

 --- Stephen Coy [EMAIL PROTECTED] a écrit :
 How do you know that you are getting the same
 instance of the SFSB on 
 the second call?
 
 Is the second call on the same JSP and responding to
 the same HTTP 
 request?
 If not,  how are you caching the instance reference
 between requests?
 
 Half a second seems like a long time to be
 processing the same page.
 
 
 Steve Coy
 
 On Friday, September 27, 2002, at 06:06  PM, wonder
 sonic wrote:
 
  Hello,
  I've spent about 4 hours on this but I couldn't
 find
  the problem.
  I've got a local SFSB with one attribut : an
 Object
  (that implements the Serializable interface).
  I use it from a JSP (embedded JBOSS+Tomcat):
 
  -1- call to the SFSB = the attribut receives an
  instance of the Object.
  -2- call (about 500ms after) to the SFSB = the
  attribut is now equals to null!
 
  The SFSB is configured to be used with XDoclet
 1.1.2
  with trans-type:Required.
  I've also a create method:
 
  public void ejbCreate() {}
 
  What should I do to make this work?
 
 
 

---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]

https://lists.sourceforge.net/lists/listinfo/jboss-user 

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Stateful Session Bean problem (newbie?)

2002-09-27 Thread Saroj Kumar

I think you need to keep that Remote reference in session so that
You get that in another JSP.

Otherwise, you will get the different SFSB.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of wonder
sonic
Sent: Friday, September 27, 2002 3:13 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Stateful Session Bean problem (newbie?)


AFAIK, a stateful session bean means, for a client, it
is the same, in the 1st point, the loginCheck.jsp
create the Object, in the 2nd point, an other JSP try
to retrieves the object... I begin to see where does
the problem comes from. But how to do what I intend
to?

It's not the same HTTP request (2 different business
methods)

half a second because the JSP is being compiled ;)

thanks for the answer :)
Wonder Sonic

 --- Stephen Coy [EMAIL PROTECTED] a écrit :
 How do you know that you are getting the same
 instance of the SFSB on 
 the second call?
 
 Is the second call on the same JSP and responding to
 the same HTTP 
 request?
 If not,  how are you caching the instance reference
 between requests?
 
 Half a second seems like a long time to be
 processing the same page.
 
 
 Steve Coy
 
 On Friday, September 27, 2002, at 06:06  PM, wonder
 sonic wrote:
 
  Hello,
  I've spent about 4 hours on this but I couldn't
 find
  the problem.
  I've got a local SFSB with one attribut : an
 Object
  (that implements the Serializable interface).
  I use it from a JSP (embedded JBOSS+Tomcat):
 
  -1- call to the SFSB = the attribut receives an
  instance of the Object.
  -2- call (about 500ms after) to the SFSB = the
  attribut is now equals to null!
 
  The SFSB is configured to be used with XDoclet
 1.1.2
  with trans-type:Required.
  I've also a create method:
 
  public void ejbCreate() {}
 
  What should I do to make this work?
 
 
 

---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]

https://lists.sourceforge.net/lists/listinfo/jboss-user 

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Stateful Session Bean Problem

2001-11-21 Thread Sacha Labourey

Hello Nicolai,

Are you sure that your SFSB lifetime hasn't expired? It looks like the bean
state has been removed from the file storage.

Cheers,


Sacha

 -Message d'origine-
 De : [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]De la part de Nicolai P
 Guba
 Envoyé : mercredi, 21 novembre 2001 10:22
 À : JBoss User
 Objet : [JBoss-user] Stateful Session Bean Problem


 What are the reasons for a stateful session bean NOT to serialize itself
 onto the filesystem?  I am getting this pretty odd exception from our
 only stateful session bean and am a bit stupefied.  H

 Log is below

  [java] java.rmi.ServerException: RemoteException occurred in server
 thread; nested exception is:
  [java]   javax.transaction.TransactionRolledbackException: Could not
 activate; nested exception is:
  [java]   java.io.FileNotFoundException:
 /usr/local/JBoss/2.4.3/jboss/db/sessions/QueryHandler/1006278857470.ser
 (No such file or directory); nested exception is:
  [java]   java.rmi.NoSuchObjectException: Could not activate; nested
 exception is:
  [java]   java.io.FileNotFoundException:
 /usr/local/JBoss/2.4.3/jboss/db/sessions/QueryHandler/1006278857470.ser
 (No such file or directory)
  [java] javax.transaction.TransactionRolledbackException: Could not
 activate; nested exception is:

 --
   Nicolai P Gubahttp://www.gnu.org http://www.frontwire.com
 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
 GSM: +44 (0)7909 960 751   DDI: +44 (0)20 7368 9708

 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user



___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Stateful Session Bean Problem

2001-11-21 Thread Nicolai P Guba

On Wed, 2001-11-21 at 09:42, Sacha Labourey wrote:
 Hello Nicolai,
 
 Are you sure that your SFSB lifetime hasn't expired? It looks like the bean
 state has been removed from the file storage.

H, this is definitively the case because the file is not there any
more.  However, this bean is being still refered to and one would expect
it to serialize and passivate, then activate later on.  Never to just
delete itself as long as the session is still open.  It doesn't make
sense.

-- 
  Nicolai P Gubahttp://www.gnu.org http://www.frontwire.com
mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
GSM: +44 (0)7909 960 751   DDI: +44 (0)20 7368 9708

___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Stateful Session Bean Problem

2001-11-21 Thread Sternagel Annegret (PN-SYS/PE)

I got this exception in two cases (jboss 2.4.3):

1. the bean has thrown a java.rmi.RemoteException before
= jboss discarded the bean

2. the automatical remove of the SessionBean by jobss has taken place,
default configuration is 30 min.

Annegret



-Ursprüngliche Nachricht-
Von: Nicolai P Guba [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 21. November 2001 10:22
An: JBoss User
Betreff: [JBoss-user] Stateful Session Bean Problem


What are the reasons for a stateful session bean NOT to serialize itself
onto the filesystem?  I am getting this pretty odd exception from our
only stateful session bean and am a bit stupefied.  H

Log is below 

 [java] java.rmi.ServerException: RemoteException occurred in server
thread; nested exception is: 
 [java] javax.transaction.TransactionRolledbackException: Could not
activate; nested exception is: 
 [java] java.io.FileNotFoundException:
/usr/local/JBoss/2.4.3/jboss/db/sessions/QueryHandler/1006278857470.ser
(No such file or directory); nested exception is: 
 [java] java.rmi.NoSuchObjectException: Could not activate; nested
exception is: 
 [java] java.io.FileNotFoundException:
/usr/local/JBoss/2.4.3/jboss/db/sessions/QueryHandler/1006278857470.ser
(No such file or directory)
 [java] javax.transaction.TransactionRolledbackException: Could not
activate; nested exception is: 

-- 
  Nicolai P Gubahttp://www.gnu.org http://www.frontwire.com
mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
GSM: +44 (0)7909 960 751   DDI: +44 (0)20 7368 9708

___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Stateful Session Bean Problem

2001-11-21 Thread Sacha Labourey

Hello Nicolai,

 H, this is definitively the case because the file is not there any
 more.  However, this bean is being still refered to and one would expect
 it to serialize and passivate, then activate later on.  Never to just
 delete itself as long as the session is still open.  It doesn't make
 sense.

Yes it does make sense if you follow the SFSB semantic. The JBoss server is
not able to know if the session is still open.

IMHO you have two choices:
- modify your SFSB settings, in this case max-bean-life which is, by
default, set to 1800 = 30 minutes (also check remover-period which is
also set to 30 minutes = SFSB lifetime is between 30 minutes and 1 hour)
- If your idea of a session is strict enough, you may better switch to
entity beans.

Good luck. Cheers,



Sacha


___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Stateful Session Bean Problem

2001-11-21 Thread Alex Loubyansky

Hello, Nicolai!

I had the same exception. My project worked fine first but after some
improvements :) in some cases JBoss printed me such an exception. The
problem was in RemoteException like Sternagel said.

Good luck!
jalex

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Nicolai P
 Guba
 Sent: Wednesday, November 21, 2001 11:22
 To: JBoss User
 Subject: [JBoss-user] Stateful Session Bean Problem


 What are the reasons for a stateful session bean NOT to serialize itself
 onto the filesystem?  I am getting this pretty odd exception from our
 only stateful session bean and am a bit stupefied.  H

 Log is below

  [java] java.rmi.ServerException: RemoteException occurred in server
 thread; nested exception is:
  [java]   javax.transaction.TransactionRolledbackException: Could not
 activate; nested exception is:
  [java]   java.io.FileNotFoundException:
 /usr/local/JBoss/2.4.3/jboss/db/sessions/QueryHandler/1006278857470.ser
 (No such file or directory); nested exception is:
  [java]   java.rmi.NoSuchObjectException: Could not activate; nested
 exception is:
  [java]   java.io.FileNotFoundException:
 /usr/local/JBoss/2.4.3/jboss/db/sessions/QueryHandler/1006278857470.ser
 (No such file or directory)
  [java] javax.transaction.TransactionRolledbackException: Could not
 activate; nested exception is:

 --
   Nicolai P Gubahttp://www.gnu.org http://www.frontwire.com
 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
 GSM: +44 (0)7909 960 751   DDI: +44 (0)20 7368 9708

 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user


___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user