Date: Fri, 29 Mar 2024 15:45:47 +0000 (UTC) Message-ID: <409543509.25493.1711727147946@ae5f4610bf64> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_25492_1927453149.1711727147946" ------=_Part_25492_1927453149.1711727147946 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page provides platform-specific notes for Ice 3.5.
On this page:
This release supports the operating systems, compilers, and run-time env= ironments listed on the ZeroC web site.
As of Ice 3.5.1, the IceGrid graphical administrative utility can be used wit= h Java6 or Java7, however the metrics graph feature is only available when running with Java7 a= nd JavaFX.
With Ice 3.5.0, the utility requires Java7 and JavaFX.
JavaFX is included in recent releases of Java7.
Linux users should be aware of the following issues.
Mono requires that a system's host name be correctly configured and that=
it resolves to an IP address. Otherwise, Mono is unable to determine the l=
ocal IP addresses, which causes the creation of object adapters that listen=
on INADDR_ANY/0.0.0.0 to fail with an Ice.DNSException
.<=
/p>
The IBM JDK ships with limited jurisdiction policy files for the cryptog= raphic libraries. More information, including a link to download unrestrict= ed jurisdiction policy files, are available at the DeveloperWorks site.
Once you have downloaded the policy files, unpack them into this directo= ry:
/usr/lib/jvm-private/java-1_6_0-ibm/jce/vanilla
Windows users should be aware of the following issues.
In previous releases, the .NET assemblies (Ice.dll
, bin
 =
;subdirectory of the Ice installation directory, such as
C:\Program Files\ZeroC\Ice-3.4.2\bin
As of Ice 3.5, the .NET assemblies are stored in a separate subdirectory=
named Assemblies
, as in
C:\Program Files\ZeroC\Ice-3.5.1\Assemblies
The Ice assembly for .NET Compact Framework can be found in A=
ssemblies\cf
.
The Ice Visual Studio Add-in automatically adds or updates the appropria= te assembly references in your projects. If you do not use the Ice Visual S= tudio Add-in, you must update your project references to use the new locati= on of the Ice assemblies.
Also note that this change means the iceboxnet
ex=
ecutable, which still resides in bin
, is no longer in the=
same directory as the Ice assemblies. For example, if your IceBox server c=
onfiguration uses the IceSSL plug-in and relies on the fact that iceboxnet.exe
and IceSSL.dll
are in the=
same directory, you may need to update your configuration. Suppose your&nb=
sp;iceboxnet
configuration included the following propert=
y:
Ice.Plugin.IceSSL=3DIceSSL:IceSSL.PluginFactory
Since IceSSL.dll
was in the same directory as the=
executable, no additional information was necessary to assist Ice in locat=
ing the plug-in's assembly. Now, however, you will need to do one of the fo=
llowing:
Ice.Plugin.IceSSL=
=3D"C:\Program Files\ZeroC\Ice-3.5.1\Assemblies\IceSSL.dll":IceSSL.PluginFa=
ctory
Ice.Plugin.IceS=
SL=3D"IceSSL,Version=3D3.5.1.0":IceSSL.PluginFactory
In previous releases, public Ice header files disabled many Visual Studi=
o compiler warnings. Now the header files disable only a minimal set of war=
nings, which means compiling your Ice application may produce compiler warn=
ings that were not reported before. To eliminate these warnings, you can mo=
dify your source code, add pragmas
or disable these warnings in your Visual Studio projects.
IPv6 is not currently supported in Java 6 on Windows due to a JVM bug.
Ice uses the QueryPerformanceCounter
Windows API =
function to measure time with a monotonic clock. If you are experiencing ti=
ming or performance issues, there are two knowledgebase articles that may b=
e relevant for your system:
http://support.microsoft.com/?id=3D896256
http://support.microsoft.com/?id=3D895980