The machine that has problems has an older version of JMX installed somewhere. That's about all I can make out from the stack traces.
"Michael Duffy" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I HATE it when I ask a question that nobody will > touch! ;) > > I learned more about my MBean server failure. It's > not working on my desktop, so I went to another > machine and installed JDK 1.4.1 and Tomcat 4.1.24 LE > clean. No MBean server failure, and the admin tool > runs great. > > Conclusion: my desktop setup is the problem. > > I've been poring through my system parameters. I > cleaned up my PATH. I don't have a CLASSPATH set for > the system. I let every app set that for itself. So > even if I have servlet.jar in several places, there's > no way Tomcat would find a bad one, because its > CLASSPATH would include those directories. > > I'm cleaning out old s'ware that might be doing it. I > had an old J2EE 1.3 hanging around. I was hoping that > getting rid of it would solve the dilemma, but no > dice. > > The root cause in the log file is: > > Caused by: java.lang.IllegalArgumentException: Invalid > descriptor passed in parameter > > Does anyone know how I can find what's being passed > and see what the problem is? I don't know anything > about JMX or MBeans. Is there any developer who's > knowledgable enough about MBeans to be able to tell me > what could be causing this? Thanks - MOD > > > > __________________________________ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to Outlook(TM). > http://calendar.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
