vaseems / xmemcached

Automatically exported from code.google.com/p/xmemcached
Apache License 2.0
0 stars 0 forks source link

Xmemcached stopped exception #229

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Run the memcached instance.
2.Run the web server.
3.Leave the server idle for some time without any request/response

What is the expected output? What do you see instead?
Web Server should not get shutdown.

What version of the product are you using? On what operating system?
xMemcahced 1.3.5 , jetty8

Please provide any additional information below.

In my application i am using memcached and jetty server.

When ever the following exception occurs in production, Jetty server is getting 
down.

2012-11-12 10:20:52,535[qtp1431814845-49] 
ERROR(LogoffServlet.java:<doPost>:42)- SESSION ID - 1fim3n8xywzw01r7eth5myoyjq
2012-11-12 10:20:52,535[qtp1431814845-49] 
ERROR(LogoffServlet.java:<doPost>:50)- Invalidating Session - 
org.eclipse.jetty.server.session.HashedSession:1fim3n8xywzw01r7eth5myoyjq@178320
3528
2012-11-12 10:20:52,842[qtp1431814845-11 Selector0] 
ERROR(AbstractSocket.java:<disconnect>:202)- onDisconnect: AbstractSocket 
[clientNumber=440312, customerId=prod101, formattedCustomerId=prod101, 
pushExceptionCount=0] reasonVal : 1006, reasonMessage : closed
2012-11-12 10:20:52,842[qtp1431814845-11 Selector0] 
ERROR(AbstractSocket.java:<disconnect>:203)- onDisconnect: AbstractSocket 
[clientNumber=440312, customerId=prod101, formattedCustomerId=prod101, 
pushExceptionCount=0] StackTrace : 
java.lang.Thread.getStackTrace(Thread.java:1479)|com.tradeking.at.servlet.Abstra
ctSocket.disconnect(AbstractSocket.java:203)|com.tradeking.at.servlet.CustomerWe
bSocket.onClose(CustomerWebSocket.java:77)|org.eclipse.jetty.websocket.WebSocket
ConnectionD13.closed(WebSocketConnectionD13.java:296)|org.eclipse.jetty.server.A
bstractConnector.connectionClosed(AbstractConnector.java:1048)|org.eclipse.jetty
.server.nio.SelectChannelConnector.endPointClosed(SelectChannelConnector.java:28
0)|org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager.
endPointClosed(SelectChannelConnector.java:345)|org.eclipse.jetty.io.nio.Selecto
rManager$SelectSet.destroyEndPoint(SelectorManager.java:948)|org.eclipse.jetty.i
o.nio.SelectChannelEndPoint.doUpdateKey(SelectChannelEndPoint.java:523)|org.ecli
pse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:469)|or
g.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:283)|org.eclip
se.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)|org.ecli
pse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)|java.lan
g.Thread.run(Thread.java:662)|
2012-11-12 10:21:30,786[ConcurrentSessionMonitorThread_5] 
FATAL(MemcachedInterface.java:<gets>:86)- Exception accessing memcache ::  
net.rubyeye.xmemcached.exception.MemcachedException: Xmemcached is stopped
    at net.rubyeye.xmemcached.XMemcachedClient.sendCommand(XMemcachedClient.java:247)
    at net.rubyeye.xmemcached.XMemcachedClient.fetch0(XMemcachedClient.java:573)
    at net.rubyeye.xmemcached.XMemcachedClient.get0(XMemcachedClient.java:971)
    at net.rubyeye.xmemcached.XMemcachedClient.gets(XMemcachedClient.java:984)
    at net.rubyeye.xmemcached.XMemcachedClient.gets(XMemcachedClient.java:1006)
    at net.rubyeye.xmemcached.XMemcachedClient.gets(XMemcachedClient.java:995)
    at com.tradeking.at.util.MemcachedInterface.gets(MemcachedInterface.java:84)
    at com.tradeking.at.sessionhandler.ConcurrentSessionMonitorThread.run(ConcurrentSessionMonitorThread.java:81)

when ever the server instance is idle for some time, session is becoming null 
and this error is observerd.

Can some one help me in this issue and let me know..why jetty server is 
stopping due to this exception?

Original issue reported on code.google.com by SwathiSt...@gmail.com on 14 Nov 2012 at 10:58

GoogleCodeExporter commented 9 years ago
Xmemcached cloud not shutdown your web server.Instead,this exception meant that 
your web server shut down the xmemcached client.
So ,you have to find out why the web servier shutdown when it was idle.

Original comment by killme2...@gmail.com on 14 Nov 2012 at 11:07

GoogleCodeExporter commented 9 years ago
any progress?

Original comment by xzhu...@avos.com on 19 Nov 2012 at 7:04

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by killme2...@gmail.com on 20 Feb 2013 at 9:10