jade-develop mailing list archive: No Not Resolved!!! AW: [jade

Subject: No Not Resolved!!! AW: [jade-develop] Resolved: String pool const ant
From: Aijaz, Amer (amer.aijaz@volkswagen.de)
Date: Wed Mar 05 2003 - 13:21:08 MET

Hi

I am experiencing the similar problem of UTF8 string in constant pool
exception... After calling doMove(nextSite).. I get the following exception
DESPITE the recommended solution for putting the key word transient
Location... Any other ideas? I am totally lost.. an older version of the
same program runs perfectly.. I have not changed the mobility part of the
code at all.. And after two days I could not find any clew.. As this matter
was already raised on Feb 15.. I take it that its a bug in Jade, during
serializing of 'Location' objects by JVM.

------- exception trace----------------

jade.core.IMTPException: Communication Failure [nested message is: Error
occurred in server thread; nested exception is:
        java.lang.ClassFormatError: Illegal UTF8 string in constant pool]
        at jade.imtp.rmi.AgentContainerAdapter.createAgent(Unknown Source)
        at jade.core.RealMobilityManager.handleMove(Unknown Source)
        at jade.core.AgentContainerImpl.handleMove(Unknown Source)
        at jade.core.Agent.notifyMove(Unknown Source)
        at jade.core.Agent.mainLoop(Unknown Source)
        at jade.core.Agent.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Nested Exception is:
java.rmi.ServerError: Error occurred in server thread; nested exception is:
        java.lang.ClassFormatError: Illegal UTF8 string in constant pool
        at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown
Source)
        at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
        at sun.rmi.server.UnicastRef.invoke(Unknown Source)
        at jade.imtp.rmi.AgentContainerRMIImpl_Stub.createAgent(Unknown
Source)
        at jade.imtp.rmi.AgentContainerAdapter.createAgent(Unknown Source)
        at jade.core.RealMobilityManager.handleMove(Unknown Source)
        at jade.core.AgentContainerImpl.handleMove(Unknown Source)
        at jade.core.Agent.notifyMove(Unknown Source)
        at jade.core.Agent.mainLoop(Unknown Source)
        at jade.core.Agent.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassFormatError: Illegal UTF8 string in constant pool

hope to get some clues from those who helped resolved this problem the first
time.

Amer

-----Ursprüngliche Nachricht-----
Von: Dick Cowan [mailto:rm.cowan@verizon.net]
Gesendet: Freitag, 14. Februar 2003 18:43
An: jade-develop
Cc: Dick Cowan
Betreff: [jade-develop] Resolved: String pool constant & agent mobility
under BlueJADE

I'd like to report that two problems reported earlier to this group have
been solved.

1. Illegal UTF8 string in constant pool.

Thanks to the help of Nicolas Lhuillier (
<mailto:Nicolas.Lhuillier@motorola.com> Nicolas.Lhuillier@motorola.com) he
tracked the problem down.
His answer follows:

The problem is certainly that the private field "Location" in MobileAgent is
not serializable (or badly serialize). This is where the issue is (I don't
know yet if this is a bug or a known feature). I simply put "transient" in
front of the field so that the JVM does not need to serialize it and it
works.

The original line in my test program was: "private Location mainLocation;"
which he changed to: "private transient Location mainLocation;"

We have provided the JADE developers with this information and the test
case. I would expect that the next version of JADE either makes Location
serializable or perhaps gives an error message which would alert you to the
problem and perhaps the problem class.

I am experiencing the similar problem of UTF8 string in constant pool exception... After calling doMove(nextSite).. I get the following exception DESPITE the recommended solution for putting the key word transient Location... Any other ideas? I am totally lost.. an older version of the same program runs perfectly.. I have not changed the mobility part of the code at all.. And after two days I could not find any clew.. As this matter was already raised on Feb 15.. I take it that its a bug in Jade, during serializing of 'Location' objects by JVM.

jade.core.IMTPException: Communication Failure [nested message is: Error occurred in server thread; nested exception is:
        java.lang.ClassFormatError: Illegal UTF8 string in constant pool]
        at jade.imtp.rmi.AgentContainerAdapter.createAgent(Unknown Source)
        at jade.core.RealMobilityManager.handleMove(Unknown Source)
        at jade.core.AgentContainerImpl.handleMove(Unknown Source)
        at jade.core.Agent.notifyMove(Unknown Source)
        at jade.core.Agent.mainLoop(Unknown Source)
        at jade.core.Agent.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Nested Exception is:
java.rmi.ServerError: Error occurred in server thread; nested exception is:
        java.lang.ClassFormatError: Illegal UTF8 string in constant pool
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
        at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
        at sun.rmi.server.UnicastRef.invoke(Unknown Source)
        at jade.imtp.rmi.AgentContainerRMIImpl_Stub.createAgent(Unknown Source)
        at jade.imtp.rmi.AgentContainerAdapter.createAgent(Unknown Source)
        at jade.core.RealMobilityManager.handleMove(Unknown Source)
        at jade.core.AgentContainerImpl.handleMove(Unknown Source)
        at jade.core.Agent.notifyMove(Unknown Source)
        at jade.core.Agent.mainLoop(Unknown Source)
        at jade.core.Agent.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassFormatError: Illegal UTF8 string in constant pool