I check in a fix for this to the trunk this morning.
Jerome Dochez wrote:
> I agree. do we have someone working on this already ?
>
> On May 11, 2009, at 5:30 PM, Jeanfrancois Arcand wrote:
>
>>
>>
>> Amy Roh wrote:
>>> Kedar Mhaswade wrote:
>>>> Ah. Thanks for the update. Yes, admin-listener should not
>>>> by dynamically reconfigurable for now.
>>>>
>>>> But I thought QL should have caught this. No?
>>> The tests aren't trying to dynamically reconfigure admin-listener.
>>> The tests are trying to dynamically reconfigure
>>> server-config.network-config.transports.transport.tcp in order to
>>> make sure it works as expected.
>>> I wouldn't think QL has transport.tcp tests?
>>> After ClosedChannelException, asadmin is pretty useless returning
>>> 404 for all subsequent calls.
>>
>> I think that needs to be fixed in Admin/AdminAdapter, e.g if the
>> connection gets closed by whatever events, admin should be able to
>> reconnect. The current situation happens because the listeners get
>> turned off then on again, and all connections needs to be closed
>> during the reconfiguration.
>>
>> A+
>>
>> -- Jeanfrancois
>>
>>
>>> Amy
>>>> -Kedar
>>>>
>>>>
>>>> Amy Roh wrote:
>>>>> Kedar Mhaswade wrote:
>>>>>> Do you randomly get this error on any command?
>>>>>>
>>>>>> Have you started getting this recently? Is it possible for you to
>>>>>> run the
>>>>>> devtests with a previous build (like b48)?
>>>>>
>>>>> Hudson started reporting this today. I was able to isolate the
>>>>> issue. It seems that new issue was introduced where dynamic
>>>>> reconfiguration for
>>>>> configs.config.server-config.network-config.transports.transport.tcp.acceptor-threads
>>>>> is causing ClosedChannelException at AdminAdapter.service - which
>>>>> caused 404. I've filed 8287.
>>>>>
>>>>> asadmin set
>>>>> configs.config.server-config.network-config.transports.transport.tcp.acceptor-threads=5
>>>>>
>>>>> Remote server does not listen for requests on [localhost:4848].
>>>>> Is the server up?
>>>>> No such local command, set. To run remote commands, start the
>>>>> application server (e.g. asadmin start-domain).
>>>>> Command set failed.
>>>>>
>>>>> [#|2009-05-11T13:23:08.492-0700|SEVERE|glassfish|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=17;_ThreadName=Thread-1;|service
>>>>> exception
>>>>> java.lang.RuntimeException: ClientAbortException:
>>>>> java.nio.channels.ClosedChannelException
>>>>> at
>>>>> com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
>>>>>
>>>>> at
>>>>> com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:165)
>>>>>
>>>>>
>>>>> Caused by: ClientAbortException:
>>>>> java.nio.channels.ClosedChannelException
>>>>> at
>>>>> com.sun.grizzly.tcp.http11.GrizzlyOutputBuffer.doFlush(GrizzlyOutputBuffer.java:436)
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Amy
>>>>>
>>>>>>
>>>>>> -Kedar
>>>>>>
>>>>>>
>>>>>> Amy Roh wrote:
>>>>>>> I am noticing 404 status returning from asadmin commands from
>>>>>>> web devtest on Hudson. What could be causing these 404s from
>>>>>>> asadmin? It seems the server is still running and is available.
>>>>>>>
>>>>>>> asadmin-common-ignore-fail:
>>>>>>> [echo] asadmin set --user anonymous --passwordfile
>>>>>>> /files/hudson/workspace/webtier-dev-tests-v3/appserv-tests/config/adminpassword.txt
>>>>>>> --host localhost --port 34182 --echo=true --terse=true
>>>>>>> configs.config.server-config.network-config.protocols.protocol.http-listener-2.http.timeout-seconds=0
>>>>>>>
>>>>>>> [exec] set --echo=true --terse=true --port=34182
>>>>>>> --host=localhost
>>>>>>> --passwordfile=/files/hudson/workspace/webtier-dev-tests-v3/appserv-tests/config/adminpassword.txt
>>>>>>> --user=anonymous
>>>>>>> configs.config.server-config.network-config.protocols.protocol.http-listener-2.http.timeout-seconds=0
>>>>>>>
>>>>>>> [exec] Status: 404
>>>>>>> [exec] Result: 1
>>>>>>>
>>>>>>> stopDomain:
>>>>>>> [echo] run.xml:stopping domain...
>>>>>>> [exec] com.sun.enterprise.cli.framework.CommandException:
>>>>>>> Status: 404
>>>>>>> [exec] Command stop-domain failed.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Amy
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>