Re: JBoss log problem

Mon, 28 Jul 2003 17:12:52 -0700

Changing this flag will cause JBoss to use classloading behaviour outlined in Servlet specification. (Instead of delegating the classloading to parent classloader, web apps try their own classloader first, which is different to usual J2SE classloading behaviour. I think what this means is a JAR packaged with Web App will take precedence over the ones included with Jboss.)

May be the failing applications might have different versions of the JARs to what's included in Jboss. I have fixed things by making sure JARs included with the server is the same version as the ones packaged with the applications. So which JAR you use doesn't really matter. Using the latest JAR out of the two is a good bet, but still can have other undesirable effects.

If I were you I will post something on JBoss mailing list and ask for a cleaner way to fix the problem. I am not a Jboss expert :-(


Roshan


From: Glen Carl <[EMAIL PROTECTED]>
Reply-To: "Jetspeed Users List" <[EMAIL PROTECTED]>
To: Jetspeed Users List <[EMAIL PROTECTED]>
Subject: Re: JBoss log problem
Date: Mon, 28 Jul 2003 16:22:09 -0700

The flag did adjust the logging. Although, changing the flag to false caused major problems with my xerces and xalan processing. However, I am running JDK1.4.2, and there already is a thread related to xerces and xalan needing to be in the endorsed directory. I am hestitant to change the ClassLoadingCompliance flag, since other apps will be running in the JBoss container.
Thanks,
Glen


I am now using a Jetspeed CVS build from July 27, 2003.

Roshan G wrote:

Hi Glen,

There is a Bugzilla entry about this issue. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18415

To change the classloading behaviour in Jboss, there is an attribute called �Java2ClassLoadingCompliance� that you can change. By default its set to �true�. You want to change this to �false�.

<attribute name="Java2ClassLoadingCompliance">true</attribute>

For JBoss+Jetty this is found in the file

JBOSS_HOME\server\default\deploy\jbossweb-jetty.sar\META-INF\jboss-service.xml


For JBoss+Tomcat it�s found in
JBOSS_HOME\server\default\deploy\jbossweb-tomcat.sar\META-INF\jboss-service.xml




Roshan


From: Glen Carl <[EMAIL PROTECTED]>
Reply-To: "Jetspeed Users List" <[EMAIL PROTECTED]>
To: Jetspeed Users List <[EMAIL PROTECTED]>
Subject: Re: JBoss log problem
Date: Sat, 26 Jul 2003 10:41:10 -0700

Thanks Harald.
I am running Jetspeed-1.4b5-dev from a cvs download on May 17. Is the new logging scheme ready now? I guess I will try the latest from CVS.

I am new to JBoss, and will therefore need to research the class loaders.
Glen


_________________________________________________________________
Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


_________________________________________________________________
Tired of 56k? Get a FREE BT Broadband connection http://www.msn.co.uk/specials/btbroadband


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to