Hashtable Serialization (Server/Client App)

by nsyed » Wed, 14 Apr 2010 03:38:47 GMT


Sponsored Links
 Hi All,

I am having a weird issue with serialization of a Hashtable. I have
made a Server, Client app. Where server(PC/MAC) is serializing a
Hashtable and sending it to Client(Android) through UDP. The data is
sent/read correctly but I get a bunch of these messages below on
LogCat.

04-12 11:19:43.059: DEBUG/dalvikvm(407): GetFieldID: unable to find
field Ljava/util/Hashtable;.loadFactor:F

Occasionally, I would see these

04-12 11:21:19.150: DEBUG/dalvikvm(407): GC freed 10814 objects /
447184 bytes in 97ms

The app would run for 2-3 mins and then crash. Interestingly enough I
do not see the Loadfactor errors on SDK 1.5. But I do see the GC Free
xxxx objects, quiet often.

After debugging I have found that the issue is with de-serialization
and the error/warning are coming from following code

Code:

ByteArrayInputStream bis = new ByteArrayInputStream(bytes);
ObjectInputStream ois = new ObjectInputStream(bis);
object = ois.readObject();
at Code:

object = ois.readObject();
on the client. My server is serializing code is the following.

Code:

ByteArrayOutputStream bos = new ByteArrayOutputStream();
ObjectOutputStream oos = new ObjectOutputStream(bos);
oos.writeObject(obj);
Any idea what is going on?

Thanks for the Help!

--



Hashtable Serialization (Server/Client App)

by Bob Kerns » Thu, 15 Apr 2010 01:23:50 GMT


 I don't have a solution, but I have a couple of recommendations --
either of which would avoid the problem.

#1 - don't use object serialization. Convert to an XML or JSON
representation instead. XML in particular would be preferred if you're
going to store these for an extended time.

#2 -- don't use Hashtable. It is a holdover from the early days of
Java, but it has inappropriate synchronization on various methods.
Use HashMap instead. This won't usually result in any other changes to
your code. If you were depending on the method synchronization of
Hashtable, you should take a good look at your code; it's likely you
weren't doing it right, and synchronizing on the table (or a larger-
scoped object) across a larger set of operations will fix bugs you may
not know you have. The synchronizing built into Hashtable is seldom
the actual synchronization needed!

Nothing in your message really suggests that your crash is related to
the message about serialization. If the loadfactor for the Hashtable
is set to zero, I suspect that would cause problems, but if it ends up
initialized to some reasonable default, this would be harmless. You
could check in the debugger pretty easily

The GC messages are not related to your problem. They indicate that
your program is causing the GC to run; this is of interest for
optimizing or analyzing performance.




--


Sponsored Links


Hashtable Serialization (Server/Client App)

by priyanka » Fri, 23 Apr 2010 13:17:27 GMT


 i All,

I am observing a similar issue. I get structured data from my server
to Android client in XML format. I parse the XML into a HashMap, and
save this HashMap object in file persistent storage. Now, when I
retrieve this HashMap object saved in file through :
HashMap<String, Object> hashMap = (HashMap<String, Object>)
objectInputStream.readObject();

I get
GetFieldID: unable to find field Ljava/util/HashMap;.loadFactor:F


for about 150 times (interspersed with about 2 GC freed commands); and
then I am able to read my object. I am not getting any crash, but I
suppose this might be slowing my app. And I am wondering how I can
resolve this. Any clues would be appreciated.

Thanks,
Priyanka


On Apr 14, 11:30pm, Naqi Syed <naqis...@gmail.com> wrote:
> >



Other Threads

1. Rooted Application yg Cespleng buat semua Android

As subject.. Ada ga ya?

Kalo mo diikutin langkah2 di XDA Developer kadang2 bikin ngantuk.. Hehehe..

Kalo untuk HTC Desire apa ya kira2 yg bagus?


..dikirim pake BB atau Desire.. yg penting nyampe! ^_^

-- 
"

2. Creating xml with image from DB

Hi,
I want to upload an image from my db to a server. But this image had
to be in a xml.
The xml format is:
<REC>
<F1>id</F1>
<F2>description</F2>
<F3><![CDATA[image_byte_array]]></F3>
<F4>date</F4>
</REC>

I'm building the XML with XmlSerializer:
XmlSerializer serializer = Xml.newSerializer();
                ByteArrayOutputStream bout = new ByteArrayOutputStream();
                serializer.setOutput(new ObjectOutputStream(bout),
HTTP.ISO_8859_1);
                        serializer.startTag("", "REC");
                        [...]
                                String testString = 
EncodingUtils.getString(c.getBlob(colIdx),
HTTP.ISO_8859_1);
                                serializer.cdsect(testString);// Doesn't work ->
IllegalArgumentExeption Illegal Caracter (0)
                                bout.write(new byte[]{'<', '!', '[', 'C', 'D', 
'A', 'T', 'A',
'['});
                                bout.write(c.getBlob(colIdx));
                                bout.write(new byte[]{']', ']', '>'}); // work 
but mtXml is only
this and not the rest of the xml
                                break;
                        [...]
                        serializer.endTag("", "REC");
                serializer.endDocument();
        mtXml = bout.toString();

In the blackberry version of the application, all the xml is build in
an outputstream. Does I need to do the same or is it possible to do it
with the XmlSerializer?

Thanks,
Sebastien

-- 

3. Running application on Dell Streak emulator

4. How declare in AndroidManifest when one application have two packages

5. Notification from database

6. CTS in android

7. is there a way to programmatically restart acore via adb shell after it's crashed?