Hi,
Is there any way to check how come Catalina.out log file is suddenly
growing too fast? It's growing every 1 hour about 4GB. Please help me to
advise.
Thanks,
Michael
Hi Michael,
Nic actually did. He perfectly explained the steps that are now needed. In case you have nobody available to debug it you would have to do it on your own or recruit a sys admin.
Nobody from here can fix it for you directly as we do not have access to your system.
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
welcome to Atlassian community!
If the growth came all of a sudden I'd recommend to compare an old catalina.out with one that is growing rapidly. There must be something in your setup that leads to let the file grow that rapidly in the past.
Please also check which Jira version you are currently using. It more recent versions the amount of data logged to catalina.out has been reduced. (Please see https://jira.atlassian.com/browse/JRASERVER-67796)
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My JIRA version is v6.0.2. Catalina.out is suddenly growing too fast since last month ago. Every 4 days I need to clear Catalina.out. Please advise.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The question remains "what did you change that triggered the sudden increase?"
If you can't remember what you did, then I would take a look at the log to see exactly what is going into it. Rapid growth usually indicates something repeatedly failing frequently, and I expecy you will see a lot of the same error over and over. That error is a good pointer to what is going wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You will need to do some log analysis - look at how the logs behaved before your change and afterwards. The new stuff appearing in the log should point you towards what is now being logged that was not before.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Anyone can advise for this issue. I saw a lot of below error in catalina.out?
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:257)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:300)
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)
at java.lang.Thread.run(Thread.java:745)
2020-05-20 10:30:04,428 webhooks-http-retriever:thread-1 ERROR [http.nio.protocol.HttpAsyncRequestExecutor] http-outgoing-11 [CLOSED] HTTP protocol exception: null
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:257)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:300)
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)
at java.lang.Thread.run(Thread.java:745)
2020-05-20 10:30:04,429 webhooks-http-retriever:thread-1 ERROR [http.nio.protocol.HttpAsyncRequestExecutor] http-outgoing-1 [CLOSED] HTTP protocol exception: null
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:257)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:300)
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)
at java.lang.Thread.run(Thread.java:745)
2020-05-20 10:30:04,428 webhooks-http-retriever:thread-9 ERROR [http.nio.protocol.HttpAsyncRequestExecutor] http-outgoing-9 [CLOSED] HTTP protocol exception: null
Thanks,
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.