On 7/18/06, David Sean Taylor <[EMAIL PROTECTED]> wrote:
Aaron Evans wrote:
> I think I have mentioned this before, but I also see this error if
> jetspeed has already deployed my updated webapp, but it has not yet
> finished the process of deleting all the old registry entries and
> re-registering the portlets.
Do you see the webapp being partially expanded, or does Tomcat fully
expand it successfully?
Sorry, my bad. In this situation, I get a different message: "Portlet
Application <my-portlet-context-name> not available".
If you still want to know though:
Note: This is in Jetspeed 2.0, not sure about later versions.
The war does get fully expanded. I can see that from a servlet-webapp
point of view, the app is ready for business (and I can hit the
deployed servlets).
What I see in deployment.log is first:
2006-07-18 14:00:45,675 [Autodeployment File Scanner Thread] INFO
deployment - File: C:\Program Files\Apache Software Foundation\Tomcat
5.5\webapps\jetspeed\WEB-INF\deploy\tpn-portlet.war deployed
And then, shortly after:
2006-07-18 14:00:57,822 [Timer-11] INFO deployment - Remove all
registry entries defined for portlet application tpn-portlet
2006-07-18 14:01:36,798 [Timer-11] INFO deployment - Loading
portlet.xml....tpn-portlet
2006-07-18 14:01:57,789 [Timer-11] INFO deployment - No extended
metadata found.
2006-07-18 14:01:57,789 [Timer-11] INFO deployment - Loading
web.xml....tpn-portlet
2006-07-18 14:02:14,873 [Timer-11] INFO deployment - Registered the
portlet application tpn-portlet
2006-07-18 14:02:14,873 [Timer-11] INFO deployment - Registered the
portlet application in the search engine... tpn-portlet
But sometimes (in my windows dev environment), there can be up to a 3
minute delay between the first message (war deployed) and the second
set of messages (that start with "Remove all registry entries..." and
ending with "Registered the portlet application...".
If I try to hit a portlet in this application between the "war
deployed" message the the "Registered the portlet application" then I
get the "Portlet Application tpn-portlet not available" message.
The problem clears up after the whole process has completed though.
So it just looks as though the timer thread that is responsible for
re-registering can sometimes take a while to get going. And then
when it does, because my war file and my portlet.xml files are so big,
it takes a bit of CPU power to complete. :)
-aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
