8:57 p.m.
Rewording to make (a little) more sense.
On 06/17/2013 04:26 PM, Scott Marlow wrote:
Which Phase is the last one that application deployment dependencies
can
be added?
I didn't mean the deployment module spec dependencies (JPA dup sets
those during the Phase.DEPENDENCIES).
The persistence unit service depends on the second level cache service
and the deployments ComponentDescriptions have a required dependency on
the persistence unit service.
However, we may wait until the Phase.INSTALL, to update the deployments
ComponentDescriptions dependencies (via
ComponentDescriptions.addDependency(persistenceUnitService, REQUIRED)).
Is Phase.INSTALL too late to add an application dependency on the 2LC?
On 06/15/2013 08:25 AM, Scott Marlow wrote:
> On 06/14/2013 11:49 PM, Jaikiran Pai wrote:
>> Hi Scott,
>>
>> I added a comment to that JIRA
>> https://issues.jboss.org/browse/WFLY-1531#comment-12781836 explaining
>> what the problem is.
>
> Thanks for the help Jaikiran! As a start, I'll try the (minimal fix
> that you mentioned) calling ServiceController.awaitValue() instead of
> getValue().
>
> As far as what the missing "proper dependencies" are, perhaps we could
> discuss that in freenode irc room #jboss-clustering sometime, so Paul
> can also be involved in the discussion.
>
>>
>> -Jaikiran
>> On Friday 14 June 2013 08:14 PM, Scott Marlow wrote:
>>> I'm looking into why the
>>> org.hibernate.cache.infinispan.InfinispanRegionFactory.manager instance
>>> variable is null after it should still be non-null (WFLY-1531) that
>>> caused
>>>
org.jboss.as.test.clustering.cluster.ejb3.security.FailoverWithSecurityTestCase
>>>
>>> to fail with a NPE on Tomaz's test machine.
>>>
>>> If anyone sees NPE failures in
>>>
org.jboss.as.test.clustering.cluster.ejb3.security.FailoverWithSecurityTestCase,
>>>
>>> please let me know. +10 if you can save the clustered testsuite
>>> server.log so we can see if the previous test completed before starting
>>> FailoverWithSecurityTestCase. :)
>>>
>>> On 06/12/2013 03:01 PM, Jason Greene wrote:
>>>> We still have a number intermittent test failures that have been
>>>> around for over a year now. I'm asking for everyone's help in
doing
>>>> what we can to make them stable. If you submit a PR, and you see what
>>>> looks like an intermittent failure, can you do some investigation and
>>>> report your findings even if it is not your area? It would be awesome
>>>> if you can report what you find to the mailing list, and rope in help.
>>>>
>>>> Nearly all of these seem to only occur when virtualization is
>>>> involved, so if need be we can work out a plan to create either a
>>>> special run to capture diagnostic info, or I can give access to a
>>>> dedicated slave.
>>>>
>>>> If anyone has any further ideas on how to tackle these issues I am
>>>> all ears.
>>>>
>>>> --
>>>> Jason T. Greene
>>>> WildFly Lead / JBoss EAP Platform Architect
>>>> JBoss, a division of Red Hat
>>>>
>>>>
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> wildfly-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev