Database connection failure

I have a fresh installation of upsource. But there is a few issues with that. The most important one - I guess - is that after a few minutes, we get a "Database connection Failure"

Log files includes this:

2018-04-02 11:24:25,857] [Upsource Error] [2018-04-02 11:24:25,856]   WARN - oxy.jetty.WebSocketProxySocket - CLIENT 3  onWebSocketError on client  
[2018-04-02 11:24:25,857] [Upsource Error] Connection refused
[2018-04-02 11:24:25,857] [Upsource Error]      at Method)
[2018-04-02 11:24:25,857] [Upsource Error]      at
[2018-04-02 11:24:25,857] [Upsource Error]      at
[2018-04-02 11:24:25,857] [Upsource Error]      at
[2018-04-02 11:24:25,857] [Upsource Error]      at$900(
[2018-04-02 11:24:25,857] [Upsource Error]      at$SelectorProducer.processSelected(
[2018-04-02 11:24:25,858] [Upsource Error]      at$SelectorProducer.produce(
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.execute(
[2018-04-02 11:24:25,858] [Upsource Error]      at
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.QueuedThreadPool$
[2018-04-02 11:24:25,858] [Upsource Error]      at



Cannot find out what is the root cause of it.

Comment actions Permalink

I'm not 100% sure it's the same database related issue but I'm experiencing disconnects with a fresh install of Upsource and am getting the error below:


[Upsource Error] [2019-03-01 16:49:17,586] WARN - oxy.jetty.WebSocketProxySocket - CLIENT 2 onWebSocketError on client
[Upsource Error] Connection refused
[Upsource Error] at Method) ~[?:1.8.0_191]
[Upsource Error] at ~[?:1.8.0_191]
[Upsource Error] at ~[jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at$900( [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at$SelectorProducer.processSelected( [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at$SelectorProducer.produce( [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume( [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume( [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.execute( [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob( [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.QueuedThreadPool$ [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at [?:1.8.0_191]
Comment actions Permalink

i did a fresh install some one month back and i can see the error log at upsource home directory/log/cassandra/
if the upsource web application UI throws an error like """Database connection failure""" 
then grep the error log and you should be able to see something like 
Caused by: (/srv/upsource-2018.2.1141/data/cassandra/data/projects/largecontent-d116e430443311e994fbcb05bfbe8967/mc-1800-big-Data.db): corruption detected, chunk at 27594928 of length 64972.

am further looking into that error

Comment actions Permalink

Any ideas.  Just had this happen to me as well

Comment actions Permalink

Just a note to the developers. I was looking though the log files and cassandra-stderr contains the following

[2019-05-15 08:54:23,751] [Apache Cassandra Error] 2019-05-15T08:54:23,740 [[APP-WRAPPER] Proxy 1] WARN o.a.cassandra.service.StartupChecks - The JVM is not configured to stop on OutOfMemoryError which can cause data corruption. Use one of the following JVM options to configure the behavior on OutOfMemoryError: -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, or -XX:OnOutOfMemoryError="<cmd args>;<cmd args>"


I guess this could cause the behavior observed by the reporters.


Please sign in to leave a comment.