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 Tender Slim <xs...@gmx.com> on 2010/03/26 00:45:53 UTC
The requested resource (/container) is not available
Does anyone know which class is generating the following message: “The
requested resource (/container) is not available”? I want to find the source
of the damned problem.
The message is generated one per fragment declared in my psml. And in the
past three days, I have tried all sorts of combinations but to no avail. I
have eye-ball checked my program more than a dozen times – also, to no
avail. I am coming very close to abandoning Jetspeed for the project I am
working on even if that cost me financially – I have heard enough of this
torture called jetspeed.
--
View this message in context: http://old.nabble.com/The-requested-resource-%28-container%29-is-not-available-tp28036609p28036609.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: The requested resource (/container) is not available
Posted by Tender Slim <xs...@gmx.com>.
Hi Woonsan Ko,
Thanks for your response.
The Jetspeed Container servlet entry in my web.xml is exactly the same as
yours except the contextName.
Also I don't have any jetspeed related jars in my web-inf/lib (in
deployment); I put them in jboss server/default/lib
>> Are you using Jetspeed-2.2.x?
>>If so, logging configuration files are in /WEB-INF/classes/ folder in each
web apps. (log4j.xml or >>log4.properties) Please have a look at the log
file locations.
I am using 2.2.0. And the log files are in my JBoss /log directory where I
have my other log files. I mentioned them earlier.
Though I already have what you suggested, still, I have carefully re-checked
every one of your suggestions against what I have. I then deployed it –
hoped for miracle –, but was disappointed to the dreaded: “The requested
resource (/container) is not available”, again.
I would imagine that using Jetspeed in production would be too much trouble
– I have already spent three days on this problem and no business can afford
to have its website down for three days.
Thanks for your help.
Woonsan Ko wrote:
>
> Hi Tender,
>
> Please see my comments below.
>
>
>
> ----- Original Message ----
>> From: Tender Slim <xs...@gmx.com>
>> To: jetspeed-user@portals.apache.org
>> Sent: Fri, March 26, 2010 2:48:24 PM
>> Subject: Re: The requested resource (/container) is not available
>>
>>
> Hi David Sean Taylor-3,
>
> Thanks for your response. The “Could be
>> caused by any number of reasons” is
> part of the problem in identifying the
>> actual problem.
>
> The error message, "The requested resource ({0}) is not available.", is
> generated by the servlet container on 404 error.
> Tomcat contains the resource property like this: [1]
>
> standardContext.notFound=The requested resource ({0}) is not available.
>
> [1]
> http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/java/org/apache/catalina/core/LocalStrings.properties
>
> It means the container cannot find a servlet mapped by /container.
> So, we could guess the following Jetspeed Container servlet and its
> mapping are not included in web.xml of your portlet app. (e.g. "/mypa")
>
> <servlet>
> <description>MVC Servlet for Jetspeed Portlet
> Applications</description>
> <display-name>Jetspeed Container</display-name>
> <servlet-name>JetspeedContainer</servlet-name>
> <servlet-class>
>
> org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class>
> <init-param>
> <param-name>contextName</param-name>
> <param-value>mypa</param-value>
> </init-param>
> <load-on-startup>100</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>JetspeedContainer</servlet-name>
> <url-pattern>/container/*</url-pattern>
> </servlet-mapping>
>
> Or, it's possible that the servlet is not initialized properly for some
> reason.
> For example, if you have either portlet-api jar, jetspeed-api jar or
> jetspeed-commons jar in /mypa/WEB-INF/lib, then it would make a problem.)
>
> I must have eyeball checked my web.xml, for mistakes, a
>> dozen times. The
> entry is there – there is not doubt about it. And I have
>> also checked in the
> following log file – I use
>> JBoss-5.1.0:
>
> log/server.log
> log/portal/jetspeed.log
> log/portal/jetspeed-deployment.log
> log/portal/jetspeed-diagnostics.log
> log/portal/jetspeed-digester.log
> log/portal/jetspeed-ojb.log
> log/portal/jetspeed-pluto.log
> log/portal/jetspeed-scheduler.log
> log/portal/jetspeed-velocity.log
> log/portal/webcontent.log
> log/portal/webcontent-velocity.log
>
> All
>> the files except the server.log are either empty or does not contain
> that
>> message. And server.log has no entry relating to the message – not even
> after
>> changing the log level to DEBUG .
>
> Are you using Jetspeed-2.2.x?
> If so, logging configuration files are in /WEB-INF/classes/ folder in each
> web apps. (log4j.xml or log4.properties) Please have a look at the log
> file locations.
>
> My project is packaged as ear
>> and it includes
>> :
> jetspeed(-demo)
> j2-admin
> webcontent
> dbbrowser
> rss
> my portlet
>> projects.
>
> I deploy the ear file to JBoss and it works. All portlets
>> application are
> registered in the portlet_application and portlet_definition
>> tables in my
> postgresql database. The problem only occurs when I try to run
>> the portlet
> from my portlet projects.
>
> Do you mean your portlet app doesn't work while other portlet apps work?
> If so, I'd like to suggest you have a look at web.xml and /WEB-INF/lib
> folder.
> FYI, with Jetspeed-2.2.x, the following jar files must be located in the
> shared lib folder only (You shouldn't include those in your portlet app):
> - apa-logging-*.jar
> - ccpp-*.jar
> - jetspeed-api-*.jar
> - jetspeed-commons-*.jar
> - pluto-container-api-*.jar
> - pluto-taglib-*.jar
> - portals-bridges-common-*.jar
> - portlet-api*.jar
>
>
> I think you could try to debug on
> org.apache.jetspeed.container.JetspeedContainerServlet#init() method on
> startup if necessary.
>
> Kind regards,
>
> Woonsan
>
>
> Portlet Bridge: I have tried the
>> following portlets bridge without
>> any
> changes
>
> portlet-bridge-api-2.0.0-alpha.jar
> portlet-bridge-impl-2.0.0-alpha.jar
>
> and
>>
>
> portletbridge-api-2.0.0.CR1.jar
> portletbridge-impl-2.0.0.CR1.jar
>
> I
>> hope someone will tell me the class where I can find the error so that I
> can
>> debug the source file and identify the real cause(s) of the
>> problem.
>
> Thanks again.
>
>
> David Sean Taylor-3 wrote:
>>
>>
>> On Thu, Mar 25, 2010 at 4:45 PM, Tender Slim <
>> ymailto="mailto:xsdt@gmx.com" href="mailto:xsdt@gmx.com">xsdt@gmx.com>
>> wrote:
>>>
>>> Does anyone know which class is generating the
>> following message: “The
>>> requested resource (/container) is not
>> available”? I want to find the
>>> source
>>> of the damned
>> problem.
>>>
>> I think it means your portlet application failed to
>> start. Could be
>> caused by any number of reasons
>> Check the tomcat
>> and jetspeed logs for exceptions, stack traces
>> Also, please verify the
>> web.xml in your *deployed* web application has
>> an entry like (but not
>> exactly):
>>
>> <servlet>
>>
>> <description>MVC Servlet for Jetspeed Portlet
>>
>> Applications</description>
>>
>> <display-name>Jetspeed Container</display-name>
>>
>> <servlet-name>JetspeedContainer</servlet-name>
>>
>> <servlet-class>
>>
>>
>> org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class>
>>
>> <init-param>
>>
>> <param-name>contextName</param-name>
>>
>> <param-value>j2-admin</param-value>
>>
>> </init-param>
>>
>> <load-on-startup>100</load-on-startup>
>>
>> </servlet>
>>
>> <servlet-mapping>
>>
>> <servlet-name>JetspeedContainer</servlet-name>
>>
>> <url-pattern>/container/*</url-pattern>
>>
>> </servlet-mapping>
>>
>>
>> ---------------------------------------------------------------------
>> To
>> unsubscribe, e-mail:
>> ymailto="mailto:jetspeed-user-unsubscribe@portals.apache.org"
>> href="mailto:jetspeed-user-unsubscribe@portals.apache.org">jetspeed-user-unsubscribe@portals.apache.org
>>
>> For additional commands, e-mail:
>> ymailto="mailto:jetspeed-user-help@portals.apache.org"
>> href="mailto:jetspeed-user-help@portals.apache.org">jetspeed-user-help@portals.apache.org
>>
>>
>>
>>
>
> --
> View this message in context:
>> http://old.nabble.com/The-requested-resource-%28-container%29-is-not-available-tp28036609p28042719.html
> Sent
>> from the Jetspeed - User mailing list archive at
>> href="http://Nabble.com">Nabble.com.
>
>
> ---------------------------------------------------------------------
> To
>> unsubscribe, e-mail:
>> ymailto="mailto:jetspeed-user-unsubscribe@portals.apache.org"
>> href="mailto:jetspeed-user-unsubscribe@portals.apache.org">jetspeed-user-unsubscribe@portals.apache.org
> For
>> additional commands, e-mail:
>> ymailto="mailto:jetspeed-user-help@portals.apache.org"
>> href="mailto:jetspeed-user-help@portals.apache.org">jetspeed-user-help@portals.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/The-requested-resource-%28-container%29-is-not-available-tp28036609p28045281.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: The requested resource (/container) is not available
Posted by Woonsan Ko <wo...@yahoo.com>.
Hi Tender,
Please see my comments below.
----- Original Message ----
> From: Tender Slim <xs...@gmx.com>
> To: jetspeed-user@portals.apache.org
> Sent: Fri, March 26, 2010 2:48:24 PM
> Subject: Re: The requested resource (/container) is not available
>
>
Hi David Sean Taylor-3,
Thanks for your response. The “Could be
> caused by any number of reasons” is
part of the problem in identifying the
> actual problem.
The error message, "The requested resource ({0}) is not available.", is generated by the servlet container on 404 error.
Tomcat contains the resource property like this: [1]
standardContext.notFound=The requested resource ({0}) is not available.
[1] http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/java/org/apache/catalina/core/LocalStrings.properties
It means the container cannot find a servlet mapped by /container.
So, we could guess the following Jetspeed Container servlet and its mapping are not included in web.xml of your portlet app. (e.g. "/mypa")
<servlet>
<description>MVC Servlet for Jetspeed Portlet Applications</description>
<display-name>Jetspeed Container</display-name>
<servlet-name>JetspeedContainer</servlet-name>
<servlet-class>
org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class>
<init-param>
<param-name>contextName</param-name>
<param-value>mypa</param-value>
</init-param>
<load-on-startup>100</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>JetspeedContainer</servlet-name>
<url-pattern>/container/*</url-pattern>
</servlet-mapping>
Or, it's possible that the servlet is not initialized properly for some reason.
For example, if you have either portlet-api jar, jetspeed-api jar or jetspeed-commons jar in /mypa/WEB-INF/lib, then it would make a problem.)
I must have eyeball checked my web.xml, for mistakes, a
> dozen times. The
entry is there – there is not doubt about it. And I have
> also checked in the
following log file – I use
> JBoss-5.1.0:
log/server.log
log/portal/jetspeed.log
log/portal/jetspeed-deployment.log
log/portal/jetspeed-diagnostics.log
log/portal/jetspeed-digester.log
log/portal/jetspeed-ojb.log
log/portal/jetspeed-pluto.log
log/portal/jetspeed-scheduler.log
log/portal/jetspeed-velocity.log
log/portal/webcontent.log
log/portal/webcontent-velocity.log
All
> the files except the server.log are either empty or does not contain
that
> message. And server.log has no entry relating to the message – not even
after
> changing the log level to DEBUG .
Are you using Jetspeed-2.2.x?
If so, logging configuration files are in /WEB-INF/classes/ folder in each web apps. (log4j.xml or log4.properties) Please have a look at the log file locations.
My project is packaged as ear
> and it includes
> :
jetspeed(-demo)
j2-admin
webcontent
dbbrowser
rss
my portlet
> projects.
I deploy the ear file to JBoss and it works. All portlets
> application are
registered in the portlet_application and portlet_definition
> tables in my
postgresql database. The problem only occurs when I try to run
> the portlet
from my portlet projects.
Do you mean your portlet app doesn't work while other portlet apps work?
If so, I'd like to suggest you have a look at web.xml and /WEB-INF/lib folder.
FYI, with Jetspeed-2.2.x, the following jar files must be located in the shared lib folder only (You shouldn't include those in your portlet app):
- apa-logging-*.jar
- ccpp-*.jar
- jetspeed-api-*.jar
- jetspeed-commons-*.jar
- pluto-container-api-*.jar
- pluto-taglib-*.jar
- portals-bridges-common-*.jar
- portlet-api*.jar
I think you could try to debug on org.apache.jetspeed.container.JetspeedContainerServlet#init() method on startup if necessary.
Kind regards,
Woonsan
Portlet Bridge: I have tried the
> following portlets bridge without
> any
changes
portlet-bridge-api-2.0.0-alpha.jar
portlet-bridge-impl-2.0.0-alpha.jar
and
>
portletbridge-api-2.0.0.CR1.jar
portletbridge-impl-2.0.0.CR1.jar
I
> hope someone will tell me the class where I can find the error so that I
can
> debug the source file and identify the real cause(s) of the
> problem.
Thanks again.
David Sean Taylor-3 wrote:
>
>
> On Thu, Mar 25, 2010 at 4:45 PM, Tender Slim <
> ymailto="mailto:xsdt@gmx.com" href="mailto:xsdt@gmx.com">xsdt@gmx.com>
> wrote:
>>
>> Does anyone know which class is generating the
> following message: “The
>> requested resource (/container) is not
> available”? I want to find the
>> source
>> of the damned
> problem.
>>
> I think it means your portlet application failed to
> start. Could be
> caused by any number of reasons
> Check the tomcat
> and jetspeed logs for exceptions, stack traces
> Also, please verify the
> web.xml in your *deployed* web application has
> an entry like (but not
> exactly):
>
> <servlet>
>
> <description>MVC Servlet for Jetspeed Portlet
>
> Applications</description>
>
> <display-name>Jetspeed Container</display-name>
>
> <servlet-name>JetspeedContainer</servlet-name>
>
> <servlet-class>
>
>
> org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class>
>
> <init-param>
>
> <param-name>contextName</param-name>
>
> <param-value>j2-admin</param-value>
>
> </init-param>
>
> <load-on-startup>100</load-on-startup>
>
> </servlet>
>
> <servlet-mapping>
>
> <servlet-name>JetspeedContainer</servlet-name>
>
> <url-pattern>/container/*</url-pattern>
>
> </servlet-mapping>
>
>
> ---------------------------------------------------------------------
> To
> unsubscribe, e-mail:
> ymailto="mailto:jetspeed-user-unsubscribe@portals.apache.org"
> href="mailto:jetspeed-user-unsubscribe@portals.apache.org">jetspeed-user-unsubscribe@portals.apache.org
>
> For additional commands, e-mail:
> ymailto="mailto:jetspeed-user-help@portals.apache.org"
> href="mailto:jetspeed-user-help@portals.apache.org">jetspeed-user-help@portals.apache.org
>
>
>
>
--
View this message in context:
> http://old.nabble.com/The-requested-resource-%28-container%29-is-not-available-tp28036609p28042719.html
Sent
> from the Jetspeed - User mailing list archive at
> href="http://Nabble.com">Nabble.com.
---------------------------------------------------------------------
To
> unsubscribe, e-mail:
> ymailto="mailto:jetspeed-user-unsubscribe@portals.apache.org"
> href="mailto:jetspeed-user-unsubscribe@portals.apache.org">jetspeed-user-unsubscribe@portals.apache.org
For
> additional commands, e-mail:
> ymailto="mailto:jetspeed-user-help@portals.apache.org"
> href="mailto:jetspeed-user-help@portals.apache.org">jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: The requested resource (/container) is not available
Posted by Tender Slim <xs...@gmx.com>.
Hi David Sean Taylor-3,
Thanks for your response. The “Could be caused by any number of reasons” is
part of the problem in identifying the actual problem.
I must have eyeball checked my web.xml, for mistakes, a dozen times. The
entry is there – there is not doubt about it. And I have also checked in the
following log file – I use JBoss-5.1.0:
log/server.log
log/portal/jetspeed.log
log/portal/jetspeed-deployment.log
log/portal/jetspeed-diagnostics.log
log/portal/jetspeed-digester.log
log/portal/jetspeed-ojb.log
log/portal/jetspeed-pluto.log
log/portal/jetspeed-scheduler.log
log/portal/jetspeed-velocity.log
log/portal/webcontent.log
log/portal/webcontent-velocity.log
All the files except the server.log are either empty or does not contain
that message. And server.log has no entry relating to the message – not even
after changing the log level to DEBUG .
My project is packaged as ear and it includes :
jetspeed(-demo)
j2-admin
webcontent
dbbrowser
rss
my portlet projects.
I deploy the ear file to JBoss and it works. All portlets application are
registered in the portlet_application and portlet_definition tables in my
postgresql database. The problem only occurs when I try to run the portlet
from my portlet projects.
Portlet Bridge: I have tried the following portlets bridge without any
changes
portlet-bridge-api-2.0.0-alpha.jar
portlet-bridge-impl-2.0.0-alpha.jar
and
portletbridge-api-2.0.0.CR1.jar
portletbridge-impl-2.0.0.CR1.jar
I hope someone will tell me the class where I can find the error so that I
can debug the source file and identify the real cause(s) of the problem.
Thanks again.
David Sean Taylor-3 wrote:
>
> On Thu, Mar 25, 2010 at 4:45 PM, Tender Slim <xs...@gmx.com> wrote:
>>
>> Does anyone know which class is generating the following message: “The
>> requested resource (/container) is not available”? I want to find the
>> source
>> of the damned problem.
>>
> I think it means your portlet application failed to start. Could be
> caused by any number of reasons
> Check the tomcat and jetspeed logs for exceptions, stack traces
> Also, please verify the web.xml in your *deployed* web application has
> an entry like (but not exactly):
>
> <servlet>
> <description>MVC Servlet for Jetspeed Portlet
> Applications</description>
> <display-name>Jetspeed Container</display-name>
> <servlet-name>JetspeedContainer</servlet-name>
> <servlet-class>
>
> org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class>
> <init-param>
> <param-name>contextName</param-name>
> <param-value>j2-admin</param-value>
> </init-param>
> <load-on-startup>100</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>JetspeedContainer</servlet-name>
> <url-pattern>/container/*</url-pattern>
> </servlet-mapping>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/The-requested-resource-%28-container%29-is-not-available-tp28036609p28042719.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: The requested resource (/container) is not available
Posted by David Sean Taylor <d....@onehippo.com>.
On Thu, Mar 25, 2010 at 4:45 PM, Tender Slim <xs...@gmx.com> wrote:
>
> Does anyone know which class is generating the following message: “The
> requested resource (/container) is not available”? I want to find the source
> of the damned problem.
>
I think it means your portlet application failed to start. Could be
caused by any number of reasons
Check the tomcat and jetspeed logs for exceptions, stack traces
Also, please verify the web.xml in your *deployed* web application has
an entry like (but not exactly):
<servlet>
<description>MVC Servlet for Jetspeed Portlet Applications</description>
<display-name>Jetspeed Container</display-name>
<servlet-name>JetspeedContainer</servlet-name>
<servlet-class>
org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class>
<init-param>
<param-name>contextName</param-name>
<param-value>j2-admin</param-value>
</init-param>
<load-on-startup>100</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>JetspeedContainer</servlet-name>
<url-pattern>/container/*</url-pattern>
</servlet-mapping>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org