> From: Jeroen ter Voorde [mailto:[EMAIL PROTECTED]] > > Hi, > > I read this problem was fixed in the latest tomcat versions. But i still got > the problem with 4.0.4. > It seems it has something to do with the classloader I'm using a singleton > server class which also gets initialized > twice making me think there are two instances of the same class. With
You have some classloading issues, but not the issue in subject of your mail. If you would have multiple servlet initializations, Cocoon will try to initialize twice, including HSQLDB which binds to the port and second instance fails to do so. In tomcat 4.0.4, this does not happen, and this issue is solved. > previous excalibur jars moving all jars from WEB-INF/lib to > tomcat/common/lib fixed the problem. > The latest excalibur jars broke the above solution so my problem is back > again :( > > Any ideas? Make your class Avalon component or make a wrapper around your class. Then Cocoon will be able to manage lifecycle of your class. Vadim > Thanks, > Jeroen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
