Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3 - Websphere

This is a discussion on Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3 - Websphere ; I install WSRR 6.3 just fine on WAS 6.1.0.25 (on Windows 2003) I try to install on WAS 7.0 (if it matters - on Windows 2008) - the deployment of WSRR fails in relative advanced step as can be seen ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

  1. Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    I install WSRR 6.3 just fine on WAS 6.1.0.25 (on Windows 2003)
    I try to install on WAS 7.0 (if it matters - on Windows 2008) - the deployment of WSRR fails in relative advanced step as can be seen in log messages below, thanks

    [wsadmin] Check WSRR enterprise applications are started
    [wsadmin] Check for WSRR JDBC DataSources
    [wsadmin] DataSource jdbc/WSRRTSDB exists.
    [wsadmin] Checking for WSRR WorkManager and Scheduler
    [wsadmin] WorkManager WSRRWorkManager found.
    [wsadmin] Scheduler WSRRScheduler found.
    [wsadmin] Checking for WSRR SIBus
    [wsadmin] Found SIBus ServiceRegistryBus
    [wsadmin] Check for WSRR Admin MBean
    [wsadmin] Testing connection to WSRR TS datasource
    [wsadmin] Check for a running WSRR server
    [wsadmin] Using server...
    [wsadmin] cell: samwin28-001Node01Cell, node: samwin28-001Node01, server: server1
    [wsadmin] Located ServiceRegistryRepository MBean
    [wsadmin] Found ServiceRegistryRepository MBean at: WebSphere:name=ServiceRegistryRepository,process=s erver1,platform=dynamicproxy,node=samwin28-001Node01,version=7.0.0.3,type=ServiceRegistryRepo sitory,mbeanIdentifier=ServiceRegistryRepository,c ell=samwin28-001Node01Cell,spec=1.0
    [wsadmin] Backing up and deleting any existing default or governance profiles
    [wsadmin] WASX7017E: Exception received while running file "C:\PROGRA~1\IBM\WEBSPH~1\SERVIC~1\install\\jython\ verifywas.py"; exception information: javax.management.MBeanException
    [wsadmin] java.lang.NullPointerException: java.lang.NullPointerException


    BUILD FAILED
    C:\PROGRA~1\IBM\WEBSPH~1\SERVIC~1\install\installs r.xml:370: The following error occurred while executing this line:
    C:\PROGRA~1\IBM\WEBSPH~1\SERVIC~1\install\installs r.xml:631: Java returned: 105

    Total time: 25 minutes 54 seconds

  2. Re: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    Turned on wsadmin trace and attach here wsadmin.traceout for this error,
    it seems these 2 lines are indicative of the exact java cause, waiting for hint

    Caused by: java.lang.NullPointerException
    at com.ibm.ws.classloader.CompoundClassLoader.library ClassLoadersFindResource(CompoundClassLoader.java: 922)

  3. Re: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    I am facing the same problem with windows 2003 server.

    Any solution

  4. Re: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    I too face the same issue in windows 2003 server. Did you found any solution for this. waiting for your reply.

    Thanks in advance

  5. Re: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    I did not encounter a solution yet for above problem on WAS 7.0.0.3 on Windows 2008.
    In addition - when trying 7.0.0.5 there is another problem - the WAS JDK is not recognized
    (definitely a WSRR bug, recorded in separate thread of this forum).
    I have hopes for the first fixpak of WSRR 6.3, not sure.

  6. Re: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    Thanks for the reply.

    When i started to see the issue, i encountered a code which is trying to read the profiles, because of the profiles are missing ( BasicProfile_v63 and GovernanceEnablementProfile_v63) and the JMX failed to locate the profiles and it throws null pointer exception.

    so now i am checking is there any way to place the profiles and make to work or i need to raise a PMR with IBM.

  7. Re: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    I believe this exception indicates that the application that registered the MBean (or some application that the MBean interacts with) has been stopped, which is likely to cause problems. That said, I suspect the NPE is a WAS product defect.

  8. Re: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    With FP001 of WSRR 6.3 problem does not occur any more on Windows 2008

  9. Re: Deploy WSRR 6.3 fails MBeanException on WAS 7.0.0.3

    Wow thats good. can you give me the link to download the FP001

+ Reply to Thread