agreed, but not many people will be duplicating those steps and/or that behavior. I think, only 'howard' will be only person duplicating those steps when installing new versions of tomee snapshot JARs. :)
On Wed, May 22, 2013 at 12:47 AM, Romain Manni-Bucau <[email protected]>wrote: > Well, the main issue was to reproduce it locally for us i think > Le 22 mai 2013 00:27, "Howard W. Smith, Jr." <[email protected]> a > écrit : > > > My apologies. I said that I will stop the noise and proceed by cleaning > up > > the NPE's in my app. Well, evidently, I didn't; I have been working on > > other things in my web app, adding new features for endusers. > > > > After this noisy thread quieted down, I kept 2013-05-10 version of tomee > > 1.6.0 snapshot on my production server, and kept the 2013-05-14 (or > 05-15) > > version on my development server. > > > > Today, I decided to download latest 2013-05-20 (latest) version of tomee > > 1.6.0 snapshot and install on production server, 'but' I forgot about > this > > discussion, until I just duplicated this behavior again. 2013-05-10 > version > > of tomee doesn't have this behavior, but seems as though later versions > > have this behavior (as reported in my previous topic below). > > > > I know, Romain, the conclusion was to re-login to app with newly-opened > > browser tab/window instead of the steps that I listed in my previous > topic > > (below). :) > > > > Well, I will go back to silencing this thread and report back later, if I > > continue experiencing this behavior, since I don't see the error after > > stopping (latest) tomee, deploy new version of my WAR file, start tomee, > > and login to web app. > > > > > > > > > > > > On Wed, May 15, 2013 at 1:12 AM, Howard W. Smith, Jr. < > > [email protected]> wrote: > > > > > I take that back. With that (latest) snapshot, I am seeing some strange > > > (and unwanted) behavior. > > > > > > On user login, I had to 'tighten up' my code and handle some null > pointer > > > exceptions. I really don't know what caused the errors. > > > > > > It seems like the exceptions occur if I do the following steps: > > > > > > 1. start tomee (an earlier version of tomee 1.6.0 snapshot) > > > 2. login to web app > > > 3. logout web app (which takes me back to login page) > > > 4. stop tomee, install latest tomee 1.6.0 snapshot > > > 5. start tomee > > > 6. login to app (since login.xhtml is still open in browser) > > > > > > in the gist[1], you will find: > > > > > > 1. local host log (earlier this evening between 6-7pm my time) which > has > > > exceptions 'after' I attempted to start 'latest' tomee 'snapshot' and > > login > > > my web app > > > > > > 2. tomcat7 stderr log (little before 1am, few minutes ago, my time) > when > > i > > > was attempting to start latest tomee snapshot and login to my web app > > > > > > 3. tomcat7 stderr log between 7pm and 1am, when I was running earlier > > > version of tomee 1.6.0 snapshot > > > > > > I wish I knew what changed in latest tomee for it to start misbehaving > > > this way. :) > > > > > > [1] https://gist.github.com/smithh032772/5581744 > > > > > > > > > > > > On Tue, May 14, 2013 at 1:29 PM, Howard W. Smith, Jr. < > > > [email protected]> wrote: > > > > > >> true... 'others' (myself) just tested latest snapshot and tomee > started > > >> and my web app running/working 'as expected'. :) > > >> > > >> > > >> > > >> > > >> On Tue, May 14, 2013 at 12:53 PM, Romain Manni-Bucau < > > >> [email protected]> wrote: > > >> > > >>> it should only affect ears, a lot of users only deploy wars ;)...but > > >>> others > > >>> can test > > >>> > > >>> *Romain Manni-Bucau* > > >>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > >>> *Blog: **http://rmannibucau.wordpress.com/*< > > >>> http://rmannibucau.wordpress.com/> > > >>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > >>> *Github: https://github.com/rmannibucau* > > >>> > > >>> > > >>> > > >>> 2013/5/14 Howard W. Smith, Jr. <[email protected]> > > >>> > > >>> > when you talk like that, it sounds like 'all' tomee community/users > > >>> should > > >>> > test. :) > > >>> > > > >>> > > > >>> > > > >>> > On Tue, May 14, 2013 at 12:46 PM, Romain Manni-Bucau > > >>> > <[email protected]>wrote: > > >>> > > > >>> > > yes, > > >>> > > > > >>> > > i hacked on the issue too (there was some real issues) so > crossing > > >>> > fingers > > >>> > > to not have broken something else but it should be better > > >>> > > > > >>> > > *Romain Manni-Bucau* > > >>> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > >>> > > *Blog: **http://rmannibucau.wordpress.com/*< > > >>> > > http://rmannibucau.wordpress.com/> > > >>> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > >>> > > *Github: https://github.com/rmannibucau* > > >>> > > > > >>> > > > > >>> > > > > >>> > > 2013/5/14 hwaastad <[email protected]> > > >>> > > > > >>> > > > Hi, > > >>> > > > I found out my problem. My EAR has skinny wars and by accident > > the > > >>> > > ear/lib > > >>> > > > contained a myface-api jar. > > >>> > > > Somehow this worked earlier.... > > >>> > > > > > >>> > > > Well, sorry for making such a fuzz due to my own mistakes :-) > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > -- > > >>> > > > View this message in context: > > >>> > > > > > >>> > > > > >>> > > > >>> > > > http://openejb.979440.n4.nabble.com/Last-1-6-0-Snapshot-exception-tp4662940p4662945.html > > >>> > > > Sent from the OpenEJB User mailing list archive at Nabble.com. > > >>> > > > > > >>> > > > > >>> > > > >>> > > >> > > >> > > > > > >
