[omniORB] (no subject)
Luyckx Joan
Joan.Luyckx@siemens.com
Thu Apr 3 15:05:03 2003
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01C2F9E9.FBAA66A0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C2F9E9.FBAA66A0"
------_=_NextPart_001_01C2F9E9.FBAA66A0
Content-Type: text/plain;
charset="iso-8859-1"
Hi,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office"
/>
We are working in a unix environment using omniORB as a C++ ORB and jacORB
as a java ORB.
We upgraded from omniORB-4.0.0 to omniORB-4.0.1 to solve a problem with
multipathing. It works fine, if we specify a clientTransportRule carrying
the ip address of the server instead of its hostname.
Is there a work-around, since we like to work with the hostname instead of
the ipaddress.
I also included the omniORB.cfg file that we use at this moment.
Kind Regards,
Joan
Joan Luyckx
SIEMENS Atea
Joan.Luyckx@siemens.com <mailto:Joan.Luyckx@siemens.>
phone: +32 14 253974
mobile:
Fax: +32 14 22 29 94
Mobile Solutions
and Enabling Services
http://www.ic.siemens.be <http://www.ic.siemens.be/eng/default_rd.shtm>
------_=_NextPart_001_01C2F9E9.FBAA66A0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4922.900" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=517065812-03042003><FONT
face="Times New Roman" size=3> </FONT>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-FAMILY: Arial">Hi,</SPAN><SPAN
style="FONT-SIZE: 12pt; mso-ansi-language: EN-GB"><?xml:namespace prefix = o ns
= "urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-FAMILY: Arial">We are working in
a unix environment <SPAN class=517065812-03042003>using omniORB as a C++
ORB and jacORB as a java ORB.</SPAN></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-FAMILY: Arial"><SPAN
class=517065812-03042003></SPAN><SPAN class=517065812-03042003>We</SPAN>
upgraded from omniORB-4.0.0 to omniORB-4.0.1 to solve a problem with
multipathing. It works fine, if we specify a clientTransportRule
carrying the ip address of the server instead of its
hostname.</SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-FAMILY: Arial"></SPAN><SPAN
lang=EN-US style="FONT-FAMILY: Arial">Is there a work-around<SPAN
class=517065812-03042003>, </SPAN>since <SPAN class=517065812-03042003>we
like to work with the </SPAN>hostname <SPAN
class=517065812-03042003>instead of the ipaddress</SPAN>.</SPAN><SPAN
lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-FAMILY: Arial">I also included
the omniORB.cfg file that we use at this moment.</SPAN><SPAN
lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-FAMILY: Arial">Kind
Regards,</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-FAMILY: Arial">Joan</SPAN><SPAN
lang=EN-US><o:p></o:p></SPAN></P></SPAN></FONT><FONT face=Arial size=2><SPAN
class=517065812-03042003></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=517065812-03042003> </SPAN></FONT></DIV>
<TABLE width="92%" align=left border=0>
<TBODY>
<TR>
<TD vAlign=top align=left width="45%"><FONT face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: windowtext; FONT-FAMILY: Arial; TEXT-DECORATION: none">Joan
Luyckx </SPAN></FONT><BR><B><FONT face="Times New Roman" color=#008080
size=3>SIEMENS</FONT> <FONT face=Arial color=#008080 size=2>Atea</FONT>
</B><BR><FONT face=Verdana color=#000000 size=1><A
href="mailto:Joan.Luyckx@siemens.">Joan.Luyckx@siemens.com
</A></FONT><BR><FONT face=Arial color=#000000
size=1><U>phone</U>: +32 14 253974 <BR><U>mobile</U>:
<BR><U>Fax:</U> +32 14 22 29 94
<BR></FONT></TD>
<TD vAlign=top align=left width="34%"><B><BR><FONT face="Courier New"
color=#000000 size=2>Mobile Solutions <BR>and Enabling
Services</FONT><BR></B><A
href="http://www.ic.siemens.be/eng/default_rd.shtm">http://www.ic.siemens.be</A>
</TD>
<TD width="21%"> </TD></TR>
<TR>
<TD vAlign=top align=left width="100%" colSpan=3></TD></TR></TBODY></TABLE>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>
------_=_NextPart_001_01C2F9E9.FBAA66A0--
------_=_NextPart_000_01C2F9E9.FBAA66A0
Content-Type: application/octet-stream;
name="omniORB.cfg"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="omniORB.cfg"
########################################################################=
####=0A=
# omniORB (4.0 or above) configuration file =
#=0A=
########################################################################=
####=0A=
=0A=
########################################################################=
####=0A=
########################################################################=
####=0A=
########################################################################=
####=0A=
# =
#=0A=
# ORB wide options =
#=0A=
# =
#=0A=
########################################################################=
####=0A=
=0A=
########################################################################=
####=0A=
# Tracing level=0A=
# level 0 - critical errors only=0A=
# level 1 - informational messages only=0A=
# level 2 - configuration information and warnings=0A=
# level 5 - the above plus report server thread creation and=0A=
# communication socket shutdown=0A=
# level 10 - the above plus execution trace messages=0A=
# level 25 - output trace message per send or receive giop =
message=0A=
# level 30 - dump up to 128 bytes of a giop message=0A=
# level 40 - dump the complete giop message=0A=
#=0A=
# Valid values =3D (n >=3D 0)=0A=
#=0A=
=0A=
traceLevel =3D 25=0A=
=0A=
########################################################################=
####=0A=
# Trace Invocations=0A=
# If true, then each local and remote invocation will generate a =
trace =0A=
# message.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
traceInvocations =3D 0=0A=
=0A=
########################################################################=
####=0A=
# Trace thread id=0A=
# If true, all trace messages include the thread id of the thread =
doing=0A=
# the logging.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
traceThreadId =3D 0=0A=
=0A=
########################################################################=
####=0A=
# dumpConfiguration=0A=
# Set to 1 to cause the ORB to dump the current set of =
configuration=0A=
# parameters.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
dumpConfiguration =3D0 =0A=
=0A=
########################################################################=
####=0A=
# maxGIOPVersion=0A=
#=0A=
# Set the maximum GIOP version the ORB should support. The ORB =
tries=0A=
# to match the <major>.<minor> version as specified.=0A=
#=0A=
# Valid values =3D 1.0 | 1.1 | 1.2=0A=
#=0A=
maxGIOPVersion =3D 1.2=0A=
=0A=
########################################################################=
####=0A=
# giopMaxMsgSize=0A=
#=0A=
# This value defines the ORB-wide limit on the size of GIOP message =
=0A=
# (excluding the header). If this limit is exceeded, the ORB will=0A=
# refuse to send or receive the message and raise a MARSHAL =
exception.=0A=
#=0A=
# Valid values =3D (n >=3D 8192)=0A=
#=0A=
giopMaxMsgSize =3D 2097152 # 2 MBytes.=0A=
=0A=
=0A=
########################################################################=
####=0A=
# strictIIOP flag=0A=
# Enable vigorous check on incoming IIOP messages=0A=
#=0A=
# In some (sloppy) IIOP implementations, the message size value =
in=0A=
# the header can be larger than the actual body size, i.e. there =
is=0A=
# garbage at the end. As the spec does not say the message size=0A=
# must match the body size exactly, this is not a clear violation=0A=
# of the spec.=0A=
#=0A=
# If this flag is non-zero, the incoming message is expected to=0A=
# be well-behaved. Any messages that have garbage at the end will=0A=
# be rejected.=0A=
# =0A=
# The default value of this flag is true, so invalid messages are=0A=
# rejected. If you set it to zero, the ORB will silently skip the=0A=
# unread part. The problem with this behaviour is that the header=0A=
# message size may actually be garbage, caused by a bug in the=0A=
# sender's code. The receiving thread may block forever on the=0A=
# strand as it tries to read more data from it. In this case the=0A=
# sender won't send any more as it thinks it has marshalled in =
all=0A=
# the data.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
strictIIOP =3D 1=0A=
=0A=
########################################################################=
####=0A=
# lcdMode=0A=
#=0A=
# Set to 1 to enable 'Lowest Common Denominator' Mode.=0A=
# This will disable various features of IIOP and GIOP which are=0A=
# poorly supported by some ORBs, and disable warnings/errors when=0A=
# certain types of erroneous message are received on the wire.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
lcdMode =3D 0 =0A=
=0A=
########################################################################=
####=0A=
# tcAliasExpand flag=0A=
#=0A=
# This flag is used to indicate whether TypeCodes associated with =
Anys=0A=
# should have aliases removed. This functionality is included =
because=0A=
# some ORBs will not recognise an Any containing a TypeCode with=0A=
# aliases to be the same as the actual type contained in the Any. =
Note=0A=
# that omniORB will always remove top-level aliases, but will not =
remove=0A=
# aliases from TypeCodes that are members of other TypeCodes =
(e.g.=0A=
# TypeCodes for members of structs etc.), unless tcAliasExpand is =
set to 1.=0A=
# There is a performance penalty when inserting into an Any if =0A=
# tcAliasExpand is set to 1. The default value is 0 (i.e. aliases =
of=0A=
# member TypeCodes are not expanded). Note that aliases won't be =
expanded=0A=
# when one of the non-type-safe methods of inserting into an Any =
is=0A=
# used (i.e. when the replace() member function or non - type-safe =
Any=0A=
# constructor is used. )=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
tcAliasExpand =3D 0=0A=
=0A=
########################################################################=
####=0A=
# useTypeCodeIndirections=0A=
#=0A=
# If true (the default), typecode indirections will be used. Set=0A=
# this to false to disable that. Setting this to false might be=0A=
# useful to interoperate with another ORB implementation that =
cannot=0A=
# handle indirections properly.=0A=
# =0A=
# Valid values =3D 0 or 1=0A=
useTypeCodeIndirections =3D 1=0A=
=0A=
########################################################################=
####=0A=
# acceptMisalignedTcIndirections=0A=
#=0A=
# If true, try to fix a mis-aligned indirection in a typecode. =
This=0A=
# is used to work around a bug in some versions of Visibroker's =
Java=0A=
# ORB.=0A=
# =0A=
# Valid values =3D 0 or 1=0A=
acceptMisalignedTcIndirections =3D 0=0A=
=0A=
=0A=
########################################################################=
####=0A=
# scanGranularity=0A=
#=0A=
# The granularity at which the ORB scans for idle connections.=0A=
# This value determines the minimum value that inConScanPeriod or=0A=
# outConScanPeriod can be.=0A=
#=0A=
# Valid values =3D (n >=3D 0 in seconds) =0A=
# 0 --> do not scan for idle connections.=0A=
#=0A=
scanGranularity =3D 5=0A=
=0A=
=0A=
########################################################################=
####=0A=
# nativeCharCodeSet=0A=
#=0A=
# set the native code set for char and string=0A=
#=0A=
#nativeCharCodeSet =3D ISO-8859-1=0A=
nativeCharCodeSet =3D UTF-8=0A=
=0A=
########################################################################=
####=0A=
# nativeWCharCodeSet=0A=
#=0A=
# set the native code set for wchar and wstring=0A=
#=0A=
nativeWCharCodeSet =3D UTF-16=0A=
=0A=
########################################################################=
####=0A=
# omniORB_27_CompatibleAnyExtraction=0A=
#=0A=
# In omniORB pre-2.8.0 versions, the CORBA::Any extraction operator =
for=0A=
# 1. unbounded string operator>>=3D(char*&)=0A=
# 2. bounded string operator>>=3D(to_string)=0A=
# 3. object reference operator>>=3D(A_ptr&) for interface A=0A=
# Return a copy of the value. The caller must free the returned=0A=
# value later.=0A=
#=0A=
# With 2.8.0 and later, the semantics becomes non-copy, i.e. the =
Any=0A=
# still own the storage of the returned value.=0A=
# This would cause a problem in a program that is written to use =
the=0A=
# pre-2.8.0 semantics. To make it easier for the transition,=0A=
# set omniORB_27_CompatibleAnyExtraction to 1.=0A=
# This would revert the semantics to the pre-2.8.0 versions.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
omniORB_27_CompatibleAnyExtraction =3D 0=0A=
=0A=
########################################################################=
####=0A=
# abortOnInternalError=0A=
#=0A=
# If the value of this variable is TRUE then the ORB will abort=0A=
# instead of throwing an exception when a fatal internal error is=0A=
# detected. This is useful for debuging the ORB -- as the stack =
will=0A=
# not be unwound by the exception handler, so a stack trace can be=0A=
# obtained.=0A=
# It is hoped that this will not often be needed by users of =
omniORB!=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
abortOnInternalError =3D 0=0A=
=0A=
=0A=
########################################################################=
####=0A=
########################################################################=
####=0A=
########################################################################=
####=0A=
# =
#=0A=
# Client Side Options =
#=0A=
# =
#=0A=
########################################################################=
####=0A=
=0A=
########################################################################=
####=0A=
# InitRef=0A=
#=0A=
# Specify the objects the ORB should return in response to calls =
to=0A=
# resolve_initial_references.=0A=
#=0A=
# There can be more than one configuration line defining InitRef.=0A=
# Each line adds one initial reference to the ORB.=0A=
#=0A=
# Here are some valid examples:=0A=
#=0A=
# Specify the root context of the Naming Service. (Notice the end of =
line=0A=
# continuation marker '\'=0A=
#=0A=
#InitRef =3D =
NameService=3DIOR:010000002800000049444c3a6f6d672e6f72672f436f734\=0A=
#e616d696e672f4e616d696e67436f6e746578743a312e300001000000000000002c0000=
00010\=0A=
#102000c0000003139322e3136382e312e3000f90a00000c000000349568c45cb1e67800=
00000\=0A=
#100000000=0A=
#=0A=
ORBInitRef NameService=3Dcorbaname::localhost=0A=
#=0A=
# Specify the Trading service and the interface repository using =
corbaloc:=0A=
#=0A=
# InitRef =3D =
TradingService=3Dcorbaloc:iiop:marrow:5009/MyObjectKey=0A=
# =3D InterfaceRepository=3Dcorbaloc::1.2@marrow:5009/Intf=0A=
#=0A=
# The default for the set of initial references is empty.=0A=
=0A=
########################################################################=
####=0A=
# DefaultInitRef=0A=
#=0A=
# DefaultInitRef provides a prefix string which is used to resolve =
=0A=
# otherwise unknown names. When resolve_initial_references() is =
unable to =0A=
# resolve a name which has been specifically configured (with =
InitRef),=0A=
# it constructs a string consisting of the default prefix, a `/' =
character,=0A=
# and the name requested. The string is then fed to =
string_to_object().=0A=
# For example, if DefaultInitRef is set up like this:=0A=
# DefaultInitRef =3D corbaloc::myhost.example.com=0A=
# A call to resolve_initial_references("MyService") will return the =
object=0A=
# reference denoted by `corbaloc::myhost.example.com/MyService'.=0A=
#=0A=
# The default is empty.=0A=
=0A=
=0A=
########################################################################=
####=0A=
# clientTransportRule=0A=
#=0A=
# When the client receives an IOR that defines 1 or more ways to =
contact=0A=
# the server, the rules in clientTransportRule filter and =
prioritise=0A=
# the order in which the transports are used. =0A=
#=0A=
# There can be more than one configuration line of this type.=0A=
# Each line adds one rule to the selection process. The rules are =
applied=0A=
# in the order they are defined. The relative positions of the rules =
define=0A=
# the relative priority. The first rule has the highest priority.=0A=
#=0A=
# The syntax of a rule is as follows:=0A=
# clientTransportRule =3D [^]<address mask> [action]+=0A=
#=0A=
# <address mask> can be:=0A=
# 1. localhost the address is this machine=0A=
# 2. w.x.y.z/m1.m2.m3.m4 IPv4 address with the bits =
selected by=0A=
# the mask. e.g. =
172.16.0.0/255.240.0.0=0A=
# 3. * the wildcard that matches any =
address=0A=
#=0A=
# <action>+ can be one or more of the following:=0A=
# 1. none Do not use this address=0A=
# 2. tcp,ssl,unix Use the 3 transports in the specified =
order =0A=
# if any or all of them are =
available=0A=
# 3. bidir Any connection to this address should =
be=0A=
# used bidirectionally.=0A=
#=0A=
# The optional prefix ^ before <address mask>, if present, =
causes=0A=
# the ORB to remove previously declared clientTransportRules =
from=0A=
# its internal store because adding the current rule.=0A=
#=0A=
# By default, no rule is defined. The ORB implicitly uses the =
following=0A=
# rule:=0A=
# clientTransportRule =3D * unix,tcp,ssl=0A=
# If any rule is specified, no implicit rule will be applied.=0A=
#=0A=
# Given an IOR, for each of the addresses within it, the ORB matches =
the=0A=
# address to the rules. If one is found, the position of the matched =
rule=0A=
# and the action is noted. If the action is none, the address is =
discarded.=0A=
# If the action does not contain the transport the address is =
specified for,=0A=
# e.g. the action is "ssl" but the address is "tcp", the address is =
=0A=
# discarded. Otherwise, the address and action is entered as one of =
the=0A=
# candidates to use. Having gone through all the addresses, the =
candidiates=0A=
# available are then ordered based on the priority of the matching =
rules and=0A=
# used accordingly.=0A=
#=0A=
# Here are some example usages:=0A=
#=0A=
# A) Restrict to only contacting server on the same host:=0A=
# clientTransportRule =3D localhost unix,tcp=0A=
# =3D * none=0A=
# B) Use tcp to contact servers in the intranet and must use =
bidirectional=0A=
# ssl otherwise.=0A=
# clientTransportRule =3D 172.16.0.0/255.240.0.0 unix,tcp=0A=
# =3D * =
bidir,ssl=0A=
# C) When a fast network (192.168.1.0) exists in the cluster, use it =
in=0A=
# preference to the external network.=0A=
# clientTransportRule =3D 192.168.1.0/255.255.255.0 =
unix,tcp=0A=
# clientTransportRule =3D 172.16.0.0/255.240.0.0 =
unix,tcp=0A=
# =3D * none=0A=
# =0A=
# =0A=
=0A=
clientTransportRule =3D 172.16.24.72 unix,tcp=0A=
=3D * none=0A=
=0A=
########################################################################=
####=0A=
# clientCallTimeOutPeriod=0A=
#=0A=
# Call timeout. On the client side, if a remote call takes longer=0A=
# than the timeout value, the ORB will shutdown the connection =
and=0A=
# raise a COMM_FAILURE.=0A=
#=0A=
# Valid values =3D (n >=3D 0 in milliseconds) =0A=
# 0 --> no timeout. Block till a reply comes back=0A=
#=0A=
clientCallTimeOutPeriod =3D 0=0A=
=0A=
########################################################################=
####=0A=
# outConScanPeriod=0A=
#=0A=
# Idle connections shutdown. The ORB periodically scans all the=0A=
# outgoing connections to detect if they are idle.=0A=
# If no operation has passed through a connection for a scan =
period,=0A=
# the ORB would treat this connection idle and shut it down.=0A=
#=0A=
# Valid values =3D (n >=3D 0 in seconds) =0A=
# 0 --> do not close idle connections.=0A=
#=0A=
outConScanPeriod =3D 120=0A=
=0A=
########################################################################=
####=0A=
# maxGIOPConnectionPerServer=0A=
#=0A=
# The ORB could open more than one connection to a server=0A=
# depending on the number of concurrent invocations to the same=0A=
# server. This variable decides the maximum number of connections =0A=
# to use per server. This variable is read only once at ORB_init.=0A=
# If the number of concurrent invocations exceeds this number, the=0A=
# extra invocations are blocked until the the outstanding ones=0A=
# return.=0A=
#=0A=
# Valid values =3D (n >=3D 1) =0A=
#=0A=
maxGIOPConnectionPerServer =3D 5=0A=
=0A=
########################################################################=
####=0A=
# oneCallPerConnection=0A=
#=0A=
# 1 means only one call can be in progress at any time per =
connection.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
oneCallPerConnection =3D 1=0A=
=0A=
=0A=
########################################################################=
####=0A=
# offerBiDirectionalGIOP=0A=
#=0A=
# Applies to the client side. Set to 1 to indicate that the=0A=
# ORB may choose to use a connection to do bidirectional GIOP=0A=
# calls. Set to 0 means the ORB should never do bidirectional.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
offerBiDirectionalGIOP =3D 0=0A=
=0A=
########################################################################=
####=0A=
# diiThrowsSysExceptions=0A=
#=0A=
# If the value of this variable is 1 then the Dynamic Invocation =
Interface=0A=
# functions (Request::invoke, send_oneway, send_deferred, =
get_response,=0A=
# poll_response) will throw system exceptions as appropriate. =
Otherwise =0A=
# the exception will be stored in the Environment pseudo object =
associated=0A=
# with the Request. By default system exceptions are passed through =
the =0A=
# Environment object.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
diiThrowsSysExceptions =3D 0=0A=
=0A=
########################################################################=
####=0A=
# verifyObjectExistsAndType=0A=
#=0A=
# If the value of this variable is 0 then the ORB will not=0A=
# send a GIOP LOCATE_REQUEST message to verify the existence of=0A=
# the object prior to the first invocation. Set this variable=0A=
# if the other end is a buggy ORB that cannot handle GIOP=0A=
# LOCATE_REQUEST. =0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
verifyObjectExistsAndType =3D 1=0A=
=0A=
########################################################################=
####=0A=
# giopTargetAddressMode=0A=
#=0A=
# On the client side, if it is to use GIOP 1.2 or above to talk to a =
=0A=
# server, use this Target Address Mode.=0A=
#=0A=
# Valid values =3D 0 (GIOP::KeyAddr)=0A=
# 1 (GIOP::ProfileAddr)=0A=
# 2 (GIOP::ReferenceAddr)=0A=
#=0A=
giopTargetAddressMode =3D 0=0A=
=0A=
########################################################################=
####=0A=
# bootstrapAgentHostname=0A=
#=0A=
# Applies to the client side. Non-zero enables the use of Sun's =
bootstrap=0A=
# agent protocol to resolve initial references. The value is the host =
name=0A=
# where requests for initial references should be sent. Only use =
this=0A=
# option to interoperate with Sun's javaIDL.=0A=
#=0A=
#bootstrapAgentHostname =3D localhost=0A=
=0A=
########################################################################=
####=0A=
# bootstrapAgentPort=0A=
#=0A=
# Applies to the client side. Use this port no. to contact the =
bootstrap =0A=
# agent.=0A=
#=0A=
bootstrapAgentPort =3D 900=0A=
=0A=
=0A=
########################################################################=
####=0A=
# principal=0A=
#=0A=
# The value of the principal field in GIOP 1.0 and 1.1 requests=0A=
#=0A=
# principal =3D me=0A=
=0A=
=0A=
=0A=
########################################################################=
####=0A=
########################################################################=
####=0A=
########################################################################=
####=0A=
# =
#=0A=
# Server Side Options =
#=0A=
# =
#=0A=
########################################################################=
####=0A=
=0A=
=0A=
########################################################################=
####=0A=
# endPoint=0A=
# endPointNoPublish=0A=
# endPointNoListen=0A=
# endPointPublishAllIFs=0A=
#=0A=
# There are 3 possible way to specify the endpoints a server should =
create.=0A=
# The 3 forms differ in the following ways:=0A=
# endPoint - create, listen on the connection and publish it in =
IORs=0A=
# endPointNoPublish - same as endPoint but do not publish it in =
IORs=0A=
# endPointNoListen - only publish it in IORs=0A=
#=0A=
# There can be more than one configuration line defining =
endPoints.=0A=
# Each line adds one endpoint to the server.=0A=
#=0A=
# Each configuration line can start with the keyword 'endPoint', =
e.g.=0A=
# endPoint =3D giop:tcp:neem:12345=0A=
# endPoint =3D giop:ssl:neem:23456=0A=
#=0A=
# Or a short hand form can be used, like this:=0A=
#=0A=
# endPoint =3D giop:tcp:neem:12345=0A=
# =3D giop:ssl:neem:23456=0A=
#=0A=
# The value of an endPoint configuration is a transport specific =
string.=0A=
# The transport strings recongised by the ORB and its supported =
transports=0A=
# are:=0A=
# 1. giop:tcp:[<host>]:[<port>]=0A=
# The <host> and <port> parameter are optional. If either =
or=0A=
# both are missing, the ORB fills in the blank. For =
example,=0A=
# "giop:tcp::" will cause the ORB to pick an arbitrary =
tcp port=0A=
# as the endpoint and it will pick one IP address of the =
host=0A=
# as the host name.=0A=
#=0A=
# 2. giop:ssl:[<host>]:[<port>]=0A=
# Similar to the tcp transport except that SSL is run on =
top=0A=
# of the tcp connection.=0A=
#=0A=
# 3. giop:unix:[<filename>]=0A=
# Create a unix domain socket and bind to the file with =
pathname=0A=
# <filename>. If <filename> is not specified, e.g. =
"giop:unix:",=0A=
# the ORB would pick a file name based on the process ID =
and =0A=
# the current timestamp.=0A=
# Therefore, if one wants to write an application that =
always=0A=
# restarts to use the same file to bind to its unix =
domain =0A=
# socket, a filename should be specified in the transport =
string.=0A=
#=0A=
# It is possible to use the ORB's transport extension framework to =
add=0A=
# a new transport to the ORB. In that case, the transport must define =
its=0A=
# own transport string format and must obey the colon separation =
rule.=0A=
# For example, if one is to create a transport which executes an =
arbitrary=0A=
# shell script and let the ORB use its stdin and stdout for sending =
and=0A=
# receiving giop messages, a transport string could look like =
this:=0A=
# giop:shell:magic_gw=0A=
# ^ ^=0A=
# | +--------- transport specific part=0A=
# +--------------- transport name=0A=
#=0A=
# By default, no endPoint configuration is defined. In this case the =
ORB=0A=
# will create just 1 tcp endpoint as if the line:=0A=
# endPoint =3D giop:tcp::=0A=
# is specified in the configuration file=0A=
#=0A=
# Other than tcp, none of the transports are guaranteed to be =
available=0A=
# on all platforms. If one specifies say:=0A=
# endPoint =3D giop:ssl::=0A=
# and the ORB cannot initialise an ssl endpoint, the INITIALIZE =
exception=0A=
# will be raised. Even though ssl is supported on a platform, its =
transport=0A=
# is implemented as a separate shared library and must be linked with =
the=0A=
# application for the ORB to initialise the endpoint.=0A=
#=0A=
# Here are some examples of valid endPoint configurations:=0A=
#=0A=
# endPoint =3D giop:tcp::=0A=
# endPoint =3D giop:unix:=0A=
# =3D giop:ssl::=0A=
#=0A=
# endPointNoPublish =3D giop:tcp::=0A=
# =3D giop:unix:=0A=
# =3D giop:ssl::=0A=
#=0A=
# endPointNoListen =3D giop:tcp:192.168.1.1:12345=0A=
#=0A=
#=0A=
# If the endPointPublishAllIFs boolean parameter is set to true, =
all=0A=
# non-loopback IP network interfaces are published in IORs, rather=0A=
# than just the first one.=0A=
=0A=
#endPoint =3D giop:tcp:172.16.24.72:2809=0A=
=0A=
########################################################################=
####=0A=
# serverTransportRule=0A=
#=0A=
# When the server sees a connection request from a client, it looks =
at the=0A=
# client's address and uses the rules in serverTransportRule to =
determine=0A=
# if the connection should be accepted.=0A=
#=0A=
# There can be more than one configuration line of this type.=0A=
# Each line adds one rule to the selection process. The rules are =
applied=0A=
# in the order they are defined until one matching rule is found. =
=0A=
#=0A=
# The syntax of a rule is as follows:=0A=
# serverTransportRule =3D [^]<address mask> [action]+=0A=
#=0A=
# <address mask> can be:=0A=
# 1. localhost if the address is this machine=0A=
# 2. w.x.y.z/m1.m2.m3.m4 IPv4 address with the bits =
selected by=0A=
# the mask. e.g. =
172.16.0.0/255.240.0.0=0A=
# 3. * the wildcard that matches any =
address=0A=
#=0A=
# <action>+ can be one or more of the following:=0A=
# 1. none Do not accept this connection.=0A=
# 2. tcp,ssl,unix Accept if the transport is any of =
the=0A=
# 3 specified.=0A=
# 3. bidir Allow bidirectional requests if =
the=0A=
# client requests it.=0A=
#=0A=
# The optional prefix ^ before <address mask>, if present, =
causes=0A=
# the ORB to remove previously declared clientTransportRules =
from=0A=
# its internal store because adding the current rule.=0A=
#=0A=
# By default, no rule is defined. The ORB implicitly uses the =
following=0A=
# rule:=0A=
# serverTransportRule =3D * unix,tcp,ssl=0A=
# If any rule is specified, the implicit rule will not be =
applied.=0A=
#=0A=
# Here are some example usages:=0A=
#=0A=
# A) Only accept connections from our intranet=0A=
# serverTransportRule =3D localhost =
unix,tcp,ssl=0A=
# =3D 172.16.0.0/255.240.0.0 tcp,ssl=0A=
# =3D * none=0A=
#=0A=
# B) Only accept ssl connections if the client is not on our =
intranet=0A=
# serverTransportRule =3D localhost =
unix,tcp,ssl=0A=
# =3D 172.16.0.0/255.240.0.0 tcp,ssl=0A=
# =3D * =
bidir,ssl=0A=
=0A=
########################################################################=
####=0A=
# serverCallTimeOutPeriod=0A=
#=0A=
# Call timeout. On the server side, if the ORB cannot completely =0A=
# unmarshal a call's arguments in the defined timeout, it shutdown =
the=0A=
# connection.=0A=
#=0A=
# Valid values =3D (n >=3D 0 in milliseconds) =0A=
# 0 --> no timeout.=0A=
#=0A=
serverCallTimeOutPeriod =3D 0=0A=
=0A=
########################################################################=
####=0A=
# inConScanPeriod=0A=
#=0A=
# Idle connections shutdown. The ORB periodically scans all the=0A=
# incoming connections to detect if they are idle.=0A=
# If no operation has passed through a connection for a scan =
period,=0A=
# the ORB would treat this connection idle and shut it down.=0A=
#=0A=
# Valid values =3D (n >=3D 0 in seconds) =0A=
# 0 --> do not close idle connections.=0A=
#=0A=
inConScanPeriod =3D 180=0A=
=0A=
=0A=
########################################################################=
####=0A=
# threadPerConnectionPolicy=0A=
#=0A=
# 1 means the ORB should dedicate one thread per connection on the =
=0A=
# server side. 0 means the ORB should dispatch a thread from a =
pool=0A=
# to a connection only when a request has arrived.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
threadPerConnectionPolicy =3D 1=0A=
=0A=
########################################################################=
####=0A=
# maxServerThreadPerConnection=0A=
#=0A=
# The max. no. of threads the server will dispatch to serve the=0A=
# requests coming from one connection.=0A=
#=0A=
# Valid values =3D (n >=3D 1) =0A=
#=0A=
maxServerThreadPerConnection =3D 100=0A=
=0A=
=0A=
########################################################################=
####=0A=
# maxServerThreadPoolSize=0A=
# The max. no. of threads the server will allocate to do various=0A=
# ORB tasks. This number does not include the dedicated thread=0A=
# per connection when the threadPerConnectionPolicy is in effect=0A=
#=0A=
# Valid values =3D (n >=3D 1) =0A=
#=0A=
maxServerThreadPoolSize =3D 100=0A=
=0A=
########################################################################=
####=0A=
# threadPerConnectionUpperLimit=0A=
#=0A=
# If the one thread per connection is in effect, this number is=0A=
# the max. no. of connections the server will allow before it=0A=
# switch off the one thread per connection policy and move to=0A=
# the thread pool policy.=0A=
#=0A=
# Valid values =3D (n >=3D 1) =0A=
#=0A=
threadPerConnectionUpperLimit =3D 10000=0A=
=0A=
########################################################################=
####=0A=
# threadPerConnectionLowerLimit=0A=
#=0A=
# If the one thread per connection was in effect and was switched=0A=
# off because threadPerConnectionUpperLimit has been exceeded=0A=
# previously, this number tells when the policy should be restored=0A=
# when the number of connections drop.=0A=
#=0A=
# Valid values =3D (n >=3D 1 && n < threadPerConnectionUpperLimit) =
=0A=
#=0A=
threadPerConnectionLowerLimit =3D 9000=0A=
=0A=
########################################################################=
####=0A=
# threadPoolWatchConnection=0A=
#=0A=
# 1 means that after dispatching an upcall in thread pool mode, =
the=0A=
# thread should watch the connection for a short time before=0A=
# returning to the pool. This leads to less thread switching for=0A=
# series of calls from a single client, but is less fair if there=0A=
# are concurrent clients.=0A=
=0A=
threadPoolWatchConnection =3D 1=0A=
=0A=
########################################################################=
####=0A=
# acceptBiDirectionalGIOP=0A=
#=0A=
# Applies to the server side. Set to 1 to indicate that the=0A=
# ORB may choose to accept a client's offer to use bidirectional=0A=
# GIOP calls on a connection. Set to 0 means the ORB should=0A=
# never accept any bidirectional offer and should stick to normal=0A=
# GIOP.=0A=
#=0A=
# Valid values =3D 0 or 1=0A=
#=0A=
acceptBiDirectionalGIOP =3D 0=0A=
=0A=
########################################################################=
####=0A=
# unixTransportDirectory=0A=
#=0A=
# Applies to the server side. Determine the directory in which=0A=
# the unix domain socket is to be created.=0A=
#=0A=
# Valid values =3D a valid pathname for a directory=0A=
#=0A=
unixTransportDirectory =3D /tmp/omni-%u=0A=
# %u is expanded into user name.=0A=
=0A=
########################################################################=
####=0A=
# unixTransportPermission=0A=
#=0A=
# Applies to the server side. Determine the permission mode bits=0A=
# the unix domain socket is set to.=0A=
#=0A=
# Valid values =3D unix permission mode bits in octal radix (e.g. =
0755)=0A=
#=0A=
unixTransportPermission =3D 0777=0A=
=0A=
########################################################################=
####=0A=
# supportCurrent=0A=
#=0A=
# If the value of this variable is TRUE, per-thread information is=0A=
# made available through the Current interfaces, e.g.=0A=
# PortableServer::Current. If you do not need this information, =
you=0A=
# can set the value to 0, resulting in a small performance=0A=
# improvement.=0A=
#=0A=
supportCurrent =3D 1=0A=
=0A=
########################################################################=
####=0A=
# objectTableSize=0A=
#=0A=
# Hash table size of the Active Object Map. If this is zero, the =
ORB=0A=
# uses a dynamically resized open hash table. This is normally the =
=0A=
# best option, but it leads to less predictable performance since =
=0A=
# any operation which adds or removes a table entry may trigger a =
=0A=
# resize. If you set this to a non-zero value, the hash table has =
=0A=
# the specified number of entries, and is never resized. Note that =
=0A=
# the hash table is open, so this does not limit the number of =
=0A=
# active objects, just how efficiently they can be located.=0A=
#=0A=
# Valid values =3D (n >=3D 0)=0A=
# 0 --> use a dynamically resized table.=0A=
#=0A=
objectTableSize =3D 0=0A=
=0A=
########################################################################=
####=0A=
# poaHoldRequestTimeout=0A=
#=0A=
# This variable can be used to set a time-out for calls being held=0A=
# in a POA which is in the HOLDING state. It gives the time in=0A=
# milliseconds after which a TRANSIENT exception will be thrown if =
the=0A=
# POA is not transitioned to a different state.=0A=
#=0A=
# Valid values =3D (n >=3D 0 in milliseconds) =0A=
# 0 --> no time-out.=0A=
#=0A=
poaHoldRequestTimeout =3D 0=0A=
=0A=
########################################################################=
####=0A=
# supportBootstrapAgent=0A=
#=0A=
# Applies to the server side. 1 means enable the support for Sun's=0A=
# bootstrap agent protocol. This enables interoperability between =
omniORB=0A=
# servers and Sun's javaIDL clients. When this option is enabled, an=0A=
# omniORB server will respond to a bootstrap agent request.=0A=
supportBootstrapAgent =3D 0=0A=
------_=_NextPart_000_01C2F9E9.FBAA66A0--