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 David Dyer <dd...@artifact-software.com> on 2010/03/16 15:09:30 UTC
Jetspeed 2.1.3 and tomcat 6 versions
More of a heads up than a question here.
We've been moving our Jetspeed portal from tomcat 5 (5.5.27
specifically) to Tomcat 6.
One thing we've come across is that under the latest 2 versions (6.0.24
and 6.0.26) is that the login procedure via the j2-admin login portlet
and the login servlets fails when the session gets invalidated somewhere
in the process.
It works ok under Tomcat 6.0.20, however. The difference appears to lie
somewhere in the catalina.jar , it may be a configuration issue that I'm
unaware of.
Has anyone else come across this?
David Dyer
Artifact Software inc.
ddyer@artifact-software.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Jetspeed 2.1.3 , Tomcat 6, no container service warning
Posted by David Dyer <dd...@artifact-software.com>.
Anything in the configuration I can do to avoid the warnings? Other than
using log levels?
David Sean Taylor wrote:
> On Mon, Mar 22, 2010 at 5:18 AM, David Dyer <dd...@artifact-software.com> wrote:
>
>> Since we've begun our upgrade of the tomcat container we're running Jetspeed
>> under I've been seeing the following WARN message in the console:
>>
>> WARN org.apache.jetspeed.engine.JetspeedEngine - No ContainerService
>> defined for org.apache.pluto.services.property.PropertyManagerService
>>
>> It appears to be non fatal and does nothing but clutter the logs.
>>
>> A google search brought up this thread from 2008:
>>
>> http://mail-archives.apache.org/mod_mbox/portals-jetspeed-user/200811.mbox/%3C7058448BC5B00647B05E15538AE8BD5801441B35@MSGMMKCLE2WIN.DMN1.FMR.COM%3E
>>
>> but it doesn't seem to provide any answers.
>>
>> Any ideas what's causing the warning?
>>
>>
> Its an optional service from Pluto 1.0.1 that we don't use in Jetspeed
> 2.1.x. So it goes to retrieve it, returns null, and its logged as a
> warning that the service doesn't exist. The property manager service
> is used in Pluto, but its always protected with checks like:
>
> public static Map getRequestProperties(PortletWindow window,
> HttpServletRequest request)
> {
> if (getService() == null)
> {
> return null;
> }
>
> return getService().getRequestProperties( window, request);
> }
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.437 / Virus Database: 271.1.1/2763 - Release Date: 03/22/10 07:33:00
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Jetspeed 2.1.3 , Tomcat 6, no container service warning
Posted by David Sean Taylor <d....@onehippo.com>.
On Mon, Mar 22, 2010 at 5:18 AM, David Dyer <dd...@artifact-software.com> wrote:
> Since we've begun our upgrade of the tomcat container we're running Jetspeed
> under I've been seeing the following WARN message in the console:
>
> WARN org.apache.jetspeed.engine.JetspeedEngine - No ContainerService
> defined for org.apache.pluto.services.property.PropertyManagerService
>
> It appears to be non fatal and does nothing but clutter the logs.
>
> A google search brought up this thread from 2008:
>
> http://mail-archives.apache.org/mod_mbox/portals-jetspeed-user/200811.mbox/%3C7058448BC5B00647B05E15538AE8BD5801441B35@MSGMMKCLE2WIN.DMN1.FMR.COM%3E
>
> but it doesn't seem to provide any answers.
>
> Any ideas what's causing the warning?
>
Its an optional service from Pluto 1.0.1 that we don't use in Jetspeed
2.1.x. So it goes to retrieve it, returns null, and its logged as a
warning that the service doesn't exist. The property manager service
is used in Pluto, but its always protected with checks like:
public static Map getRequestProperties(PortletWindow window,
HttpServletRequest request)
{
if (getService() == null)
{
return null;
}
return getService().getRequestProperties( window, request);
}
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Jetspeed 2.1.3 , Tomcat 6, no container service warning
Posted by David Dyer <dd...@artifact-software.com>.
Since we've begun our upgrade of the tomcat container we're running
Jetspeed under I've been seeing the following WARN message in the console:
WARN org.apache.jetspeed.engine.JetspeedEngine - No ContainerService
defined for org.apache.pluto.services.property.PropertyManagerService
It appears to be non fatal and does nothing but clutter the logs.
A google search brought up this thread from 2008:
http://mail-archives.apache.org/mod_mbox/portals-jetspeed-user/200811.mbox/%3C7058448BC5B00647B05E15538AE8BD5801441B35@MSGMMKCLE2WIN.DMN1.FMR.COM%3E
but it doesn't seem to provide any answers.
Any ideas what's causing the warning?
David Dyer
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Jetspeed 2.1.3 and tomcat 6 versions
Posted by David Dyer <dd...@artifact-software.com>.
I fail at google.
Ate Douma wrote:
> On 03/16/2010 03:09 PM, David Dyer wrote:
>> More of a heads up than a question here.
>>
>> We've been moving our Jetspeed portal from tomcat 5 (5.5.27
>> specifically) to Tomcat 6.
>>
>> One thing we've come across is that under the latest 2 versions (6.0.24
>> and 6.0.26) is that the login procedure via the j2-admin login portlet
>> and the login servlets fails when the session gets invalidated somewhere
>> in the process.
>>
>> It works ok under Tomcat 6.0.20, however. The difference appears to lie
>> somewhere in the catalina.jar , it may be a configuration issue that I'm
>> unaware of.
>>
>> Has anyone else come across this?
> Yes and fixed it too, see: https://issues.apache.org/jira/browse/JS2-1119
>
> Ate
>
>>
>> David Dyer
>> Artifact Software inc.
>> ddyer@artifact-software.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: 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
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.436 / Virus Database: 271.1.1/2750 - Release Date: 03/16/10 07:33:00
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Jetspeed 2.1.3 and tomcat 6 versions
Posted by Ate Douma <at...@douma.nu>.
On 03/16/2010 03:09 PM, David Dyer wrote:
> More of a heads up than a question here.
>
> We've been moving our Jetspeed portal from tomcat 5 (5.5.27
> specifically) to Tomcat 6.
>
> One thing we've come across is that under the latest 2 versions (6.0.24
> and 6.0.26) is that the login procedure via the j2-admin login portlet
> and the login servlets fails when the session gets invalidated somewhere
> in the process.
>
> It works ok under Tomcat 6.0.20, however. The difference appears to lie
> somewhere in the catalina.jar , it may be a configuration issue that I'm
> unaware of.
>
> Has anyone else come across this?
Yes and fixed it too, see: https://issues.apache.org/jira/browse/JS2-1119
Ate
>
> David Dyer
> Artifact Software inc.
> ddyer@artifact-software.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: 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