XLD becomes unresponsive during Garbage Collection.

Follow

Rohit Yadav -

Issue

Sometimes , while GC job is running XLD becomes unresponsive or might be inaccessible from browser or rest call.

Environment

XL Deploy

Resolution

Increase the JVM and restart XLD..

Cause

Due to having long gc running on large vloume of packages to be purged and the XLD runs with relatively low heap memory.

Additional Information

2017-02-16 02:25:15.869 [task-sys-task.step-dispatcher-2903] {stepDescription=Running garbage collection on the repository, taskId=bcc2e170-ee45-4194-baae-5206ef6f5908, username=admin} DEBUG o.a.j.core.gc.GarbageCollector - version (1/3): analyzed 5806000 nodes...
2017-02-16 02:33:37.737 [Thread-37] {} INFO com.xebialabs.deployit.Server - Shutting down XL Deploy Server.
2017-02-16 03:00:18.300 [qtp856937591-45] {} WARN o.e.jetty.server.HttpConnection - HttpConnection@2cc9760d{FILLING}
java.lang.IllegalStateException: s=DISPATCHED i=true a=null
at org.eclipse.jetty.server.HttpChannelState.handling(HttpChannelState.java:232)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:282)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
2017-02-16 03:08:40.468 [Thread-37] {} INFO o.e.jetty.server.ServerConnector - Stopped ServerConnector@8a325ca{HTTP/1.1}{0.0.0.0:4517}
2017-02-16 03:37:43.596 [qtp856937591-25] {username=admin} ERROR c.x.d.UnhandledExceptionMapper - Unhandled Exception: {}
java.lang.RuntimeException: org.eclipse.jetty.io.EofException: Early EOF

Tags

We can map those tags to tags we have in Zendesk.

Have more questions? Submit a request
Powered by Zendesk