On Jan 15, 2013, at 5:25 PM, Stacy W. Smith <st...@acm.org> wrote: > On Jan 15, 2013, at 2:57 AM, Dennis Krul | Tilaa <den...@tilaa.nl> wrote: >>> Can you tell the PR number you tried to avoid initially ? >> >> I wasn't trying to avoid it. I just thought it wouldn't be interesting, >> because it's an internal PR. But here it is: PR843475 > > I suspect you may have answered a different question than Tima asked. > > It looks like you gave us the internal PR number (843475) tracking your > current issue in 11.4R5 code. > > Please also give us the PR number which JTAC claimed would be fixed by your > upgrade from 10.4 to 11.4R5 per this comment:
Oh yes, I misread, sorry for the confusion. :) The PR for the original issue on 10.4 is not known to us. JTAC told us that was also an internal PR (and obviously because of that there is no mention of it in the release notes either). (To be honest it wouldn't surprise me if they only claimed this to get us to upgrade to the JTAC recommended release, but perhaps that's just me being paranoid.) >> JTAC analysed our core dumps and told us this was a known issue (null >> pointer exception). It would not be resolved in 10.4 but was resolved in >> 11.2R5.5, the recommended JTAC release for EX4200. Regards, -- Dennis Krul Tilaa _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
