Menu

#34 Can't connect to Websphere

v1.2b7
open
nobody
5
2004-11-19
2004-11-19
Anonymous
No

The MC4J classloader that is trying to make the
connection to websphere does not have all the valid
classes in its classpath... eg, getting
java.lang.ClassNotFoundException:
com.ibm.websphere.management.AdminClient

When configuring a connection to websphere in step2, I
selected the server location of a local websphere
installation: c:\Program Files\WebSphere. It would not
let me specify the lib directory: c:\Program
Files\WebSphere\AppServer\lib where all the websphere
jars reside.

What's the deal? Can anyone help. Thanks.

tony.dean@sas.com

Discussion

  • Greg Hinkle

    Greg Hinkle - 2004-11-19

    Logged In: YES
    user_id=773314

    Its a bug in the beta 7 release. Its been fixed, but I've
    got a few more things to get done before I can do another
    release.

     
  • Nobody/Anonymous

    Logged In: NO

    I backed down to beta 5 and I am able to connect to the
    websphere soap connector. However, when I mc4j performs
    the QueryObjects operation a SOAP exception is returned
    from websphere. From what I can gather it appears that the
    javax.management.ObjectName class on the mc4j client side
    is imcompatible with the same class on the websphere. I
    determined that mc4jlib\JDMK\jmxri.jar, mc4jlib\JSR160
    \jmxri.jar, and mx4j-jmx1.1.1.jar all have a
    javax.management.ObjectName class and I disassembled
    these classes and they all have the same serialVersionUID.
    However the server's version in jmxc.jar does not contain an
    explicit serialVersionUID so its auto-generated and it is
    ofcourse different from the version on the client side hence
    incompatible classes. How can I get this to work? Any
    suggestions. Wait till beta 8? Pull the javax.management
    classes from server over to client... what jar should I put
    them in? Any help is appreciated.

     
  • kclarke

    kclarke - 2005-11-24

    Logged In: YES
    user_id=1387227

    In the config wizard, try sepcifying the local websphere
    installation as just c:\program files\WebSphere. When I
    picked the root level of the WAS install (which MC4J
    highlighted in bold for me) it was smart enough to bring in
    all the libs from the AppServer\lib folder. Did this today
    so it's fresh in my head.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.