Results 1 to 10 of 11

Thread: Spring JMX and Weblogic 8.1.4

Hybrid View

  1. #1

    Default Spring JMX and Weblogic 8.1.4

    I am testing Spring JMX and weblogic 8.1.4

    I am able to register mbean with the server. I can see my bean via MC4J. However when I am trying to invoke the method I am getting this exception:

    java.lang.reflect.UndeclaredThrowableException at $Proxy10.invoke(Unknown Source) at org.mc4j.console.bean.operation.OperationExecution ResultsVisualPanel$2.run(OperationExecutionResults VisualPanel.java:126) at java.lang.Thread.run(Thread.java:534) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.mc4j.console.connection.proxy.GenericMBeanServ erProxy.invoke(GenericMBeanServerProxy.java:79) ... 3 more Caused by: javax.management.ReflectionException: The target object class class javax.management.modelmbean.ModelMBeanOperationInf o could not be found at weblogic.rjvm.BasicOutboundRequest.sendReceive(Bas icOutboundRequest.java:108) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicR emoteRef.java:137) at weblogic.management.internal.RemoteMBeanServerImpl _814_WLStub.invoke(Unknown Source) ... 8 more java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.mc4j.console.connection.proxy.GenericMBeanServ erProxy.invoke(GenericMBeanServerProxy.java:79) at $Proxy10.invoke(Unknown Source) at org.mc4j.console.bean.operation.OperationExecution ResultsVisualPanel$2.run(OperationExecutionResults VisualPanel.java:126) at java.lang.Thread.run(Thread.java:534) Caused by: javax.management.ReflectionException: The target object class class javax.management.modelmbean.ModelMBeanOperationInf o could not be found at weblogic.rjvm.BasicOutboundRequest.sendReceive(Bas icOutboundRequest.java:108) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicR emoteRef.java:137) at weblogic.management.internal.RemoteMBeanServerImpl _814_WLStub.invoke(Unknown Source) ... 8 more javax.management.ReflectionException: The target object class class javax.management.modelmbean.ModelMBeanOperationInf o could not be found at weblogic.rjvm.BasicOutboundRequest.sendReceive(Bas icOutboundRequest.java:108) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicR emoteRef.java:137) at weblogic.management.internal.RemoteMBeanServerImpl _814_WLStub.invoke(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.mc4j.console.connection.proxy.GenericMBeanServ erProxy.invoke(GenericMBeanServerProxy.java:79) at $Proxy10.invoke(Unknown Source) at org.mc4j.console.bean.operation.OperationExecution ResultsVisualPanel$2.run(OperationExecutionResults VisualPanel.java:126) at java.lang.Thread.run(Thread.java:534)
    Here is a snippet of my configuration:

    Code:
    	<bean id="profilingInterceptor" class="shaw.spectrum.framework.aop.ProfilingInterceptor">
    		<property name="enableProfiling" value="true"/>
    	</bean>
    	
    	<bean id="adapter" class="org.springframework.jmx.export.MBeanExporter">
    		<property name="beans">
    			<map>
    				<entry key="spring:name=profilingInterceptor" value-ref="profilingInterceptor"/>
    			</map>
    		</property>
    		<property name="server" ref="mbeanServer"/>
    	</bean>
    	
    	<bean id="mbeanServer" class="org.springframework.jmx.support.WebLogicJndiMBeanServerFactoryBean">
    	</bean>
    I appreciate any help.

    Thanks,

    Vitaliy

  2. #2

    Default

    After some digging here is what I discovered.

    I am using Spring 1.2.6 with Weblogic 8.1 SP4 (JDK 1.4.2-05). Trying to connect from MC4J 1.2 beta 9. What interesting is that exception referes to the missing file javax.management.modelmbean.ModelMBeanOperationInf o which is part of JDK 1.5.

    MC4J 1.2 b9 says that 1.4 is supported but 1.5 is recommended. I will try to upgrade to 1.5 but I am curious if anybody else had similar problem.

    Thanks,
    Vitaliy

  3. #3
    Join Date
    Jan 2005
    Location
    Bucharest, Romania
    Posts
    5,403

    Default

    Try using a different jmx console (a servlet base if you want) and see how it behaves. If you don't get any exception then is a problem with the client pretty much.
    Costin Leau
    SpringSource - http://www.SpringSource.com- Spring Training, Consulting, and Support - "From the Source"
    http://twitter.com/costinl
    Please use [ c o d e ] [ / c o d e ] tags

  4. #4

    Default

    That was my thought exactly but I tried jManage and got exactly same message. I tried both clients against same weblogic instance too.

    Vitaliy

  5. #5
    Join Date
    Jan 2005
    Location
    Bucharest, Romania
    Posts
    5,403

    Default

    Does weblogic runs on jdk 1.5 while your client on an older jdk? The notifications send across the wire might be incompatible.
    Costin Leau
    SpringSource - http://www.SpringSource.com- Spring Training, Consulting, and Support - "From the Source"
    http://twitter.com/costinl
    Please use [ c o d e ] [ / c o d e ] tags

  6. #6

    Default

    I don't have jdk 1.5 installed on my computer. JAVA_HOME is set to jdk inside of bea installation.

    Vitaliy

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •