Hi all, Asankha, I finally found time to have a look at your small webapp example as well and would like to provide some feedback and raise some questions.
I adjusted the web.xml to include a context param for each of my three esb test nodes. I than deployed the webapp to an outside JBoss AS 4.2.1 GA If all nodes are started via the wrapper, the index.jsp shows three nodes in Status "Started" and everything looks fine. No connection refused exceptions on my side. Besides an java.net.MalformedURLException showing in the JBoss server.log. It seems as if addServer is called with a malformed String (maybe some default context param not intended to be passed to the addServer method?). But that's not that important. Now I have some questions regarding the intended behaviour of each action. THREAD DUMP: This one is clear to me and it works fine for all three nodes. RESTART: The same applies to this. The only thing is that during the restart the status does not update. You can't see what's going on there. But it works. One question: Is this restart graceful? I didn't try whether working processes will get time to finish their work. STOP: What was your intention here? I thought it would stop the esb instance, but not the controlling wrapper. You should be able to start it up again if you like. Stopping the wrapper doesn't seem logical to me. If you do this, you will loose control. Or am I wrong. I tried it and the wrapper stops. Subsequent calls of the index.jsp result in a java.net.ConnectException: Connection refused exception. Of course this should not be the case, even if an esb instance or its corresponding wrapper is down. On the other side the status still reports "Started". So the status does not seem to work at all for me. Now I have not possibility to bring this instance up again. Restart does not work, because I lost the connection. START_MAINTENANCE What is this for? I guess it will stop the esb from accepting new requests while requests which are processed or queued will finish their work. Is this understanding correct? So this feature might be useful for example if you notice problems on one instance in a cluster. You could switch this instance to maintenance. A loadbalancer in front would receive a connection refused and consider the esb instance to be down while using other instances. This sounds quite useful to me. Regards, Eric > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:esb-java-user- > [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: Monday, February 11, 2008 11:27 AM > To: [email protected] > Subject: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: [esb-java- > user]Basicquestions!!! > > > Hi Asankha, > > you got a solution, that pretty good :-) > > I tried it out and I run in an connection problem. :-( > I do configure the wrapper.conf and run your sample as an webapplication. > > Failed to retrieve RMIServer stub: > javax.naming.ServiceUnavailableException > [Root exception is java.rmi.ConnectException: Connection refused to host: > ... > > > > Hartmut Zimmermann > > > Phone: +49 621 60-49477, Fax: +49 621 60-78817, E-Mail: > [EMAIL PROTECTED] > Postal Address: BASF IT Services GmbH, HS-AA - J660, 67059 Ludwigshafen, > Germany > > > www.basf-it-services.com > > > BASF IT Services GmbH, Registered Office: 67059 Ludwigshafen, Germany > Companies' Register: Amtsgericht Ludwigshafen, HRB 3541 > Managing Directors: > Dr. Kurt Ettmüller, Dr. Ralf Sonnberger > Chairman of the Supervisory Board: Andrew Pike > > > > > > "Asankha C. > Perera" > <[EMAIL PROTECTED] An > > [email protected] > Gesendet von: Kopie > esb-java-user-bou > [EMAIL PROTECTED] Thema > Re: Antwort: Re: Antwort: Re: > Antwort: Re: [esb-java-user] > 06.02.2008 11:06 Basicquestions!!! > > > Bitte antworten > an > [EMAIL PROTECTED] > 2.org > > > > > > > Alex, Hubert and Hartmut > > I have attached a sample WAR application with code that can connect to one > or more ESB nodes on a cluster and do basic management via JMX.. please > note that as this is an illustrative sample at the moment, logging and > error handling etc are at basic levels > > asankha > > Alex Reis wrote: > Created JIRA ESBJAVA-425, https://wso2.org/jira/browse/ESBJAVA-425 > > Paul, Asankha, is voting necessary? > > Alex > > 2008/1/31 Asankha C. Perera <[EMAIL PROTECTED]>: > > Hi Alex, Hubert and Hartmut > > When our users ask for any feature we always give higher > priority to them > :-) > > So please file a JIRA for this against the ESB > http://wso2.org/jira/browse/ESBJAVA and I will get it done > probably around > next week > > asankha > > > Alex Reis wrote: > +1 for adding the feature... Probably we should file a JIRA > for the > commons project? > > On Jan 31, 2008 9:42 AM, Hubert, Eric <[EMAIL PROTECTED]> > wrote: > > > Hi, > > Paul, I really like your idea of such an example. I think this > will be > very useful for a lot of users - maybe including us. ;-) > > -- > Eric Hubert > Software Architect > Associate Director Research & Development > > > > > -----Original Message----- > Asankha > > How about we write a sample that shows how to do this? For > example a > portlet that can be used to control an ESB instance and then a > user > could just double it up to build a page of monitoring/control > for a > cluster of WSO2 engines? > > Paul > > _______________________________________________ > Esb-java-user mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > > > > > _______________________________________________ > Esb-java-user mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > > > > > _______________________________________________ > Esb-java-user mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > > > _______________________________________________ > Esb-java-user mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
