Getting "Cannot open <nil> as a Reader" in Synchrony logs when editing a page

関連コンテンツ

  • 関連コンテンツがありません

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Data Center のみ - この記事は、Data Center プラットフォームのアトラシアン製品にのみ適用されます。

この KB は Data Center バージョンの製品用に作成されています。Data Center 固有ではない機能の Data Center KB は、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。

*Fisheye および Crucible は除く

要約

Users are unable to edit some or all Confluence pages. 

環境

Confluence 7.19

診断

In the atlassian-synchrony.log  the following error message can be found: 

2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]] 2023-10-26 06:50:44,603 ERROR [async-dispatch-16] [synchrony.middleware.errors] error processing request {:id "uHL-hFlKENudoLvHatCRcQ", :throwable #error {
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]   :cause "Cannot open <nil> as a Reader."
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]   :via
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]   [{:type java.lang.IllegalArgumentException
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]     :message "Cannot open <nil> as a Reader."
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]     :at [clojure.java.io$fn__11520 invokeStatic "io.clj" 288]}]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]   :trace
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]   [[clojure.java.io$fn__11520 invokeStatic "io.clj" 288]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [clojure.java.io$fn__11422$G__11398__11429 invoke "io.clj" 69]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [clojure.java.io$reader invokeStatic "io.clj" 102]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [clojure.lang.RestFn applyTo "RestFn.java" 139]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [clojure.core$apply invokeStatic "core.clj" 667]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [clojure.core$slurp invokeStatic "core.clj" 6942]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [clojure.lang.RestFn invoke "RestFn.java" 439]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [tilt.bayeux.server$message_str_from_request_body invokeStatic "server.clj" 516]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [tilt.bayeux.server$request_handler$fn__33934$fn__34008 invoke "server.clj" 544]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [tilt.utils (take?) "utils.clj" 186]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [tilt.utils$wrap_simple_cors$fn__31466$fn__31507 invoke "utils.clj" 184]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [clojure.lang.AFn run "AFn.java" 22]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [java.util.concurrent.ThreadPoolExecutor runWorker "ThreadPoolExecutor.java" 1128]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [java.util.concurrent.ThreadPoolExecutor$Worker run "ThreadPoolExecutor.java" 628]
2023-10-26 08:50:44,603 DEBUG [253:StdOutHandler [/opt/java/openjdk/bin/java]]    [java.lang.Thread run "Thread.java" 834]]}}

原因

From the exception above, It seems that Synchrony try to process a web socket connection request but the Reader to read request content is NULL. The assumption is that Synchrony tries to serve a request which is not aiming for Synchrony.

So the most suspicious resource that could cause this behaviour is the reverse proxy configured on top of Confluence/Synchrony. 

ソリューション

The best approach is to confirm if this is an issue related with the Load Balancer or Reverse Proxy configuration. You can make use of the indications outlined in our KB How to bypass a reverse proxy or SSL in Application Links to provide a direct connection to Confluence for your users, where to validate if the issue still happens or not.

If bypassing the LB/Proxy, the issue does not reoccurs and the users can edit the page(s), please check your configuration. You can make use of our multiple KBs depending on the situation and technology used: 


最終更新日: 2023 年 12 月 14 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する

関連コンテンツ

  • 関連コンテンツがありません
Powered by Confluence and Scroll Viewport.