Hi again,
I am adding our LDAP configuration template.
Thanks a lot
Axel
This is a discussion on Problems accessing Domino LDAP - Websphere ; Hi, we have configured Domino LDAP for our WAS Portal 6.1. The wpsbind and wpsadmin have been added to the Domino NAB. They can login into the portal without any problem. Unfortunatedly all other users can not login. I haven't ...
Hi,
we have configured Domino LDAP for our WAS Portal 6.1. The wpsbind and wpsadmin have been added to the Domino NAB. They can login into the portal without any problem. Unfortunatedly all other users can not login.
I haven't experienced this problem in another environment.
Has anybody else have come across a similar problem?
Thanks a lot
Axel
Hi again,
I am adding our LDAP configuration template.
Thanks a lot
Axel
A last one,
the Domino server used is Domino 8.5.
When a Domino user tries to access portal, the following messages are written to the SystemOut.log of Was Portal
00026d TimeoutManage I WTRN0006W: Transaction 000001223BDB953E000000060000011CDB09CC2A61E721D4C4 1C59A14CF075F5B0270B6B000001223BDB953E000000060000 011CDB09CC2A61E721D4C41C59A14CF075F5B0270B6B000000 01 has timed out after 120 seconds.
[7/2/09 14:29:09:521 GMT] 00000242 TimeoutManage I WTRN0006W: Transaction 000001223BDC9C4F000000060000012BDB09CC2A61E721D4C4 1C59A14CF075F5B0270B6B000001223BDC9C4F000000060000 012BDB09CC2A61E721D4C41C59A14CF075F5B0270B6B000000 01 has timed out after 120 seconds.
Here are further log messages that may be related:
[7/2/09 14:38:57:200 GMT] 00000052 ThreadMonitor W WSVR0605W: Thread "WebContainer : 1" (00000265) has been active for 775322 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
[7/2/09 14:38:57:216 GMT] 00000052 ThreadMonitor W WSVR0605W: Thread "WebContainer : 6" (0000028a) has been active for 707884 milliseconds and may be hung. There is/are 2 thread(s) in total in the server that may be hung.
[7/2/09 14:38:57:247 GMT] 00000052 ThreadMonitor W WSVR0605W: Thread "WebContainer : 8" (00000292) has been active for 604914 milliseconds and may be hung. There is/are 3 thread(s) in total in the server that may be hung.
As allways, thanks a lot
Axel
testserver.org is not considered as valid hostname by many. You should have a machine name, and a domain name with at least one embedded dot ".". So "org" itself is not a valid domain.
-FF
The postings on this site are my own and do not necessarily represent the positions, strategies or opinions of IBM.
configwizard.bat -W setLdapPropertie
s.propertiesFile=D:\IBM\WebSphere\wp_profile\Confi gEngine\config\helpers\wp_secu
rity_domino.properties
I receive the following message on the console: Could not find bean setLdapProperties
any help welcome
Axel
See if clearing the tranlog helps (this was written for 6.0 but I think the same should apply to 6.1):
http://www.ibm.com/support/docview.w...id=swg21293390
Hi,
thanks for the reply.
We switched to another Domino NAB (test domain) as LDAP. The error does not happen with this new LDAP. Don't know why it happened integrating the production NAB.
thx