weird serialization issue with long

[Daisy]

I'd appreciate some help with a weird problem.

A long in an object that I serialize is read as zero every other
iteration. Since I'm creating new instances every time, I don't think
it has to do with reset() or flush(). Also, it seems inefficient to
keep recreating the Byte and ObjectOutput streams. I'm going to try
reset() and flush() rather than new instances once I close this long
issue. Is there a better approach?

// create event
MyEvent event = new MyEvent("test",123);

// serialize the event into a byte stream
ByteArrayOutputStream baos = new ByteArrayOutputStream( );
ObjectOutputStream oos = new ObjectOutputStream( baos );
oos.writeObject( event );

// put the byte stream into our friendly ByteBuffer
ByteBuffer buffer = ByteBuffer.wrap( baos.toByteArray( ) );

public class MyEvent implements Serializable {

private long long1;

private final String string1;

public MyEvent( String stringArg , long longArg ) {
long1 = longArg;
string1=stringArg;
}
}


To read the event, I use:
ByteArrayInputStream bais = new ByteArrayInputStream( buffer.array( )
);

ObjectInputStream ois = new ObjectInputStream( bais );

MyEvent eventRead = ( MyEvent ) ois.readObject( );

Thanks for the help!

 

[Venkatesh]

Hi,

I'm unable to reproduce ur problem. Things work fine for me .... Where
are you reading the object back? Is it in the same method or in a
different method?

FYI, here is the code that I have written:

package com.trilogy.temp;

import java.io.ByteArrayInputStream;
import java.io.ByteArrayOutputStream;
import java.io.IOException;
import java.ibjectInputStream;
import java.ibjectOutputStream;
import java.io.Serializable;
import java.nio.ByteBuffer;

class MyEvent implements Serializable {

private long long1;

private final String string1;

public MyEvent( String stringArg , long longArg ) {
long1 = longArg;
string1=stringArg;
}

public String toString() {
return("MyEvent[string1=" + string1 + ", long1=" + long1 +
"]");
}

}

public class TestSerialization {

public void testSerialize() throws IOException,
ClassNotFoundException {

MyEvent event = new MyEvent("test", 123);

ByteArrayOutputStream baos = new ByteArrayOutputStream();
ObjectOutputStream oos = new ObjectOutputStream(baos);

oos.writeObject(event);

ByteBuffer buffer = ByteBuffer.wrap(baos.toByteArray());

ByteArrayInputStream bais = new
ByteArrayInputStream(buffer.array());
ObjectInputStream ois = new ObjectInputStream(bais);

MyEvent eventRead = ((MyEvent)ois.readObject());

System.out.println("eventRead = " + eventRead);

}

/**
* @param args
*/
public static void main(String[] args) {

try {
(new TestSerialization()).testSerialize();
} catch(Exception e) {
System.err.println("Got exception: " + e.getMessage());
e.printStackTrace();
}

}

}


The output I get is:

eventRead = MyEvent[string1=test, long1=123]

 

[Mike Schilling]

I'd appreciate some help with a weird problem.

A long in an object that I serialize is read as zero every other
iteration. Since I'm creating new instances every time, I don't think
it has to do with reset() or flush(). Also, it seems inefficient to
keep recreating the Byte and ObjectOutput streams. I'm going to try
reset() and flush() rather than new instances once I close this long
issue. Is there a better approach?

// create event
MyEvent event = new MyEvent("test",123);

// serialize the event into a byte stream
ByteArrayOutputStream baos = new ByteArrayOutputStream( );
ObjectOutputStream oos = new ObjectOutputStream( baos );
oos.writeObject( event );

// put the byte stream into our friendly ByteBuffer
ByteBuffer buffer = ByteBuffer.wrap( baos.toByteArray( ) );

public class MyEvent implements Serializable {

private long long1;

private final String string1;

public MyEvent( String stringArg , long longArg ) {
long1 = longArg;
string1=stringArg;
}
}


To read the event, I use:
ByteArrayInputStream bais = new ByteArrayInputStream( buffer.array( )
);

ObjectInputStream ois = new ObjectInputStream( bais );

MyEvent eventRead = ( MyEvent ) ois.readObject( );

This shows the reading and writing of only one instance. Can you show us an
exmaple that doesn more than one and demonstrates the every-other-time
behavior?