Skip to Content.
Sympa Menu

grouper-users - [grouper-users] Re: Grouper WS Error

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] Re: Grouper WS Error


Chronological Thread 
  • From: Akki Kumar <>
  • To: "Hyzer, Chris" <>
  • Cc: "" <>, Stephen A Sazama <>
  • Subject: [grouper-users] Re: Grouper WS Error
  • Date: Mon, 25 Sep 2017 10:52:28 -0400
  • Ironport-phdr: 9a23:Q+p/1Re5/y2RnsuPjI/rdMZklGMj4u6mDksu8pMizoh2WeGdxc26Zx2N2/xhgRfzUJnB7Loc0qyN4vCmATRIyK3CmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+KPjrFY7OlcS30P2594HObwlSijewZbB/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbDVwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4rx1QxH0ligIKz858HnWisNuiqJbvAmhrAF7z4LNfY2ZKOZycqbbcNwUX2pBWttaWTJHDI2ycoADC/cNMfpdo4T7ulAArwaxBRO0CeztxD9GhnH4064n3eo/DQ7LxxYvE84UvXnOsNn5KKUfXOaox6fI1zXDaPZW1C/h5YjLcRAhoOyHU7dtccrU00YvDR7Og1KKpozgJTyU1+UNs26U7+p5SOKglXUnqx1wojiowMcskZXFip4Xx13f+iV5xZw6Jdy8SEJhfdGkF55QujicOoBrTM0iRGRotzw7yr0AoZO7cy8KyJMoxx7bdfOLaZSH4hXmVOqJLjd4hW5leLKihxmp60Sv1ur8Vsys3FZFtCpFlcTMtmgT2BzJ8MSGROB98l+l2TaI2ADT5f9LLl0umaraLZ4t2rwwmYANsUvZBCP2nlv5jLOOeko+++io7/7rbanhpp+ZL4N0jgb+MqshmsOhG+Q0KBYBUHWG+em6ybbt/lX5Ta1UgvA3jqXUspXXJcoYq6GiHwNY14ku5wqjAzi71dkXgWULI09AdR+CkYTlJVXDLfblBvmlmVusii1kx/XeM73hHJrNKn/Dna/kfbln6k5czBM/zclD555IE70AL+z/VlH1udDCAR85NAu0w+njCNpjzI8RRWWPAqqBPKPTt1+H+P4vLvGSaIIUpDrwKf0o5/DtgHAihVMQeKak0YcLZH+lG/lpP1mVbmfpj9oED2sGoA4zQPTviFKYUD5TY3iyX7g75jE+EI+pF4LDSZqsgbyA2ie7EYRWZn1YBVCXDXfodoKEW/EXaC6OPsNskCcJVbekS4A71BGusBX2xKZgLurR4iEYr47s1MBp5+3PkhE/7TN0D96a02GQV2F7gHkISyYr3KBkv0N90EyD3LN8g/xZDtxT++hJXhkgOZ7dyex6F879WhjHftiXVFaqXM+qDi8sQdIskJcyZBM3O8SwgwqHlwGqGb4O3fTfAZc047DRxVDwPM071m7L0q9nglU7FJhhL2qj04d89AmbJJPMml/Rw6+vfLYd2iHU6WqY0WuJuloACFFYXqDMXHRZbUzT+4eqrnjeRqOjXOx0ejBKztSPf+4bMtA=

Hi Chris,

I'm finally able to get the stack trace from the Grouper WS. Even though below properties is set in the in the grouper-ws.properties file, the Grouper WS still makes a call to LDAP.  Looks like WS makes a call in the retrieveSubjectLoggedIn() line 263. Any suggestions as to why is it making a call to the LDAP even though I set properties in the  grouper-ws.properties file. Is this a bug in the source code?

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




Thank you,
Akki

On Fri, Sep 8, 2017 at 1:31 PM, Akki Kumar <> wrote:
Hi Chris,

I'm using GcHasMember() and GcGetMembers() to get users from the group. In the grouper-ws.properties, I am only using ws.security.prependToUserIdForSubjectLookup = etc:servicePrincipals: 

I am setting up the environment to debug further, couple more questions:
  • Any idea if GcHasMember() and GcGetMembers() some how calling actAs method? or Is there work around?

Thank you,
Akki

On Wed, Sep 6, 2017 at 8:51 PM, Hyzer, Chris <> wrote:

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:

 

 

 

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?

 

 

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

 

Any guidance is truly appreciated.

 

Thank you,

Akki

 






Archive powered by MHonArc 2.6.19.

Top of Page