Removing / disabling data-sources requires restart

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Removing / disabling data-sources requires restart

Dominik Pospisil
As adding & enabling can be done on the fly I would expect the same for
removing and disabling. Is this intended?

Thanks,
Dominik
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Removing / disabling data-sources requires restart

Jason T. Greene
There is a special flag you have to pass to the management operation which enables services to restart as a result of the operation. This is more risky because it restarts portions of deployments using the datasource. For example, it will completely restart JPA on every deployment using it, and everything using JPA. The console does not yet allow you to pass in the flag, as it would need to warn what you are about to do.

Sent from my iPhone

On Feb 21, 2012, at 5:26 AM, Dominik Pospisil <[hidden email]> wrote:

> As adding & enabling can be done on the fly I would expect the same for
> removing and disabling. Is this intended?
>
> Thanks,
> Dominik
> _______________________________________________
> jboss-as7-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Removing / disabling data-sources requires restart

Dominik Pospisil
Thanks for clarification Jason. Should the flag (resourceServiceRestartAllowed
?) be required even in the case that the data-source is unused?

Thanks,
Dominik


On Tuesday 21 February 2012 08:04:37 you wrote:

> There is a special flag you have to pass to the management operation which
> enables services to restart as a result of the operation. This is more
> risky because it restarts portions of deployments using the datasource. For
> example, it will completely restart JPA on every deployment using it, and
> everything using JPA. The console does not yet allow you to pass in the
> flag, as it would need to warn what you are about to do.
>
> Sent from my iPhone
>
> On Feb 21, 2012, at 5:26 AM, Dominik Pospisil <[hidden email]> wrote:
> > As adding & enabling can be done on the fly I would expect the same for
> > removing and disabling. Is this intended?
> >
> > Thanks,
> > Dominik
> > _______________________________________________
> > jboss-as7-dev mailing list
> > [hidden email]
> > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Removing / disabling data-sources requires restart

Jason T. Greene
In theory yes, however practically its very difficult to know it's unused. Especially considering a JNDI lookup without a proper dep is possible.

We have a solution for socket bindings were we use on demand services, but data sources can't be trivially be made on demand, due to the way resource ref deps currently work. See what happens when you do a programatic lookup on a lazy infinispan cache using jndi to see what I mean

In the short term the best we could do is change disable to leave the pool but make it throw errors when it's used. Remove would still be hostile.

Sent from my iPhone

On Feb 22, 2012, at 3:56 AM, Dominik Pospisil <[hidden email]> wrote:

> Thanks for clarification Jason. Should the flag (resourceServiceRestartAllowed
> ?) be required even in the case that the data-source is unused?
>
> Thanks,
> Dominik
>
>
> On Tuesday 21 February 2012 08:04:37 you wrote:
>> There is a special flag you have to pass to the management operation which
>> enables services to restart as a result of the operation. This is more
>> risky because it restarts portions of deployments using the datasource. For
>> example, it will completely restart JPA on every deployment using it, and
>> everything using JPA. The console does not yet allow you to pass in the
>> flag, as it would need to warn what you are about to do.
>>
>> Sent from my iPhone
>>
>> On Feb 21, 2012, at 5:26 AM, Dominik Pospisil <[hidden email]> wrote:
>>> As adding & enabling can be done on the fly I would expect the same for
>>> removing and disabling. Is this intended?
>>>
>>> Thanks,
>>> Dominik
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev