So when does the cluster restart? :-)
The spec compliant method is use an init() on a servlet.
You can also use an MBean.
> So when does the cluster restart? :-)
Yes, how to know that... :-)
> The spec compliant method is use an init() on a
What do you mean? I didn't get it...
> You can also use an MBean.
I'm not familiar with MBeans. Are them related to JMX? Can you give some directions...
So, in JBOSS cluster is there any way to track users requests? I'm using a Web services handler to catch the entrance and the exit... But, what happens in a maintenance operation where a jboss cluster instance goes down...How do I prevent that all the users pending requests are shutdown and cleaned on my database/entity beans?
I was joking about a cluster restart.
A cluster shouldn't restart ideally, there will always be
an instance running.
Read the servlet or JMX spec.
See above, why would the cluster ever go down?
I don't follow your requirement?
If you specifically take down the whole the cluster,
why don't you set some state somewhere (the db?)
that says clean the db.
First one to see the "clean" flag resets it and performs the
clean, select for update would be a good way to
hold competing machines.
How can we do a safety shutdown of a single JBOSS instance? In every second, requests are entering the system. If I apply a politic to increase the count a user request in the system, and decrease it when it leaves, during the operation a jboss instance handling that request goes down.
What happens now? Other jboss instance will assume the pending jobs?
How can I improve the performance, the only way of synchronization of entity beans is through the database, right?
If a entity bean could be almost the time updating the counter, it should occurs stores in database every time, right? And, entity beans should be clustered? (since we have the database working on persistence...) Are entity beans adequate for the job? Could it be better doing a JDBC procedure to do this?
I'm trying to improve a solution but I'm really not experienced with J2EE and I would like to avoid system design errors!!
Any precious hints?