<?xml version="1.0" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.jacorb.org/bugzilla/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.2"
          urlbase="https://www.jacorb.org/bugzilla/"
          
          maintainer="jacorb@goots.org"
>

    <bug>
          <bug_id>425</bug_id>
          
          <creation_ts>2003-12-04 17:58:39 +0000</creation_ts>
          <short_desc>Improper use of ERROR message for NON-ERROR</short_desc>
          <delta_ts>2006-05-09 16:36:25 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>JacORB</product>
          <component>POA</component>
          <version>2.0 beta3</version>
          <rep_platform>Other</rep_platform>
          <op_sys>AIX</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>378</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>john.seltzer</reporter>
          <assigned_to name="Gerald Brose">gerald.brose</assigned_to>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>897</commentid>
    <comment_count>0</comment_count>
    <who name="">john.seltzer</who>
    <bug_when>2003-12-04 17:58:39 +0000</bug_when>
    <thetext>org.jacorb.poa.POA._getChildPOA seems to make an assumption that any 
application writer will only have ONE java corba process PER MACHINE.  It logs 
the following type of exception when you try to connect to ANOTHER java corba 
process with a DIFFERENT POA name on the SAME machine:
[jacorb] ERROR : org.omg.CORBA.OBJECT_NOT_EXIST: no adapter activator exists 
for BackupFileReadServiceImplPOA
Not only that, but it prints a long stack dump on every attempt to connect to 
the other jvm on the SAME machine, REGARDLESS of whether that connection can or 
can&apos;t be made.  (Stack trace shown at end of bug description).
This is on a _non_exist call.  Although _non_exist will return me either true 
or false, depending on whether the object is really up or not, this 
excessive/wrong ERROR logging is filling up our own error log file with 
extraneous, NON-ERRORS.
*** Although I know that there is a facility to redirect jacorb errors to 
jacORB&apos;s own log file, I really don&apos;t want this.  I want the jacorb errors 
interspersed with our own errors so we can see the connection between what we 
were doing at the time and what caused jacorb to generate errors.
Here is a typical stack trace, of which we have hundreds generated every few 
minutes:  (There is more, but I&apos;ve only printed what is relevant:
[NeMoWFault]:[jacorb] ERROR : org.omg.CORBA.OBJECT_NOT_EXIST: no adapter 
activator exists for BackupFileReadServiceImplPOA
12/04 10:44:13:ERR:[NeMoWFault]:	at org.jacorb.poa.POA._getChildPOA
(Unknown Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at org.jacorb.orb.ORB.findPOA(Unknown 
Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at org.jacorb.orb.Delegate.resolvePOA
(Unknown Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at 
org.jacorb.orb.Delegate.is_really_local(Unknown Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at org.jacorb.orb.Delegate.non_existent
(Unknown Source)
12/04 10:44:13:ERR:[NeMoWFault]:	at 
org.omg.CORBA.portable.ObjectImpl._non_existent(Unknown Source)

***** Please note that BackupFileReadServiceImplPOA is what we&apos;re trying to 
connect to.  However, the process that is trying to make the connect to 
BackupFileReadServiceImplPOA is NeMoWFaultImplPOA, which is a different named 
POA.
**** This error will be dumped regardless of whether 
BackupFileReadServiceImplPOA is up or not.  IN this case, it WAS up.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>906</commentid>
    <comment_count>1</comment_count>
      <attachid>49</attachid>
    <who name="">john.seltzer</who>
    <bug_when>2003-12-15 18:44:06 +0000</bug_when>
    <thetext>Created attachment 49
Willing to lower priority to P3</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1756</commentid>
    <comment_count>2</comment_count>
    <who name="Alphonse Bendt">bendt</who>
    <bug_when>2006-05-09 16:36:25 +0000</bug_when>
    <thetext>

*** This bug has been marked as a duplicate of 378 ***</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>49</attachid>
            <date>2003-12-15 18:44:06 +0000</date>
            <delta_ts>2003-12-15 18:44:06 +0000</delta_ts>
            <desc>Willing to lower priority to P3</desc>
            <filename>425Attachment.txt</filename>
            <type>text/plain</type>
            <size>612</size>
            <attacher>john.seltzer</attacher>
            
              <data encoding="base64">SSdtIHdpbGxpbmcgdG8gaGF2ZSB0aGlzIHBhdGNoIGxvd2VyZWQgdG8gYSBQMy4gIEkndmUgZGlz
Y292ZXJlZCB0aGF0IGJ5DQp1c2luZyBqYWNvcmIuaW1wbG5hbWUsIEkgY2FuIHByZXZlbnQgYWxs
IG9mIHRoaXMgZXhjZXNzIHN0YWNrIHRyYWNlIGR1bXBpbmcNCmZyb20gc2hvd2luZyB1cC4gIA0K
DQpUbyBtZSwgaXQncyBhIHdvcmthcm91bmQgYmVjYXVzZSBJJ20gbm90IHVzaW5nIGltcGxlbWVu
dGF0aW9uDQpyZXBvc2l0b3J5LiAgT3VyIGFwcGxpY2F0aW9uIHdhcyBub3Qgb3JpZ2luYWxseSBk
ZXNpZ2VkIHRvIHVzZSB0aGUgSW1yLCBhbmQNCndlIGRvbid0IHBsYW4gb24gcmV3cml0aW5nIGl0
J3MgaGFuZHNoYWtpbmcgdG8gZW5hYmxlIGl0IHRvIHdvcmsgaW4gdGhpcw0KZW52aXJvbm1lbnQu
DQoNCkphY09SQiBpcyBtYWtpbmcgYW4gYXNzdW1wdGlvbiB0aGF0IGlmIHlvdSBoYXZlIG11bHRp
cGxlIFZNcyBydW5uaW5nIENvcmJhDQpvbiB0aGUgc2FtZSBtYWNoaW5lLCB0aGVuIHlvdSBzaG91
bGQgYmUgdXNpbmcgSW1SLiAgSSBkb24ndCB0aGluayB0aGUgY29kZQ0Kc2hvdWxkIHJlcXVpcmUg
dGhpcy4gIFJhdGhlciwgaXQgc2hvdWxkIG9ubHkgZW5hYmxlIGl0Lg0K
</data>

          </attachment>
      

    </bug>

</bugzilla>