Hi,
One of our applications running on RHEL is not working as expected - the application supplier has advised that a port is not allowing the correct traffic.
I know the port is open for incoming connections (checked with nmap and telnet) however is there a way I check the port is open for outgoing connections?
Iptables is disabled, so is SELinux.
Thanks
Maybe describing a bit more your issue and giving more information can help alot
What isnt working/ or as expected ? what error messgaes do you get?
What ports is it using ? etc...
All I need to know if there is a way to confirm whether the port allows outgoing (not just incoming) traffic?
I can then pass the information to the supplier to fix.. I have just read that tcp ports allow connections bidirectionally as default, is this correct (it was in another forum post)?
I have tried various commands now and by all appearences the port is working exactly as our test environment (which is on the same server for this application).
Error messages all point to a problem connecting to the client (there are no firewalls between the server/client it is all on an internal network), jboss should communicating through this port. I can't provide the exact error just now as I am no longer at work but it was along the lines of Broken Pipe/Stream can't communicate.
Thanks for the reply.
shut down the application server and run netstat -pan, is there anything listening on the port already?
If so your app can't bind to the port.
Error posted below - still thinking along the lines of ports...!?
port 8446 is open/listening.
2013-07-02 10:51:27,129 TRACE [org.jboss.remoting.transport.socket.ServerThread.processInvocation] preparing to process next invocatio
n invocation
2013-07-02 10:51:27,129 TRACE [org.jboss.remoting.transport.socket.ServerThread.readVersion] blocking to read version from input strea
m
2013-07-02 10:51:27,203 TRACE [org.jboss.remoting.transport.socket.ServerThread.dorun] SocketException received. This is likely due to
client disconnecting and resetting connection.
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2196)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2376)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2443)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2515)
at java.io.ObjectInputStream.read(ObjectInputStream.java:800)
at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:824)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:510)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
2013-07-02 10:51:27,204 DEBUG [org.jboss.remoting.transport.socket.ServerThread.dorun] WorkerThread#0[xx.xx.xx.xx1419] closing socketW
rapper: ServerSocketWrapper[Socket[addr=/xx.xx.xx.xx,port=1419,localport=8446].2909a1]
2013-07-02 10:51:27,204 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper.close] unable to writing CLOSING byte
java.net.SocketException: Broken pipe
That maybe a red herring, after investigating further the final message logged to the server.log is actually a timeout:
2013-07-02 13:35:41,382 TRACE [org.jboss.remoting.transport.socket.ServerThread.dorun] java.net.SocketTimeoutException: Read timed out
2013-07-02 13:35:41,382 DEBUG [org.jboss.remoting.transport.socket.ServerThread.dorun] WorkerThread#0[xx.xx.xx.xx:8859] closing socket
Wrapper: ServerSocketWrapper[Socket[addr=/xx.xx.xx.xx,port=8859,localport=8446].180e475]