I have encountered problems today on TSS main page and other pages.
kodo.util.DataStoreException: java.util.NoSuchElementException: Timeout waiting for idle object
Can you explain why did it happen? Was your web site overloaded and KODO JDO (or Spring) could not handle it anymore? Where is the bottleneck?
This will be quite interesting lesson to learn what technologies to use...
-
kodo.util.DataStoreException: java.util.NoSuchElementException: (3 messages)
- Posted by: Ruslan Zenin
- Posted on: September 19 2005 14:41 EDT
Threaded Messages (3)
- Same here by Horia Muntean on September 19 2005 15:16 EDT
- Spring/KODO by Ruslan Zenin on September 21 2005 11:45 EDT
- long as by Pedro Costa on October 03 2005 06:15 EDT
- Spring/KODO by Ruslan Zenin on September 21 2005 11:45 EDT
-
Same here[ Go to top ]
- Posted by: Horia Muntean
- Posted on: September 19 2005 15:16 EDT
- in response to Ruslan Zenin
Well, nice you were able at least to report the issue. Happened to me also 1 week ago but ironically I couldn't event post the issue to this forum because of those errors.
Regards,
Horia Muntean -
Spring/KODO[ Go to top ]
- Posted by: Ruslan Zenin
- Posted on: September 21 2005 11:45 EDT
- in response to Horia Muntean
I guess no one from TSS is itterested to follow up on this issue.
Would be nice if it was some decent architect on TSS available who can explain why it has such performance problems since it has been migrated to Spring/KODO (including missing posts).
... -
long as[ Go to top ]
- Posted by: Pedro Costa
- Posted on: October 03 2005 18:15 EDT
- in response to Ruslan Zenin
I think that TSS was migrated to Tapestry/KODO. Theres no Spring involved.
As long as I know the problems are caused by a not so well tested migration from Weblogic to JBoss.
Pedro Costa