You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Hemant Malik <he...@gmail.com> on 2009/02/26 15:14:29 UTC
Error:Portlet Application Not Available
Hi,
I am facing this peculiar problem while using Jetspeed. Please pardon me for
my over descriptive mail but want to figure out the root of other unreliable
experiences as well that I keep on getting while using Jetspeed.
My application on a whole roughly has the below components:
*a) WebApplication [*JSF 1.2 Application*] - *Contains few jsp pages with
Portlets on them(need for jetspeed)
*b) birt-viewer [ *version 2.2.1* ] - *Which contains
reports
*c) Jetspeed war [ *version 2.1.3* ]*
All three of them gets deployed as separate wars on JBoss [Version 4.2.0].
1) To accommodate portlets in the Web Aplication(*a*) I have added
portlet.xml to it. In the web.xml of WebApplication I have added the
following :
<servlet>
<servlet-name>JetspeedContainer</servlet-name>
<display-name>Jetspeed Container</display-name>
<description>
MVC Servlet for Jetspeed Portlet Applications
</description>
<servlet-class>
org.apache.jetspeed.container.JetspeedContainerServlet
</servlet-class>
<init-param>
<param-name>contextName</param-name>
<param-value>ReadiONEPortal</param-value>
</init-param>
<load-on-startup>0</load-on-startup>
</servlet>
- l do not deploy the Web Application(*a*) inside
jetspeed.war/web-inf/deploy/ [ Would that be a problem? ]
- birt-viewer(*b*) also has not been integrated with jetspeed(*c*) as a
portlet application [ Would that be a problem? ]
Now when I use the application it works fine, until this "Portlet
Application WebApplication Not Available" error starts coming on the screen
and the only way to get over is to restart the JBoss server. Once I start
the server again, the same portlet works fine until the next time. On the
JBoss server console the errors I get look something like below:
2009-02-26 19:04:53,866 ERROR
[org.apache.jetspeed.aggregator.impl.RenderingJobImpl] Error rendering
portlet OID SamplePortlet: javax.portlet.UnavailableException: Portlet
Application WebApplication not available
2009-02-26 19:04:54,022 ERROR
[org.apache.jetspeed.aggregator.impl.RenderingJobImpl] Error rendering
portlet OID SamplePortlet: javax.portlet.UnavailableException: Portlet
Application WebApplication** not available
Things I have done with jetspeed(*c*) are:
*a) *In jetspeed.war/web-inf/assembly/jetspeed-spring.xml file I have passed
false to the below bean
<!-- Security: Session Manager -->
<bean
id="org.apache.jetspeed.container.session.PortalSessionsManager"
class="org.apache.jetspeed.container.session.PortalSessionsManagerImpl">
<!-- By default force invalidate portal and portlet applications
when a user logs out (or a session timesout)
For Jetty 6.x which does that already automatically set to
false to prevent ConcurrentModificationException
see https://issues.apache.org/jira/browse/JS2-735
-->
<constructor-arg><value type="boolean">*false*
</value></constructor-arg>
</bean>
I had done this intutively for a problem that I was encountering the first
time Portlets were accessed. I was being sessioned time out in the portlets
for the first time. I did not find any help in particular for the problem,
and guessed this fix just by looking at the comments for the above bean. The
problem got fixed after doing this.
*b) *Added the session-timeout to be 2 hours in the jetspeed's web.xml. This
is because my web application has a time out of 2 hours. Again done
intutively.
c) Added the following filter to jetspeed.
<filter>
<filter-name>staticResourceCachingFilter</filter-name>
<filter-class>org.apache.jetspeed.engine.servlet.StaticResourceCachingFilter</filter-class>
<init-param>
<param-name>ExpireHours</param-name>
<param-value>48</param-value>
</init-param>
</filter>
Al though it seems I had mail already boring, but could someone please guide
me if I am here facing an architectural problem ( the way I have integrated
the three wars) or there is something I need to configure for the above
problem.
Thanks in anticipation.
Hemant Malik
>
>
>
Re: Error:Portlet Application Not Available
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Feb 26, 2009, at 6:14 AM, Hemant Malik wrote:
> Hi,
> I am facing this peculiar problem while using Jetspeed. Please
> pardon me for
> my over descriptive mail but want to figure out the root of other
> unreliable
> experiences as well that I keep on getting while using Jetspeed.
>
> My application on a whole roughly has the below components:
>
> *a) WebApplication [*JSF 1.2 Application*] - *Contains few jsp pages
> with
> Portlets on them(need for jetspeed)
> *b) birt-viewer [ *version 2.2.1* ] - *Which contains
> reports
> *c) Jetspeed war [ *version 2.1.3* ]*
>
> All three of them gets deployed as separate wars on JBoss [Version
> 4.2.0].
>
> 1) To accommodate portlets in the Web Aplication(*a*) I have added
> portlet.xml to it. In the web.xml of WebApplication I have added the
> following :
> <servlet>
> <servlet-name>JetspeedContainer</servlet-name>
> <display-name>Jetspeed Container</display-name>
> <description>
> MVC Servlet for Jetspeed Portlet Applications
> </description>
> <servlet-class>
> org.apache.jetspeed.container.JetspeedContainerServlet
> </servlet-class>
> <init-param>
> <param-name>contextName</param-name>
> <param-value>ReadiONEPortal</param-value>
> </init-param>
> <load-on-startup>0</load-on-startup>
> </servlet>
>
> - l do not deploy the Web Application(*a*) inside
> jetspeed.war/web-inf/deploy/ [ Would that be a problem? ]
>
Should not be a problem, since you added the required servlet entries
in the web.xml. In that case, Jetspeed will automatically register
your application without dropping in the deploy directory
> - birt-viewer(*b*) also has not been integrated with jetspeed(*c*)
> as a
> portlet application [ Would that be a problem? ]
What do you mean by *version 2.2.1 above?
Not sure what you mean by integrated with Jetspeed. We just require
the container servlet for registration, either by (1) dropping in
deploy directory, (2) adding the servlet entry yourself
>
>
> Now when I use the application it works fine, until this "Portlet
> Application WebApplication Not Available" error starts coming on the
> screen
> and the only way to get over is to restart the JBoss server. Once I
> start
> the server again, the same portlet works fine until the next time.
> On the
> JBoss server console the errors I get look something like below:
>
So you are saying that the portlet applications are available for a
while, but then after some time they are not available?
Have you checked the log files? Note that Jetspeed actually keeps log
files in its webapp under the "logs" directory, look under jetspeed.log
Do you actually have a web application named "WebApplication" ... that
sounds like the name used when deploying to JBoss.
Man its been a while since I worked with JBoss and Jetspeed, Im
thinking you need to go through some special deployment and make sure
to give it the same name as the context name in the Jetspeed container
servlet definition in web.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org