this may be very well linked to the fact that I added parental
notification. so if the new http-listener is changed (like setting its
id if I read you correctly) than the parent is also notified. And the
parent is the http-service...
Amy is already asking me to start notifying the grand parents so I am
not sure this is all headed in the right direction. We need a consensus
on how much you want to be notified on your children change ?
Jan, as as quick test, can you see who is the event.getSource() for the
CHANGE event, my wild guess is that it is not the http-service object
but the http-listener. I guess this could be a cheap way for you to
ignore it ;-)
Jerome
Jan Luehe wrote:
> During its execution, QL creates a new http-listener on port 1234, and
> then removes it.
>
> I see these dynamic reconfig events, in this order:
>
> HttpService config changed ADD interface
> com.sun.enterprise.config.serverbeans.HttpListener
>
> HttpService config changed CHANGE interface
> com.sun.enterprise.config.serverbeans.HttpService
>
> HttpService config changed REMOVE interface
> com.sun.enterprise.config.serverbeans.HttpListener
> org.glassfish.config.support.GlassFishConfigBean_at_55a58f
>
> I can explain the ADD and REMOVE events (which are related to the
> creation and removal of the new http-listener ("ls123456") on port 1234,
> respectively), but I'm not sure about the CHANGE event affecting
> http-service, which causes all http-listeners (except for
> admin-listener), including the one on 8080, to be restarted, which is
> causing the subsequent "connection refused" error because the test
> does not wait long enough for the listener (in this case
> http-listener-1) to have completed its restart before accessing it.
>
> Is the CHANGE event for http-service related to the fact that the new
> http-listener (on port 1234) declares the server with id "server" as its
> default-virtual-server, meaning that the "http-listeners" attribute of
> this
> virtual server is updated to include the new http-listener ("ls123456"),
> in addition to "http-listener-1" (the listener on port 8080)?
>
> Question to the admin team:
>
> Rather than emitting a CHANGE event for http-service, could this have
> been emitted as a CHANGE event for the virtual-server "server", which
> would
> be more limited in scope and would avoid a restart of all
> http-listeners, and
> ultimately the issue we are seeing?
>
> Thanks,
>
> Jan
>
> On 09/ 9/08 09:42 AM, Jeanfrancois Arcand wrote:
>> Hi,
>>
>> I've just re-assign issue:
>>
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=6001
>>
>> Can someone from SQE take a look at the issue description. The fix is
>> there :-)
>>
>> A+
>>
>> -- Jeanfrancois
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>