Databases
StackOverflow2013
Postsdbo
POHow to handle StackOverflowError happended when serialize a big object?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to handle StackOverflowError happended when serialize a big object?
    primarykey
    data
    text
    <p>Here is my java code:</p> <pre><code> FileOutputStream fos = null; ObjectOutputStream out = null; try { fos = new FileOutputStream(pathName); out = new ObjectOutputStream(fos); out.writeObject(index); out.close(); fos.close(); } catch (IOException e) { LogManager.writeLogToFile(e.getMessage()); e.printStackTrace(); } </code></pre> <p>The index is an instance of inverted document index by myself. I have built the object index in memory, but when I pass it to the method writeObject(index), I get the error StackOverflowError. My question is: Why does this error happen after that I have built the object in the memory?</p> <p>Suppose that the data structure of index is as follow:</p> <pre><code>class InvertedIndex{ private HashMap&lt;String, PostList&gt; index; } class PostList{ private int size; private PostNode first; } class PostNode{ private String key; private double weight; private PostNode next; } </code></pre> <p>To avoid recursive call, I overwrite the method writeObject and readObject of the PostList because it may be a very long list:</p> <pre><code>class PostList{ private void writeObject(ObjectOutputStream out) throws IOException{ PostNode temp = first; while(temp != null){ out.writeObject(temp); temp = temp.getNext(); } } private void readObject(ObjectInputStream in) throws IOException, ClassNotFoundException{ in.defaultReadObject(); } } </code></pre> <p>Then I get two questions:</p> <ul> <li>out.writeObject(temp); Because temp has a reference to the next node, when I write temp, recursive call will also happen. The same situation will continue even if I overwrite the writeObject method of PostNode with defaultWriteObject. Am I right? If so, what can I do to avoid this recursive call?</li> <li>How to overwrite the method readObject()? </li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjerry_sjtu
    1. USjerry_sjtu
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to handle StackOverflowError happended when serialize a big object?
      1. USKuldeep Jain
      1. VTFavorite
    1. CODifficult to say without seeing what the index is. Possible duplicate: http://stackoverflow.com/questions/6416222/akka-stackoverflowerror-during-object-serialization
      singulars
      1. POHow to handle StackOverflowError happended when serialize a big object?
      1. USassylias
    2. COThis could help you too: http://stackoverflow.com/questions/438875/stackoverflowerror-when-serializing-an-object-in-java
      singulars
      1. POHow to handle StackOverflowError happended when serialize a big object?
      1. USassylias
    3. COI think my problem is that the post list of the index is a long linked list according to your advice. Thanks for your help. @assylias
      singulars
      1. POHow to handle StackOverflowError happended when serialize a big object?
      1. USjerry_sjtu
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload