コミュニティアチーブメントバーを展開する。

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

この会話は、活動がないためロックされています。新しい投稿を作成してください。

解決済み

IllegalStateException in every page in CQ5 author

Avatar

以前のコミュニティメンバー

Hi,

in every page of my author instance, I see logged in error.log this exception:

http://pastebin.com/RrquajzW

This doesn't happen in my publish instance and I've tried to install my bundles in a different environment and everything works fine, even in the author instance. I'm using Tomcat7.

 

[If this question gets deleted could you at least explain why? Thanks]

1 受け入れられたソリューション

Avatar

正解者
以前のコミュニティメンバー

Maybe I got it. The problem seems to appear when I click on a jsp page which calls a web service. If I see that the service is taking too long to respond, I stop the loading of the page, but I'm still actually waiting for the service response. Then, when I reload the page, another call is done to the same service which is already waiting, so I get the error. That's how I could replicate it.

I think it could be solved by restarting the web services server, like Tomcat in my case.

Maybe it could be something like that for you too, rrakesh...

元の投稿で解決策を見る

4 返信

Avatar

Level 10

The community team will never delete a question (unless its offensive or spam) - we hide duplicate threads however. So if a community member posts the same question twice - we will hide one and keep one visible. 

As far for this question - what version of CQ are you using?  

Avatar

Level 1

i m also getting the same error. I have also posted the question.

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

I m using CQ5.6.1 version.

Avatar

以前のコミュニティメンバー

rrakesh wrote...

i m also getting the same error. I have also posted the question.

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

I m using CQ5.6.1 version.

 

I'm using Version 5.5.0.

[the post was cancelled earlier because of the pastebin link, sorry]

Avatar

正解者
以前のコミュニティメンバー

Maybe I got it. The problem seems to appear when I click on a jsp page which calls a web service. If I see that the service is taking too long to respond, I stop the loading of the page, but I'm still actually waiting for the service response. Then, when I reload the page, another call is done to the same service which is already waiting, so I get the error. That's how I could replicate it.

I think it could be solved by restarting the web services server, like Tomcat in my case.

Maybe it could be something like that for you too, rrakesh...