JMX-RI Problem

I'm not sure where to post this... I am trying to run the jmx-ri tutorial. Everything compiles and appears to run. However, I cannot get the Agent View to show up in my browser (IE or Netscape). Instead I get a tomcat-looking directory page with nothing on it... Here is my trace output file:
(MBeanServer new) Initializing domain DefaultDomain
(MBeanServer registerMBean) ObjectName = JMImplementation:type=MBeanServerDelegate
(MBeanServer internal_addObject) Name= JMImplementation:type=MBeanServerDelegate
(Repository addMBean) name=JMImplementation:type=MBeanServerDelegate
(MBeanServer addObject) Send create notification of object JMImplementation:type=MBeanServerDelegate
(MBeanServer sendNotification) Incr sequenceNumber = 1
(DefaultLoaderRepository addClassLoader) sun.misc.Launcher$AppClassLoader@bac748
(DefaultLoaderRepository addClassLoader) sun.misc.Launcher$AppClassLoader@bac748
(MBeanServer registerMBean) ObjectName = Adaptor:name=html,port=8082
(MBeanServer internal_addObject) Name= Adaptor:name=html,port=8082
(Repository addMBean) name=Adaptor:name=html,port=8082
(MBeanServer addObject) Send create notification of object Adaptor:name=html,port=8082
(MBeanServer sendNotification) Incr sequenceNumber = 2
THANKS in advance!

You could try here:
http://archives.java.sun.com/jmx-forum.html

Similar Messages

JMX Adapter problem

Hi experts! Hope you can help me with this problems.
I have a Java WAS 2004s.
Problem number 1. In the SAPMMC, the JMX Adapter is in red. The Max Entries and the Replaced Entries nodes are in red. I tried to increase the value of the ObjectNameCompletionMaxSize from 2000 to 4000, and it was grey untill I triggered a WebDynpro application. After that, the Max Entries node became red and has the value 4000. The Replaced Entries node has the value 2842.
Is there any way of cleaning the cache and those numbers?
Problem number 2. When I deploy my webdynpro application, the messages is succesfull, but when I run it, it opens me the internet browser with the following error:
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
This application was running correctly untill yesterday morning, on the afternoon it started to send this message. Any idea of how to correct this?

Hi Pedro,
Have you managed to solve this issue?
I am currently facing this during my local portal installation!
Regards,
/Luí

JMX Authantication Problem

Hi all,
I am trying to implement 2 use case explained in http://blogs.sun.com/lmalventosa/entry/jmx_authentication_authorization..
But i got such an exception on the server side..
Also jconsole is printing some exception too. (shown bottom of this post)
Any idea about it ?
note: I am sure that password file is being used..This exception does not come for the first method.invoke is called on the Proxy..
Any help is appreciated..
Thanks..
JConsole throws this exception..
[root@martinlnx danvas] jconsole "service:jmx:rmi:///jndi/rmi://11.12.13.14:9999/moserver"
Exception in thread "Worker-Memory-service:jmx:rmi:///jndi/rmi://11.12.13.14:9999/moserver" java.lang.NullPointerException
at sun.tools.jconsole.ProxyClient.getMBeans(ProxyClient.java:263)
at sun.tools.jconsole.MemoryTab$1.run(MemoryTab.java:164)
at sun.tools.jconsole.Worker.run(Worker.java:37)
Error when synchronizing with MBeanServer : java.lang.NullPointerException
I am getting this exception on the server side.. (i mean jmx agent) .I have printed the method name for extra info here..
Method Name :getClassLoaderFor
Method Name :addNotificationListener
Method Name :queryNames
Method Name :addNotificationListener
Method Name :isInstanceOf
Method Name :getClassLoaderFor
Method Name :isInstanceOf
Method Name :isInstanceOf
java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.telenity.mgmt.jmx.MOJmxAgent$MBSFInvocationHandler.invoke(MOJmxAgent.java:196)
     at $Proxy0.isInstanceOf(Unknown Source)
     at com.sun.jmx.remote.security.MBeanServerAccessController.isInstanceOf(MBeanServerAccessController.java:439)
     at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1414)
     at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
     at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
     at javax.management.remote.rmi.RMIConnectionImpl.isInstanceOf(RMIConnectionImpl.java:892)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
     at sun.rmi.transport.Transport$1.run(Transport.java:153)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
     at java.lang.Thread.run(Thread.java:595)
Caused by: javax.management.InstanceNotFoundException: java.lang:type=Runtime
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isInstanceOf(DefaultMBeanServerInterceptor.java:1319)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.isInstanceOf(JmxMBeanServer.java:1074)
     ... 24 more
Method Name :isInstanceOf
java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)

Find the answer here: http://forum.java.sun.com/thread.jspa?forumID=537&threadID=5218024

Jmx notification problem

There is
getNotificationInfo Successful
The operation [getNotificationInfo] was successfully invoked for the MBean [bean:name=test].
The operation returned with the value:
[Ljavax.management.modelmbean.ModelMBeanNotificationInfo;@1b9d4d8
in http://127.0.0.1:9292/ and
getNotificationInfo button in jconsole doesn't print any error. But there is
21-Feb-2006 17:39:11 RequiredModelMBean getAttributes(String[])
SEVERE: Failed to get "NewNumber": javax.management.AttributeNotFoundException: getAttribute failed: NewNumber is not readable
21-Feb-2006 17:39:11 RequiredModelMBean getAttributes(String[])
SEVERE: Failed to get "NotificationInfo": javax.management.MBeanException: An exception occured while trying to get an attribute value through a RequiredModelMBean
when making some operation on the bean in jconsole. Where should I check?
Tried to extend NotificationBroadcasterSupport class instead of NotificationBroadcaster interface implementation (like is many examples in web), but that gave absolutely no affect....
In general everything must be easy.
The steps seem to be such:
Server must be started, beans must be exported to the server.
The beans that must be listened should implement NotificationBroadcaster interface or extend NotificationBroadcasterSupport class.
On the client side Notification listener on a specific bean on the server must be registered via addNotificationListener. And that addNotificationListener defines the action when notification comes. And notification listener must implement NotificationListener interface.
And that seems to be all, right?

Hi Nikolay,
If you're running on Sun's Tiger JVM you can enable the JMX logging traces:
- start your application with -Djava.util.logging.config.file=<logging.properties>
- use the logging.properties given below:
------------------------------------------logging.properties------------------------------------
handlers= java.util.logging.ConsoleHandler
.level=INFO
java.util.logging.FileHandler.pattern = %h/java%u.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter
java.util.logging.ConsoleHandler.level = FINEST
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
// Use FINER or FINEST for javax.management.remote.level - FINEST is
// very verbose...
javax.management.level=FINEST
javax.management.remote.level=FINER
------------------------------------------logging.properties------------------------------------
Alternatively you may also try to switch on the traces dynamically - see my
blog on the subject:
http://blogs.sun.com/roller/page/jmxetc?entry=tracing_jmx_what_s_going
Hope this helps,
-- daniel
JMX, SNMP, Java, etc...
http://blogs.sun.com/roller/page/jmxetc
There is
getNotificationInfo Successful
The operation [getNotificationInfo] was successfully
invoked for the MBean [bean:name=test].
The operation returned with the value:
[Ljavax.management.modelmbean.ModelMBeanNotificationIn
fo;@1b9d4d8
in http://127.0.0.1:9292/ and
getNotificationInfo button in jconsole doesn't print
any error. But there is
21-Feb-2006 17:39:11 RequiredModelMBean
getAttributes(String[])
SEVERE: Failed to get "NewNumber":
javax.management.AttributeNotFoundException:
getAttribute failed: NewNumber is not readable
21-Feb-2006 17:39:11 RequiredModelMBean
getAttributes(String[])
SEVERE: Failed to get "NotificationInfo":
javax.management.MBeanException: An exception occured
while trying to get an attribute value through a
RequiredModelMBean
when making some operation on the bean in jconsole.
Where should I check?
Tried to extend NotificationBroadcasterSupport class
instead of NotificationBroadcaster interface
implementation (like is many examples in web), but
that gave absolutely no affect....
In general everything must be easy.
The steps seem to be such:
Server must be started, beans must be exported to
to the server.
The beans that must be listened should implement
nt NotificationBroadcaster interface or extend
NotificationBroadcasterSupport class.
On the client side Notification listener on a
a specific bean on the server must be registered via
addNotificationListener. And that
addNotificationListener defines the action when
notification comes. And notification listener must
implement NotificationListener interface.
And that seems to be all, right?

JMX thread problems

We have a JMX deployment utility we wrote. It works fine for most cases but
when we get into any decent sized clustered environment we always end up
getting screwey results. For example, we have an admin server that manages
10 non-clustered managed servers. We have various developers deploying code
to these managed servers using the JMX tool. Periodically we get this
javax.management.InstanceNotFoundException. When that happens, we have to
bounce the Admin server to deploy anything new! Why should the failure of
deployment of one application to one non-clustered managed server cause the
Admin server to fail to deploy anything else to any managed server?
We've seen the javax.management.InstanceNotFoundException all over the
place. We've seen lots of other screwy errors that only happen when we
deploy to a large cluster (10 or more machines) but not with one server or
just a few managed servers.
Any ideas?
thanks

Hi,
What is the version of the weblogic server you are using and the service pack in that version?
Regards
Anilkumar kari

JMX threading problems

We have a JMX deployment utility we wrote. It works fine for most cases but
          when we get into any decent sized clustered environment we always end up
          getting screwey results. For example, we have an admin server that manages
          10 non-clustered managed servers. We have various developers deploying code
          to these managed servers using the JMX tool. Periodically we get this
          javax.management.InstanceNotFoundException. When that happens, we have to
          bounce the Admin server to deploy anything new! Why should the failure of
          deployment of one application to one non-clustered managed server cause the
          Admin server to fail to deploy anything else to any managed server?
          We've seen the javax.management.InstanceNotFoundException all over the
          place. We've seen lots of other screwy errors that only happen when we
          deploy to a large cluster (10 or more machines) but not with one server or
          just a few managed servers.
          Any ideas?
          thanks


Can you please describe the exact scenario when this exception shows up?
          Also you have posted to the wrong group, you should use weblogic.developer.interest.management , and you may get a faster answer there.

JMX Connection Problem

**Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 172.22.1.35; nested exception is:**
** java.net.ConnectException: Connection refused: connect]**
Can any body tell, what are the reasons for throwing the exception?

Rama,
The exception "ResponseTimedOutException: Participant XXXXX did not return..." indicates that a request was send to another server node, with ID XXXXX. You should investigate in the log files of the server node what happened.
It could be that the request takes more than 100 seconds to process, and you need to increase the timeout.
Or it could be that some error occures during the processing of the request, and a response is never returned.
The exception is generic and from the information that you provided it is not possible to tell.
Regards,
Ventsi Tsachev

Random jmx communication port

i have a setup with 2 node agents and 1 DAS behind a firewall.
from what i understand, in order for the node agents to communicate with the DAS, a communication channel is created on a random port via JMX.
the problem here is with the random port having to operate over a firewall. Is there any way to assign a fixed port for JMX communication?

8686 is the initial communication port for JMX,
do an "grep jmx-connector" on server.xml, you can see 3 ports as a result. Open those ports in your firewall and try.
One will be 8686 which will be for DAS-SERVER
<admin-service system-jmx-connector-name="system" type="das-and-server">another with variable JMX_SYSTEM_CONNECTOR_PORT, which you can see from admin console. This is for Server
<admin-service system-jmx-connector-name="system" type="server">another some random port number after nodeagent definition for JMX
<node-agent name="node agent name" start-servers-in-startup="true" system-jmx-connector-name="system">Regards
Activexpert

Problem with JMX Remote Port - JBoss & Apache on same machine

Hi,
I have a server which hosts Apache that uses mod_jk to pass requests to three Tomcat instances. Apache listens to port 80.
I want to install a different application on the same machine that runs on JBoss. Foreseeing the problem with port numbers, I got a different IP address (Let's say IP2, and original IP for Apache is IP1) on the same machine to run JBoss application. I changed HTTP Connector configuration in server.xml to add "address=IP1:8080" for Tomcat, "address=IP2:8080" for JBoss. I also modified Apache Listen directive in httpd.conf from "Listen 80" to "Listen IP1:80".
Now when I try to start JBoss server by running run.bat, I get below error.
Can any one please suggest how can I resolve this port conflict? Is there even a way to resolve it? As JAVA_HOME can point to a single location and both JBoss & Apache use it?
Thanks.
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\jboss
JAVA: C:\Java\jdk1.6.0_01\bin\java
JAVA_OPTS: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=
9004 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.aut
henticate=false -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.
client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: C:\Java\jdk1.6.0_01\lib\tools.jar;E:\jboss\bin\run.jar
===============================================================================
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port alr
eady in use: 9004; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
Press any key to continue . . .

What's running on JMX port without the Jboss running ?
Seems that u have something it.
Btw, try to discover how to bind JMX of portal to IP2, not to IP1 or to global Ip.

JMX over t3 problem (WLS 10.0)

Has anyone attempted to retrieve JMX data from a WebLogic 10 instance and succeeded? I am attempting to connect to a out-of-the-box installation of Weblogic Server. I am using the sample code at http://e-docs.bea.com/wls/docs100/jmx/accessWLS.html#wp1112969, yet whenever I connect I get the exception pasted below. Nothing shows up in the servers logs, but I have verified with TCPdump that the connection is occurring.
If I connect via iiop instead of t3 and set a default name/password on the iiop config page, it works. Doing so is rather insecure so I'd like to avoid that.
The exception is:
Exception in thread "main" java.io.IOException
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:156)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
at MyConnection.initConnection(MyConnection.java:55)
at MyConnection.main(MyConnection.java:123)
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
java.io.EOFException]
at weblogic.jrmp.Context.lookup(Context.java:189)
at weblogic.jrmp.Context.lookup(Context.java:195)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:144)
... 5 more
Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
java.io.EOFException
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:273)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at weblogic.jrmp.BaseRemoteRef.invoke(BaseRemoteRef.java:221)
at weblogic.jrmp.RegistryImpl_Stub.lookup(Unknown Source)
at weblogic.jrmp.Context.lookup(Context.java:185)
... 8 more
Caused by: java.io.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:243)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
... 13 more

It turned out my problem was my classpath. I pared it down to just wlclient.jar and wljxmclient.jar and that did it.

Mx4j 2.0 (jmx 1.2) class resolution problem

I'm having a problem where the resolution of the MX4J javax.management.ObjectName
getInstance() method is failing. I'm using MX4J 2.0 (jmx 1.2), and the method
that can't be found makes it look like WL is referencing jmx 1.1 or 1.0 class
files (this method does't exist prior to jmx 1.2). I've set <prefer-web-inf-classes>true</prefer-web-inf-classes>
in weblogic.xml, and put the correct MX4J jars in the war file.
Has anyone run MX4J 2.0 succesfully? Any hints?
The dump is below, any help appreciated. - jim
===
./startWebLogic.sh
Using java memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m
-XX:MaxPermSize=128m
WLS Production Mode=
CLASSPATH=/opt/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/opt/bea/weblogic81/common/lib/log4j.jar:/opt/bea/weblogic81/server/lib/debugging.jar:/opt/bea/weblogic81/server/lib/knex.jar:/opt/bea/weblogic81/javelin/lib/javelin.jar:/opt/bea/weblogic81/server/lib/wlw-lang.jar:/opt/bea/jdk141_05/lib/tools.jar:/opt/bea/weblogic81/server/lib/weblogic_sp.jar:/opt/bea/weblogic81/server/lib/weblogic.jar:/opt/bea/weblogic81/server/lib/ojdbc14.jar:/opt/bea/weblogic81/server/lib/ant/ant.jar:/opt/bea/jdk141_05/jre/lib/rt.jar:::/opt/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/opt/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/opt/bea/weblogic81/server/lib/webserviceclient.jar:/opt/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/opt/bea/weblogic81/server/lib/xbean.jar:/opt/bea/weblogic81/server/lib/wlxbean.jar:/opt/bea/weblogic81/server/lib/xqrl.jar:/opt/bea/weblogic81/server/lib/netui/netui-compiler.jar:/opt/bea/weblogic81/server/lib/wli.jar:/opt/bea/weblogic81/server/lib/fop.jar:/opt/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar:/opt/bea/weblogic81/portal/lib/wps_system.jar
PATH=/opt/bea/weblogic81/server/bin:/opt/bea/weblogic81/server/bin:/opt/bea/jdk141_05/jre/bin:/opt/bea/jdk141_05/bin:/usr/j2sdk1.4.1_03/bin:.:/sw/p4-2003.1:/usr/bin:/bin:/usr/sbin:/sbin:/usr/sbin:/usr/local/bin:/sw/bin:/usr/ccs/bin:/sw/ant-1.6.1/bin:/sw/eclipse-2.1.1/eclipse:/opt/oracle/9.2.0/bin:/opt/oracle/bin:/sw/bin:/home/qautolab1/shared/devtools/bin:/sw/ant-1.6.1/bin:/usr/local/eclipse:/opt/oracle/bin:/home/qalab01/tomcat/bin:/opt/WebSphere/AppServer/bin:/opt/bea/weblogic81/server/bin:/home/qalab01/ellington/SunOS/ptsearchlib/5.0X/lib:/home/qalab01/ellington/SunOS/ptportal/5.0/lib/native:/home/stanleyl/devtools/scripts/simple:/home/stanleyl/devtools/scripts/batch
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
=== Debugging ===
This window is necessary for debugging code using WebLogic Workshop
java version "1.4.1_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01)
Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode)
Starting WLS with line:
/opt/bea/jdk141_05/bin/java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n
-Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m
-XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic...
-Dplatform.home=/opt/bea/weblogic81 -Dwls.home=/opt/bea/weblogic81/server -Dwli.home=/opt/bea/weblogic81/integration
-Dlog4j.configuration=file:/opt/bea/weblogic81/common/lib/workshopLogCfg.xml
-Dweblogic.management.discover=true -Dejbruntime.database=pointbase44 -Dweblogic.security.SSL.ignoreHostnameVerify=false
-Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=pt_server
-Dweblogic.ProductionModeEnabled= -Djava.security.policy=/opt/bea/weblogic81/server/lib/weblogic.policy
weblogic.Server
<May 5, 2004 3:01:07 AM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic
Server with Java HotSpot(TM) Client VM Version 1.4.1_05-b01 from Sun Microsystems
Inc.>
<May 5, 2004 3:01:07 AM PDT> <Info> <Configuration Management> <BEA-150016> <This
server is being started as the administration server.>
<May 5, 2004 3:01:07 AM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic
Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883
WebLogic Portal 8.1 SP2 Thu Dec 11 22:03:57 PST 2003 148883>
<May 5, 2004 3:01:08 AM PDT> <Notice> <Management> <BEA-140005> <Loading domain
configuration from configuration repository at /opt/configlab/bea/pt_domain/./config.xml.>
<May 5, 2004 3:01:13 AM PDT> <Notice> <Log Management> <BEA-170019> <The server
log file /opt/configlab/bea/pt_domain/pt_server/pt_server.log is opened. All server
side log events will be written to this file.>
<May 5, 2004 3:01:16 AM PDT> <Notice> <Security> <BEA-090082> <Security initializing
using security realm myrealm.>
<May 5, 2004 3:01:16 AM PDT> <Notice> <WebLogicServer> <BEA-000327> <Starting
WebLogic Admin Server "pt_server" for domain "pt_domain">
<May 5, 2004 3:02:07 AM PDT> <Warning> <EJB> <BEA-014006> <The message driven
bean (MDB) named "ProcessTrackingEventErrorListener" has a dispatch policy "wli.internal.ProcessTracking"
that refers to an unknown execute queue thread pool. The default execute thread
pool will be used instead.>
<May 5, 2004 3:02:07 AM PDT> <Warning> <EJB> <BEA-014006> <The message driven
bean (MDB) named "InstanceInfoEventListener" has a dispatch policy "wli.internal.ProcessInstanceInfo"
that refers to an unknown execute queue thread pool. The default execute thread
pool will be used instead.>
<May 5, 2004 3:02:07 AM PDT> <Warning> <EJB> <BEA-014006> <The message driven
bean (MDB) named "ProcessTrackingEventListener" has a dispatch policy "wli.internal.ProcessTracking"
that refers to an unknown execute queue thread pool. The default execute thread
pool will be used instead.>
Initializing filter BinaryGatewayFilter... DONE.
33 05-05 03:02:50 portal_ui_infrastructure FATAL 1 (main)
PTAppWarmUpHelper Error creating directory var pack.java.lang.NoSuchMethodError:
javax.management.ObjectName.getInstance(Ljava/lang/String;)Ljavax/management/ObjectName;
at com.plumtree.openkernel.impl.sysmgmt.jmx.JMXService.RegisterMBean(JMXService.java:288)
at com.plumtree.openkernel.impl.sysmgmt.jmx.JMXService.RegisterObservableObject(JMXService.java:252)
at com.plumtree.openkernel.impl.sysmgmt.SysMgr.RegisterObservableObject(SysMgr.java:269)
at com.plumtree.openkernel.impl.sysmgmt.SysMgr.RegisterObservableObject(SysMgr.java:279)
at com.plumtree.openkernel.impl.sysmgmt.counters.Counter.RegisterCounterInstanceMBean(Counter.java:720)
at com.plumtree.openkernel.impl.sysmgmt.counters.Counter.AddInstance(Counter.java:548)
at com.plumtree.openkernel.impl.sysmgmt.counters.CounterCategory.AddCategoryCounterInstance(CounterCategory.java:168)
at com.plumtree.openkernel.impl.sysmgmt.counters.CounterCategory.AddCategoryCounterInstances(CounterCategory.java:203)
at com.plumtree.openkernel.impl.sysmgmt.counters.CounterMgr.RefreshCPPMetadata(CounterMgr.java:1757)
at com.plumtree.openkernel.impl.sysmgmt.counters.CounterMgr.RefreshCPPMetadata(CounterMgr.java:1721)
at com.plumtree.openkernel.impl.sysmgmt.SysMgr.Startup(SysMgr.java:161)
at com.plumtree.openkernel.OpenKernel.StartService(OpenKernel.java:757)
at com.plumtree.openkernel.OpenKernel.Startup(OpenKernel.java:343)
at com.plumtree.openkernel.OpenKernel.Init(OpenKernel.java:278)
at com.plumtree.openkernel.OpenKernel.Init(OpenKernel.java:96)
at com.plumtree.server.PortalObjectsFactory.Init(PortalObjectsFactory.java:52)
at com.plumtree.server.PortalObjectsFactory.CreateSession(PortalObjectsFactory.java:137)
at com.plumtree.portaluiinfrastructure.application.varpacks.PTDirPrefsVarPack.Load(PTDirPrefsVarPack.java:228)
at com.plumtree.uiinfrastructure.web.BaseVarPack.LoadVarPack(BaseVarPack.java:164)
at com.plumtree.portaluiinfrastructure.application.PTAppWarmUpHelper.LoadCustomVarPacks(PTAppWarmUpHelper.java:100)
at com.plumtree.uiinfrastructure.application.AppWarmUp.Init(AppWarmUp.java:556)
at com.plumtree.portal50.application.AppWarmUpServlet.init(AppWarmUpServlet.java:174)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:993)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:869)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3197)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3174)
at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:688)
at weblogic.servlet.internal.WebService.preloadResources(WebService.java:483)
at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
at weblogic.Server.main(Server.java:32)

From Metalink Note 236914.1:
Solution
To fix this check that you have your oui HOME in the location
C:\program files\oracle
If not. Copy the whole oracle folder from where your OUI HOME are now and place it under c:\program files
Change your inst_loc variable in the registry to c:\program files\oracle\inventory
The location of this variable in the registry is HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
Now apply the patch with opatch
After the patch has been applied you can of course move your oui HOME back again but remember to update your inst_loc variable in the registry.
RELATED DOCUMENTS
Note:229626.1 How to apply interim patches and the functionality of opatch on Windows
Business Intelligence Beans Product Management Team
Oracle Corporation

Problems with WSAD 5.1.1 and JMX

Hi At All!
I'm really newbie with JMX and i'm trying to implement a quick-and-dirty client JMX which connect with a server using IIOP://. I'm using a WSAD 5.1.1
When try to execute, throws the next exception:
"Exception in thread "P=xxxxxx:O=0:CT" java.lang.NoSuchMethodError: com.ibm.ws.orbimpl.transport.WSTCPTransportConnection: method getConnectTimeout()I not found"
I don't understand what's happens!
The client code is this:
String jndiPath="/jndi/JMXConnector";
String urlString = "service:jmx:iiop://127.0.0.1:2809" +jndiPath;
JMXServiceURL url = new JMXServiceURL(urlString);
Hashtable h = new Hashtable();
h.put(InitialContext.PROVIDER_URL,"corbaloc:iiop:1.0@localhost:2809/NameService");
h.put(InitialContext.PROVIDER_URL,"corbaloc:iiop:1.0@localhost:2809/HelloAgent");
h.put(InitialContext.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
try{
JMXConnector jmxc = (JMXConnector) JMXConnectorFactory.connect(url,h);
JMXConnectorFactory.connect(url);
MBeanServerConnection mbsc = jmxc.getMBeanServerConnection();}
catch(Exception e){
System.out.println("Error creating connection:");
e.printStackTrace();
Reading in forums I put the following jars in the client side
naming.jar;namingclient.jar;jtsPrivate.jar;
jmx-ri.jar;jmxremote.jar;ecutils.jar;
bootstrap.jar; ffdc.jar; idl.jar;
sas.jar; admin.jar; wsexception.jar;
jmxc.jar; jmxext.jar; jmxx.jar;
wasjmx.jar;ras.jar; iwsorb.jar;
ibmorb.jar; ibmorbapi.jar
Also i configure the implfactory.properties as follows:
#Config Repository Remote Client
com.ibm.websphere.management.repository.client.ConfigRepositoryClient.remote=
com.ibm.ws.management.repository.client.JMXRemoteConfigRepositoryClient
I hope your answers and thanks in advance!
Best Regards!
PD: Sorry my poor english!

Same problem since last night (imac 2.5 i5, Lion 10.7.4, Safari 5.1.7).

Problem start JavaService with JMX agent

My application start ok in console with password authenticate set to true. I have the password file configured correctly under my login account. however, when I start my application with the Windows Service created by JavaService, it failed with the authentication option. I am pretty sure it's the password file permission failed it. but don't know the workaround. Here is the setting for JavaService setting:
JavaService -install MyServer "C:\Program Files\Java\jre1.5.0_07\bin\client\jvm.dll" -Xrs -Xms67108864 -Xmx524288000 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8004 -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.password.file=C:\JConsoleAccess\jmxremote.password -Djava.class.path=[JarFiles]; -start com.MyServer -params D:\MyServer\bin\Config.ini -stop com.ShutdownThread -current d:\myserver\bin -shutdown 90 -description "My Application Server"
Note: if I set authenticate option to false, it works just fine.

Hi,
I think your problem might be due to a file read access problem due to the fact that you're running
a Java service probably as SYSTEM but your jmxremote.password file was created with another
USER and SYSTEM cannot read it. Run "cacls C:\JConsoleAccess\jmxremote.password" in order
to check the privileges of the password file.
Have a look also at "How to secure the password file on Windows systems?" in the JConsole FAQ:
http://java.sun.com/javase/6/docs/technotes/guides/management/faq.html#win3
Regards,
Luis-Miguel Alventosa - JMX/JConsole dev team - http://blogs.sun.com/lmalventosa

JMX Problem - Retriving Physical Address (MAC)

Hello Everybody,
I am working in a class that has to poll information from a router using SNMP protocol and I am using JMX's API
specification, for all the scalars and values that have a string representation works well, but when I am polling
the information from the MAC address - which is represented in Hexadecimal format I retrieve a Variable Binding
with IOD and Value, where the value is complete wired, I do not know why I can not represent the value since the
method I am trying to use cast it to String, I really tried different appoaches and also other clases like Vector
or List for solve the problem but seems that the value has not been interpreted in the correct way, and that's why
I would like to hear if someboday has been experienced the same situation and what suggestions you can offer to me
for solve the problem.
Thanks,
Al
//Code definitions for variables and declarations
final SnmpVarBindList Iteratorlist = new SnmpVarBindList("SyncManager varbind list");
for (int j=1; j<=i; j++)
Iteratorlist.addVarBind("1.3.6.1.2.1.2.2.1.6." + j);
SnmpRequest requestIterator = session1.snmpGetRequest(null, Iteratorlist);
//... Code for validate complete request and errors, etc.
final SnmpVarBindList resultIterator = requestIterator.getResponseVarBindList();
for (int j=0; j<resultIterator.getVarBindCount(); j++)
SnmpVarBind bind2 = resultIterator.getVarBindAt(j);
println(">>Val " + bind2.getStringValue());
println(">>ValStr " + bind2.getStringValue().toString());
println(">>Length " + bind2.getStringValue().length());
// ... code for other manipulations

Just to be sure ....you know bytes are NOT characters in java?
From your posting it is not clear if you are having a problem converting a binary value to a string value, or if you are having trouble getting to the value at all.
Keep in mind that the "SNMP protocol" in of itself is almost worthless in describing the format of the data that you will get back. A MIB of course is much more useful.
Normally I would expect an octet string for a MAC address.

Coherence 3.4.2 JMX: invoking operation problem

Hi,
we have run into two issues invoking JMX ModelMBean operations via JMX in Coherence 3.4.2
1. if a JMX operation has got any parameters /like doFoo(String a)/
it can not be invoked at all
this issue can be worked around by overriding RequiredJMXBean.invoke()
2. if any of a JMX operation's parameters is of a primitive type /doFoo(int i)/
a different error message is generated
this issue can not be worked around by overriding RequiredJMXBean.invoke()
because RequiredJMXBean.invoke() doesn't get invoked in this case
---here's sample code, a full project, 4 files total ---
/* please put this into src/main/java/foo/c34/Main.java */
package foo.c34;
import javax.management.MBeanParameterInfo;
import javax.management.modelmbean.ModelMBeanAttributeInfo;
import javax.management.modelmbean.ModelMBeanConstructorInfo;
import javax.management.modelmbean.ModelMBeanInfo;
import javax.management.modelmbean.ModelMBeanInfoSupport;
import javax.management.modelmbean.ModelMBeanNotificationInfo;
import javax.management.modelmbean.ModelMBeanOperationInfo;
import javax.management.modelmbean.RequiredModelMBean;
import com.tangosol.net.CacheFactory;
import com.tangosol.net.management.Registry;
* This sample program demonstrates Coherence 3.4.2 JMX difficulties with invoking methods
* Please invoke this program with
* -Dcom.sun.management.jmxremote
* otherwise bean "Coherence" won't be exposed in JMX console
* Not sure why this is necessary because this would imply this is no longer required
* http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
* ===
* To see the problem please try invoking method "operation1" and "operation2"
* via JMX console.
* Different error messages will be shown for each method
* To work around "operation1" problem please comment out this line
* final RequiredModelMBean rmb = new RequiredModelMBean();
* land uncomment the alternative one
* final RequiredModelMBean rmb = new WorkaroundRequiredModelMBean();
* You shall be able to invoke "operation1" then.
* Please note that you still won't be able to invoke "operation2"
public class Main {
   public static void main(final String[] args) throws Exception {
      configureProperties();
      Registry registry = CacheFactory.ensureCluster().getManagement();
      final RequiredModelMBean rmb = new RequiredModelMBean();
      //final RequiredModelMBean rmb = new WorkaroundRequiredModelMBean();
      final ModelMBeanInfo mbi = createModelMBeanInfo();
      rmb.setModelMBeanInfo(mbi);
      final Object managed = new Managed();
      rmb.setManagedResource(managed, "ObjectReference");
      final String name = registry.ensureGlobalName("type=A");
      registry.register(name, rmb);
      for (;;) {
         Thread.sleep(1000);
   private static ModelMBeanInfo createModelMBeanInfo() {
      final MBeanParameterInfo p1 = new MBeanParameterInfo("a", "java.lang.Integer", "a desc");
      final MBeanParameterInfo p2 = new MBeanParameterInfo("a", "int", "a desc");
      final ModelMBeanOperationInfo op1 = new ModelMBeanOperationInfo("operation1", "operation 1",
            new MBeanParameterInfo[]{p1}, "void", ModelMBeanOperationInfo.UNKNOWN);
      final ModelMBeanOperationInfo op2 = new ModelMBeanOperationInfo("operation2", "operation 2",
            new MBeanParameterInfo[]{p2}, "void", ModelMBeanOperationInfo.UNKNOWN);
      return new ModelMBeanInfoSupport("foo", "desc", new ModelMBeanAttributeInfo[0],
            new ModelMBeanConstructorInfo[0], new ModelMBeanOperationInfo[]{op1, op2},
                  new ModelMBeanNotificationInfo[0]);
   public static class Managed {
      public void operation1(Integer p1) {
         System.out.println("operation1 invoked p1=" + p1);
      public void operation2(int p2) {
         System.out.println("operation2 invoked p2=" + p2);
   private static void configureProperties() {
      System.setProperty("tangosol.coherence.cacheconfig", "a-cache-config.xml");
      System.setProperty("tangosol.coherence.ttl", "0");
      System.setProperty("tangosol.coherence.log", "jdk");
      System.setProperty("tangosol.coherence.log.level", "9");
      System.setProperty("tangosol.coherence.clusterport", "5878");
      System.setProperty("com.sun.management.jmxremote", "");
      System.setProperty("tangosol.coherence.management", "all");
      System.setProperty("tangosol.coherence.management.remote", "true");
/* please put this into src/main/java/foo/c34/WorkaroundRequiredModelMBean.java */
package foo.c34;
import javax.management.MBeanException;
import javax.management.ReflectionException;
import javax.management.RuntimeOperationsException;
import javax.management.modelmbean.RequiredModelMBean;
public class WorkaroundRequiredModelMBean extends RequiredModelMBean {
   public WorkaroundRequiredModelMBean() throws MBeanException, RuntimeOperationsException {
   public Object invoke(final String opName, final Object[] params,
         final String[] signature) throws MBeanException, ReflectionException {
      final String[] fakeSignature = fakeSignature(opName);
      return super.invoke(opName, params, fakeSignature);
   protected String[] fakeSignature(final String methodName) {
      if (methodName.equals("operation1")) {
         return new String[]{"java.lang.Integer"};
      if (methodName.equals("operation2")) {
         return new String[]{"int"};
      return new String[0];
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">

<cache-config>
   <caching-scheme-mapping>
      <cache-mapping>
         <cache-name>*</cache-name>
         <scheme-name>AAA</scheme-name>
      </cache-mapping>
   </caching-scheme-mapping>
   <caching-schemes>
      <local-scheme>
         <scheme-name>AAALocal</scheme-name>
         <autostart>true</autostart>
         <high-units>0</high-units>
      </local-scheme>
      <distributed-scheme>
         <scheme-name>AAA</scheme-name>
         <service-name>AAACache</service-name>
         <backing-map-scheme>
            <local-scheme>
               <scheme-ref>AAALocal</scheme-ref>
            </local-scheme>
         </backing-map-scheme>
         <autostart>true</autostart>
      </distributed-scheme>
   </caching-schemes>
</cache-config>

<project xmlns="http://maven.apache.org/POM/4.0.0"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>foo-group</groupId>
   <artifactId>c34-jmx-demo</artifactId>
   <name>Coherence 34 JMX Demo</name>
   <version>0.0.1-SNAPSHOT</version>
   <description>Demonstrate Coherece 3.4 JMX Difficulties</description>
   <dependencies>
      <dependency>
         <groupId>com.oracle</groupId>
         <artifactId>coherence</artifactId>
         <version>3.4.2</version>
      </dependency>
   </dependencies>
</project>

Hi Dave,
I wanted to let you know that we do not have an answer yet but we are looking into it. Thanks!
Out of curiosity what type of impact is this having with your application?We've managed to temporarily work around both of the issues.
Of course we shall be very glad to remove the work-arounds when it becomes possible.

JMX-RI Problem

Similar Messages

Maybe you are looking for