TOC Showing "Loading, click here to cancel..." for every entry that's 3 levels deep

[Rocky_XYZZY]

The title pretty much says it all. Expanding the TOC (WebHelp Pro, RoboHelp Server hosted using SQL instead of Access) results in "Loading, click here to cancel..." forever for each such topic.

We've tried the fix that's referenced in this technote, to no avail (and may have even increased the problem from intermittent to consistent).

Looking at the robohelpserver.log file, we see the content below. It appears that the server code crashes when expanding that level of the TOC and this is the stack trace that gets reported every time.

Whether it's caused by a config problem, content problem or code bug, I don't know.

Any thoughts?

--------------------------snip-----------------------------

2012-01-03 09:53:11.117 [WARN] http-8080-5 adobe.robohelp.server.TocCreatorJS -

java.lang.NullPointerException

    at

org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:1178)

    at

org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:1060)

    at

org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1279)

    at

org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1262)

    at adobe.robohelp.server.TocCreatorJS.CreateHtmlChunk(TocCreatorJS.java:142)

    at adobe.robohelp.server.TocCreatorJS.CreateHtml(TocCreatorJS.java:84)

    at adobe.robohelp.server.WHTOCAgent.doCommand(WHTOCAgent.java:158)

    at adobe.robohelp.server.TOCAgent.doCommand(TOCAgent.java:54)

    at adobe.robohelp.server.AgentManager.doCommand(AgentManager.java:84)

    at adobe.robohelp.server.HelpArea.doGet(HelpArea.java:101)

    at adobe.robohelp.server.AreaManager.doGet(AreaManager.java:80)

    at adobe.robohelp.server.RoboHelpServer.doGet(RoboHelpServer.java:172)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

    at

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

    at

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

    at

org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

    at

org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

    at

org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)

    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

    at

org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)

    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

    at

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)

    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

    at java.lang.Thread.run(Unknown Source)

[johndaigle]

(See my reply to your other post)

Meanwhile, the technote link you have in your latest post is broken. Could you send that to my email address?

Thanks

john

[Rocky_XYZZY]

Some additional information that may be useful:

When I wipe the TOC in the RoboHelp project and create a test TOC with only a few topics, structured four levels deep, it works fine when published and hosted as WebHelpPro.

If, however, I add to this test TOC another folder of topics, all at a single level and containing 20 entries, it breaks the hierarchical portion of the TOC, causing the topics deeper than 3 levels deep to once again show "Loading, click to cancel" when published to the server and viewed.

If I go back in and remove half of the 20 topics in the new folder (resulting in 10 topics), the hierarchical portion of the TOC begins working again.

Going back in and adding five topics back (resulting in 15 topics), the hierarchical portion of the TOC fails but differently: topics deeper than level 2 fail.

There seems to be a distinct and reproduceable correlation between the number of topics and the "Loading, click to cancel..." failure. I had to leave the office before I could determine if this is total topics in the TOC or if it was a limitation of the number of topics that a single book could contain but it's startling that 15 topics in a single book and four topics in a second book is sufficient content to cause the TOC to fail. It makes me wonder if this is some sort of server-side memory allocation issue or something.