-
Bug
-
Resolution: Handled by Support
-
Medium
-
None
-
2.8.2
-
None
-
None
-
Ubuntu
After starting Stash I am usually able to use it for some time, several hours or less than hour in some cases. After that exception is shown when Stash accessed from web or via Git client.
HTTP Status 500 - Filter execution threw an exception type Exception report message Filter execution threw an exception description The server encountered an internal error that prevented it from fulfilling this request. exception javax.servlet.ServletException: Filter execution threw an exception org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) root cause java.lang.NoClassDefFoundError: ch/qos/logback/core/status/ErrorStatus ch.qos.logback.core.recovery.ResilientOutputStreamBase.postIOFailure(ResilientOutputStreamBase.java:101) ch.qos.logback.core.recovery.ResilientOutputStreamBase.write(ResilientOutputStreamBase.java:55) java.io.OutputStream.write(OutputStream.java:75) ch.qos.logback.core.encoder.LayoutWrappingEncoder.doEncode(LayoutWrappingEncoder.java:135) ch.qos.logback.core.OutputStreamAppender.writeOut(OutputStreamAppender.java:188) ch.qos.logback.core.FileAppender.writeOut(FileAppender.java:206) ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:212) ch.qos.logback.core.rolling.RollingFileAppender.subAppend(RollingFileAppender.java:175) ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:103) ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:48) ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:272) ch.qos.logback.classic.Logger.callAppenders(Logger.java:259) ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:441) ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:395) ch.qos.logback.classic.Logger.info(Logger.java:599) com.atlassian.stash.internal.request.DefaultRequestManager.logEndRequest(DefaultRequestManager.java:166) com.atlassian.stash.internal.request.DefaultRequestManager.doAsRequest(DefaultRequestManager.java:79) com.atlassian.stash.internal.web.filters.RequestAttributeFilter.doFilterInternal(RequestAttributeFilter.java:46) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:343) org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:260) com.atlassian.johnson.spring.web.filter.BypassableDelegatingFilterProxy.doFilter(BypassableDelegatingFilterProxy.java:54) org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) note The full stack trace of the root cause is available in the Apache Tomcat/7.0.40 logs. Apache Tomcat/7.0.40
Also in catalina.out such events
java.util.logging.ErrorManager: 4: Unable to create [/home/common/atlassian-stash-2.8.2/logs]
Exception in thread "scheduler_Worker-5" java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy
at ch.qos.logback.classic.spi.LoggingEvent.<init>(LoggingEvent.java:126)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:439)
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:395)
at ch.qos.logback.classic.Logger.error(Logger.java:558)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:560)
Exception in thread "scheduler_Worker-2" java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy
at ch.qos.logback.classic.spi.LoggingEvent.<init>(LoggingEvent.java:126)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:439)
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:395)
at ch.qos.logback.classic.Logger.error(Logger.java:558)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:560)
Other events
Nov 23, 2013 7:35:43 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Nov 23, 2013 7:35:44 PM org.apache.catalina.session.StandardManager doUnload
SEVERE: IOException while saving persisted sessions: java.io.FileNotFoundException: /home/common/atlassian-stash-2.8.2/work/Catalina/localhost/_/SESSIONS.ser (No such file or directory)
java.io.FileNotFoundException: /home/common/atlassian-stash-2.8.2/work/Catalina/localhost/_/SESSIONS.ser (No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
at java.io.FileOutputStream.<init>(FileOutputStream.java:110)
at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:386)
at org.apache.catalina.session.StandardManager.unload(StandardManager.java:353)
at org.apache.catalina.session.StandardManager.stopInternal(StandardManager.java:518)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5569)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1575)
at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1564)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
User that running Stash has rights to create files in log folder and in other folders of stash home folder as well. Generally folder logs already created and Stash is able to write logs to it.
[BSERV-4146] Stash stopping functioning after some time after starting
Hello Oleksiym
I have created a JIRA support ticket for you at support.atlassian.com (https://support.atlassian.com/browse/SSP-2911) but I see that you've never logged in to https://support.atlassian.com. Once you do, please comment here so that I can assign the ticket to you enabling your access.
In the future, please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. Our support engineers respond to cases in https://support.atlassian.com and creating an issue ticket there will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case and therefore it is a more appropriate location for us to gather any required system and/or configuration data from you.
Thank you,
Daniel
I'll ask our support team to look into this. Something like this is best raised via support.atlassian.com
Thank you! I created my account in support.atlassian.com under the same username.