> From: Christofer Dutz [mailto:[EMAIL PROTECTED]] > > I thought that the double initialisation would cause my problems, but > the error seems to occur on both initialisations. Is there a way to > prevent Cocoon from doing these two inits?
Cocoon is being initialized twice. That's the bug introduced in the Tomcat 4.0.4b1 and fixed in the 4.0.4-dev. Wait for next Tomcat beta or fallback to previous (say, 4.0.1) release. > The code I used for writing > this component was based on the code of the hsqldb component. > > But to my other question ... the XML-RPC server wants to connect to a > webserver to be able to communicate with client requests. I don't think > that I want to start a new server as described by the XML-RPC guys. > Since I am in a real webserver there should be a way to connect my > XML-RPC server to it ... any ideas? What is XML-RPC server? Servlet? Then deploy it in web.xml, as Cocoon is deployed. Vadim > Regards, > > Christofer Dutz > C-Ware IT-Service > > > -----Ursprüngliche Nachricht----- > Von: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] > Gesendet: Sonntag, 17. März 2002 17:24 > An: [EMAIL PROTECTED] > Betreff: RE: eXist component for Cocoon > > Christofer, > > >>> > When starting this service I get a “java.io.IOException: Address in use: > JVM_Bind” no matter what port I configure eXist to use as RPC-Port. > > ... > > Another question. When looking at the logs it looks like the > initialisation process of most components is run twice on every start up > … why? > <<< > > Assuming that your component is ThreadSafe... I have seen such behavior > with the HSQLDB server bundled with Cocoon and Tomcat 4.0.4. However, > same Cocoon works just fine under Tomcat 4.0.1 - which is strange... I > don't know the reason of this issue yet. > > I think that your server started twice also, and exception is because > second instance couldn’t bind to the port. > > Regards, > Vadim > > > -----Original Message----- > From: Christofer Dutz [mailto:[EMAIL PROTECTED]] > Sent: Sunday, March 17, 2002 10:50 AM > To: [EMAIL PROTECTED] > Subject: eXist component for Cocoon > > Hi > > I have almost finished a first version of a eXist component which allows > eXist to be configured and run from within Cocoon. Everything worked > absolutely fine except one thing. When starting eXist you are usually > able to start up a XML-RPC server for answering XML-RPC requests. When > starting this service I get a “java.io.IOException: Address in use: > JVM_Bind” no matter what port I configure eXist to use as RPC-Port. I > guess that there could be a problem with staring the small Webserver for > serving RPC-Calls. Is there already a XML-RPC server running with Cocoon > and I can simply connect to It? > The code producing the exception is: > > try { > XmlRpc.setEncoding("UTF-8"); > WebServer webServer = new > WebServer(rpcPort); // create a webserver on a give port > RpcServer rpcserv = new > RpcServer(config); // create an eXist RPC-server instance > webServer.addHandler("$default", > rpcserv); // add the eXist RPC handler to the webserver > if (this.getLogger().isDebugEnabled()) { > this.getLogger().debug("Exist RPC-Server > started"); > } > } catch (IOException ioe) { > this.getLogger().debug("IOException - Error > starting RPC-Server ", ioe); > } > > Any ideas? > > Another question. When looking at the logs it looks like the > initialisation process of most components is run twice on every start up > … why? > > Thanx in advance, > > Christofer Dutz > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
