[dhi-servers] NameServer communication problems
Sue Schoch
sue at iris.washington.edu
Mon Aug 20 11:21:58 PDT 2007
Hi Chuck,
We've reverted back to the old pathing. As Rob said, we are working
on other solutions.
Sue
On Aug 20, 2007, at 11:11 AM, Charles Ammon wrote:
> Hi,
>
> I will change the codes for the future - Victor has already
> modified his orb. I am worried about people who are looking at
> blank screens right now and won't know to update. The clients
> worked for more than a year with the UTF-8 encoding.
>
> I thought that IRIS had hopes a number of Asian countries would
> establish data sharing with this technology. I would think that
> their OS's would be set up with something more modern than ASCII.
>
> It would be great if you can register a UTF converter with the server.
>
> Chuck
> ======================================================================
> Charles J. Ammon, Department of Geosciences
> Penn State University / 440 Deike Bldg / University Park, PA 16802
> VOICE: (814) 865 2310 / FAXES: (814) 863 7823 or (814) 863 8724
> http://eqseis.geosc.psu.edu/~cammon/
> http://www.personal.psu.edu/faculty/c/j/cja12/
>
> On Aug 20, 2007, at 10:12 AM, Sue Schoch wrote:
>
>> Hi Chuck,
>>
>> We did change the classpath for the nameserver as we were getting
>> some errors that was causing the nameserver to abort. Our change
>> seems to have fixed the problem. What we did was ensure that the
>> orbacus libraries were called before the sun Corba libraries.
>> This is likely the cause of your problems. This has cured all of
>> our internal error problems with the nameserver. I am hesitant to
>> revert back to a known problem. This is not out of the question
>> of course. Perhaps we could revert back until you can add the
>> modification below? I will do some research to see if there is
>> anything that can be done from the server side to allow multiple
>> char sets.
>>
>> Sue
>>
>> On Aug 18, 2007, at 5:30 PM, Charles Ammon wrote:
>>
>>> Hi,
>>>
>>> I contacted the author of ADORB (Victor Ananiev) and he seems to
>>> have
>>> figured out what is going on. The issue is the character code set
>>> translation (good call Philip).
>>>
>>> If Victor is right, it appears that the server restart was not
>>> exactly
>>> what was running before Wednesday. Please see the response from him
>>> below. He makes several suggestions for me to work around the issue,
>>> but if possible, the easiest for the group of people running my
>>> clients would be to make the adjustment at the server to be the same
>>> as it was before restart on Wednesday.
>>>
>>> Would this be possible? If not, I can start on the workarounds.
>>>
>>> Chuck
>>>
>>> ---------- Forwarded message ----------
>>> From: Victor Ananiev <v_ananiev at mac.com>
>>> Date: Aug 18, 2007 12:51 PM
>>> Subject: Re: ADORB stopped talking to another orb
>>> To: Charles Ammon <cammon at geosc.psu.edu>
>>>
>>>
>>> Hi Charles,
>>>
>>> The problem is in the character codeset negotiation. For some reason
>>> they don't allow UTF8 (CORBA code 0x0501001).
>>> It connects if I send ASCII (0x00010020) or no codesets at all.
>>> Apparently they have changed something in the configuration or,
>>> according to their log, forgot to register a converter for UTF8.
>>>
>>> For the time being you can change the value for native char code in
>>> the file IDLTaggedComponent.m
>>> //static int _nativeCharCode = 0x05010001;
>>> static int _nativeCharCode = 0x00010020;
>>>
>>> I don't know how this can affect the rest of your application
>>> though.
>>>
>>> I will look for a better solution meanwhile.
>>> The other way is to remove codesets from the service context using
>>> interceptors that I have added in the version 1.5.
>>>
>>> Regards,
>>> Victor Ananiev
>>>
>>>
>>> On Aug 18, 2007, at 9:04 AM, Charles Ammon wrote:
>>>
>>> Hi,
>>>
>>> I am sorry to bother you. I am an ADORB user and you helped me
>>> figure
>>> some things out about using CORBA a long time ago. Since then, I
>>> have
>>> been developing and using ADORB to talk with a seismic data server -
>>> and all has been running well until this week. Now I can't
>>> connect to
>>> the nameserver I have been talking to for more than a year. They did
>>> restart the machine running the server, but they don't think that
>>> anything has changed - it must have. I have codes that I have not
>>> recompiled that used to work, but don't any more...
>>>
>>> I downloaded the most recent version of IDLBrowser and have been
>>> trying to connect to the server, but all I get is a time out. I
>>> appear
>>> to be the only one who is having problems (all others use java-based
>>> orbs to communicate).
>>>
>>> The server address is 128.95.166.129:6371. Using IDLBrowser, I have
>>> tried talking to the server with GIOP 1.0, 1.1, and 1.2 (1.2 used to
>>> work). All time out.
>>>
>>> I have been in touch with the server administrators and this is the
>>> error that they see when I try to connect:
>>>
>>> id: iiop
>>> local address: 192.168.167.2:6371
>>> remote address: 128.118.174.210:49185 ]
>>> com.ooc.OB.AssertionFailed: ORBacus encountered an internal error
>>> at com.ooc.OB.Assert._OB_assert(Assert.java:19)
>>> at com.ooc.OB.CodeSetDatabase.getConverter
>>> (CodeSetDatabase.java:230)
>>> at com.ooc.OB.GIOPServerWorker.getCodeConverters
>>> (GIOPServerWorker.java:1
>>> 00)
>>> at com.ooc.OB.GIOPServerWorker.executeRequest
>>> (GIOPServerWorker.java:441)
>>> at com.ooc.OB.GIOPServerWorker.execute
>>> (GIOPServerWorker.java:314)
>>> at com.ooc.OB.GIOPServerWorkerThreaded.receiverRun
>>> (GIOPServerWorkerThrea
>>> ded.java:521)
>>> at com.ooc.OB.GIOPServerWorkerThreaded$ReceiverThread.run
>>> (GIOPServerWork
>>> erThreaded.java:70)
>>> com.ooc.OB.AssertionFailed: ORBacus encountered an internal error
>>> at com.ooc.OB.Assert._OB_assert(Assert.java:19)
>>> at com.ooc.OB.GIOPServerWorkerThreaded$ReceiverThread.run
>>> (GIOPServerWork
>>> erThreaded.java:75)
>>>
>>> If you have any ideas, can you please let me know?
>>>
>>> Thank you,
>>> Chuck Ammon
>>> ====================================================================
>>> ==
>>> Charles J. Ammon, Department of Geosciences
>>> Penn State University / 440 Deike Bldg / University Park, PA 16802
>>> VOICE: (814) 865 2310 / FAXES: (814) 863 7823 or (814) 863 8724
>>> http://eqseis.geosc.psu.edu/~cammon/
>>> http://www.personal.psu.edu/faculty/c/j/cja12/
>>>
>>>
>>>
>>>
>>> --
>>> ====================================================================
>>> ==
>>> Charles J. Ammon, Department of Geosciences
>>> Penn State University / 440 Deike Bldg / University Park, PA 16802
>>> VOICE: (814) 865 2310 / FAXES: (814) 863 7823 or (814) 863 8724
>>> http://eqseis.geosc.psu.edu/~cammon/
>>> http://www.personal.psu.edu/faculty/c/j/cja12/
>>> _______________________________________________
>>> dhi-servers mailing list
>>> dhi-servers at iris.washington.edu
>>> http://www.iris.washington.edu/mailman/listinfo/dhi-servers
>>
>>
>
> _______________________________________________
> dhi-servers mailing list
> dhi-servers at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/dhi-servers
More information about the dhi-servers
mailing list