Okay I checked per your suggestion, two files feed_apache.xreg and feed_local.xreg were incomplete, the other xreg files are complete, ie the two faulty ones is somehow cut-off right after <description> tag. I do not have the server connected to the internet so I suspect thats what is causing the incomplete xreg. Is it necessary to have the server working (locally) without internet connetion? Btw, are these faulty xreg gets filled at initialization? I have waited a good 10 minutes between tomcat restart to give ample time for a graceful shutdown but this did not cure it either, still getting same exception. Also I have discovered that the session SESSIONS.ser is indeed stashed on work/Standalone/localhost/jetspeed/ at tomcat shutdown. But then at re-start of tomcat or re-start of just jetspeed(via the manager console) this SESSIONS.ser is erased immediately. I tried to store this SESSIONS.ser in another dir and copied it back upon re-start hoping it would cure the problem but no luck.
Still awaiting resolution. Thanks. --- Aurelien Pernoud <[EMAIL PROTECTED]> wrote: > > Dev are currently busy on JS 2.0 ;) You're on the > good place to ask for > help. > > If I remember well, I've also seen this NPE when I > didn't wait for tomcat to > properly close (windows says that tomcat isn't > responding, asks if I should > kill it or wait, and here one should NEVER kill it, > click wait, it will > work). The story is that when tomcat shutdowns, it > shutdowns jetspeed > servlet, and at shutdown, jetspeed registry service > rewrites xreg files > (there may be new portlets added via jetspeed web > interface that are only in > memory and needs to be saved). If you don't wait for > jetspeed to finish its > regitry rewriting, then your xreg files are > corrupted and at next startup > you get that exception (again, I *think* it's this > exception but I'm not > sure). > > Check all the xreg files in the WEB-INF/conf > directory, and see if one > (portlets.xreg, admin.xreg, whatever.xreg) isn't > good (which means it starts > by <registry> tag but suddenly stops, like if tomcat > process was killed > during shutdown). > > HTH, > Aurelien > > aps ku a ecrit : > > > I have just downloaded version > > jetspeed-1.4-b4-src.zip and same Horrible > Exception > > error. Is there any resolution to this at all? or > > this is the wrong list to ask or no developers > ever > > look in this list to help us new users of > jetspeed? > > Where would be the right place to ask this > question > > and get some kind of definite resolution? > > > > > > --- aps ku <[EMAIL PROTECTED]> wrote: > >> Interesting to know. I did a re-install, got > >> things > >> working and followed your suggestion of logging > out, > >> BUT still same error shows when restarting > Tomcat. I > >> even had the browser shutdown and closed and > start > >> fresh just in case it has something to do with it > >> but > >> same errors. > >> Anyhow, why would a mere a user not logged out > >> would cause such havoc? Whats behind all these > >> causing such a headache? What is triggering that > >> at > >> > > > org.apache.jetspeed.modules.pages.JetspeedTemplatePage.doBuild > > BeforeAction(JetspeedTemplatePage.java:159) > >> > >> aps ku > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
