1

Recently, I am facing some issues with the Endeca DefaultFileStoreFactory component. Site is not coming up and when checked for this component, the initialized property is becoming false automatically. We are giving a temporary solution to bring up the site. Could you please assist why this behavior is happening.

Below are the logs seen at the time of server start up.

**** Error      Tue Jan 02 15:22:34 -03:00 2018 1514917354914   /       Unable to resolve component /atg/endeca/assembler/cartridge/manager/DefaultFileStoreFactory     java.lang.StackOverflowError
**** Error      Tue Jan 02 15:22:34 -03:00 2018 1514917354914   /               at java.util.TreeMap$NavigableSubMap$SubMapIterator.nextEntry(TreeMap.java:1700)
**** Error      Tue Jan 02 15:22:34 -03:00 2018 1514917354914   /               at java.util.TreeMap$NavigableSubMap$SubMapEntryIterator.next(TreeMap.java:1747)
**** Error      Tue Jan 02 15:22:34 -03:00 2018 1514917354914   /               at java.util.TreeMap$NavigableSubMap$SubMapEntryIterator.next(TreeMap.java:1741)
radimpe
  • 3,197
  • 2
  • 27
  • 46
Newbie
  • 11
  • 3
  • Can you add more of the stack trace? The first 4 lines isn't enough. – radimpe Jan 03 '18 at 13:38
  • Please check, maybe you will find [this](https://support.oracle.com/epmos/faces/DocumentDisplay?parent=EXTERNAL_SEARCH&sourceId=PROBLEM&id=2129110.1&_adf.ctrl-state=12d7pax6tg_4&_afrLoop=379149074002655) helpful: https://support.oracle.com/epmos/faces/DocumentDisplay?parent=EXTERNAL_SEARCH&sourceId=PROBLEM&id=2129110.1&_adf.ctrl-state=12d7pax6tg_4&_afrLoop=379149074002655 – Panagiotis Stoupos Jan 03 '18 at 15:08
  • According to the ticket: Cause The default stack size of 256k was exceeded, causing the error seen in the application server logging. Solution The size of the Java stack must be increased. The default Java stack size is configured using the Xss argument in JAVA_ARGS (or JAVA_OPTS on JBoss). In many scenarios, this value defaults to 256k. Doubling this value resolved this issue ( -Xss512k ). The optimal value will depend on the customer's specific application needs. – Panagiotis Stoupos Jan 03 '18 at 15:09
  • @PanagiotisStoupos Perhaps you can add your last comment as an answer. Looks like it should solve the problem. – radimpe Jan 04 '18 at 11:13
  • Thank you @radimpe . I will try the above suggestion – Newbie Jan 08 '18 at 17:16

2 Answers2

2

According to this oracle support ticket:

The default stack size of 256k was exceeded, causing the error seen in the application server logging. In order to resolve this, the size of the Java stack must be increased. The default Java stack size is configured using the Xss argument in JAVA_ARGS (or JAVA_OPTS on JBoss). In many scenarios, this value defaults to 256k. Doubling this value resolved this issue ( -Xss512k ). The optimal value will depend on the customer's specific application needs.

Panagiotis Stoupos
  • 140
  • 1
  • 12
1

I had the same situation. I agree that increasing -Xss param is standard way of solving the issue (reason is that DefaultStoreFactory build "tree" based on Experience Manager content with recursive algorithm). But I would suggest also to review structure of Experience Manager in order to decrease unused and useless data, in other case - you will need to keep this "tree" in memory (heap) and it can raise out of memory issue (it's actually was my case :) )

child_ron
  • 9
  • 2
  • Child_ron, Could you please tell what kind of data you are referring here? – Newbie Jan 22 '18 at 10:12
  • Could you please tell me what kind of data you are referring to. Is it some thing like Experience Manager workspaces? – Newbie Jan 22 '18 at 10:13