Thanks Ajit for trying to run Liferay to recreate this issue. Will need
developer help to take a look to see why NullPointerException at
start-domain time.
The information I collected: "when asadmin start-domain to start the
server, from the exceptions it seems that there is some NPE while
initializing the admin console (GUI)
which prevents the server from starting ..."
Thanks,
Judy
Ajit Kamble wrote:
> I tried building latest Liferay trunk with GFv3 prelude b25. The
> building process was successful.
> But iam getting below error when i start GF. I made sure that ports
> 8080 and 4848 are free before executing start-domain command.
> Note : The Liferay configuration happens during the first start of
> glassfish after build is successful
>
> [#|2008-09-23T13:38:46.040+0530|SEVERE|GlassFish10.0|global|_ThreadID=12;_ThreadName=Thread-3;|Unable
> to start v3. Closing all ports
> java.lang.NullPointerException
> at
> com.sun.enterprise.v3.admin.adapter.AdminConsoleAdapter.init(AdminConsoleAdapter.java:339)
>
> at
> com.sun.enterprise.v3.admin.adapter.AdminConsoleAdapter.postConstruct(AdminConsoleAdapter.java:301)
>
> at
> com.sun.hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java:150)
> at
> com.sun.hk2.component.ConstructorWomb.initialize(ConstructorWomb.java:86)
> at
> com.sun.hk2.component.AbstractWombImpl.get(AbstractWombImpl.java:75)
> at
> com.sun.hk2.component.SingletonInhabitant.get(SingletonInhabitant.java:58)
>
> at
> com.sun.hk2.component.LazyInhabitant.get(LazyInhabitant.java:107)
> at
> com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:60)
>
> at org.jvnet.hk2.component.Habitat$1.get(Habitat.java:252)
> at java.util.AbstractList$Itr.next(AbstractList.java:345)
> at
> com.sun.enterprise.v3.services.impl.GrizzlyService.registerNetworkProxy(GrizzlyService.java:293)
>
> at
> com.sun.enterprise.v3.services.impl.GrizzlyService.postConstruct(GrizzlyService.java:208)
>
> at
> com.sun.hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java:150)
> at
> com.sun.hk2.component.ConstructorWomb.initialize(ConstructorWomb.java:86)
> at
> com.sun.hk2.component.AbstractWombImpl.get(AbstractWombImpl.java:75)
> at
> com.sun.hk2.component.SingletonInhabitant.get(SingletonInhabitant.java:58)
>
> at
> com.sun.hk2.component.LazyInhabitant.get(LazyInhabitant.java:107)
> at
> com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:60)
>
> at
> com.sun.enterprise.v3.server.ApplicationLoaderInjector.postConstruct(ApplicationLoaderInjector.java:52)
>
> at
> com.sun.hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java:150)
> at
> com.sun.hk2.component.ConstructorWomb.initialize(ConstructorWomb.java:86)
> at
> com.sun.hk2.component.AbstractWombImpl.get(AbstractWombImpl.java:75)
> at
> com.sun.hk2.component.SingletonInhabitant.get(SingletonInhabitant.java:58)
>
> at
> com.sun.hk2.component.LazyInhabitant.get(LazyInhabitant.java:107)
> at
> com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:60)
>
> at
> com.sun.enterprise.v3.server.AppServerStartup.run(AppServerStartup.java:184)
>
> at
> com.sun.enterprise.v3.server.AppServerStartup$1.run(AppServerStartup.java:114)
>
> |#]
>
> [#|2008-09-23T13:38:46.350+0530|WARNING|GlassFish10.0|javax.enterprise.system.tools.admin|_ThreadID=13;_ThreadName=Thread-3;|JNDI
> provider for JNDI URLs that look like rmi://host:port/name is not
> working. The JMX RMI connector will not be accessible to clients, even
> if it appears to load correctly. See issues #6025, 5637|#]
>
>
> Thanks
> Ajit
>
> Judy Tang wrote:
>> Thanks Kin-man and Jerome for looking into this issue. We will work
>> together on this. We are asking
>> help from our SQE WebSynergy team to try to see if the issue can be
>> recreated.
>>
>> Thanks,
>> Judy
>> Jerome Dochez wrote:
>>> Kin-man Chung wrote:
>>>>
>>>>
>>>> On 09/22/08 11:10, Jerome Dochez wrote:
>>>>> Kin-man Chung wrote:
>>>>>>
>>>>>>
>>>>>> On 09/22/08 10:49, Jerome Dochez wrote:
>>>>>>> ok good.
>>>>>>>
>>>>>>> I think you ought to say that in the bug report update because
>>>>>>> it did sound like you didn't try. Just mention that it is
>>>>>>> working fine with our internal tests when you request the test
>>>>>>> case.
>>>>>>>
>>>>>> I said so on my first evaluation.
>>>>> all right, sorry for the whistle then.
>>>>>
>>>> No problem. I've worked on Tomcat long enough to learn to ignore
>>>> reports from users that are not willing to even narrow down the
>>>> problem
>>>> or do a little investigation on their own. I won't go as far as as
>>>> Remy
>>>> did most of the time, but...
>>> I certainly hope so :)
>>>
>>> in this particular case, it comes from Adam who has been a very
>>> consistent and reliable source of bug reports so that's why I would
>>> like to ensure we just don't "overlook".
>>>
>>> thanks, jerome
>>>>
>>>> -Kin-man
>>>>
>>>>> jerome
>>>>>>
>>>>>> -Kin-man
>>>>>>
>>>>>>> in any case, I don't think we need the steps, from what Adam
>>>>>>> says, just get liferay...
>>>>>>>
>>>>>>> thanks, jerome
>>>>>>>
>>>>>>> Kin-man Chung wrote:
>>>>>>>> Of course! If thing as basic as this doesn't work, we would have
>>>>>>>> noticed it long ago. TCK and dev tests have such tests. I've
>>>>>>>> also
>>>>>>>> manually tested it.
>>>>>>>>
>>>>>>>> The classpath for JSP compilation is computed and passed to
>>>>>>>> jasper from
>>>>>>>> either the deployer (pre-compilation) or catalina (compiled on
>>>>>>>> demand). The user reported problem with the later. I was asking
>>>>>>>> him to try pre compiling, just to narrow the problem down a
>>>>>>>> little, but I didn't get that info.
>>>>>>>>
>>>>>>>> -Kin-man
>>>>>>>>
>>>>>>>>
>>>>>>>> On 09/22/08 09:57, Jerome Dochez wrote:
>>>>>>>>> So are you saying that we have a test with a WEB-INF/lib jar
>>>>>>>>> file accessed from a JSP and it passes ?
>>>>>>>>>
>>>>>>>>> Sherry Shen wrote:
>>>>>>>>>> Hi Adam,
>>>>>>>>>>
>>>>>>>>>> Can you send us the test steps so that we can reproduce the
>>>>>>>>>> issue?
>>>>>>>>>> Thanks!
>>>>>>>>>>
>>>>>>>>>> Sherry
>>>>>>>>>> Adam Bien wrote, On 9/22/2008 9:31 AM:
>>>>>>>>>>
>>>>>>>>>>> Hi Kchung,
>>>>>>>>>>>
>>>>>>>>>>> you were able to deploy liferay into GF v3 b24/25?
>>>>>>>>>>> Liferay is a part of WebSynergy, Sun / Liferay commitment...
>>>>>>>>>>>
>>>>>>>>>>> I cannot send you the whole portal, because it is too big.
>>>>>>>>>>> It works with TP 2, but not with b24...
>>>>>>>>>>>
>>>>>>>>>>> thanks and regards,
>>>>>>>>>>>
>>>>>>>>>>> adam
>>>>>>>>>>> kchung_at_dev.java.net schrieb:
>>>>>>>>>>>
>>>>>>>>>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=5980
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> User kchung changed the following:
>>>>>>>>>>>>
>>>>>>>>>>>> What |Old value |New value
>>>>>>>>>>>> ================================================================================
>>>>>>>>>>>>
>>>>>>>>>>>> Status|UNCONFIRMED |RESOLVED
>>>>>>>>>>>> --------------------------------------------------------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>> Resolution| |WORKSFORME
>>>>>>>>>>>> --------------------------------------------------------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------- Additional comments from kchung_at_dev.java.net Mon
>>>>>>>>>>>> Sep 22 16:26:44 +0000 2008 -------
>>>>>>>>>>>> Since the test case and clarifications are not forthcoming,
>>>>>>>>>>>> I am closing this as
>>>>>>>>>>>> WFM. Please reopen with a concrete test.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>> quality-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> quality-help_at_glassfish.dev.java.net
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>> quality-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> quality-help_at_glassfish.dev.java.net
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>