Joćo Clemente wrote:
This is new in 3.0.5.On Fri, 17 Jan 2003 07:36:57 +0000 Jules Gosnell <[EMAIL PROTECTED]> wrote:Joćo Clemente wrote:As I've reported some days ago, when using 3.0.5RC2, I am getting these strange lines in my log file. This time I'm using 3.0.5 binaries available in sourceforge.
01:16:45,502 INFO [JBossWebApplicationContext] setDistributable true
01:16:46,062 INFO [JBossWebApplicationContext#/webmail] using Distributable HttpSession Manager: or
g.mortbay.j2ee.session.Manager@779959
01:16:46,102 WARN [Manager] No Store. Falling back to a local session implementation - NO HTTPSESSI
ON DISTRIBUTION
As anyone seen this before?If you set the <distributable/> tag in your web.xml you should: 1. be doing so intentionally - it is a costly thing to do.
Yes, I am, since I'll need to support failover. My app keeps references in http layer (httpsession) to ejb layer objects. If I do not support http session replication the whole thing goes down.
2. uncomment the JGStore block in deploy/jbossweb.sar/META-INF/jboss-service.xml
Hey! Is this new? I haven't done this step with the previous jboss versions, and I had some small test applications working correctly (with http replication enabled) then! Was this some jetty change introduced in the last days?
Components in the session replication layer are now configured by allocating and configuring an instance in the ConfigurationElement of you jbossweb.sar/META-INF/jboss-service.xml. Previously, you just had to specify the classes, not the instances.
The advantage of this approach is that it is considerably more flexible and exposes the instance's full interface to configuration.
The disadvantage is that you actually need the class present at configure-time. JavaGroups is not present in some of the JBoss configurations, so this block is commented out, to avoid nasty exceptions on startup.
NB.
You should upgrade to Jetty 4.2.5 to avoid a couple of nasty bugs that crept into 4.2.4 (release in 3.0.5).
See the FAQ - http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=HEAD&content-type=text/vnd.viewcvs-markup
Jules
3. run the 'all' configuration, which contains JavaGroups which is needed for session distribution.
Yep, I'm doing that. Ok, let me try out and I'll post my new findings. Once again, thank you Jules.
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your clients even if they use browsers that are limited to 40 bit encryption. Get a guide here: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user Herve Tchepannou wrote:
jboss-dev has ~16000 messages and there is no seach facility on sf for mailing lists.
Can you jsut tell me how to fix that prob?
thanx
-----Original Message-----
From: Jules Gosnell [ mailto:[EMAIL PROTECTED] ]
Sent: 20 January 2003 05:07
To: [EMAIL PROTECTED]
Cc: jboss
Subject: Re: [JBoss-user] unable to deploy my application to
JBoss-Jetty: java.lang.ClassNotFoundException:
org.mortbay.j2ee.session.JGStore
search this list's and jboss-dev's archive, I've already answered this
question,
Jules
Herve Tchepannou wrote:
>I'm trying to deploy an application that I've successfully deployed on
>JBoss-Tomcat, but Im receiving the following errors:
>
>java.lang.ClassNotFoundException: org.mortbay.j2ee.session.JGStore
> at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
> at
>org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:227)
> at
>org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:200)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:217)
> at org.mortbay.j2ee.session.Manager.initialize(Manager.java:249)
> at
>org.mortbay.jetty.servlet.ServletHandler.setSessionManager(ServletHandler.java:167)
> at
>org.jboss.jetty.JBossWebApplicationContext.setUpDistributableSessionManager(JBossWebApplicationContext.java:293) at org.jboss.jetty.JBossWebApplicationContext.startHandlers(JBossWebApplicationContext.java:270)
> at org.mortbay.http.HttpContext.start(HttpContext.java:1763)
> at
>org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:471)
> at
>org.mortbay.j2ee.J2EEWebApplicationContext.start(J2EEWebApplicationContext.java:85)
> at org.jboss.jetty.Jetty.deploy(Jetty.java:414)
> at
>org.jboss.jetty.JettyService.performDeploy(JettyService.java:243)
> at
>org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:300)
> at
>org.jboss.deployment.MainDeployer.start(MainDeployer.java:807)
> at
>org.jboss.deployment.MainDeployer.start(MainDeployer.java:799)
> at
>org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:621)
> at
>org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:585)
> at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
> at
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
>org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
> at
>org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
> at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
> at $Proxy4.deploy(Unknown Source)
> at
>org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:435)
> at
>org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:656)
> at
>org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
> at
>org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:212)
> at
>org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:225)
> at
>org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:202)
>22:23:40,387 INFO [JBossWebApplicationContext#/xpetstore] using
>Distributable HttpSession Manager: org.mortbay.j2ee.sessio
>
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________ ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
