Re: [Resin-interest] memory and temp-file problem

2012-02-13 Thread Scott Ferguson 

On 02/13/2012 09:37 AM, smallufo wrote:
I also noticed a lot of com.caucho.db.block.Block... exceptions like 
this :

(and resin seems running slower and slower )

[12-02-14 01:32:03.974] {http://*:8080-63} 
SessionImpl[aaaxhkKBWCkiL-WwxX3vt,]: can't serialize session
   java.lang.IllegalStateException: block 
Block[Table[data:3],42603] is not an index code=2

at com.caucho.db.block.Block.validateIsIndex(Block.java:150)
at com.caucho.db.index.BTree.validateIndex(BTree.java:1723)

Lots of same errors  :

$ grep -e 'IllegalStateException: block Block' jvm-app-0.log
   java.lang.IllegalStateException: block
Does it means there's something wrong with 'data.db' ?


Thanks.

Yes, that would be a db corruption issue. I've filed this at 
http://bugs.caucho.com/view.php?id=4956.




-- Scott


(resin 4.0.25)


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Re: [Resin-interest] memory and temp-file problem

2012-02-13 Thread smallufo 
I also noticed a lot of com.caucho.db.block.Block... exceptions like this :
(and resin seems running slower and slower )

[12-02-14 01:32:03.974] {http://*:8080-63}
SessionImpl[aaaxhkKBWCkiL-WwxX3vt,]: can't serialize session
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
at
com.caucho.db.block.Block.validateIsIndex(Block.java:150)
at
com.caucho.db.index.BTree.validateIndex(BTree.java:1723)

Lots of same errors  :

$ grep -e 'IllegalStateException: block Block' jvm-app-0.log
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2
   java.lang.IllegalStateException: block
Block[Table[data:3],42603] is not an index code=2

Does it means there's something wrong with 'data.db' ?
(resin 4.0.25)
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Re: [Resin-interest] memory and temp-file problem

2012-02-13 Thread Scott Ferguson 

On 02/12/2012 06:21 AM, smallufo wrote:

I found my resin 4.0.25 still suffers from terrible memory usage ...
sometime over GC , sometimes FULL GC (and then OOM)...


For memory, you should check the /resin-admin or the pdf-report to get a 
quick view of the main memory problems.




My frontend is  wicket (1.4.19) ,
After running resin just for hours , WEB-INF/tmp/App-filestore grows 
immensely...

It takes minutes to rm -rf the directory...
Not only the files generated by wicket ,
Resin itself also generates terrible BIG file under 
resin_home/resin-data/app-0/distcache :


-rw-rw-r-- 1 smallufo smallufo 30903631872  Feb 12 22:05 data.db
-rw-rw-r-- 1 smallufo smallufo33554432  Feb 12 22:03 mnode.db

It takes about 30GB within hours ...
It grows and grows , and finally resin hangs ...

What's the problem here ?


Probably persistent sessions. If you're using persistent sessions and 
wicket is storing massive sessions and changing them on each operation, 
it can get large. Although 30G is pretty strange.


The data.db is garbage collected, not deleted immediately on session change.

Does that sound possible in your configuration?

-- Scott


Any way to get rid of it ? Is it related to wicket ?

Anyway to limit the size of "data.db"  ?
And is it safe to delete it ?


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest