Aaron Evans wrote:
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. :)
That helps a lot, thanks.
Gives me an idea of where to start digging
How big is your portlet.xml?
I can't imagine commons digester being that slow....
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
