Objects serialization

Suppose I am serializing a custome object of class
class Employee implements java.io.Serializable{
long id;
String name;
String department;
//setter and getter methods for each attribute
if i am serializing the object of Employee
Employee key = new Employee();
key.setId(1000);
key.setName("xyz");
key.setDepartment("aaa");
//using serial binding for key, instead of tuple binding - application requirement
SerialBinding binding = new SerialBinding(new StoredClassCatalog(db),Employee.class);
DatabaseEntry keyEntry = new DatabaseEntry();
binding.objectToEntry(key, keyEntry);
- what is order of serilization, represented by byte array, of each attribute of object?
- is the byte array contains first, bytes of id then name and so on?
- If this object key is used to find the record, will it use entire byte array representation of serialized object to compare or it will first, use byte array representation of 'id' then 'name' and so on... to compare

I don't want to use custom tuple binding for custom
objects as any arbitrary objects can be stored in
database. In this case which binding I should use. It
seems that TupleBinding supports only java primitive
objects.I don't understand why you're using arbitrary objects for keys. If you do that, I don't know of any way to get a meaningful sort order. So you might as well use SerialBinding.
If you can think of a way to use arbitrary objects for keys and implement a binding that provides a meaningful sort order, for your application at least, please do so. You are free to implement the EntryBinding and EntityBinding interfaces in any way you choose. It is up to you.
Any clue for my query? It is unreasonable for you to expect answers so quickly. I suggest that you read the source code in the com.sleepycat.bind package and try to get answers on your own.
--mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

Similar Messages

  • 2D objects Serialization problem

    Welcome!
    I'm making a net game using RMI and I have this problem.
    When I'm trying to join my client with the server an error occures:
    Error: error marshalling arguments; nested exception is:
         java.io.NotSerializableException: java.awt.geom.Ellipse2D$Double
    My client contains an Object extending a JPanel class. There are 2D object used to make the map, and that's why this error occures.
    It's a funny thing, cause I'm not sending a whole Object of my client, but only it's refference (using "this" in the join() method) so I dont know why does the 2D object need to be serialized and sent :|?
    Any way, my question is how to make 2D objects serializable!? I have jdk1.5.0_06 and as far as I remember they should be srializable in this version. Mabey I'm dooing something wrong!? Mabey it's nessesary to ad an appropreate code-line or import sth... i don't know
    please help me... I have little time to finish my project, and this thing is blocking my work.
    Big thanks to anybodey who will help.
    regards floW

    I'll tel u the whole story then, my problem is as follows:
    public class BounceThread{
       public static void main(String[] args)   {
          JFrame ramka = new BounceFrame();
             ramka.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
             ramka.setVisible(true);
    class BounceFrame extends JFrame{
    public BounceFrame()
          setSize(DEFAULT_WIDTH, DEFAULT_HEIGHT);
          setTitle("MiniGolf v 1.0");
          panel = new BallPanel(); // this contains maps made with 2D objects
          panel.setBackground(Color.green);
          panel.setVisible(panel.czy_widać_panel());
          add(panel, BorderLayout.CENTER);
    // I add a menu bar, that starts a net game:
    JMenuBar pasekMenu = new JMenuBar();
              setJMenuBar(pasekMenu);
              JMenu menuGra = new JMenu("Game");
           // and so on... and finaly I add an option:
              menuGame_Nowa.add(new
                        AbstractAction("Net game")
                             public void actionPerformed(ActionEvent event)
                                  net_game(panel);
    // here i write my net_game method:
    public void net_game(BallPanel aPanel)
         //here, i make an Client object, and connect him with my server
         client = new mgClient(panel);
         client.join();
         // I give panel as a paramete, cause I cant think of another way of leting my server to uce it's (panels) methods
         // If I join only a name of my client, then how can I change the panel in my BounceFrame from the Clients method
         // "shouted" by the server!? It has to be a field in the client's object.
         // Is there any other way out!?
    // Class BouceFrame holds the panel as a field:
    private mgClient client;
    private BallPanel panel;
    //and so on...
    }and that's the real problem I'm facing here. Is there any solution!? I think, that making a Client's field out of my panel is the only way ot. And that means I need those 2D objects serialized... :(
    Please help if u can.
    Regards floW

  • Servlet and Object Serialization

    Hi,
    I am developing a routing server in Java
    2 Instances of the same server will be running in 2 different data centers.
    The servers have a Jetty server embedded with a Servlet inside.
    Server 1 will use a GET method to talk to the Server 2 -> Servlet which will write the state of an object back which will read by Server 1 and reconstruct the object back.
    Do you find any issues in Object Serialization/DeSerialization in the Servlet.
    What are the factors that I need to consider in this case?
    Regards,
    Jana

    Make sure that your servlet handles the transaction in the same thread that doPost() or doGet() is called in.
    I ended up porting some old ServerSocket based code to a servlet, and was handing off the request and response objects to a handler thread on the server side. I ended up with a ton of intermittent errors like this.
    Once I started handling the transactions in the same thread things worked heartbreakingly well.

  • Customizing Forte object serialization

    Forte supports serialization of arbitrary object graphs into streams.
    However, there do not seem to be any well documented ways to customize
    this serialization, e.g. by using a different encoding scheme. It would
    seem there must be some support in there somewhere. I suppose at the
    very least, one could parse a serialized object (once one decoded the
    Forte encoding scheme) and do the conversion from that. That seems
    suboptimal, though.
    Has anyone done this? Any thoughts on how it might be done?
    Regards,
    Coty
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

    JavaFunda wrote:
    Object serialization is the process of saving an object's state to a sequence of bytes. Does it saves only the instance variable or also the object methods(like getter and setter methods) ? Only the state--the instance variables. It doesn't save the class definition. That has to be available separately (via classloader) at deserilaization time. In other words, you cannot deserialize an instance of a class that is not on your classpath.
    Once we we write the object to outputstream or some text file, how does it get transmitted over network?The same way any other bytes get transmitted. You have a Socket. You get its OutputStream. You wrap that in an ObjectOutputStream. When you write to the ObjectOutputStream, that writes through to the Socket's OutputStream, which is responsible for putting the bytes on the wire.
    Does we write the java object to text file only duuring serialization?We write the objects to wherever the other end of the ObjectOutputStream is connected to. Just like any other I/O.

  • Runtime Object serialization

    Hi,
    Could someone explain the concept of Runtime Object Serialization with a simple example?
    Thanks

    import java.io.*;
    /* you NEED to make the class implement Serializable */
    class Client implements Serializable {
        private String name;
        private String address;
        public String getName() { return name; }
        public String getAddress() { return address; }
        public void setName(String name) { this.name = name; }
        public void setAddress(String address) { this.address = address; }
        public String toString() { return "name='" + name + "' and address= " + address + "'"; }
    public class Test17 {
        public static void main(String[] args)  throws Exception {
            ObjectOutputStream oos = new ObjectOutputStream (new FileOutputStream ("test.bin"));
            Client myClient = new Client();
            myClient.setName("Steve Jobs");
            myClient.setAddress("1 Infinite Loop; Cupertino, CA 95014");
            System.out.println (myClient);
            oos.writeObject (myClient);
            oos.close();
            ObjectInputStream ois = new ObjectInputStream (new FileInputStream ("test.bin"));
            Client yourClient = (Client) ois.readObject();
            System.out.println (yourClient);
    }Run the program above. It creates an object of the class "Client", serializes it into a file named "test.bin" and recreates the object reading it from the same file.
    Dumping the binary file you get this:
    0000    AC ED 00 05 73 72 00 06  43 6C 69 65 6E 74 F1 D7   ....sr..Client..
    0010    74 76 C4 64 FD 43 02 00  02 4C 00 07 61 64 64 72   tv.d.C...L..addr
    0020    65 73 73 74 00 12 4C 6A  61 76 61 2F 6C 61 6E 67   esst..Ljava/lang
    0030    2F 53 74 72 69 6E 67 3B  4C 00 04 6E 61 6D 65 71   /String;L..nameq
    0040    00 7E 00 01 78 70 74 00  24 31 20 49 6E 66 69 6E   .~..xpt.$1 Infin
    0050    69 74 65 20 4C 6F 6F 70  3B 20 43 75 70 65 72 74   ite Loop; Cupert
    0060    69 6E 6F 2C 20 43 41 20  39 35 30 31 34 74 00 0A   ino, CA 95014t..
    0070    53 74 65 76 65 20 4A 6F  62 73                     Steve JobsYou can see a lot of things in the serialization of the object Client - the name of the class is written, the names of the fields, the type (java/lang/String), and the values of the fields as UTF-8 encoded strings.

  • Object serializable?

    Hi,
    When writing a vector of my own objects out to a file, do the objects need to be serializable even though it is actually the vector I am outputting?
    Also, each of my objects in this vector have a field that is a vector of other objects...do I need to declare those objects serializable also?

    I think you still need to implement serializable on objects contained in the vector. I tried serializing a hashmap and my hashmap contained objects which needed to be serialized before the hashmap could be stored in a file.

  • SetAttribute() makes object serializable Recursively ?

              Hi everyone,
              could anyone answer me whether httpSession.setAttribute(key, very big object)
              makes the object serializable recursively.
              What I mean is, I am storing an object bigObject in http session using setAttribute().
              This bigObject contains several other objects which are not serialized.
              But I have read that setAttribute() makes the object serializable.
              So, does it mean that all the objects stored in bigObject also will be serialized
              thanks,
              jyothi
              

    But you can't serialize an Object that isn't Serializable somewhere in it's
              inheritance. A method can't make an Object Serializable.
              "jyothi" <[email protected]> wrote in message
              news:[email protected]...
              >
              > But i read clearly some where in bea online manual that use
              setAttribute() which
              > makes the object searializable. So I wonder whether this
              setAttribute() does
              > the searlization recursively ?
              >
              > thanks,
              > jyothi
              >
              > "justin" <[email protected]> wrote:
              > >
              > >Cluster requirement is that all objects placed in a session should be
              > >serializable.
              > >So your Big objects with small object which are not serializable is going
              > >to be
              > >a problem.
              > >
              > >"jyothi" <[email protected]> wrote:
              > >>
              > >>Hi everyone,
              > >>
              > >>could anyone answer me whether httpSession.setAttribute(key, very
              > >>big object)
              > >> makes the object serializable recursively.
              > >>
              > >>What I mean is, I am storing an object bigObject in http session using
              > >> setAttribute().
              > >> This bigObject contains several other objects which are not serialized.
              > >>
              > >>But I have read that setAttribute() makes the object serializable.
              > >>
              > >>So, does it mean that all the objects stored in bigObject also will
              > >>be serialized
              > >>?
              > >>
              > >>thanks,
              > >>jyothi
              > >
              >
              

  • Object serialization failure during OutOfMemory error (EOFException)

    Hello all,
    We are seeing a very strange situation when writing a serializable object to a flat file, specifically during an OutOfMemory condition. Our application saves the state of an object if an error occurs, and retries at a later point by reviving the object from its serialized form. We recently encountered a series of EOFExcetions when trying to reload the serialized object. Looking at the serialized data, we see that the file is indeed incomplete, and that it appears to be the serialized representation of the data contained within the object that is missing (the structure of the object appears to be stored in the serialized file, but not the runtime data).
    The code that produces and consumes these serialized objects is used in a variety of locations, and even in the case where these EOF errors occurred usually works as expected. The difference appears to be that the error condition which lead to the object serialization was in-fact an OutOfMemory error. That is, we had an OOM error elsewhere in our application, which caused our objects to be serialized to disk. During this serialization process we end up with corrupt (incomplete) serialization data.
    So.. the question is: Is it possible that the OutOfMemory situation causes the JVM to incorrectly serialize an object (without an error), and specifically to omit runtime data (variables) from the serialized form of the object?
    Thanks/

    jasonpolites wrote:
    So.. the question is: Is it possible that the OutOfMemory situation causes the JVM to incorrectly serialize an object (without an error), and specifically to omit runtime data (variables) from the serialized form of the object?you're sure that the serialization process completed without an error? how do you know the the OOME did not cause the serialization to fail (because the serialization process itself will require more memory, hence if it is happening while the system is near the memory peak, it is likely to fail as well)? generally, when a jvm starts throwing OOME's all bets are off. failures in random places can easily cause the whole internal state of a system to become invalid.

  • Object serialization EOFException

    Essentially what I want to do is write to an object to a file. The program can terminate and then when I start the program again, it will read the object from the file and restore the program's original state before it was terminated.
    I get an EOFException with this code
    //insert code that gets input which will be stored in a hashtable
    //save Hashtable in "data.dat" using ObjectOutputStream
    //program terminates
    //program is re-ran again and checks for existing file
    File f = new File("data.dat");
    if(f.exists()){
           ObjectInputStream ois = new ObjectInputStream(new FileInputStream(f));
           Object obj = ois.readObject(); //EOF exception occurs here
    }I know the above code works if I write the Hashtable and then read it back immediately without terminating in between. Am I missing something? Can object serialization be used in such a way that I can restore a program's original state before it was terminated?

    Sorry, I led you to believe that the actual class itself was going to be written to a file. I meant to say that the Hashtable in the class should be written to a file and then later on when I start the program again, it will restore the Hashtable to it's original state.
    My writing coding is something like this:
    Hashtable accounts = new Hashtable();
    //do stuff to the hashtable
    FileOutputStream fos = new FileOutputStream("data.dat");
    ObjectOutputStream oos = new ObjectOutputStream(fos);
    oos.writeObject(accounts);
    //Program can be terminated from this point
    //there is no further oos.writeObject() if it wasn't terminated
    //immediately after the above writeObject() call
    //Program is ran again and at startup it checks for existing file
    File f = new File("data.dat");
    if(f.exists()){
    ObjectInputStream ois = new ObjectInputStream(new FileInpuStream(f));
    Object obj = obj.readObject(); //EOFException occurs here
    }Again those lines work perfectly fine if I do not terminate the program and I force it to check for an existing file. If I terminate, it's almost as if the program thinks there's nothing in "data.dat" eventhough it's obvious by my code that I did write something to "data.dat".

  • Object Serialization(Materialization and Dematerialization)

    I've encountered some issues with mapping my objects to an RDBMS and am hoping for some advice.
    I've tried various O/R mapping frameworks like Castor(too complex and too slow for my liking), JRF(nice but very repetitive and difficult to extend) and then some, but have yet to find one which I'm comfortable with building an application on.
    Instead, I've chosen to do it the low-tech way, with each domain class, say Book for instance, having a Broker class which knows how to communicate with the chosen form of persistence. So, since I chose an RDBMS, Book class has a BookRelationalBroker class which knows how to materialize and dematerialize Book objects to and from a RDBMS. If so required, I can plug in a BookXMLBroker which knows how to serialize the object in the form of an xml data file.
    I've also implemented a primitive object caching system which (when enabled), caches objects requested so we only have to materialize it from the db once.
    Here are 2 issues I have with my system:
    It is amazingly tedious (not to mention inefficient) to recreate the entire object from the database. This is even more so because I've implemented the Event Notification pattern, such that when say a book is deleted, the members who have reserved it are notified. The whole point of the Event Notification mechanism is so that the object being watched does not need to know of the objects which need to be notified on a state change. However, I've found it necessary to re-attach all the listeners on an object when it is materialized from the DB, defeating the purpose of the pattern.
    Complex object relationships are mapped poorly and recursive materialization leads to slow response times. If a Group object has a Vector of Members and other Groups, then whenever a Group object is materialized, all its constituent Members and Group objects also need to be materialized. (I understand O/R frameworks solve this through lazy instantiation)
    I studied the Jive2 architecture and found that they approached this problem by accessing the DB directly for any complex object relationships. In other words, the Group object does not actually contain a Vector of Members and Groups. Instead, it has a method called say getMembers() which proceeds to retrieve the necessary data from the DB and then materialize these objects.
    I'm not too excited about this approach for 2 reasons:
    How object-oriented is this approach? Seems more like database-oriented programming to me.
    Every call to retrieve Members necessitates a call to the DB. The data isn't cached with the Group object because the Group object does not actually contain the necessary reference to the Members and Groups.
    Can anyone shed some light on this topic?

    How object-oriented is this approach? Seems more like database-oriented programming to me. There is a reason people still use Relational databases rather than OO DBs. First, is that the vast majority of data in the real world maps easily to a relational model, consequently there is no advantage to a OO model. Second, either because of this or simply because OO models are not computationally simple, OO databases tend to be slower than relational DBs.
    It sounds like you are trying to implement a OO DB model using a relational database. So you basically end up with two problems. The DB is not optimized for OO models, and you have to find a way to map it in the OO model itself. And this is slow and messy.
    To solve the slowness problem you could, just like EJB servers, cache the data in memory. Lot of work but if you want to do it then have fun.
    The second way is to give up. Realize that your data model is not inherently OO'd and just implement it efficiently as a relational model. Then provide an interface that loads it into the OO model. And where needed add pass through logic to allow the database itself to do things it is really good at - like queries.

  • Bussiness object serialization problem

    Hi, I have a little problem with serialization, when I want to create xml from Business object. Example:
    MyBoObject obj = new MyBoObject ();
    obj.atr1 = "aaa";
    obj.atr2 = "bbb";
    String xml = DynamicXml.createXmlTextFor(object : obj, topLevelTag : "something");
    display(xml);
    And displayed result is:
    <something>
    <atr2>bbb</atr2>
    </something>
    atr1 is attribute, which is inherited from db table.
    atr2 is atribute, which I created (it is not inherited from db table)
    Whole problem is, that it only serialize atr2 - from some reason it completely ignores atr1 and his value.
    Like I can't serialize attributes, which are inherited from db table.
    But when I created new attribute atr2 in my Business Object (which is not inherited from db table), everything work ok. Where's the problem? I read docs, but found nothing...
    Edited by: user12189610 on Nov 9, 2009 2:42 AM
    Edited by: user12189610 on Nov 9, 2009 2:46 AM

    If you need a simple project that duplicates this problem for customer support, here's where I put one: http://www.4shared.com/file/181611971/d21e9444/_2__DynamicXMLBug.html.
    Have them import the project, start Studio's Engine, login as "test" and start the Workspace. Create a work item instance and then run the work item when it reaches the "Test" activity. When you run the logic, you'll see this displayed:
    <?xml version="1.0" encoding="UTF-8"?>
    <poHeir xmlns="http://bea.com/albpm/DynamicXml/version/2.0">
        <nameForPO>Dan</nameForPO>
    </poHeir>They should note that only the "nameForPO" tag is created by the DynamicXml.createXmlTextFor() method. "nameForPO" is an attribute I manually added to the XML Heir BPM Object. The attributes of the inherited heir (e.g. "poHeir.orderDate" and "poHeir.billTo") are not included as tags in the generated XML even though these attributes have been set in the logic.

  • Making an object serializable

    Hey guys, im new at this so i dont know almost anything about serialization, so here's my problem:
    Got an array of an object "Article" that i defined, wanna write it to a file but i get the "NotSerializableException",
    here's my object's constructor:
    Article (String n, int u, float p)
    name = n;
    amount = u;
    price = p;
    fmt = new DecimalFormat ("0.##");
    by the way, all of the variables are private, i dont have any problem storing several articles in my array, i just get my exception at runtime here:
    public static void save(Object obj, String nombrearch) throws IOException
    ObjectOutputStream objstream = new ObjectOutputStream(new FileOutputStream(nombrearch));
    objstream.writeObject(obj);
    objstream.close();
    apologizing for inconviniences, hope you can help me work this out

    sanu018 wrote:
    When ever u are writing to a stream all the objects that u r exporting should be serializable. Primitive types are as such non serializable so replace all those int with Integer type objects.Absolute total rubbish. Just pure bullshit.
    If you don't have a clue what you're talking about then please don't offer "advice" on these forums.

  • Slow T3 Object Serialization.

    Hi,
    Our project is running into a serious problem on the weblogic server. We have
    dedicate WLS running only as EJB container for business logic, and another physical
    server house an instant of WLS running as web app server for web presentation.
    The problem is when the servlet side is trying to call a session bean and get
    the result object, it show a very big delay. We timed the business logic running
    in the session bean is less than 0.5sec and the overall call from web side is
    7sec+. We are suspecting that it is due to the serialization by t3 protocol of
    this large object (140kb if write to file). Any clue, thanks in advance.
    Rgds,
    Arthur

    "Arthur Tang" <[email protected]> writes:
    You should raise a support call, it could be almost
    anything. Certainly 7s seems a little slow for 140kb.
    andy
    Hi,
    Our project is running into a serious problem on the weblogic server. We have
    dedicate WLS running only as EJB container for business logic, and another physical
    server house an instant of WLS running as web app server for web presentation.
    The problem is when the servlet side is trying to call a session bean and get
    the result object, it show a very big delay. We timed the business logic running
    in the session bean is less than 0.5sec and the overall call from web side is
    7sec+. We are suspecting that it is due to the serialization by t3 protocol of
    this large object (140kb if write to file). Any clue, thanks in advance.
    Rgds,
    Arthur

  • Object Serialization Question.

    Hello, I'm working on a MUD client and I have a DataHolder class to store settings. I'm having problems getting the serialization process to work properly, could someone please give me an example of how to serialize this class and then restore it again? I would like to save the class as "prefs.ser" Here is an example class to use:
    import java.awt.*;
    import java.net.*;
    import java.io.*;
    public class DataHolder
         public Color foreground = Color.black;
         public Color background = Color.yellow;
    // i dont want to save the socket info since it will change many times during actual operation
    // also i know you have to catch the exception from the socket creation : )
         public transient Socket socket = new Socket("lordsoftherealm.org", 1234);
         public DataHolder()
         public setColors(Color foreground, Color background)
              // set background and foreground colors
              // the actual class include methods to retrieve colors, sockets, and other relevent data
              this.foreground = foreground;
              this.background = background;
         public Socket getSocket()
              return socket;
    }Thank you for your time in helping me,
    Joeyford1

    Try this,
    I am using this method to serializeand deserialize my objects ..
    import java.util.Date;
    import java.math.BigDecimal;
    import java.io.*;
    * This object compliments MyObjectTranslator and provides a method to translate
    * any object into a type the database engine can process.
    public class MyObjectTranslator {
    public static Object translate(Object ob) {
    if (ob == null ||
    ob instanceof NullObject ||
    ob instanceof String ||
    ob instanceof BigDecimal ||
    ob instanceof Date ||
    ob instanceof ByteLongObject ||
    ob instanceof Boolean) {
    return ob;
    else if (ob instanceof Serializable) {
    return serialize(ob);
    else {
    // System.out.println("Ob is: (" + ob.getClass() + ") " + ob);
    System.out.println("Unable to translate object. " +
    "It is not a primitive type or serializable.");
    * Serializes the Java object to a ByteLongObject.
    public static ByteLongObject serialize(Object ob) {
    try {
    ByteArrayOutputStream bout = new ByteArrayOutputStream();
    ObjectOutputStream ob_out = new ObjectOutputStream(bout);
    ob_out.writeObject(ob);
    ob_out.close();
    return new ByteLongObject(bout.toByteArray());
    catch (IOException e) {
    System.out.println("Serialization error: " + e.getMessage());
    * Deserializes a ByteLongObject to a Java object.
    public static Object deserialize(ByteLongObject blob) {
    if (blob == null) {
    return null;
    else {
    try {
    ByteArrayInputStream bin =
    new ByteArrayInputStream(blob.getByteArray());
    ObjectInputStream ob_in = new ObjectInputStream(bin);
    Object ob = ob_in.readObject();
    ob_in.close();
    return ob;
    catch (ClassNotFoundException e) {
    System.out.println("Class not found: " + e.getMessage());
    catch (IOException e) {
    System.out.println("De-serialization error: " + e.getMessage());
    so if you want it to translate it use it something like :
    private Object translateObjectType(Object ob) {
    return MyObjectTranslator.translate(ob);
    and when you wana retrive it use it like :
    Object ds = MyObjectTranslator .deserialize((ByteLongObject) ob);

  • Object Serialization and IO Error

    Hi,
    I am trying to serialize 3 hashtable objects, with serializable keys and elements, on to disk. Here is a snippet of the code disk management code:
         public void loadData(StoreManager s_man) {
              // read from disk
              Hashtable o = (Hashtable)readObjects();
              Hashtable c = (Hashtable)readClasses();
              Hashtable i = (Hashtable)readIndex();
              //Hashtable e = (Hashtable)readEnv();
              Integer id = (Integer)readEnv();
              // set the store manager objects
              s_man.setObjects(o);
              s_man.setClasses(c);
              s_man.setIndex(i);
              Env.setCurrentID(id);
    Here is what the readObject method looks like:
         * Deserialize disk data and return Object data.
         public synchronized Object readObjects() {
              if (!objectdatafile.exists())
                   return null;
              Object o = new Object();
              try {
                   FileInputStream istream = new FileInputStream(objectdatafile);
                   ObjectInputStream pack = new ObjectInputStream(istream);
                   o = pack.readObject();
                   istream.close();
              catch (Exception e) {
                   e.printStackTrace();
    Occasionally, when starting the program (i.e. when it initially reads all data from disk), I am getting the following exceptions:
    java.io.EOFException
    at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2426)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1238)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:325)
    at java.util.Hashtable.readObject(Hashtable.java:799)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:42)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:28)
    at java.lang.reflect.Method.invoke(Method.java:327)
    at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:812
    at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1736)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
    639)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1267)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:325)
    at DiskManager.readObjects(DiskManager.java:165)
    at DiskManager.loadData(DiskManager.java:42)
    at LoadDataAction.run(LoadDataAction.java:30)
    at java.lang.Thread.run(Thread.java:539)
    java.lang.ClassCastException: java.lang.Object
    at DiskManager.loadData(DiskManager.java:42)
    at LoadDataAction.run(LoadDataAction.java:30)
    at java.lang.Thread.run(Thread.java:539)
    I would like to repeat that I am not getting this error everytime, but about once every two runs. Please share your feelings about possible errors I am making or if there is an inherent bug with serialization of hashtables.
    Thanks

    the java.io.EOFException looks like you did not properly close the stream on writing. to me this seems like there is an error in the writing code rather than the reading code. although there are some things you can improve...
    robert

Maybe you are looking for

  • Clearing document F.13

    Hello Experts :    We have two system here SAP 1 and SAP 2 1) Invoice get created in SAP 1 and Replicated in SAP 2 via Interface as open item (Accounting entries also done in SAP 2) 2) Invoice get cleared in SAP 1 say after 6 days (Account entries al

  • CreateInsert and Commit in one operation

    Is there a way to CreateInsert and Commit in one operation? I just want the user to click one button to create a new record.

  • USB data manipulation from Java to all OS

    Hello currently I'm developing on a software where I need to detect the USB Device and get access to the data send from the USB Devices. I googled but couldn't find the perfect library for usb for all platform. My program is used by many clients of d

  • Changing FROM header during Forwarding from PSTN to PSTN

    Hi, Is there a possibility to change the FROM header in INVITE message: 1. calling from PSTN network to lync user 2. user got call forwarding to PSTN number set that the FROM header got user's number? Lync is 2013 with newest update.

  • How can I squish a tall movie?

    I have a QT movie that is at the 4:3 ratio, but appears tall. I want to use this video in a 4:3 iMovie, but have it appear natural (it will have to be letter-boxed) How can I do this?