Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting hostname for tcp transport table fails #31

Open
GoogleCodeExporter opened this issue Mar 30, 2015 · 0 comments
Open

Setting hostname for tcp transport table fails #31

GoogleCodeExporter opened this issue Mar 30, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Jeff:  From Martin Marcher.  Might no longer be an issue.

Hello,

short: change the service=TcpTable MBean under the subetha Options. (stop,
change, apply, start) - still returns the localhost IP
trying to get the tcp transport to work with postfix.

My setup is the following:

DNS is set up for internal and external network separately but yields the right
values.

mx.example.com :: Postfix
  2 NICs (1 Public, 1 Private)
  Private IP 10.0.0.1
subetha.example.com :: jboss with subetha
  1 NIC
  Private IP 10.0.0.2 (hostname is subetha.example.com)
  reachable by postfix
  all mail to lists.example.com is routed there

Now looking up the protocol in http://www.postfix.org/tcp_table.5.html I made up
the following session.

# nc subetha.example.com 2502
get everyone@lists.example.com
200 smtp:[127.0.0.1]:2500

# postmap -q "everyone@lists.example.com" tcp:subetha.example.com:2502
smtp:[127.0.0.1]:2500

as you can see the problem is that subetha returns 127.0.0.1 as the transport
endpoint which of course won't work.

 * Now go to you jboss at Port 8080
 * Open the jmx Management Console
 * Search for the Subetha Options
 * go to the the "service=TcpTable" link
 * invoke "stop()"
 * HostName set to subetha.example.com
 * Apply Changes
 * Refresh MBean View reloads the page with the correct hostname
 * invoke "start()" (No errors until here)

Now again (first postmap then nc):

# postmap -q "everyone@lists.example.com" tcp:subetha.example.com:2502
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)

# postmap -q "everyone@lists.example.com" tcp:subetha.example.com:2502
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
postmap: warning: read TCP map reply from subetha.example.com:2502: unexpected
EOF (Operation now in progress)
smtp:[127.0.0.1]:2500
#

# nc subetha.openforce.com 2502
get everyone@lists.openforce.com
#


Problems:

1. Subetha still returns the localhost IP
2. as postmap indicates there seems to be some problem restarting the MBean
correctly (forgive me the lack of terms, new to JBoss and SubEtha)

Original issue reported on code.google.com by lhori...@gmail.com on 4 Jun 2009 at 11:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant