Problem Note 42882: An exception might occur when you select Internet Protocol version 6 (IPv6) in the SAS® Deployment Wizard
When you select IPv6 in the SAS Deployment Wizard, you might receive the following error when you start your Web application server:
ERROR [] org.jgroups.protocols.UDP - failed sending message to null (0 bytes)
java.net.BindException: Cannot assign requested address: Datagram send failed
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(Unknown Source)
at org.jgroups.protocols.UDP._send(UDP.java:316)
at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:286)
at org.jgroups.protocols.TP.doSend(TP.java:937)
at org.jgroups.protocols.TP.send(TP.java:926)
at org.jgroups.protocols.TP.down(TP.java:712))
at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
at org.jgroups.protocols.PING.sendMcastDiscoveryRequest(PING.java:214)
at org.jgroups.protocols.PING.sendGetMembersRequest(PING.java:208)
at org.jgroups.protocols.PingSender.run(PingSender.java:59)
at java.lang.Thread.run(Unknown Source)
This problem occurs when the zone identifier is present ub the IPv6 multicast.address= Java Virtual Machine option. You can resolve this issue by removing the zone identifier. To do that you must edit the SAS_configuration_directory\Lev1\Web\Applications\RemoteServices\environment.properties file and remove the zone identifier from the IPv6 multicast address. For example, in the following environment.properties file, you need to remove "%4":
#Mon Mar 28 10:32:20 EDT 2011
multicast.port=8561
multicast.address=ff14\:0\:0\:0\:250\:56ff\:fe91\:de%4
metadata.user=sastrust@saspw
publish.user=sasadm@saspw
The corrected file appears as follows:
#Mon Mar 28 10:32:20 EDT 2011
multicast.port=8561
multicast.address=ff14\:0\:0\:0\:250\:56ff\:fe91\:de
metadata.user=sastrust@saspw
publish.user=sasadm@saspw
Operating System and Release Information
SAS System | SAS Enterprise BI Server | z/OS | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows XP 64-bit Edition | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft® Windows® for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2003 for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2008 | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2008 for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows XP Professional | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Enterprise 32 bit | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Enterprise x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Home Premium 32 bit | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Home Premium x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Professional 32 bit | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Professional x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Ultimate 32 bit | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Ultimate x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Windows Vista | 9.2 TS2M3 | 9.4 TS1M0 |
Windows Vista for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
64-bit Enabled AIX | 9.2 TS2M3 | 9.4 TS1M0 |
64-bit Enabled HP-UX | 9.2 TS2M3 | 9.4 TS1M0 |
64-bit Enabled Solaris | 9.2 TS2M3 | 9.4 TS1M0 |
HP-UX IPF | 9.2 TS2M3 | 9.4 TS1M0 |
Linux | 9.2 TS2M3 | 9.4 TS1M0 |
Linux for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Solaris for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
The following error occurs when you select IPv6 during configuration: "java.net.BindException: Cannot assign requested address: Datagram send failed"
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2011-04-13 12:49:03 |
Date Created: | 2011-04-07 08:15:46 |