Bugs item #860175, was opened at 2003-12-14 22:35
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=860175&group_id=22866
Category: JBossMX
Group: v3.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Srivatsan (srivatsanp)
Assigned to: Scott M Stark (starksm)
>Summary: NotSerializableException when using "twiddle" for
Initial Comment:
When a XMBean has an attribute of type Element,
invoking that MBean through twiddle results in
NotSerializableException.
Please find attached the zip containing the source,
descriptors and the sar used for testing.
sh twiddle.sh invoke "jboss.test:service=TestXMBean" create
twiddle.sh: RuntimeMBeanException: null
Cause: org.jboss.util.NestedRuntimeException: error
unmarshalling return; nested exception is:
java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
org.apache.crimson.tree.ElementNode; - nested
throwable: (java.rmi.UnmarshalException: error
unmarshalling return; nested exception is:
java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
org.apache.crimson.tree.ElementNode)
I am using JBoss 3.2.1
----------------------------------------------------------------------
>Comment By: Scott M Stark (starksm)
Date: 2004-04-25 16:49
Message:
Logged In: YES
user_id=175228
This has been fixed for 3.2.4RC2 by not serializing
non-Serializable XMBean descriptor values. A dom Element may
be serializable depending on which xml parser you are using.
----------------------------------------------------------------------
Comment By: Scott M Stark (starksm)
Date: 2004-01-20 15:01
Message:
Logged In: YES
user_id=175228
twiddle obtains the MBeanInfo for the target to determine
what the operation signature is. The MBeanInfo contains the
attribute info and their descriptors including the current
value, and the Element based attribute descriptor fails to
serialize. The jmx-invoker-adaptor-server needs to filter
out the attribute info for types that are not serializable.
----------------------------------------------------------------------
Comment By: Srivatsan (srivatsanp)
Date: 2004-01-18 21:13
Message:
Logged In: YES
user_id=687037
I have already attached the zip containing the sar and
sources when submitting the bug.
The twiddle command is:
sh twiddle.sh invoke "jboss.test:service=TestXMBean" create
Thanks,
Srivatsan
----------------------------------------------------------------------
Comment By: Scott M Stark (starksm)
Date: 2004-01-15 05:05
Message:
Logged In: YES
user_id=175228
Submit the mbean as an attachment along with the twiddle
command that produces the error.
----------------------------------------------------------------------
Comment By: Srivatsan (srivatsanp)
Date: 2004-01-05 20:52
Message:
Logged In: YES
user_id=687037
I am not accessing the non serializable attribute from twiddle.
I am just invoking some other operation on the MBean. It
fails even in that case.
Thanks,
Srivatsan
----------------------------------------------------------------------
Comment By: Scott M Stark (starksm)
Date: 2004-01-05 09:10
Message:
Logged In: YES
user_id=175228
Accessing JMX over a remote channel as twiddle requires,
will only work with types that are serializable. Until the
JMX1.2 with remoting you are restricted to accessing
serializable attributes.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=860175&group_id=22866
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
