Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Macro hangs from time to time

Amir Shehata June 3, 2019

I have an installation of Confluence 6.15. The server is behind a fire wall that blocks port 8443 and 8090, so I have NAT rules which redirect ports 443 and 80 to their respective confluence counter parts. This seems to work fine.

 

Occasionally, especially after installing a new plugin, the Macro system doesn't work. Basically, I can't insert macros on a page. When I look at the catalina.out, I see:

03-Jun-2019 15:55:31.896 WARNING [Catalina-utility-2] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [https-jsse-nio2-8443-exec-20] (id=[43]) has been active for [66,857] milliseconds (since [6/3/19 3:54 PM]) to serve the same request for [https://ss.stgeorge.ca/plugins/macrobrowser/browse-macros.action?detailed=false&macroMetadataClientCacheKey=1559602311766] and may be stuck (configured threshold for this StuckThreadDetectionValve is [60] seconds). There is/are [1] thread(s) in total that are monitored by this Valve and may be stuck.
java.lang.Throwable
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

 

In atlassian-confluence.log I see errors like:

2019-06-03 15:57:41,263 ERROR [https-jsse-nio2-8443-exec-1] [[Standalone].[localhost].[/].[file-server]] log Servlet.service() for servlet [file-server] threw exception
-- referer: https://ss.stgeorge.ca/pages/viewpage.action?pageId=4915207 | url: /s/958d712f2c5a152a73e647749b050514-CDN/en_GB/8100/b0984b7297905b7c7bd946458f753ce0130bfc8c/c801f297b0de92bd412b9bcc2be6f215/_/download/contextbatch/js/editor-v4,editor,macro-browser,-_super,-atl.general,-main,-page,-viewcontent/batch.js | traceId: 834f889536b66408 | userName: admin

I captured packets using tcp dump and I see a lot of TCP retransmits going from the local interface to the public IP address of the machine over 443, these should hit the NAT rule and get forwarded to 8443

After leaving it idle for a period of time, it starts working. Seems like there is a timeout somewhere

Anyone know what could be going on?

1 answer

0 votes
Amir Shehata June 7, 2019

I got an email stating that there is an answer from Shannon Spaniol, but seems when I click view answer, I don't have enough permissions!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events