HP-UX Workload Manager Toolkits A.01.07.01 Release Notes for HP-UX 11.0, HP-UX 11i V1, and HP-UX 11i V2

Workaround This message typically occurs when your system has no more processors available for
activation. (The message is not an indication that utilitydc failed to operate normally.)
WebLogicTK: javax/security/auth/callback/CallbackHandler error
Issue Monitoring a WebLogic instance with wlmwlsdc can produce a
javax/security/auth/callback/CallbackHandler error.
In particular, running the wlmwlsdc data collector with a single argument:
% /opt/wlm/toolkits/weblogic/bin/wlmwlsdc \
/home/wladmin/wlm/myinstA.props
on a version of WebLogic other than 7.0 can produce the following error:
Exception in thread "main" java.lang.NoClassDefFoundError:
nl
javax/security/auth/callback/CallbackHandler
nl
at weblogic.jndi.Environment.getContext(Environment.java:164)
nl
at weblogic.jndi.Environment.getInitialContext(Environment.java:143)
nl
at weblogic.management.Helper.getMBeanHomeForName(Helper.java:94)
nl
at weblogic.management.Helper.getMBeanHome(Helper.java:59)
nl
at com.hp.wrm.tk.weblogic.ExecQueueFetcher.connect2localhome(ExecQueueFetcher.java:328)
nl
at
nl
com.hp.wrm.tk.weblogic.ExecQueueFetcher.fetch(ExecQueueFetcher.java:224)
nl
at com.hp.wrm.tk.DataCollector.run(DataCollector.java:355)
nl
at com.hp.wrm.tk.DataCollector.run(DataCollector.java:434)
nl
at
nl
com.hp.wrm.tk.weblogic.ExecQueueDataCollector.main(ExecQueueDataCollector.java:67)
This message occurs when the WL_HOME environment variable has been set to
override wlmwlsdc’s default, but wlmwlsdc is using a JAVA_HOME variable
set to /opt/java1.3, which is not supported by WebLogic 8.1.
Workaround Provide a setting for both JAVA_HOME and WL_HOME when using WLS 8.1.
There are two ways for settings these variables, as explained below.
• Use a custom shell file
You can provide custom environment variables in a new file specified when
you invoke wlmwlsdc:
% /opt/wlm/toolkits/weblogic/bin/wlmwlsdc
\ /home/wladmin/wlm/myinstA.props \
my_custom_env_settings.sh
The file my_custom_env_settings.sh contains the lines:
JAVA_HOME=/opt/java1.4
nl
WL_HOME=/opt/bea/weblogic81
To invoke wlmwlsdc with this file inside a WLM configuration file, your
coll_argv statement would be as follows:
coll_argv = {
wlmrcvdc /opt/wlm/toolkits/weblogic/bin/wlmwlsdc
nl
/home/wladmin/wlm/myinstA.props
my_custom_env_settings.sh
}
• Use an existing setEnv.sh file
You can provide the custom environment variables using an existing setEnv.sh
file, which you specify when invoking wlmwlsdc as follows:
% /opt/wlm/toolkits/weblogic/bin/wlmwlsdc
\ /home/wladmin/wlm/myinstA.props \
/opt/bea/user_projects/domains/mydomain/setEnv.sh
The /opt/bea/user_projects/domains/mydomain/setEnv.sh file is produced
when the instance is created with the WebLogic tools.
Known problems and workarounds 9