dev@glassfish.java.net

Re: repeated hudson problems with undeploy/shutdown

From: Justin Lee <justin.d.lee_at_oracle.com>
Date: Wed, 16 Jun 2010 15:55:22 -0400

I don't think the create-protocol-* problems are related to the @NotNull
change. I saw those errors, though, and I'll take a look when I get
chance here in a bit.

On 6/16/10 3:52 PM, Amy Roh wrote:
> Web devtests finally went through - the restart problem seems to be
> resolved. However, we are seeing regressions.
>
> These config changes are failing with "No configuration found" - we
> might need @NotNull
>
> server.web-container.property.dispatcher-max-depth
> server.web-container.session-config.session-manager.manager-properties
> server.web-container.session-config.session-properties.property.enableCookies
>
>
> Also, problems with monitoring-service, create-protocol-finder,
> create-protocol-filter - see below for more info.
>
> Amy
>
> ============
>
> request-dispatcher-max-depth: FAIL
>
> No configuration found for
> server.web-container.property.dispatcher-max-depth
>
> [java] Connecting to:
> http://localhost:60538/monitoring/domain/server/http-service/server/request/count503
>
> [java] Get response code: 500
> [java] parseCount:
> [java] [Fatal Error] :1:1: Premature end of file.
> [java] org.xml.sax.SAXParseException: Premature end of file.
> [java] at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:249)
>
> [java] at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
>
> [java] at WebTest.parseCount(Unknown Source)
> [java] at WebTest.getCount(Unknown Source)
> [java] at WebTest.doTest(Unknown Source)
> [java] at WebTest.main(Unknown Source)
> [java]
> [java]
> [java] -----------------------------------------
> [java] - monitor-http-service: FAIL -
> [java] -----------------------------------------
> [java] - Total PASS : 0 -
> [java] - Total FAIL : 1 -
> [java] - Total DID NOT RUN : 0 -
> [java] -----------------------------------------
>
> monitor-servlet-instance: FAIL
>
> monitor-web-request: FAIL
>
> [java] asadmin --host localhost --port 60538 --user anonymous
> --passwordfile
> /files/hudson/workspace/webtier-dev-tests-v3/appserv-tests/config/adminpassword.txt
> --interactive=false --echo=true --terse=true create-protocol-finder
> --protocol pu-protocol --target-protocol pu-dummy-protocol --classname
> org.glassfish.devtests.web.portunif.DummyProtocolFinder --target
> server dummy-finder
> [java]
> [java] remote failure: dummy-finder create failed:
> org.glassfish.devtests.web.portunif.DummyProtocolFinder
> [java] org.glassfish.devtests.web.portunif.DummyProtocolFinder
>
> [java] asadmin --host localhost --port 60538 --user anonymous
> --passwordfile
> /files/hudson/workspace/webtier-dev-tests-v3/appserv-tests/config/adminpassword.txt
> --interactive=false --echo=true --terse=true create-protocol-filter
> --protocol pu-dummy-protocol --classname
> org.glassfish.devtests.web.portunif.DummyProtocolFilter --target
> server dummy-filter
> [java]
> [java] remote failure: dummy-filter create failed:
> org.glassfish.devtests.web.portunif.DummyProtocolFilter
> [java] org.glassfish.devtests.web.portunif.DummyProtocolFilter
>
>
> [java] - create-protocol-finder-dummy: FAIL -
> [java] - create-protocol-filter-dummy: FAIL -
>
> 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 60538 --echo=true --terse=true
> server.web-container.session-config.session-manager.manager-properties.session-id-generator-classname=test.MyUuidGenerator
>
> [exec] asadmin --host localhost --port 60538 --user anonymous
> --passwordfile
> /files/hudson/workspace/webtier-dev-tests-v3/appserv-tests/config/adminpassword.txt
> --interactive=false --echo=true --terse=true set
> server.web-container.session-config.session-manager.manager-properties.session-id-generator-classname=test.MyUuidGenerator
>
> [exec] remote failure: No configuration found for
> server.web-container.session-config.session-manager.manager-properties
> [exec]
> [exec] Result: 1
>
> [java] - session-id-custom-generator: FAIL -
>
> 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 60538 --echo=true --terse=true
> server.web-container.session-config.session-properties.property.enableCookies=false
>
> [exec] asadmin --host localhost --port 60538 --user anonymous
> --passwordfile
> /files/hudson/workspace/webtier-dev-tests-v3/appserv-tests/config/adminpassword.txt
> --interactive=false --echo=true --terse=true set
> server.web-container.session-config.session-properties.property.enableCookies=false
>
> [exec] remote failure: No configuration found for
> server.web-container.session-config.session-properties.property.enableCookies
>
> [exec]
> [exec] Result: 1
>
> [java] - session-property-enableCookies-instance-level: FAIL -
>
>
>
> Shing Wai Chan wrote:
>> The problems seems to be resolved.
>> But I notice the following failure in asadmin command:
>>
>> asadmin --host localhost --port 4848 --user admin --passwordfile
>> /export/gfv3/src/v2/appserv-tests/config/adminpassword.txt
>> --interactive=false --echo=true --terse=true set
>> server.web-container.session-config.session-manager.manager-properties.session-id-generator-classname=test.MyUuidGenerator
>>
>> remote failure: No configuration found for
>> server.web-container.session-config.session-manager.manager-properties
>>
>> There is no error messages in server.log.
>> Shing Wai Chan
>>
>>
>> On 6/14/10 9:16 AM, Hong Zhang wrote:
>>> Yes, seems we need to add @NotNull to the getSystemApplication in
>>> the domain with Jerome's recent changes. I will take care of it.
>>> Thanks!
>>>
>>> - Hong
>>>
>>> On 6/14/2010 11:58 AM, Jennifer Chou wrote:
>>>> Do you need to add @NotNull in the domain or applications config api?
>>>>
>>>> On 6/14/2010 4:49 PM, Hong Zhang wrote:
>>>>> When I was looking into the NPE (which is related to the
>>>>> <system-applications> element), I noticed the create-cluster
>>>>> command somehow removes the <system-applications> element from the
>>>>> domain.xml.
>>>>>
>>>>> I installed a freshly built server, and the <system-applications>
>>>>> element was there as expected. Then I set the environment variable
>>>>> and started the domain, and created a cluster:
>>>>> export ENABLE_REPLICATION=true
>>>>> asadmin start-domain
>>>>> asadmin create-cluster cluster1
>>>>>
>>>>> I noticed after the last command, the <system-applications>
>>>>> element was gone from the domain.xml which caused the NPE in
>>>>> server shutdown.
>>>>>
>>>>> I can add a check in the ApplicationLoaderService to avoid the
>>>>> NPE, but someone should take a look at this as the
>>>>> <system-applications> element need to be there in the domain.xml.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Hong
>>>>>
>>>>> On 6/14/2010 11:15 AM, Hong Zhang wrote:
>>>>>> Hi, Justin
>>>>>> I had trouble with starting server since Friday night, I don't
>>>>>> think it's related to the NPE you saw in the server.log as part
>>>>>> of the server shutdown. That part of the code has not changed for
>>>>>> a while, but I will fix the NPE.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> - Hong
>>>>>>
>>>>>>
>>>>>> On 6/14/2010 11:01 AM, Justin Lee wrote:
>>>>>>> I'm seeing repeated failures with this:
>>>>>>>
>>>>>>> startDomainUnix:
>>>>>>> [echo] Starting DAS, ENABLE_REPLICATION=${ENABLE_REPLICATION}
>>>>>>> [exec] Waiting for the server to start
>>>>>>> ........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
>>>>>>>
>>>>>>> [exec] Command start-domain failed.
>>>>>>> [exec] Error starting domain: domain1. It didn't start in
>>>>>>> 600 seconds
>>>>>>>
>>>>>>>
>>>>>>> Looking in the logs, I see this exception:
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.477-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin|_ThreadID=92;_ThreadName=Thread-1;|Server
>>>>>>> shutdown initiated|#]
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.509-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|java.lang.NullPointerException|#]
>>>>>>>
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.508-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|
>>>>>>> at
>>>>>>> com.sun.enterprise.v3.server.ApplicationLoaderService.preDestroy(ApplicationLoaderService.java:404)|#]
>>>>>>>
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.508-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|
>>>>>>> at
>>>>>>> com.sun.hk2.component.AbstractWombInhabitantImpl.dispose(AbstractWombInhabitantImpl.java:74)|#]
>>>>>>>
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.508-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|
>>>>>>> at
>>>>>>> com.sun.hk2.component.SingletonInhabitant.release(SingletonInhabitant.java:66)|#]
>>>>>>>
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.508-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|
>>>>>>> at
>>>>>>> com.sun.hk2.component.LazyInhabitant.release(LazyInhabitant.java:112)|#]
>>>>>>>
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.508-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|
>>>>>>> at
>>>>>>> com.sun.enterprise.v3.server.AppServerStartup.stop(AppServerStartup.java:393)|#]
>>>>>>>
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.509-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|
>>>>>>> at
>>>>>>> org.jvnet.hk2.osgiadapter.HK2Main$StartupContextService.updated(HK2Main.java:91)|#]
>>>>>>>
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.509-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|
>>>>>>> at
>>>>>>> org.apache.felix.cm.impl.ConfigurationManager$DeleteConfiguration.run(ConfigurationManager.java:1582)|#]
>>>>>>>
>>>>>>>
>>>>>>> [#|2010-06-12T16:28:58.510-0400|SEVERE|glassfish3.1|null|_ThreadID=11;_ThreadName=Thread-1;|
>>>>>>> at
>>>>>>> org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:88)|#]
>>>>>>>
>>>>>>> At least 3 different jobs are failing right after the
>>>>>>> jsp-caching-instance-level test. Anyone have any ideas about
>>>>>>> that? The failing jobs are Grizzly_Integration,
>>>>>>> webtier-dev-tests-v3, and webtier-dev-tests-v3-source. Others
>>>>>>> might be as well, but I know for sure those are.
>>>>>>>
>>>>
>>
>