[SOLVED] Sim-eth-basic on android

Rushline · June 10, 2019, 1:31pm

ran the server with a windows client success and android client fail and compared the logs. In the Server Debugger, I’m not get passed the setClient(client) callable for the Android client.

@pspeed

I don’t think i’m registering classes after the server has been started… however I’ve seen the number(ing) of the classes vary…

The win server side logs… with the delay code from tonihele in Gameserver ( thank you)
(sorry… if this didn’t format… not sure howto yet )

20:31:36,967 INFO  [GameServer] Initializing game systems...
20:31:36,968 INFO  [GameServer] Starting game server...
20:31:37,204 DEBUG [SelectorKernel] Hosting TCP connection:0.0.0.0/0.0.0.0:4000.
20:31:37,205 DEBUG [SelectorKernel] Kernel started for connection:0.0.0.0/0.0.0.0:4000.
20:31:37,210 DEBUG [UdpKernel] Hosting UDP connection:0.0.0.0/0.0.0.0:4000.
20:31:37,210 DEBUG [UdpKernel] Kernel started for connection:0.0.0.0/0.0.0.0:4000.
20:31:37,211 DEBUG [SelectorKernel] Hosting TCP connection:0.0.0.0/0.0.0.0:4001.
20:31:37,212 DEBUG [ServiceManager] Starting service:com.jme3.network.service.serializer.ServerSerializerRegistrationsService[serviceManager.class=class com.jme3.network.service.HostedServiceManager]
20:31:37,212 DEBUG [SelectorKernel] Kernel started for connection:0.0.0.0/0.0.0.0:4001.
20:31:37,213 DEBUG [SerializerRegistrationsMessage] Number of registered classes:14
20:31:37,213 DEBUG [SerializerRegistrationsMessage]     Registration[-19 = com.jme3.math.Vector3f, serializer=com.jme3.network.serializing.serializers.Vector3Serializer]
20:31:37,213 DEBUG [SerializerRegistrationsMessage]     Registration[-41 = com.jme3.network.serializing.serializers.FieldSerializer, serializer=null]
20:31:37,213 DEBUG [SerializerRegistrationsMessage]     Registration[-43 = [I, serializer=com.jme3.network.serializing.serializers.ArraySerializer]
20:31:37,213 DEBUG [SerializerRegistrationsMessage]     Registration[-46 = [Lcom.jme3.network.message.SerializerRegistrationsMessage$Registration;, serializer=com.jme3.network.serializing.serializers.ArraySerializer]
20:31:37,213 DEBUG [SerializerRegistrationsMessage]     Registration[-49 = [Ljava.lang.Object;, serializer=com.jme3.network.serializing.serializers.ArraySerializer]
20:31:37,213 DEBUG [SerializerRegistrationsMessage]     Registration[-48 = com.jme3.network.service.rpc.msg.RpcCallMessage, serializer=null]
20:31:37,213 DEBUG [SerializerRegistrationsMessage]     Registration[-50 = com.jme3.network.service.rpc.msg.RpcResponseMessage, serializer=null]
20:31:37,214 DEBUG [SerializerRegistrationsMessage]     Registration[-51 = com.jme3.network.service.rmi.ClassInfo, serializer=null]
20:31:37,214 DEBUG [SerializerRegistrationsMessage]     Registration[-52 = com.jme3.network.service.rmi.MethodInfo, serializer=null]
20:31:37,214 DEBUG [SerializerRegistrationsMessage]     Registration[-53 = com.jme3.math.Quaternion, serializer=null]
20:31:37,214 DEBUG [SerializerRegistrationsMessage]     Registration[-54 = com.simsilica.ethereal.net.ClientStateMessage, serializer=null]
20:31:37,214 DEBUG [SerializerRegistrationsMessage]     Registration[-56 = [B, serializer=com.jme3.network.serializing.serializers.ArraySerializer]
20:31:37,214 DEBUG [SerializerRegistrationsMessage]     Registration[-55 = com.simsilica.ethereal.net.ObjectStateMessage, serializer=null]
20:31:37,214 DEBUG [SerializerRegistrationsMessage]     Registration[-57 = com.simsilica.mathd.Vec3d, serializer=null]
20:31:37,214 DEBUG [ServiceManager] Starting service:example.net.server.GameServer$DelayService[serviceManager.class=class com.jme3.network.service.HostedServiceManager]
DelayService.start()
DelayService.delay done
20:31:42,214 DEBUG [ServiceManager] Starting service:com.jme3.network.service.rpc.RpcHostedService[serviceManager.class=class com.jme3.network.service.HostedServiceManager]
20:31:42,214 DEBUG [ServiceManager] Starting service:com.jme3.network.service.rmi.RmiHostedService[serviceManager.class=class com.jme3.network.service.HostedServiceManager]
20:31:42,214 DEBUG [ServiceManager] Starting service:example.net.server.AccountHostedService[serviceManager.class=class com.jme3.network.service.HostedServiceManager]
20:31:42,214 DEBUG [ServiceManager] Starting service:example.net.server.GameSessionHostedService[serviceManager.class=class com.jme3.network.service.HostedServiceManager]
20:31:42,214 DEBUG [ServiceManager] Starting service:example.net.chat.server.ChatHostedService[serviceManager.class=class com.jme3.network.service.HostedServiceManager]
20:31:42,214 DEBUG [ServiceManager] Starting service:com.simsilica.ethereal.EtherealHost[serviceManager.class=class com.jme3.network.service.HostedServiceManager]
20:31:42,215 INFO  [StateCollector] Starting state collector.
20:31:42,215 INFO  [GameServer] Game server started.

Ali_RS · June 10, 2019, 3:40pm

pspeed · June 10, 2019, 6:05pm

Hmmm… that shouldn’t be the case. If you are always registering the classes the same then there should be consistent ordering/numbering.

Ali_RS · June 12, 2019, 7:33pm

Seems to be related:

mitm · June 12, 2019, 7:38pm

Ugh, I dont read android posts so sorry I missed this.

Rushline · June 13, 2019, 10:04am

thanks Ali_RS

The masked exception ( class ID:-48 error ) in the client is:
attempt to unlock read lock, not locked by current thread

In my case/testing, I don’t think the delayservice in GameServer.java for:
serialization object , class ID:-48 exception is a solution.

D/com.jme3.network.serializing.Serializer: FINE Registered class[-57]:class com.simsilica.mathd.Vec3d to:com.jme3.network.serializing.serializers.FieldSerializer@cf43e0d
D/com.jme3.network.message.SerializerRegistrationsMessage: FINE    result:SerializerRegistration[-57, class com.simsilica.mathd.Vec3d, com.jme3.network.serializing.serializers.FieldSerializer@cf43e0d]
D/com.jme3.network.message.SerializerRegistrationsMessage: FINE Done registering serializable classes.

D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private java.lang.Object[] com.jme3.network.service.rpc.msg.RpcCallMessage.args using serializer:com.jme3.network.serializing.serializers.ArraySerializer@a7e080e
                                                            FINER Reading field:private com.jme3.network.service.rmi.MethodInfo[] com.jme3.network.service.rmi.ClassInfo.methods using serializer:com.jme3.network.serializing.serializers.ArraySerializer@a7e080e
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private com.jme3.network.service.rmi.CallType com.jme3.network.service.rmi.MethodInfo.callType using serializer:com.jme3.network.serializing.serializers.EnumSerializer@9e733dc
                                                            FINER Reading field:private short com.jme3.network.service.rmi.MethodInfo.id using serializer:com.jme3.network.serializing.serializers.ShortSerializer@1b9bc8f
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private java.lang.String com.jme3.network.service.rmi.MethodInfo.representation using serializer:com.jme3.network.serializing.serializers.StringSerializer@2847838
                                                            FINER Reading field:private com.jme3.network.service.rmi.CallType com.jme3.network.service.rmi.MethodInfo.callType using serializer:com.jme3.network.serializing.serializers.EnumSerializer@9e733dc
                                                            FINER Reading field:private short com.jme3.network.service.rmi.MethodInfo.id using serializer:com.jme3.network.serializing.serializers.ShortSerializer@1b9bc8f
                                                            FINER Reading field:private java.lang.String com.jme3.network.service.rmi.MethodInfo.representation using serializer:com.jme3.network.serializing.serializers.StringSerializer@2847838
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private java.lang.String com.jme3.network.service.rmi.ClassInfo.name using serializer:com.jme3.network.serializing.serializers.StringSerializer@2847838
                                                            FINER Reading field:private short com.jme3.network.service.rmi.ClassInfo.typeId using serializer:com.jme3.network.serializing.serializers.ShortSerializer@1b9bc8f
                                                            FINER Reading field:private byte com.jme3.network.service.rpc.msg.RpcCallMessage.channel using serializer:com.jme3.network.serializing.serializers.ByteSerializer@db5a969
                                                            FINER Reading field:private long com.jme3.network.service.rpc.msg.RpcCallMessage.msgId using serializer:com.jme3.network.serializing.serializers.LongSerializer@4f67325
                                                            FINER Reading field:private short com.jme3.network.service.rpc.msg.RpcCallMessage.objId using serializer:com.jme3.network.serializing.serializers.ShortSerializer@1b9bc8f
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private short com.jme3.network.service.rpc.msg.RpcCallMessage.procId using serializer:com.jme3.network.serializing.serializers.ShortSerializer@1b9bc8f
D/com.jme3.network.base.DefaultClient: FINER com.jme3.network.base.DefaultClient@1091cf8 received:RpcCallMessage[#-1, channel=-2, async, objId=-1, procId=0, args.length=1]
D/com.jme3.opencl.OpenCLObjectManager: FINE no active natives
D/com.jme3.network.base.MessageListenerRegistry: FINER Delivering RpcCallMessage[#-1, channel=-2, async, objId=-1, procId=0, args.length=1] to:com.jme3.network.util.ObjectMessageDelegator@9e5e827
D/com.jme3.network.service.rpc.RpcConnection: FINEST handleMessage(RpcCallMessage[#-1, channel=-2, async, objId=-1, procId=0, args.length=1])
D/com.jme3.network.service.rmi.RmiRegistry: FINEST rmiUpdate(0, [ClassInfo[example.net.AccountSession]])
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private java.lang.Object[] com.jme3.network.service.rpc.msg.RpcCallMessage.args using serializer:com.jme3.network.serializing.serializers.ArraySerializer@a7e080e
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private byte com.jme3.network.service.rpc.msg.RpcCallMessage.channel using serializer:com.jme3.network.serializing.serializers.ByteSerializer@db5a969
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private long com.jme3.network.service.rpc.msg.RpcCallMessage.msgId using serializer:com.jme3.network.serializing.serializers.LongSerializer@4f67325
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private short com.jme3.network.service.rpc.msg.RpcCallMessage.objId using serializer:com.jme3.network.serializing.serializers.ShortSerializer@1b9bc8f
D/com.jme3.network.serializing.serializers.FieldSerializer: FINER Reading field:private short com.jme3.network.service.rpc.msg.RpcCallMessage.procId using serializer:com.jme3.network.serializing.serializers.ShortSerializer@1b9bc8f
D/com.jme3.opencl.OpenCLObjectManager: FINE no active natives
D/com.jme3.network.base.DefaultClient: FINER com.jme3.network.base.DefaultClient@1091cf8 received:RpcCallMessage[#-1, channel=-2, async, objId=-1, procId=1, args.length=4]
D/com.jme3.network.base.MessageListenerRegistry: FINER Delivering RpcCallMessage[#-1, channel=-2, async, objId=-1, procId=1, args.length=4] to:com.jme3.network.util.ObjectMessageDelegator@9e5e827
D/com.jme3.network.service.rpc.RpcConnection: FINEST handleMessage(RpcCallMessage[#-1, channel=-2, async, objId=-1, procId=1, args.length=4])
D/com.jme3.network.service.rmi.RmiRegistry: FINEST rmiUpdate(1, [-2, 1, example.net.AccountSession, 0])
D/com.jme3.network.service.rmi.RmiRegistry: FINEST addRemoveObject(1, example.net.AccountSession, ClassInfo[example.net.AccountSession])
D/com.jme3.opencl.OpenCLObjectManager: FINE no active natives
D/com.jme3.network.base.DefaultClient: FINER com.jme3.network.base.DefaultClient@1091cf8 received:com.jme3.network.message.ClientRegistrationMessage[id=-1, gameName=null, version=0]
D/com.jme3.network.base.DefaultClient: FINE Starting client services.
D/com.jme3.network.service.ServiceManager: FINE Starting service:com.jme3.network.service.serializer.ClientSerializerRegistrationsService[serviceManager.class=class com.jme3.network.service.ClientServiceManager]
D/com.jme3.network.service.ServiceManager: FINE Starting service:com.jme3.network.service.rpc.RpcClientService[serviceManager.class=class com.jme3.network.service.ClientServiceManager]
D/com.jme3.network.service.ServiceManager: FINE Starting service:com.jme3.network.service.rmi.RmiClientService[serviceManager.class=class com.jme3.network.service.ClientServiceManager]
D/com.jme3.opencl.OpenCLObjectManager: FINE no active natives
E/AndroidRuntime: FATAL EXCEPTION: com.jme3.network.kernel.tcp.SocketConnector@8a0b5e
                  Process: example.sim, PID: 14065
                  java.lang.RuntimeException: java.lang.IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread
                      at example.ConnectionState$ConnectionObserver.handleError(ConnectionState.java:297)
                      at example.ConnectionState$ConnectionObserver.handleError(ConnectionState.java:273)
                      at com.jme3.network.base.DefaultClient.handleError(DefaultClient.java:425)
                      at com.jme3.network.base.DefaultClient$Redispatch.handleError(DefaultClient.java:517)
                      at com.jme3.network.base.ConnectorAdapter.handleError(ConnectorAdapter.java:149)
                      at com.jme3.network.base.ConnectorAdapter.run(ConnectorAdapter.java:178)
                   Caused by: java.lang.IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread
                      at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:446)
                      at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:430)
                      at java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1365)
                      at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:888)
                      at com.jme3.network.service.rmi.ClassInfoRegistry.getClassInfo(ClassInfoRegistry.java:92)
                      at com.jme3.network.service.rmi.RmiRegistry.share(RmiRegistry.java:131)
                      at com.jme3.network.service.rmi.RmiClientService.start(RmiClientService.java:169)
                      at com.jme3.network.service.ServiceManager.start(ServiceManager.java:86)
                      at com.jme3.network.base.DefaultClient.startServices(DefaultClient.java:397)
                      at com.jme3.network.base.DefaultClient.dispatch(DefaultClient.java:472)
                      at com.jme3.network.base.DefaultClient$Redispatch.messageReceived(DefaultClient.java:508)
                      at com.jme3.network.base.ConnectorAdapter.dispatch(ConnectorAdapter.java:132)
                      at com.jme3.network.base.ConnectorAdapter.run(ConnectorAdapter.java:174)

pspeed · June 13, 2019, 10:18am

Because you tried it and it didn’t work… or you just don’t expect it to work?

Rushline · June 13, 2019, 10:45am

yes, i tried… pasted the code in from previous post before the commit.
Compared the commit to what i tested… same same. You can see a delay in the server log

Rushline · June 13, 2019, 10:51am

they don’t vary… my bad

Rushline · September 11, 2019, 11:22am

thanks @Pspeed … your new LazyMessageBuffer in the networking is all class.

Works on Android with 3.3.0 SNAPSHOT

Many thanks !!

Ali_RS · September 11, 2019, 11:37am

Great… Very glad it works now.

Also not directly related to this topic but in case you are interested to also try Lemur GUI groovy style on Android (the default “glass” style which used in sim-eth-basic), there is this plugin for groovy support on Android. Putting the link to it here in case you want to give it a try.

Ali_RS · September 11, 2019, 11:55am

If you feel extra adventure there is also a sim-eth-es version of the example implemented with Entity Component System design using Zay-ES library. You may like to try that on Android also.

kaloyan.katsarov · September 13, 2019, 9:15pm

Good, back in the time I only manage to run on android with messages api, so off topic is it more efficient to use this jme rmi over sending messages back and forth between client and server.

Ali_RS · September 14, 2019, 5:14am

My understanding is JME RMI is a layer on top of JME message api means it uses massages in behind to communicate between client/server. So my understanding is it should be as efficient as JME message api while making communication very easy and your code more cleaner.

(Note that JME RMI is not the same Java RMI. Also afaik Java RMI is not supported on Android at all.)

danielp · September 16, 2019, 1:12pm

Yes - it’s just using a small handful of its own (very compact) messages to do the calls. As long as you mark interface methods as asynchronous there’s really no cause for concern - it’s far, far easier, faster, & cleaner to develop with than using raw messages.