Hi Phillip,
Thanks for the response and info. My jmx.properties file has
jmx.address=127.0.0.1 port=9999 (unchanged from the default template).
I can run the james-cli with no problem. So it looks like the registry
is happy with the host ip.
It's interesting that IMAP works fine, but SMTP does not. I don't
really know what all JAMES is doing with JMX. But I would expect that
whatever types of connections it's trying to do on SMTP that it would be
doing the same on IMAP. Wouldn't it?
Thanks again. But no luck with the fix that worked for you.
Any idea if there are any JAMES developers that monitor this forum any more?
Jerry
On 2/25/2014 5:53 PM, Phillip Odam wrote:
Hi Jerry
Your exception below looks similar to one I came across in the last
day and resolved.
# using the command ./james-cli.sh -h <private ip> -p 9999 listusers
Error connecting to remote JMX agent!
java.rmi.ConnectException: Connection refused to host: <public ip>;
nested exception is:
java.net.ConnectException: Connection timed out
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:129)
at
javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
The issue ended up being nothing to do with james, the RMI registry
was doing a lookup on the machines hostname to determine the IP to
advertise for connecting to the JMX server.
To resolve this all I needed to do was make the hostname of the
machine resolve to the private ip of the server (on the server itself)
and not the public (since the public ip doesn't allow JMX connections
coming in). Then a restart of james picked up the new IP and all
resolved... real head spinner tho as it took quite some time to
realise just what was going on.
Hope this helps in your investigation. Feel free to ask for more
detail as I know I haven't gone into specifics here.
Thanks
Phillip
On 2/24/14, 10:30 PM, Jerry M wrote:
After a very long day, I got James 3 installed and almost up and
running. IMAP is working and the database tables were created, etc.
But I can't get anything to work on SMTP. With default log levels, i
got these log entries:
INFO 21:12:13,150 | james.smtpserver | Id='9288089' User=''
Connection established from 99.55.143.34
DEBUG 21:12:13,150 | james.smtpserver | Id='9288089' User='' Unable
to process request
INFO 21:12:13,166 | james.smtpserver | Id='9288089' User=''
Connection closed for 99.55.143.34
I turned on debug level in all of the logs. And it showed an
exception stack dump as well:
java.rmi.ConnectException: Connection refused to host: 64.34.163.186;
nested exception is:
java.net.ConnectException: Connection refused: connect
at
sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:340)
at sun.rmi.registry.RegistryImpl_Stub.list(Unknown Source)
I have reviewed all of my configuration settings. I'm sure I'm doing
something wrong. But this exception message tells me very little
other than it is refused. I'm pretty sure it's not a firewall
issue. I can get through to port 25 as indicated that log entries
appear. It fails when running telnet from my local client as well as
running telnet on the server. And since it appears to be at the
TCPIP connection level, I don't think it has anything to do with SMTP
authorization.
I had an earlier post about mixing v2 and v3 instances on the same
server. I am doing that. But v2 is configured to listen only on one
IP address, and v3 is configured to listen on a separate IP address
(as far as I can tell...) v2 is still running fine. I've checked to
configurations of both. But that doesn't mean I didn't miss something.
Can someone explain the problem or give me something else i can look
at that might indicate the problem?
Thanks.
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4335 / Virus Database: 3705/7124 - Release Date: 02/25/14
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
