Are you running the java command with the WebLogic jvm or a standard system JVM?
I would add a -Dlog=debug to your command. It may give you a bit more visibility into why its failing.
>From there, open up sigar to see what the process looks like. Make sure to run it as the same UID.
java -jar sigar.jar
> ps State.Name.eq=java
Identify the Weblogic server, and grab its pid
>pargs <pid>
That will display the command line args that sigar has visibility into for the process that helps it identify the app server.
The plugin by default looks for a process query like this:
State.Name.eq=java,Args.-1.eq=weblogic.Server
For 9.1 specifically(possibly 10 as well) it also looks for this:
-Dweblogic.management.server
You can try this in Sigar to see if a match shows up.
If your process arguments are different than this, than it can explain why auto discovery is failing.
|
