Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

Might be searching your sources for the logged in subject.  Still a little concerning if a subject lookup takes that long.

 

Can you try setting this in grouper-ws.properties?

 

# if you have subject namespace overlap (or not), set the default subject

# sources (comma-separated) to lookup the user if none specified in user name

ws.logged.in.subject.default.source =

 

Put the source id of the source that the logged in subject should be in.  If it is LDAP then this wont help…

 

When you do a search in GSH for the logged in subject does it take a while?  Maybe tune your subject source?

 

Just curious is your web service request using an actAs?

 

Thanks

Chris

 

From: Akki Kumar [mailto:]
Sent: Wednesday, September 06, 2017 5:19 PM
To: Hyzer, Chris <>
Cc:
Subject: Re: Grouper WS Error

 

Hi Chris,

 

I troubleshoot the timeout error and pinpoint to the Class LdapClient.java ==>  getSearchReply(LdapRequest, int, LdapResult, Hashtable) method. The part that I'm not sure is why does Grouper WS searching LDAP, any idea?

 

I added a screenshot below that pinpoint error method:

 

Screenshot Link: https://drive.google.com/open?id=1BmcSS-FNqUDVbYCcZgCzLN1yiNQ-hN4f0Rw7elk6rg4

 

 

Any guidance to fixed the timeout issue is truly appreciated. 

 

Thank you,

Akki

 

 

 

On Wed, Sep 6, 2017 at 11:00 AM, Hyzer, Chris <> wrote:

do you see a timeout setting in the client you can increase?  

can you analyze tables in the grouper database to make calls quicker?  maybe bounce the WS?  rebuild indexes?

---

From: Akki Kumar <>
Sent: Wednesday, August 30, 2017 4:25 PM
To: Hyzer, Chris
Cc:
Subject: Grouper WS Error

 

Hi Chris,

 

Currently, I am working on integrating the application with the Grouper WS. When I run the application, it takes around 20-30 seconds (a little longer) to get a response from the WS and after some times, it throws an error (Caused by: java.net.SocketTimeoutException: Read timed out - in the link below). After troubleshooting, the root cause is Grouper WS is not very responsive or having a stale connection. Is there a way to fix below issue?

 

Error Link: https://drive.google.com/open?id=1BmcSS-FNqUDVbYCcZgCzLN1yiNQ-hN4f0Rw7elk6rg4

 

Note: There are no errors in the grouper_error.log file.   

 

Any guidance is truly appreciated.

 

Thank you,

Akki