J
Jan Jonasen
(recently sent to openorb-users and comp.lang.java.corba, but no reply)
Hello,
I'm having an issue with the speed of communication between client and
server with the following setup:
OpenORB 1.3.1
Client: Java client running on Mac OS 10.3.3, JDK 1.4.2_04. Not in the
local DNS nor servers host file.
Server: Windows 2000 server, JDK 1.4.2_02. This is in the local DNS.
Nameservice started with the following parameters:
java -Dorg.omg.CORBA.ORBClass=org.openorb.CORBA.ORB
-Dorg.omg.CORBA.ORBSingletonClass=org.openorb.CORBA.ORBSingleton
-Diiop.publishIP=true org.openorb.tns.Server -ORBPort=14100 -printIOR
So far it seems it's the server having issues communicating back to the
client, because adding the client to either DNS or the servers host file
makes it run just fine.
As you can see above I've tried utillizing the iiop.publishIP setting,
besides as above it's also set to true in default.xml, same has been
done on the client. I've also tried setting it to false for all
components because of reading about a bug causing it to have revers
meaning. Having both client and server printing their IOR and parsing
this with an omniorb app, suggests these are indeed including IPs rather
than hostnames.
It should be mentioned running the same client in a pure Windows
environment acts as if the client was in DNS, I suppose Windows resolves
the names internally by WINS or similiar.
1. How can I determin with a 100% certainty all communication is done by
IPs?
2. Where do I look for the problem server side or on the client?
3. Is there some (other) way to force the IP only communication?
4. Since the communication eventually takes place, how can this be, does
the server end up broadcasting?
The problem looks very similiar to this:
http://sourceforge.net/mailarchive/message.php?msg_id=3785943 yet as
mentioned the iiop.publishIP doesn't seem to do the job.
Thanks in advance and best regards
Jan Oksfeldt Jonasen
Hello,
I'm having an issue with the speed of communication between client and
server with the following setup:
OpenORB 1.3.1
Client: Java client running on Mac OS 10.3.3, JDK 1.4.2_04. Not in the
local DNS nor servers host file.
Server: Windows 2000 server, JDK 1.4.2_02. This is in the local DNS.
Nameservice started with the following parameters:
java -Dorg.omg.CORBA.ORBClass=org.openorb.CORBA.ORB
-Dorg.omg.CORBA.ORBSingletonClass=org.openorb.CORBA.ORBSingleton
-Diiop.publishIP=true org.openorb.tns.Server -ORBPort=14100 -printIOR
So far it seems it's the server having issues communicating back to the
client, because adding the client to either DNS or the servers host file
makes it run just fine.
As you can see above I've tried utillizing the iiop.publishIP setting,
besides as above it's also set to true in default.xml, same has been
done on the client. I've also tried setting it to false for all
components because of reading about a bug causing it to have revers
meaning. Having both client and server printing their IOR and parsing
this with an omniorb app, suggests these are indeed including IPs rather
than hostnames.
It should be mentioned running the same client in a pure Windows
environment acts as if the client was in DNS, I suppose Windows resolves
the names internally by WINS or similiar.
1. How can I determin with a 100% certainty all communication is done by
IPs?
2. Where do I look for the problem server side or on the client?
3. Is there some (other) way to force the IP only communication?
4. Since the communication eventually takes place, how can this be, does
the server end up broadcasting?
The problem looks very similiar to this:
http://sourceforge.net/mailarchive/message.php?msg_id=3785943 yet as
mentioned the iiop.publishIP doesn't seem to do the job.
Thanks in advance and best regards
Jan Oksfeldt Jonasen