Link to home
Start Free TrialLog in
Avatar of AhmedFayaz
AhmedFayaz

asked on

Portal server with Wily Introscope installed fail to startup after fix pack installation

We had installed Wily Introscope agent on our Portal 6.1.5 with WAS 6.1.0.27 , and when we upgraded to WAS 6.1.0.29, Portal JVM failed to start. We had disable the Introscope Agent on Portal JVM by deleteing the JVM argument as given below
From Priamry node with wily agent argument:
${WPS_JVM_ARGUMENTS_EXT} -Dderby.system.home=${USER_INSTALL_ROOT}/PortalServer/derby -Dibm.stream.nio=true -Xgcpolicy:gencon -verbose:gc -Xverbosegclog:${SERVER_LOG_ROOT}/verbosegc.%Y%m%d.%H%M%S.%pid.txt,20,10000 -Xbootclasspath/p:/opt/Agent8.1.0.0/wily/connectors/AutoProbeConnector.jar:/opt/Agent8.1.0.0/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/opt/Agent8.1.0.0/wily/IntroscopeAgent.profile

Had to delete the follwoing argument:-
-Xbootclasspath/p:/opt/Agent8.1.0.0/wily/connectors/AutoProbeConnector.jar:/opt/Agent8.1.0.0/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/opt/Agent8.1.0.0/wily/IntroscopeAgent.profile

Whats the right argument we should use to enable WIlyIntroscopeAgent again.



ASKER CERTIFIED SOLUTION
Avatar of AhmedFayaz
AhmedFayaz

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of AhmedFayaz
AhmedFayaz

ASKER

Regenerated the AutoProdConnector.jar,this is always required when there is JAVA version change for WAS.