Eric
Hmm, normally I would like to restart the instances gracefully. Of
course there might be situations were I would like to do a forceful
shutdown/restart, but I would see this as exceptions to the rule.
If I go to maintenance mode first, how do I know when it is safe to
restart the instance? How do I know if all requests are processed? It
would be good if this could be "automated" and transparent to the user.
Yes :-) .. we are already working on improving the maintenance mode to
be 'automatic' for another user request! This will be available with the
next release, as we need to dig a bit deep into the core to actually
initiate a graceful shutdown. i.e. all thread pools, and "Tasks" etc
must be in a clean state for this
https://issues.apache.org/jira/browse/SYNAPSE-239
Yep, again I invoked on the stop() exposed via JMX by the service
wrapper.. The solution to handle this correctly as you suggest is to
shutdown - but not exit the VM, and will require some changes to the
core ESB code. Shall we file a new JIRA for this, so that we can get
this functionality into the next release? So far, I have not made any
changes to the core distribution to support this illustrative webapp..
However, I agree that your comments are valid and good
Yes! I would love to see this feature in the next release. The WSO2ESB
definitely runs in the right direction from my point of view.
There are only a couple of features missing I would need to be able to
use it in production. I will come up with some of these to discuss it
here on this list during the next days.
http://wso2.org/jira/browse/ESBJAVA-438
Regarding configuration of the esb I would like to make some suggestion in a
separate thread, because this is one of my major concerns with the
current solution.
Sure, we would love to hear your suggestions!
Ok, finally here comes the stack trace:
11:26:35,322 ERROR [STDERR] java.net.MalformedURLException: Service URL
must start with service:jmx:
11:26:35,323 ERROR [STDERR] at
javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:143)
11:26:35,323 ERROR [STDERR] at
org.wso2.esb.ext.manage.ESBManager$NodeManager.connect(ESBManager.java:1
09
Seems like an invalid URL got used from somewhere.. proper logging and
error handling should help us nail this down.. I will do this with the
UI improvements
asankha
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
