[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1430) org.jboss.jms.server.messagecounter.MessageCounter class is not Serializable

org.jboss.jms.server.messagecounter.MessageCounter class is not Serializable ---------------------------------------------------------------------------- Key: JBMESSAGING-1430 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1430 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Affects Versions: 1.4.0.SP3_CP03 Environment: JBoss Messaging 1.4.0 SP3_CP03 in JBoss EAP4.3 HP-UX B11.23 JDK 1.5.0_14 Reporter: Ji-Woong Choi Assignee: Tim Fox Fix For: 1.4.0.SP3.CP05, 1.4.1.GA Hi~ Tim There is a problem with class serialization of org.jboss.jms.server.messagecounter.MessageCounter during I am making a GUI QueueBrowser outside of JBoss container. I found that MessageCounter class was not implemented java.io.Serializable. I have to get total message count after server startup and current message count in queue for displaying data. This is the access code thru JMX: QueueMBean queueMBean = (QueueMBean) MBeanServerInvocationHandler .newProxyInstance(server, objName, QueueMBean.class, false); currentMessageCount = queueMBean.getMessageCount(); totalMessageCount = queueMBean.getMessageCounter().getCount(); Exception is following : Created LoginContext jboss.messaging.destination:service=Queue,name=testQueue java.lang.reflect.UndeclaredThrowableException at $Proxy1.getMessageCounter(Unknown Source) at com.jboss.monitor.QueueBrowser.retrieve(QueueBrowser.java:49) at com.jboss.monitor.QueueBrowser.main(QueueBrowser.java:69) Caused by: java.io.NotSerializableException: org.jboss.jms.server.messagecounter.MessageCounter at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at java.rmi.MarshalledObject.<init>(MarshalledObject.java:92) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:423) 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) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy0.getAttribute(Unknown Source) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:175) ... 3 more Is there any reason for this(not serialization)?