[jboss-dev-forums] [Design of the JBoss EJB Container] - Behavior with AbstractKernelController

[anil.saldhana@jboss.com]

I have a usecase wherein a Service needs an attribute set to start correctly. So my testcase does the following:

a) Start the service.  (basically needs to fail)
b) Set the required attribute and start the service.
c) Service should start.

There are issues I see:
1) When the service fails to start, instead of throwing an exception for the following call:

  | server.invoke(serviceOName,"start", new Object[0], new String[0]); 
  | 
the MC logs the error.   So **no** exception is thrown.

2) After the service has failed to start, then removal of the -service.xml from the deploy directory, does not remove the registration of the service (that was done through "create" step)
Basically, what I am saying is that if for any reason, a service fails to "start" after a successful "create" step, then we can not deal with this service in a undeploy->redeploy situation  (Mainly via a testsuite) Until the server bounce, this service is stuck.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966510#3966510

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966510