[#PETALSESBCONT-130] Add default option -Djava.net.preferIPv4Stack=true when starting petals - Petals Link JIRA

Details

Type: Improvement Request
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 3.1.1
Fix Version/s: 3.1.2, 4.0.0
Component/s: Launcher
Security Level: Public

Description:

Hide

When starting, the petals ESB server opens ports for at least the registry service. For some reasons, the protocol IPv6 is sometimes used instead of IPv4 as usual, and the result is petals ESB appears to be frozen.

Below is an example of opened ports and associated programs when petals uses IPv6

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      735/smbd        
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      735/smbd        
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      795/sshd        
tcp6       0      0 :::7900                 :::*                    LISTEN      975/java        
tcp6       0      0 :::7600                 :::*                    LISTEN      975/java        
tcp6       0      0 :::7700                 :::*                    LISTEN      975/java        
tcp6       0      0 :::22                   :::*                    LISTEN      795/sshd

This can be solved by adding the option -Djava.net.preferIPv4Stack=true to the JVM
(see http://download.oracle.com/javase/6/docs/technotes/guides/net/properties.html).

I think this behavior should be documented and maybe the option added by default while IPv6 is not yet widely used.

Show

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      735/smbd        
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      735/smbd        
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      795/sshd        
tcp6       0      0 :::7900                 :::*                    LISTEN      975/java        
tcp6       0      0 :::7600                 :::*                    LISTEN      975/java        
tcp6       0      0 :::7700                 :::*                    LISTEN      975/java        
tcp6       0      0 :::22                   :::*                    LISTEN      795/sshd

This can be solved by adding the option -Djava.net.preferIPv4Stack=true to the JVM (see http://download.oracle.com/javase/6/docs/technotes/guides/net/properties.html). I think this behavior should be documented and maybe the option added by default while IPv6 is not yet widely used.