Forums

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

You can only read using the application read buffer provided by the handler

Yogesh Mude
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 1, 2018

Hi Team,

Found below error in  <Confluence_Home>/logs/atlassian-confluence.log file...

java.lang.IllegalArgumentException: You can only read using the application read buffer provided by the handler

Could you please anyone assist me how to deal with this.

3 answers

0 votes
Bernhard Berger February 11, 2019

Check my feedback

0 votes
Bernhard Berger February 11, 2019

Hi there

I dit find the same error in the confluence log:

11-Feb-2019 21:36:48.221 SEVERE [https-jsse-nio-7443-exec-21] org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error reading request, ignored                                                                                         
 java.lang.IllegalArgumentException: You can only read using the application read buffer provided by the handler.                                                                                                                                 
        at org.apache.tomcat.util.net.SecureNioChannel.read(SecureNioChannel.java:571)                                                                                                                                                            
        at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1204)                                                                                                                                          
        at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1140)                                                                                                                                                    
        at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:72)                                                                                                                                                
        at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171)                                                                                                                                             
        at org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:151)                                                                                                                                           
        at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:148)                                                                                                                                 
        at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54)                                                                                                                                   
        at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:53)                                                                                                                                                       
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:770)                                                                                                                                                
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415)                                                                                                                                                    
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)                                                                                                                                                        
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)                                                                                                                                                        
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)                                                                                                                                                        
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)                                                                                                                                                     
        at java.lang.Thread.run(Thread.java:748)                                                                                                                                                                                                  
Bernhard Berger February 11, 2019

I get this error by calling "edit" a confluence page.

Bernhard Berger February 11, 2019

after disabling "Collaborative editing" in the administration area the error disappears :-)

Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 12, 2019

Bernhard,

This tells me that your server is having an issue handling the Collaborative editing, so you'll want to troubleshoot it.

In the past, we discovered these errors are coming from Tomcat and are not related to Confluence.

The issue looks very similar to this one logged in Apache bug repository. It looks like a Tomcat/SSL/Proxy issue.

Have a look at that and if you continue to have issues, I would encourage you to either raise a newer thread here on Community, or a creating a Support Ticket.

Regards,

Shannon

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 5, 2018

Yogesh,

Are you experiencing a particular issue, or did you just notice that message in your logs?

I had a look in our past support tickets, and it seems that it may not be related to Confluence, and is similar to this issue. It could be an issue with a proxy, SSL, or Tomcat.

If you can provide us better clarity on the issue you're experiencing with Confluence, we can help you with that.

Regards,

Shannon

Yogesh Mude
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 7, 2018

Hi @Shannon S

Thanks for your response.

Actually, a few days back our Confluence was down and I get into log files to see what exactly reason for this so I saw only below message logged in to the log (atlassian-confluence.log) files.

java.lang.IllegalArgumentException: You can only read using the application read buffer provided by the handler 

Could you please let me know what else details you to want for this so that I can provide you.

Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 8, 2018

Hi Yogesh,

Unfortunately that's not enough information to go on. It's also not likely that is the only message in the logs, so the next time Confluence crashes you'll want to have a thorough look at ALL log files, not just atlassian-confluence.log. See Working with Confluence Logs.

It's highly unlikely that would be the only message if Confluence is even being used at all, since further messages are generated just by using Confluence. For example, you'd see the Starting Confluence message while starting Confluence.

How often does Confluence go down, and if you attempt to restart it, and you tail the logs, can you let us know what series of messages you see?

You'll want to have a look at this as well for help troubleshooting: 

Regards,

Shannon

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events