Dustin,
I immediately responded about "not running as root" and "client piece of
code", as soon as I saw your first response. I guessed you missed seeing my
response (here it is below again). Also you seem to respond without
"original message thread" so we keep loosing the responses :).
Thanks again for your patience on this.
Siddharth
I have modified my memcached load to "/usr/bin/memcached -m 64 -U 11211 -p
11211 -u root -l 127.0.0.1"
Client class extends from spy memcachedclientnow and uses "super(new
InetSocketAddress("127.0.0.1", 11211));"
On the server I ran ps -ef
prompt>:~$ sudo ps -ef | grep memcached
[sudo] password for username:
username 26614 14126 0 09:34 pts/2 00:00:00 /usr/bin/memcached -m 64
-U 11211 -p 11211 -u root -l 127.0.0.1
Also
prompt$ sudo netstat -anp | grep 11211
tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN
26614/memcached
tcp 0 0 127.0.0.1:11211 127.0.0.1:56746
ESTABLISHED 26614/memcached
tcp6 0 0 127.0.0.1:56746 127.0.0.1:11211
ESTABLISHED 26625/java
udp 0 0 127.0.0.1:11211 0.0.0.0:*
26614/memcached
I obvious still get the warn message. I know I am missing something really
basic here.
A flip question : Does this have any side effect ? Performance, CPU util or
anything else ? If not, is there a log4j setting ?
2012-02-06 14:06:14.106 INFO net.spy.memcached.MemcachedConnection:
Connection state changed for sun.nio.ch.SelectionKeyImpl@1d439fe
2012-02-06 14:06:14.107 INFO net.spy.memcached.MemcachedConnection:
Reconnecting due to failure to connect to {QA sa=0.0.0.0/0.0.0.0:11211,
#Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0}
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592)
at
net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:313)
at
net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:199)
at net.spy.memcached.MemcachedClient.run(MemcachedClient.java:1622)
Thanks again
Siddharth
On Wed, Feb 8, 2012 at 1:11 PM, Dustin <[email protected]> wrote:
>
> On Tuesday, February 7, 2012 7:59:32 PM UTC-8, Siddharth Jagtiani wrote:
>>
>> So is there a way to fix the annoying message or a way to mask it. Since
>> it obviously has no impact on my setup and functionality.
>
>
> Do you honestly believe that not being able to connect to the server
> you've configured it to talk to has no impact on your setup and/or
> functionality?
>
> If you want it to stop giving you that error, you should not configure
> it to connect there. I don't know how you think you're connecting, but I
> have a hard time imagining the client just made up that address, tried to
> connect to it, and complained when it couldn't. Can you post your actual
> connection code, at least?
>
> I'd also strongly recommend you not run the server as root. That's
> still not a good idea.
>
