<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: com.sas.svcs.search.index.SearchIndexFeedScheduler - Execution of index feeding (for notified ty in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/950014#M29234</link>
    <description>&lt;P&gt;Increasinging stack size&amp;nbsp;-Xss to 512K solved the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;</description>
    <pubDate>Wed, 06 Nov 2024 11:50:28 GMT</pubDate>
    <dc:creator>afa1</dc:creator>
    <dc:date>2024-11-06T11:50:28Z</dc:date>
    <item>
      <title>com.sas.svcs.search.index.SearchIndexFeedScheduler - Execution of index feeding (for notified types</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/949845#M29219</link>
      <description>&lt;P&gt;Keep seeing ton of these in our&amp;nbsp;SASSearchService.log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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&lt;BR /&gt;java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 500 for URL: &lt;A href="http://slsasw02.aintern.se:7981/SASLogon/proxy?pgt=PGT-3-IWiefVK33qCbjm7DIE-qqY25jfFwy9ZvzWoWAIFMfeIeMsUKysxb7WlZFaH3g1HviiY-slsasw02&amp;amp;targetService=http%3A%2F%2FLazySecurityContext" target="_blank"&gt;http://slsasw02.aintern.se:7981/SASLogon/proxy?pgt=PGT-3-IWiefVK33qCbjm7DIE-qqY25jfFwy9ZvzWoWAIFMfeIeMsUKysxb7WlZFaH3g1HviiY-slsasw02&amp;amp;targetService=http%3A%2F%2FLazySecurityContext&lt;/A&gt;&lt;BR /&gt;at org.jasig.cas.client.util.CommonUtils.getResponseFromServer(CommonUtils.java:467) ~[cas-client-core.jar:3.6.2]&lt;BR /&gt;at org.jasig.cas.client.proxy.Cas20ProxyRetriever.getProxyTicketIdFor(Cas20ProxyRetriever.java:87) ~[cas-client-core.jar:3.6.2]&lt;BR /&gt;at org.jasig.cas.client.authentication.AttributePrincipalImpl.getProxyTicketFor(AttributePrincipalImpl.java:107) ~[cas-client-core.jar:3.6.2]&lt;BR /&gt;at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getSecurityContextWithAuthManager(LazySpringSecurityContext.java:157) ~[sas.svcs.security.helper.jar:904800.0.0.20221221190000_v940m8]&lt;BR /&gt;at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getSecurityContext(LazySpringSecurityContext.java:236) ~[sas.svcs.security.helper.jar:904800.0.0.20221221190000_v940m8]&lt;BR /&gt;at com.sas.svcs.authentication.helper.LazySpringSecurityContext.getAuthentication(LazySpringSecurityContext.java:247) ~[sas.svcs.security.helper.jar:904800.0.0.20221221190000_v940m8]&lt;BR /&gt;at com.sas.svcs.search.index.SearchIndexFeederScheduledTask.runFeederForNotifiedTypes(SearchIndexFeederScheduledTask.java:56) ~[sas.searchsas.jar:105000.0.0.20221019190000_d4srchr9]&lt;BR /&gt;at com.sas.svcs.search.index.SearchIndexFeedScheduler$3.run(SearchIndexFeedScheduler.java:120) ~[sas.searchsas.jar:105000.0.0.20221019190000_d4srchr9]&lt;BR /&gt;at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context.jar:5.3.21]&lt;BR /&gt;at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:95) ~[spring-context.jar:5.3.21]&lt;BR /&gt;at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]&lt;BR /&gt;at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]&lt;BR /&gt;at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]&lt;BR /&gt;at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]&lt;BR /&gt;at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]&lt;BR /&gt;at java.lang.Thread.run(Thread.java:829) ~[?:?]&lt;BR /&gt;Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: &lt;A href="http://slsasw02.aintern.se:7981/SASLogon/proxy?pgt=PGT-3-IWiefVK33qCbjm7DIE-qqY25jfFwy9ZvzWoWAIFMfeIeMsUKysxb7WlZFaH3g1HviiY-slsasw02&amp;amp;targetService=http%3A%2F%2FLazySecurityContext" target="_blank"&gt;http://slsasw02.aintern.se:7981/SASLogon/proxy?pgt=PGT-3-IWiefVK33qCbjm7DIE-qqY25jfFwy9ZvzWoWAIFMfeIeMsUKysxb7WlZFaH3g1HviiY-slsasw02&amp;amp;targetService=http%3A%2F%2FLazySecurityContext&lt;/A&gt;&lt;BR /&gt;at sun.net.&lt;A href="http://www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1939" target="_blank"&gt;www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1939&lt;/A&gt;) ~[?:?]&lt;BR /&gt;at sun.net.&lt;A href="http://www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1525" target="_blank"&gt;www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1525&lt;/A&gt;) ~[?:?]&lt;BR /&gt;at org.jasig.cas.client.util.CommonUtils.getResponseFromServer(CommonUtils.java:447) ~[cas-client-core.jar:3.6.2]&lt;BR /&gt;... 15 more&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have checked that&amp;nbsp;SASInformationRetrievalStudioforSAS is running according to&amp;nbsp;&lt;A href="https://sas.service-now.com/csm?id=kb_article_view&amp;amp;sysparm_article=KB0036467" target="_blank"&gt;SAS Support - A "Search Interface to SAS Content encountered error while feeding the content to the Indexing Server ..." email is generated&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can also see following in&amp;nbsp;SASLogon9.4.log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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]&lt;BR /&gt;java.lang.StackOverflowError: null&lt;BR /&gt;at com.sas.svcs.security.authentication.ticket.registry.ProxyGrantingTicket.grantProxyTicket(ProxyGrantingTicket.java:76) ~[sas.svcs.security.authentication.server.jar:904801.5.0.20240304104949_v940m8f]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone encountered this issue?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm new at my job and this was setup by a predecessor so not sure it has been looked at.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone encountered this issue?&lt;/P&gt;</description>
      <pubDate>Mon, 04 Nov 2024 14:57:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/949845#M29219</guid>
      <dc:creator>afa1</dc:creator>
      <dc:date>2024-11-04T14:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: com.sas.svcs.search.index.SearchIndexFeedScheduler - Execution of index feeding (for notified ty</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/949867#M29222</link>
      <description>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.&lt;BR /&gt;You could try increasing the stack size  (-Xss option) from 256k to say 512k in &amp;lt;SASConfig&amp;gt;/Levn/Web/WebAppServer/SASServer1_1/bin/setenv.sh and restarting SASServer1_1.</description>
      <pubDate>Mon, 04 Nov 2024 18:57:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/949867#M29222</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2024-11-04T18:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: com.sas.svcs.search.index.SearchIndexFeedScheduler - Execution of index feeding (for notified ty</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/950014#M29234</link>
      <description>&lt;P&gt;Increasinging stack size&amp;nbsp;-Xss to 512K solved the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2024 11:50:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/950014#M29234</guid>
      <dc:creator>afa1</dc:creator>
      <dc:date>2024-11-06T11:50:28Z</dc:date>
    </item>
    <item>
      <title>Re: com.sas.svcs.search.index.SearchIndexFeedScheduler - Execution of index feeding (for notified ty</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/950026#M29235</link>
      <description>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.</description>
      <pubDate>Wed, 06 Nov 2024 13:51:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/950026#M29235</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2024-11-06T13:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: com.sas.svcs.search.index.SearchIndexFeedScheduler - Execution of index feeding (for notified ty</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/950027#M29236</link>
      <description>&lt;P&gt;Alright. Thanks for the response!&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2024 13:53:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/com-sas-svcs-search-index-SearchIndexFeedScheduler-Execution-of/m-p/950027#M29236</guid>
      <dc:creator>afa1</dc:creator>
      <dc:date>2024-11-06T13:53:07Z</dc:date>
    </item>
  </channel>
</rss>

