And removing the static? Le 10 oct. 2017 11:45, "Paul Carter-Brown" < paul.carter-br...@opposablethumbs.io> a écrit :
> Hi Andy/Romain, > > I'll load on github today and create a ticket. > > I have verified that it is a single instance by having a static > initializer: private static final String uuid = > UUID.randomUUID().toString(); > > The uuid remains the same on both calls to the postconstruct method > > Paul > > On Tue, Oct 10, 2017 at 7:56 AM, Romain Manni-Bucau <rmannibu...@gmail.com > > > wrote: > > > Hi Paul, > > > > Did you check the instance - identity hashcode for instance? I wonder if > it > > is not 2 instances triggered on the same event. > > > > Otherwise Andy is fully right in terms of enabling us to help you. > > > > Le 10 oct. 2017 01:25, "Andy Gumbrecht" <agumbre...@tomitribe.com> a > > écrit : > > > > > Hi Paul, > > > > > > In the interest of safety first, and benefit second, please create a > > > ticket here: https://issues.apache.org/jira/projects/TOMEE > > > > > > Rather than attaching a ZIP here, please consider creating a GitHub > > > project and sharing it in the ticket. > > > > > > Thanks, > > > > > > Andy. > > > > > > On 09/10/17 15:00, Paul Carter-Brown wrote: > > > > > >> Hi, > > >> > > >> Please see attached a test project in which a simple singleton is > being > > >> initialised twice (post construct is called twice). Deploy the ear to > > TomEE > > >> (i'm using 7.0.3) and look at the logs. > > >> > > >> I picked up this issue in a large project with an ear containing many > > >> wars packaged as "skinny". The injected bean is in one of the shared > > >> libraries. > > >> > > >> If the pom in the ear project is changed to > > <skinnyWars>false</skinnyWars> > > >> and lines 44-48 are removed then the issue goes away and the init is > > only > > >> called once. > > >> > > >> Any ideas? > > >> > > >> Paul > > >> > > >> > > >> This email is subject to the disclaimer of Smile Communications > > athttp:// > > >> www.smilecoms.com/home/email-disclaimer/ < > http://www.smilecoms.com/home > > >> /email-disclaimer/> > > >> > > > > > > > > >
