|
Home > Archive > WebSphere Portal Server > May 2005 > WPS long login time
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WPS long login time
|
|
| Fredrik Andersson 2005-05-16, 2:57 am |
| Hi,
I am experiencing problem with login for WPS 5.0 connected to an LDAP
server.
The first time I login, it takes several seconds. If I immediately logout
from the portal
and log right back in it goes fast, so it seems like it during relogin uses
cached values.
I also have a problem when a user has been inactive for a while. The first
request after
inactivity takes longer time to execute than normal. After the first
request, the behavior
is normal. This problem does not seem to occur during times when the load on
the system
is low.
Has anyone had similar problems and found a solution for them?
Does anyone have any good general optimization settings for LDAP connection,
e.g.
time for cache to live, size of cache.
Regards,
Fredrik Andersson
| |
| Tony Cooke 2005-05-17, 8:48 pm |
| Hi Fredrik.
The support site has the download to fix this. (I gather you have also run
the JSPBatchCompiler script?)
http://www-306.ibm.com/software/gen...xpress/support/
Here are the fix packs you'll need to download (the first is required before
the second gets installed). Also there is a fixpack update installer that is
required.
Hope this helps.
All the best,
Tony
PQ99439
WebSphere Portal is missing the shell scripts to read the APAR install
history. Also the wps<timestamp>.log does not list the installed APARs.
PQ97613
After a portal restart, portal access control response time is higher
than it needs to be. Typically the first login request takes pretty long.
After that portal access control performs fast.
This APAR introduces a new service that pre-initializes the caches
used by portal access control during portal start. This improves portal
response times after a server restart.
Following steps are required to activate the WarmUp service:
1. Add the following line AT THE END of the file
<Portal>/shared/app/config/services.properties:
com.ibm.wps.ac.impl.AccessControlWarmUpService =
com.ibm.wps.ac.impl.AccessControlWarmUpServiceImpl
2. Restart the portal server.
The WarmUp service can be configured via the file
<Portal>/shared/app/config/services/AccessControlWarmUpService.properties
To enable the WarmUp service, set "enabled=true" in
AccessControlWarmUpService.properties.
"Fredrik Andersson" <noone@noone.com> wrote in message
news:d69has$2tn8$1@news.boulder.ibm.com...
> Hi,
>
> I am experiencing problem with login for WPS 5.0 connected to an LDAP
> server.
> The first time I login, it takes several seconds. If I immediately logout
> from the portal
> and log right back in it goes fast, so it seems like it during relogin
uses
> cached values.
>
> I also have a problem when a user has been inactive for a while. The first
> request after
> inactivity takes longer time to execute than normal. After the first
> request, the behavior
> is normal. This problem does not seem to occur during times when the load
on
> the system
> is low.
>
> Has anyone had similar problems and found a solution for them?
>
> Does anyone have any good general optimization settings for LDAP
connection,
> e.g.
> time for cache to live, size of cache.
>
> Regards,
>
> Fredrik Andersson
>
>
| |
| Fredrik Andersson 2005-05-18, 2:52 am |
| Hi,
thanks for the response, however it is not exactly the problem I am
experiencing.
I will try to clarify a bit. My problem is not that the very first login
after restart
takes too long time and then it is okay for everyone else. The problem is
that if a
user that hasn't logged in for some time (where time seems to be just 10-15
minutes),
it takes too long time. If the user logs out and logs right back in it, the
second login
goes fast. If the user logs out waits for about 10-15 minutes, the login
takes long time
again.
Therefore the question is if there is some caching performed when accessing
LDAP
and if this cache in that case can be tuned in some way (like expanding size
and extending
its time to keep objects).
Regards,
Fredrik
"Tony Cooke" <TCooke@elders.com.au> wrote in message
news:d6e226$2o1c$1@news.boulder.ibm.com...
> Hi Fredrik.
>
> The support site has the download to fix this. (I gather you have also run
> the JSPBatchCompiler script?)
> http://www-306.ibm.com/software/gen...xpress/support/
>
> Here are the fix packs you'll need to download (the first is required
before
> the second gets installed). Also there is a fixpack update installer that
is
> required.
>
> Hope this helps.
>
> All the best,
> Tony
>
> PQ99439
> WebSphere Portal is missing the shell scripts to read the APAR
install
> history. Also the wps<timestamp>.log does not list the installed APARs.
>
> PQ97613
> After a portal restart, portal access control response time is higher
> than it needs to be. Typically the first login request takes pretty long.
> After that portal access control performs fast.
>
>
>
> This APAR introduces a new service that pre-initializes the caches
> used by portal access control during portal start. This improves portal
> response times after a server restart.
>
>
>
> Following steps are required to activate the WarmUp service:
>
> 1. Add the following line AT THE END of the file
> <Portal>/shared/app/config/services.properties:
>
>
>
> com.ibm.wps.ac.impl.AccessControlWarmUpService =
> com.ibm.wps.ac.impl.AccessControlWarmUpServiceImpl
>
> 2. Restart the portal server.
>
>
>
> The WarmUp service can be configured via the file
>
>
> <Portal>/shared/app/config/services/AccessControlWarmUpService.properties
>
>
>
> To enable the WarmUp service, set "enabled=true" in
> AccessControlWarmUpService.properties.
>
>
>
>
> "Fredrik Andersson" <noone@noone.com> wrote in message
> news:d69has$2tn8$1@news.boulder.ibm.com...
logout[vbcol=seagreen]
> uses
first[vbcol=seagreen]
load[vbcol=seagreen]
> on
> connection,
>
>
| |
| UBUSSMAN@de.ibm.com 2005-05-18, 6:05 pm |
| Hello Fredrik,
do you have any strong indication that this is related to LDAP connection
?
Can you be more specific on the numbers of pages/documents in portal and
on the numbers of users ?
What kind of DB setup do you use ? What DB ? Is it installed on a
differen system ?
When you say "Under Load" - What is CPU usage - at limits, or still far
below ?
The 5.0 performance tuning guide gives very good hints on improve
performance.
http://www-1.ibm.com/support/docvie...g27004492&aid=1
From what you say you may want to try to increase the pac cache lifetime.
This is described in the peformance tuning guide at the end of the
document.
What fixpack level do you have ?
If you are not yet at 5023 then please install PQ99236.
That improves Login performance in either case.
Regards
Udo
|
|
|
|
|