How would you look for defaults of the configuration that is not loaded? Is
there a load-config-on-demand API?
thanks,
-marina
Marina Vatkina wrote:
> Jerome Dochez wrote:
>
>> On Jun 21, 2010, at 12:40 AM, Jane Young wrote:
>>
>>
>>> No need to compare. It's intended with Jerome's latest changes.
>>> Empty elements in domain.xml are removed in configuration handling code.
>>> Please see Jerome's e-mail:
>>> http://old.nabble.com/Heads-up-%3A-change-in-configuration-handling-td28851178.html
>>>
>>>
>>> I'm pretty sure what you're seeing is related to getMdbContainer()
>>> does not have @NotNull annotation.
>>
>>
>> or more likely, someone should test against a null injected value...
>
>
> It's not injected. In this case, the class that represents the
> configuration is used, but is not loaded by the habitat.
>
> -marina
>
>>
>>
>>> Jane
>>>
>>>
>>> Sanjeeb Sahoo wrote:
>>>
>>>> I will try after upgrading the workspace. In the mean while,
>>>> Jagadish told me that because of some config changes, after QL run,
>>>> mdb-container element vanishes from domain.xml after a QL run. You
>>>> can compare this yourself by comparing between domain.xml in staging
>>>> area and in your installation. Does it indicate a bigger problem?
>>>>
>>>> Thanks,
>>>> Sahoo
>>>>
>>>> On Monday 21 June 2010 12:06 PM, Jane Young wrote:
>>>>
>>>>> I couldn't reproduce this. I ran QL 2 consecutive times without
>>>>> creating a new domain and both times passed.
>>>>>
>>>>> BTW: You may want to update your workspace. From the exception,
>>>>> looks like getMdbContainer(); is missing @NullNull annotation. The
>>>>> fix was committed on Friday.
>>>>>
>>>>> Jane
>>>>>
>>>>>
>>>>> Sanjeeb Sahoo wrote:
>>>>>
>>>>>> It seems QL needs a new domain for it to succeed. Any subsequent
>>>>>> QL run in an existing domain seems to be failing with the
>>>>>> following report:
>>>>>> Total tests run: 115, Failures: 1, Skips: 3
>>>>>>
>>>>>> I have seen it in two to three times now. If I start with a clean
>>>>>> domain, all tests pass. Test report shows
>>>>>> deployJMSAppTest failed. Server.log contains the following:
>>>>>>
>>>>>> [#|2010-06-20T13:48:55.375+0530|SEVERE|glassfish3.1|javax.enterprise.system.container.ejb.mdb.com.sun.ejb.co
>>>>>> Exception in creating message-driven bean container:
>>>>>> [java.lang.NullPointerException]|#]
>>>>>>
>>>>>> [#|2010-06-20T13:48:55.380+0530|SEVERE|glassfish3.1|javax.enterprise.system.container.ejb.mdb.com.sun.ejb.co
>>>>>> ption
>>>>>> java.lang.NullPointerException
>>>>>> at
>>>>>> com.sun.ejb.containers.MessageBeanContainer.createMessageBeanPool(MessageBeanContainer.java:255)
>>>>>> at
>>>>>> com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:188)
>>>>>> at
>>>>>> com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:116)
>>>>>> at
>>>>>> org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:220)
>>>>>> at
>>>>>> org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:207)
>>>>>> at
>>>>>> org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:76)
>>>>>> at
>>>>>> org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:176)
>>>>>> at
>>>>>> org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:229)
>>>>>> at
>>>>>> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:355)
>>>>>> at
>>>>>> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:199)
>>>>>> at
>>>>>> org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:286)
>>>>>> at
>>>>>> com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:324)
>>>>>> at
>>>>>> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:339)
>>>>>> at
>>>>>> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:989)
>>>>>> at
>>>>>> com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:94)
>>>>>>
>>>>>> Is this a known bug?
>>>>>>
>>>>>> Sahoo
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> 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
>