Bug #3399
cn.reserveIdentifier occasionally timing out in DEV and STAGE
Status:
Closed
Priority:
Normal
Assignee:
Ben Leinfelder
Category:
Environment.Development
Target version:
Start date:
2012-11-14
Due date:
2013-01-05
% Done:
100%
Milestone:
CCI-1.1
Product Version:
*
Story Points:
Sprint:
Description
while testing d1_client_r, I'm using reserveIdentifier prior to creating an object, but sometimes it is timing out (after 30 sec) Other times it is very fast. Need to check if it is a round-robin issue (sending traffic to a machine that's down) or a system resource issue on a particular machine or every machine.
History
#1 Updated by Rob Nahf over 11 years ago
- Due date changed from 2012-11-14 to 2013-01-05
- Target version changed from Sprint-2012.44-Block.6.2 to Sprint-2012.50-Block.6.4
#2 Updated by Rob Nahf over 11 years ago
- Subject changed from cn.reserveIdentifier occasionally timing out in dev to cn.reserveIdentifier occasionally timing out in DEV and STAGE
#3 Updated by Rob Nahf over 11 years ago
- Assignee changed from Rob Nahf to Chris Jones
- Milestone changed from None to CCI-1.1
#4 Updated by Chris Jones over 11 years ago
- Assignee changed from Chris Jones to Ben Leinfelder
Assigning to Ben, since he's most familiar with the Identifier service.
#5 Updated by Ben Leinfelder over 11 years ago
Is the client connection to the service where the timeout is happening or is it the service trying to communicate with LDAP that times out?
#6 Updated by Ben Leinfelder over 11 years ago
- Status changed from New to Closed
I ended up having to restart tomcat to get this error to go away. I imagine something happened with the LDAP connection, but not sure why it showed as a timeout. All three cn-dev servers have been "fixed"
