You probably have some kind of classloader 'layering' problem, in that
some of the classes are being loaded using reflection by classes that
are further down the classloader chain and therefore they cannot be
found.  I can't tell for sure from the information you've provided - but
if all the classes are present this seems the most likely cause.

Steve

-----Original Message-----
From: Tatalovich, Nicki [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 05, 2005 12:11 PM
To: Tatalovich, Nicki; James Users List
Subject: RE: JMX and James mailets

More comments below. 

Nicki
[EMAIL PROTECTED]
(714) 327-3690
 

-----Original Message-----
From: Steve Short [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 05, 2005 10:33 AM
To: James Users List
Subject: RE: JMX and James mailets


Yes - standalone, in JBoss and in WebSphere.
[Nicki] I've created a JMX Server that can be accessed remotely rather
than trying to load directly into Weblogic, Websphere & JBoss, because
these are for our services that don't need to run on a system with an
App Server directly. However, we would like to be able to start/stop
them from another system with an App Server or client app.

We add our mailets into their own jar file which is then included in the
SAR-INF/lib folder within the james.sar file.
[Nicki] We've done the same thing.

The problem is probably loading the classes that your mailet depends on
- what are these and where have you put them?
[Nicki] They are jars to access another application we've written and
also located in the SAR-INF/lib folder within the james.sar

I would not try to mix 2 JMX implementations in one classloader - that
path leads to certain trouble.
[Nicki] This can't mean that I'm stuck using the MX4J 1.1.1 beta 1
version?, which is what comes with James 2.2.0.
There must be a way around this. The App Servers cannot all be using
this same version. How do they work with the JMXLauncher? Are you adding
the jmx jars for MX4J to the classpath when using JMXLauncher with the
other App Servers?

What is your server environment?
[Nicki] Currently testing on WinXP & Win2K Server, needs to also work on
Win2003 Svr, Unix, Solaris, HPUX, AIX, Linux.


Steve

-----Original Message-----
From: Tatalovich, Nicki [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 05, 2005 10:22 AM
To: James-User Mailing List
Subject: JMX and James mailets

Is anyone using JMX to launch Phoenix & James with James loading a
mailet you've written?
I'm having trouble with it finding the mailet's jars, which are in the
apps\james.sar file under SAR-INF\lib.
If I comment out our mailet then Phoenix & James will start up ok using
JMX, with the mailet James fails when trying to initialize the spooler
because it cannot seem to find the jars for our mailet.
FYI, we've been using our mailet for over a year and it works fine when
Phoenix & James are started using the bin\run.bat file.

Do I need to use createMBean with a class loader for JMXLauncher?
There are notes that say Phoenix JMX implementation uses MX4J rather
than jmx reference implementation. Can I use Sun JMX 1.2.1 for my server
app?, which requires both sets of jmx libs in the classpath to run, or
will this cause problems?
I'm using Sun jmxremote 1.0 in a client app or HtmlAdaptorServer to
setup and kick off the JMXLauncherMBean.

I know we're not supposed to cross post but should this be in the dev
list instead of the user list?
Can someone please help?

Nicki



---------------------------------------------------------------------
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]





---------------------------------------------------------------------
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]

Reply via email to