dev@glassfish.java.net

Re: Unresolved constraint in bundle org.glassfish.main.jdbc.runtime and endless stack traces on failed deployment?

From: Romain Grecourt <romain.grecourt_at_oracle.com>
Date: Thu, 13 Sep 2012 21:03:47 +0200

On 9/13/12 8:55 PM, Marina Vatkina wrote:
> Thanks Romain. I'll rerun the tests.
>
> How about the *3678 lines of stack traces* for a single failed
> deployment of a war file? Which feature is this?
I have no idea !

Thanks,
Romain
>
> -marina
>
> Romain Grecourt wrote:
>> Hi Marina,
>>
>> Simon (cced) made some changes to connector runtime today, he changed
>> some javax.annotation.jms import to javax.jms.
>> It only happened with the Web Profile distribution, however it is
>> currently fixed as he reverted his changes.
>>
>> Thanks,
>> Romain
>>
>> On 9/13/12 8:43 PM, Marina Vatkina wrote:
>>> Several EJB devtests failed on the WEB profile (web.zip) with the
>>> messages like:
>>>
>>> [exec] Caused by: org.osgi.framework.BundleException: Unresolved
>>> constraint in bundle org.glassfish.main.jdbc.runtime [153]: Unable
>>> to resolve 153.0: missing requirement [153.0] osgi.wiring.package;
>>> (&(osgi.wiring.package=com.sun.enterprise.connectors)(version>=4.0.0)(!(version>=5.0.0)))
>>> [caused by: Unable to resolve 207.0: missing requirement [207.0]
>>> osgi.wiring.package; (osgi.wiring.package=javax.jms)]
>>>
>>> JMS is not part of the web profile, so the dependency is wrong.
>>>
>>> Also, the failed deployment produced 41(!) endless stack traces as a
>>> MultiException.
>>>
>>> -marina
>>