On 1/2/07, David Sean Taylor <[EMAIL PROTECTED]> wrote:
Audrey MORELLE wrote:
> Hello,
>
> I have two problems that I don't understand.
>
> The first :
>
> Sometimes I deploy my portlet application (which is already deployed
> and working before) and I get this error : Portlet Application X not
> available But the thing that looks strange to me is that I have
> sometimes 1 or 2 portlets of the page which are working not the
> others, how is it possible if they come from the application which is
> said as not available ?!
>
> I'm note sure if my english is clear, so to recapitulate. (With
> fictitious names) I have 2 portlets P1 and P2 in the application
> portlet AP. I already deployed this AP and my two portlets are
> working on my page, everything is ok. Then I put my new version of
> AP.war in deploy directory and it is correctly (log are ok like other
> times) and fully deployed (I checked all files in the
> webapps/AP/WEB-INF directory). I refresh my page containing my two
> portlets and there, only P1 works, P2 shows "Portlet Application AP
> not available". In the console, I only have my trace of P1 and
> nothing about P2, not even an error. If I try to deploy another time,
> It's the same problème P1 is ok, P2 doesn't work. The only thing to
> do is to restart...
>
> I don't know what is the problem...
I haven't seen that one either. Usually when there is a failure, its on
the entire portlet application, not just one of the portlets, and not
the other ones. This kind of problem is usually because of jar locking
on Windows, but that doesn't sound like the case here
Perhaps a review of the Jetspeed and Tomcat log files might uncover a
clue...
>
I have seen this issue. Audrey, which version of jetspeed are you on?
2.0 I suspect...
This happens to me when we re-deploy an app where there is a change to
the portlet.xml file. Most of the time, all portlets in that web app
are "hosed" (technical term meaning non-functional) until we restart
jetspeed/tomcat but sometimes one or two of the portlets in that app
continue to function. Not sure why.
But in 2.0, if you make changes to portlet.xml, you have to restart
and that fixes it. I believe this is fixed in 2.1.
-aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
