And there is nothing in Jetspeed logs? Look for jetspeed-deployment.log jetspeed.log
On Mar 14, 2012, at 6:00 AM, Jeff Pierce wrote: > Our custom portal is built on JS 2.2.0 > > Server version: Apache Tomcat/6.0.18 > Server built: Jul 22 2008 02:00:36 > Server number: 6.0.18.0 > > During some further testing it appears as if the portal web app (ui in our > case) is attempting to start but never comes fully online and therefore > fails to load the other portal apps. > > I'm wondering if we need to turn off autoDeploy and *infuse* our portlet > apps with the necessary settings in web.xml that is typically done for us > by JS. > > Here is a snippet from the catalina log file. This repeats a few times > before finally stopping. Notice the time change when DST rolled. > Mar 11, 2012 1:58:17 AM org.apache.catalina.startup.Catalina start > INFO: Server startup in 48540 ms > Mar 11, 2012 3:00:07 AM org.apache.catalina.startup.HostConfig > checkResources > INFO: Reloading context [/ui-pa] > Mar 11, 2012 3:00:08 AM org.apache.catalina.startup.HostConfig > checkResources > INFO: Reloading context [/host-manager] > Mar 11, 2012 3:00:09 AM org.apache.catalina.startup.HostConfig > checkResources > INFO: Reloading context [/ui] > Mar 11, 2012 3:00:19 AM org.apache.catalina.startup.HostConfig > checkResources > INFO: Reloading context [/sample-pa] > Mar 11, 2012 3:00:21 AM org.apache.catalina.startup.HostConfig > checkResources > INFO: Reloading context [/j2-admin] > Mar 11, 2012 3:00:25 AM org.apache.catalina.startup.HostConfig > checkResources > INFO: Reloading context [/manager] > Mar 11, 2012 3:00:25 AM org.apache.catalina.startup.HostConfig > checkResources > INFO: Reloading context [] > > > And here is a snippet from > > On Tue, Mar 13, 2012 at 10:14 PM, David Sean Taylor < > davidseantay...@gmail.com> wrote: > >> Which version of Jetspeed are you using? >> >> On Mar 13, 2012, at 11:39 AM, Jeff Pierce wrote: >> >>> So this issue has been posted on several sites around the net. I >> understand >>> why the restart is happening so we don't need to go into that. However, >>> because we support running our custom Jetspeed portal on several >> platforms >>> including the IBM i (AS/400,System i) I am hoping that someone on the >>> Jetspeed list can help us figure out why our apps don't come back to life >>> after Tomcat reloads them. Better yet would be to turn off the >> reload/scan >>> completely but more on that below. >>> >>> Due to a permanent IBM restriction and the manner in which lastModified() >>> behaves when the system clock on the IBM i is adjusted for DST this >> causes >>> the class reload function in Tomcat to start recycling the webapps. >>> However, there appears to be some sort of issue occurring that is >>> preventing the portal and the portal apps from fully recycling and coming >>> back up. When you try to access the portal you get the message "Portlet >>> Application ui-pa not available" is not available. This is where our log >>> in occurs. >>> >>> During the recycle you can see the shutdown of the webapps in the log. >> You >>> can then see the attempt to reload them. This behavior seems to cycle >>> through the webapps (portal and different portal apps) a few times then >> the >>> webapps are shutdown and not attempted again. They never get started. >>> >>> We have done some experimenting with the context reloadable attribute >>> without luck. Seems a bit odd as well that the reload is happening given >>> the default value is false for this. >>> >>> We've also changed the autoDeploy Tomcat option. Setting to false >>> prevented the classloader reload from happening. However that has the >>> adverse side-effect that our Jetspeed portal apps don't get deployed when >>> copied to the Jetspeed deploy directory. They get copied to the webapps >>> folder but it takes a second Tomcat restart to get them deployed. That >>> behavior also makes sense but not really an option for us. >>> >>> Ideally we want the Jetspeed deploy to work on Tomcat startup AND not >>> reload the webapps or turn off the scanning by Tomcat to avoid the reload >>> at DST (or any other time). >>> Deploying our portal apps on Tomcat startup only is fine with us. >>> >>> I have the logs if that helps. >>> >>> IBM Restriction Link for those interested: >>> >> http://www-912.ibm.com/8625680A007CA5C6/1AC66549A21402188625680B0002037E/E2A352BBB273A5DC86257861005F0595 >>> >>> >>> Thanks >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org >> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
