Nevermind, that was really a stupid question...
Anyway I found out where the stackoverflow occurs!
Loading the hashmap as maximum as possible as I was trying to do was right, but
I wasn't initializing internal collections of my complex objects before
serialization.
Once all collections of my ob
Hi again,
so I'm back from vacation, digging on the problem again.
anonymous wrote :
| A recursive write is okay, but if you keep adding circular references you
won't have stack to process the recursive calls necessary here.
|
| Something like:
|
| Map.put(key, AnotherMap);
| An
anonymous wrote : Well, it could be, but not sure that this TreeMap could get
too big. I have to check if somewhere else in the code I have similar maps.
| Still, about my first question: if all SFSB are destroyed, when can
serialization happen? Passivation applies only on inactive beans right?
anonymous wrote : This might be happening because of the excessive stack on the
TreeMap.
Well, it could be, but not sure that this TreeMap could get too big. I have to
check if somewhere else in the code I have similar maps.
Still, about my first question: if all SFSB are destroyed, when can
se
This might be happening because of the excessive stack on the TreeMap.
Maybe you could increase your Stack configuration?
I would need a testcase replicating this problem for being able to help more.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165110#4165
Thanks for your reply.
anonymous wrote : This looks like a recursive write. Are you trying to use
HashMaps as trees?
Actually I do not have Maps of Maps if that's what you mean. The "candidate"
for this Serialization problem seems the following map (which is the field of a
SFSB):
TreeMap> ma
Since I don't have any evidence of what happened I will have to guess:
This looks like a recursive write. Are you trying to use HashMaps as trees?
A recursive write is okay, but if you keep adding circular references you won't
have stack to process the recursive calls necessary here.
Something
I am sorry I can't be more precise about this bug, nobody has ANY clue?
Just some more precisions about environment. I am using
Jboss Serialization 1.0.3.GA (included in JBoss Messaging 1.2.0.sp1)
>From another log file on one of our servers I digged out the same exception
>and noticed that the
