com.sas.svcs.search.index.SearchIndexFeedScheduler - Execution of index feeding (for notified types

[afa1]

Keep seeing ton of these in our SASSearchService.log

2024-11-04 15:50:36,862 [pool-7-thread-1] ERROR [26e1feee-9abc-11ef-a0ea-005056818e72] com.sas.svcs.search.index.SearchIndexFeedScheduler - Execution of index feeding (for notified types only) scheduled task failed abruptly
java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 500 for URL: http://slsasw02.aintern.se:7981/SASLogon/proxy?pgt=PGT-3-IWiefVK33qCbjm7DIE-qqY25jfFwy9ZvzWoWAIFMfeI...
at org.jasig.cas.client.util.CommonUtils.getResponseFromServer(CommonUtils.java:467) ~[cas-client-core.jar:3.6.2]
at org.jasig.cas.client.proxy.Cas20ProxyRetriever.getProxyTicketIdFor(Cas20ProxyRetriever.java:87) ~[cas-client-core.jar:3.6.2]
at org.jasig.cas.client.authentication.AttributePrincipalImpl.getProxyTicketFor(AttributePrincipalImpl.java:107) ~[cas-client-core.jar:3.6.2]
at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getSecurityContextWithAuthManager(LazySpringSecurityContext.java:157) ~[sas.svcs.security.helper.jar:904800.0.0.20221221190000_v940m8]
at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getSecurityContext(LazySpringSecurityContext.java:236) ~[sas.svcs.security.helper.jar:904800.0.0.20221221190000_v940m8]
at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getAuthentication(LazySpringSecurityContext.java:247) ~[sas.svcs.security.helper.jar:904800.0.0.20221221190000_v940m8]
at com.sas.svcs.search.index.SearchIndexFeederScheduledTask.runFeederForNotifiedTypes(SearchIndexFeederScheduledTask.java:56) ~[sas.searchsas.jar:105000.0.0.20221019190000_d4srchr9]
at com.sas.svcs.search.index.SearchIndexFeedScheduler$3.run(SearchIndexFeedScheduler.java:120) ~[sas.searchsas.jar:105000.0.0.20221019190000_d4srchr9]
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context.jar:5.3.21]
at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:95) ~[spring-context.jar:5.3.21]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: http://slsasw02.aintern.se:7981/SASLogon/proxy?pgt=PGT-3-IWiefVK33qCbjm7DIE-qqY25jfFwy9ZvzWoWAIFMfeI...
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1939) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1525) ~[?:?]
at org.jasig.cas.client.util.CommonUtils.getResponseFromServer(CommonUtils.java:447) ~[cas-client-core.jar:3.6.2]
... 15 more

I have checked that SASInformationRetrievalStudioforSAS is running according to SAS Support - A "Search Interface to SAS Content encountered error while feeding the content to the ....

I can also see following in SASLogon9.4.log

2024-11-04 15:50:36,851 [tomcat-http--39] ERROR org.springframework.boot.web.servlet.support.ErrorPageFilter - Forwarding to error page from request [/proxy] due to exception [null]
java.lang.StackOverflowError: null
at com.sas.svcs.security.authentication.ticket.registry.ProxyGrantingTicket.grantProxyTicket(ProxyGrantingTicket.java:76) ~[sas.svcs.security.authentication.server.jar:904801.5.0.20240304104949_v940m8f]

Has anyone encountered this issue? 

I'm new at my job and this was setup by a predecessor so not sure it has been looked at.

Has anyone encountered this issue?

[gwootton · Accepted solution]

Looks like search is getting an HTTP 500 when it tries to call SASLogon, and SASLogon is returning the 500 because of a Stack Overflow.
You could try increasing the stack size (-Xss option) from 256k to say 512k in <SASConfig>/Levn/Web/WebAppServer/SASServer1_1/bin/setenv.sh and restarting SASServer1_1.

[afa1]

Increasinging stack size -Xss to 512K solved the issue.

Thanks!

Just out of curiosity why did the stack size have an impact on our environment? Was it set low or is it depended on how our envrionment is setup?

[gwootton]

256k is the default, so this is likely specific to your configuration. You'd probably need some trace level logging to really get at the root cause of why the default was insufficient in your case. You can open a case with SAS Technical Support if you want to dig into it.

[afa1]

Alright. Thanks for the response!