[Design of JBossCache] - Re: Serialization Compatibility Tests
by pavel.tsekov@redhat.com
I've just commited the test cases for JBossCache 1.3.0 GA and 1.4.0 GA.
Those tests can by executed by using the "compat-tests" target. Both tests fail due to issues with jgroups and some issues with jbosscache classes - see below. Please, advise whether I should mark those failures as expected.
Failed classes when testing against 1.4.0 GA:
org.jboss.cache.marshall.JBCMethodCall
org.jboss.serial.objectmetamodel.DataContainer
org.jgroups.Message
org.jgroups.blocks.DistributedHashtable
org.jgroups.blocks.DistributedLockManager$LockDecree
org.jgroups.blocks.NotificationBus$Info
org.jgroups.blocks.ReplicatedHashtable
org.jgroups.blocks.ReplicatedTree$Node
org.jgroups.blocks.ReplicatedTree$Request
org.jgroups.blocks.VotingAdapter$VoteResult
org.jgroups.demos.Draw$DrawPanel
org.jgroups.demos.MyCanvas
org.jgroups.demos.QuoteClient
org.jgroups.demos.TotalOrder
org.jgroups.demos.wb.SendDialog
org.jgroups.protocols.ENCRYPT$EncryptHeader
org.jgroups.protocols.FD_PROB$FdHeader
org.jgroups.protocols.FD_SIMPLE$FdHeader
org.jgroups.protocols.JMS$JMSAddress
org.jgroups.protocols.PerfEntry
org.jgroups.protocols.SMACK$SmackHeader
org.jgroups.protocols.TOTAL$Header
org.jgroups.protocols.TunnelHeader
org.jgroups.protocols.VIEW_SYNC$ViewSyncHeader
org.jgroups.protocols.pbcast.JoinRsp
org.jgroups.protocols.pbcast.STATE_TRANSFER$StateHeader
org.jgroups.util.List
org.jgroups.util.TimedWriter$Timeout
Failed classes when testing against 1.3.0 GA:
org.jboss.cache.OptimisticTreeNode
org.jboss.cache.optimistic.DefaultDataVersion
org.jboss.cache.optimistic.FqnComparator
org.jgroups.ChannelException
org.jgroups.MergeView
org.jgroups.Message
org.jgroups.View
org.jgroups.ViewId
org.jgroups.blocks.DistributedHashtable
org.jgroups.blocks.DistributedLockManager$LockDecree
org.jgroups.blocks.NotificationBus$Info
org.jgroups.blocks.ReplicatedHashtable
org.jgroups.blocks.ReplicatedTree$Node
org.jgroups.blocks.ReplicatedTree$Request
org.jgroups.blocks.RequestCorrelator$Header
org.jgroups.blocks.VotingAdapter$VoteResult
org.jgroups.debug.Debugger
org.jgroups.demos.Draw$DrawPanel
org.jgroups.demos.MyCanvas
org.jgroups.demos.QuoteClient
org.jgroups.demos.Topology
org.jgroups.demos.TotalOrder
org.jgroups.demos.applets.DrawApplet
org.jgroups.demos.wb.GraphPanel
org.jgroups.demos.wb.SendDialog
org.jgroups.demos.wb.Whiteboard
org.jgroups.protocols.ENCRYPT$EncryptHeader
org.jgroups.protocols.ExampleHeader
org.jgroups.protocols.FC$FcHeader
org.jgroups.protocols.FD$FdHeader
org.jgroups.protocols.FD_PROB$FdHeader
org.jgroups.protocols.FD_SIMPLE$FdHeader
org.jgroups.protocols.FD_SOCK$FdHeader
org.jgroups.protocols.FLOW_CONTROL$FCInfo
org.jgroups.protocols.HTOTAL$HTotalHeader
org.jgroups.protocols.JMS$JMSAddress
org.jgroups.protocols.PerfHeader
org.jgroups.protocols.SMACK$SmackHeader
org.jgroups.protocols.StateTransferRequest
org.jgroups.protocols.TOTAL$Header
org.jgroups.protocols.TOTAL_OLD$TotalHeader
org.jgroups.protocols.TransportedVectorTime
org.jgroups.protocols.TunnelHeader
org.jgroups.protocols.UNICAST$UnicastHeader
org.jgroups.protocols.WanPipeAddress
org.jgroups.protocols.pbcast.Digest
org.jgroups.protocols.pbcast.GMS$GmsHeader
org.jgroups.protocols.pbcast.JoinRsp
org.jgroups.protocols.pbcast.NakAckHeader
org.jgroups.protocols.pbcast.STABLE$StableHeader
org.jgroups.protocols.pbcast.STATE_TRANSFER$StateHeader
org.jgroups.stack.IpAddress
org.jgroups.util.List
org.jgroups.util.TimedWriter$Timeout
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996014#3996014
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996014
18 years
[Design of JBoss Internal Benchmarking] - Changes required in jboss-specj2004-kit-1.3.7 for using TWID
by mahendra_kutare
Hi,
I am using jboss-specj2004-kit-1.3.7 with jboss4.0.4 and MySQL 5.0.18.
My application is deployed and running fine am also able to see the JMX web console.
But when i am trying to run the TWIDDLE script ./twddle.sh it throws following NAMENOTFOUNDEXCEPTION -
[mahendra@autonomic bin]$ sh ./twiddle.sh -s 10.129.50.4 serverinfo --count
04:29:29,352 ERROR [Twiddle] Exec failed
org.jboss.util.NestedRuntimeException: jmx not bound; - nested throwable: (javax.naming.NameNotFoundException: jmx not bound) at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:143)
at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:59)
at org.jboss.console.twiddle.command.ServerInfoCommand.execute(ServerInfoCommand.java:130)
at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305)
Caused by: javax.naming.NameNotFoundException: jmx not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
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.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.console.twiddle.Twiddle.createMBeanServerConnection(Twiddle.java:250)
at org.jboss.console.twiddle.Twiddle.connect(Twiddle.java:268)
at org.jboss.console.twiddle.Twiddle.access$300(Twiddle.java:62)
at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:139)
... 3 more
Are there any specific changes required in specj2004 server instance deployed through the kit to resolve this and get TWIDDLE scripts running ??
- Mahendra
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995994#3995994
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995994
18 years