Hi,
After installing the latest version of HipChat for JIRA. I keep getting this error in my logs literally every 2 seconds...
2014-10-06 13:48:47,879 hipchat-client-io:thread-10 ERROR [http.nio.protocol.HttpAsyncRequestExecutor] http-outgoing-250 [CLOSED] HTTP protocol exception: null
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:252)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:295)
at org.apache.http.nio.reactor.ssl.SSLIOSession.receiveEncryptedData(SSLIOSession.java:340)
at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:366)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118)
at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:220)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:284)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
Any ideas?
Hello,
I'm facing the same problem.
Similar log entries appear couple of times per second, thus filling our logfiles.
JIRA version 6.3.9
I've removed all old hipchat plugin files as recommended and restarted JIRA service but it didn't work.
Entries doesn't appear after service restart for some time (minutes/hours) so I suppose it may start after first connection between JIRA and hipchat. I will try to setup HipChat server in staging environment and check if this problem can be reproduced. I can't switch to safe mode on production.
Do you have other solution?
Is there a way to turn off logging these entries?
Miguel and Ricardo, can you please try to see if enabling Safe Mode helps? Is it affecting your JIRA / Confluence instance in any way? I am suspecting that it might be related to one or more installed plugin(s) that you have on your instance(s).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have the same on our Confluence instance. This is real pain!! Atlassian, appreciate some input here please.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.