Spring Integration TCP: How to get local IP address - spring-integration

Question

I'm new to Spring Integration and experimenting with its TCP support. I have implemented a very basic TCP server that accepts connections and just logs the messages from the clients. This works fine, but I'm stuck in finding out how to get the local IP address to which the client has connected (the server machine has multiple IP addresses). It seems that the MessageHeaders contain only the remote address.
Here's my configuration:
#EnableIntegration
#Configuration
public class SpringConfig {
#Bean
public MessageChannel requestChannel() {
return new DirectChannel();
}
#Bean
public AbstractServerConnectionFactory serverConnectionFactory() {
TcpNetServerConnectionFactory connectionFactory =
new TcpNetServerConnectionFactory(2000);
return connectionFactory;
}
#Bean
public TcpReceivingChannelAdapter tcpReceivingChannelAdapter() {
TcpReceivingChannelAdapter adapter = new TcpReceivingChannelAdapter();
adapter.setOutputChannel(requestChannel());
adapter.setConnectionFactory(serverConnectionFactory());
return adapter;
}
#Bean
public PrintService printService() {
return new PrintService();
}
}
And my PrintService:
#MessageEndpoint
public class PrintService {
#ServiceActivator(inputChannel = "requestChannel")
public String print(Message<byte[]> message) {
// How can I get the local IP address here?
}
}
Edit 1
Basically, I would like to have the result from java.net.Socket.getLocalAddress() available in my print(...) function. Maybe like this: message.getHeaders().get(IpHeaders.LOCAL_IP_ADDRESS)
I also tried to add a custom message header by subclassing TcpMessageMapper and overriding supplyCustomHeaders(...), but I couldn't find out how to access the underlying socket.

Answer 1

Basically, I would like to have the result from java.net.Socket.getLocalAddress() available in my print(...) function. Maybe like this: message.getHeaders().get(IpHeaders.LOCAL_IP_ADDRESS)
Yeah, I'd better expose something like T getTarget() on the TcpConnection to allow to get access to underlying socket from the TcpMessageMapper.supplyCustomHeaders() implementation...
Feel free to raise a JIRA on the matter and we'll try to figure out what to do from the Framework perspective.
Meanwhile, as a workaround: I guess you should extend the TcpNetServerConnectionFactory a bit and override its initializeConnection(TcpConnectionSupport connection, Socket socket) to store the connectionId <-> socket relationship in some global map. Maybe even in your custom TcpMessageMapper? Having connectionId in the supplyCustomHeaders() you will be able to restore the particular socket for your purpose.