RE: [JBoss-user] Help with Clustering

2003-02-21 Thread Bill Burke
The only workaround I can think of is to place your classes in a JAR that is
outside the scope of the WAR.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Dennis
 Muhlestein
 Sent: Friday, February 21, 2003 12:41 PM
 To: [EMAIL PROTECTED]
 Subject: [JBoss-user] Help with Clustering


 Having still had no luck in getting Http Session Clustering to cluster
 objects, I thought I'd simplify the test.

 Using tomcat4.1.18 embedded
 Tried jboss 3.0.6 and 3.2.0rc2.
 jdk 1.4.1.01
 linux.

 clustering with two identical linux boxes/ idenitical cluster configs in
 jboss.  I used the default config files provided with jboss so I didn't
 attach them.  If anyone is interested in them let me know.

 TEST 1:

 * simple servlet sets a String session attribute for login management.
 ie: request.getSession().setAttribute ( username, username );

 * take one of the boxes down. - attribute is in clusted session -
 continued browsing works.

 * bring box back up. - attribute is distributed to new box - browsing
 works.

 * bring other box down - attribute is still clustered - browsing works.

 TEST 1 result: clustering works ok.

 TEST 2:

 * simple servlet uses simple Data Object instead of string:
 ie:
 --- Login class
 public class LoginData implements java.io.Serializable {
 public String username = null;
 public LoginData ( String username ) { this.username = username; }
 }
 --- Session usage
 LoginData ld = New LoginData( username );
 request.getSession().setAttribute ( logindata, ld );

 * login works but exception is thrown:

 EJBException:
 javax.ejb.EJBException: java.lang.ClassNotFoundException: LoginData (no
 security manager: RMI class loader disabled)
 at
 org.jboss.ha.httpsession.beanimpl.ejb.ClusteredHTTPSessionBeanImpl
 .unserializeSession(ClusteredHTTPSessionBeanImpl.java:139)
 at
 org.jboss.ha.httpsession.beanimpl.ejb.ClusteredHTTPSessionBeanImpl
 .getSession(ClusteredHTTPSessionBeanImpl.java:79)
 at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
 cessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at
 org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityCo
 ntainer.java:1194)at
 org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(Enti
tySynchronizationInterceptor.java:330)
 at
 org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInsta
 nceInterceptor.java:174)
 at
 org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInter
 ceptor.java:107)
 at
 org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:208)
 at
 org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493)
 at org.jboss.ejb.Container.invoke(Container.java:712)
 at
 org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1058)
 at
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
 at
 org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:99)
 at
 org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.
 java:102)
 at
 org.jboss.proxy.TransactionInterceptor.invoke(TransactionIntercept
 or.java:77)
 at
 org.jboss.proxy.ejb.EntityInterceptor.invoke(EntityInterceptor.java:116)
 at
 org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
 at $Proxy27.getSession(Unknown Source)
 at
 org.jboss.ha.httpsession.server.ClusteredHTTPSessionService.getHtt
 pSession(ClusteredHTTPSessionService.java:132)
 .. more

 * if next request goes to same box, the LoginData is in the session and
 the username can be retrieved.  The LoginData attribute is NOT clustered
 though.

 * if I take the first box down, the request now fails to grab the
 session on the second box.  The exception on the 2nd box is the exact
 same as the one above.


 I tried putting the data class in a jar by itself in the lib directory
 just for kicks but I still got the exact same issue.

 Any help would be appriciated.  At this point, I'm going to consider
 alternate technology for clustering.  Am I doing something drastically
 wrong?  I couldn't find any bugs related to this issue on sourceforge so
 I'm assuming it hasn't been addressed very well.

 Does anyone have anything like this implemented yet?

 Any thoughts appreciated.

 -Dennis






 ---
 This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
 The most comprehensive and flexible code editor you can use.
 Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
 www.slickedit.com/sourceforge
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-user



---
This SF.net email is sponsored by: 

RE: [JBoss-user] Help with Clustering

2003-02-21 Thread Dennis Muhlestein
Tried that. I made a note at the bottom of that post, but it was pretty
small. 

I placed the class in a jar file in the lib folder.  Still got the same
exception though.  It's like the ClusteredHttpSessionBean can't find
anything except system classes.  Does this have anything to do with it
being started from an sar file?

-Dennis

On Fri, 2003-02-21 at 11:51, Bill Burke wrote:
 *This message was transferred with a trial version of CommuniGate(tm) Pro*
 The only workaround I can think of is to place your classes in a JAR that is
 outside the scope of the WAR.
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Behalf Of Dennis
  Muhlestein
  Sent: Friday, February 21, 2003 12:41 PM
  To: [EMAIL PROTECTED]
  Subject: [JBoss-user] Help with Clustering
 
 
  Having still had no luck in getting Http Session Clustering to cluster
  objects, I thought I'd simplify the test.
 
  Using tomcat4.1.18 embedded
  Tried jboss 3.0.6 and 3.2.0rc2.
  jdk 1.4.1.01
  linux.
 
  clustering with two identical linux boxes/ idenitical cluster configs in
  jboss.  I used the default config files provided with jboss so I didn't
  attach them.  If anyone is interested in them let me know.
 
  TEST 1:
 
  * simple servlet sets a String session attribute for login management.
  ie: request.getSession().setAttribute ( username, username );
 
  * take one of the boxes down. - attribute is in clusted session -
  continued browsing works.
 
  * bring box back up. - attribute is distributed to new box - browsing
  works.
 
  * bring other box down - attribute is still clustered - browsing works.
 
  TEST 1 result: clustering works ok.
 
  TEST 2:
 
  * simple servlet uses simple Data Object instead of string:
  ie:
  --- Login class
  public class LoginData implements java.io.Serializable {
  public String username = null;
  public LoginData ( String username ) { this.username = username; }
  }
  --- Session usage
  LoginData ld = New LoginData( username );
  request.getSession().setAttribute ( logindata, ld );
 
  * login works but exception is thrown:
 
  EJBException:
  javax.ejb.EJBException: java.lang.ClassNotFoundException: LoginData (no
  security manager: RMI class loader disabled)
  at
  org.jboss.ha.httpsession.beanimpl.ejb.ClusteredHTTPSessionBeanImpl
  .unserializeSession(ClusteredHTTPSessionBeanImpl.java:139)
  at
  org.jboss.ha.httpsession.beanimpl.ejb.ClusteredHTTPSessionBeanImpl
  .getSession(ClusteredHTTPSessionBeanImpl.java:79)
  at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
  cessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at
  org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityCo
  ntainer.java:1194)at
  org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(Enti
 tySynchronizationInterceptor.java:330)
  at
  org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInsta
  nceInterceptor.java:174)
  at
  org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInter
  ceptor.java:107)
  at
  org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:208)
  at
  org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493)
  at org.jboss.ejb.Container.invoke(Container.java:712)
  at
  org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1058)
  at
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
  at
  org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:99)
  at
  org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.
  java:102)
  at
  org.jboss.proxy.TransactionInterceptor.invoke(TransactionIntercept
  or.java:77)
  at
  org.jboss.proxy.ejb.EntityInterceptor.invoke(EntityInterceptor.java:116)
  at
  org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
  at $Proxy27.getSession(Unknown Source)
  at
  org.jboss.ha.httpsession.server.ClusteredHTTPSessionService.getHtt
  pSession(ClusteredHTTPSessionService.java:132)
  .. more
 
  * if next request goes to same box, the LoginData is in the session and
  the username can be retrieved.  The LoginData attribute is NOT clustered
  though.
 
  * if I take the first box down, the request now fails to grab the
  session on the second box.  The exception on the 2nd box is the exact
  same as the one above.
 
 
  I tried putting the data class in a jar by itself in the lib directory
  just for kicks but I still got the exact same issue.
 
  Any help would be appriciated.  At this point, I'm going to consider
  alternate technology for clustering.  Am I doing something drastically
  wrong?  I couldn't find any bugs related to this issue on sourceforge so
  I'm assuming it hasn't been addressed very well.
 
  Does anyone have anything like this implemented