f



RE: [tao-users] Strange warning when updating from tao 1.4.4 to 1.4.8 #2

Hi,

> I do use PortableServer for POA, my config.h follows. But 
> what I don't 
> understand is how the application works ?? The TAO_PI.dll is 
> not loaded 
> because it's not available on the system, but even after logging the 
> warnings, the application runs OK. So why TAO/PortableServer tries to 
> load a DLL it doesn't need to run ?

We try to load the DLL's when we could use them, if they are not found, then
just certain functionality will not be available runtime, but if you don't
use them, then you don't get problems.

Johnny


0
Johnny
1/6/2006 9:48:25 PM
comp.soft-sys.ace 20326 articles. 1 followers. marlow.andrew (167) is leader. Post Follow

0 Replies
646 Views

Similar Articles

[PageSpeed] 54

Reply:

Similar Artilces:

RE: [tao-users] Strange warning when updating from tao 1.4.4 to 1.4.8
Hi, Please always use the PRF form. Some of the TAO libraries itself use ORBInitializers and PI (for example PortableServer and Messaging). Because of that it can be that the libraries are searched. If you don't need portable interceptors, the best is to disable that then during compilation, that will reduce footprint and improve performance. Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl > -----Original Message----- > From: owner-tao-users@cse.wustl.edu > [mailto:owner-tao-users@cse.wustl.edu] On Behalf Of Olivier Brunet > Sent: woensdag 4 januari 2006 23:32 > To: tao-users@cs.wustl.edu > Subject: [tao-users] Strange warning when updating from tao > 1.4.4 to 1.4.8 > > > Hi all, > > I'm using TAO 1.4.8 on WinXP Pro SP2 32 Bits using VC7.1. > > I updated my build environement from 1.4.4 to 1.4.8. This has been > without any bother, but now when I start my app, I have this warning: > > 3544 -- 20051224-00:00:40 3 ACE_DLL::open failed for TAO_PI: Error: > check log for details. > > 3544 -- 20051224-00:00:40 3 Unable to find service: > ORBInitializer_Registry > > > Aa far as I know, I'm not using portable interceptors, so why > TAO tries > to load this PI.dll ?? > > Here is the initialization parameters I use (unchanged since > the 1...

[tao-users] Strange warning when updating from tao 1.4.4 to 1.4.8
Hi all, I'm using TAO 1.4.8 on WinXP Pro SP2 32 Bits using VC7.1. I updated my build environement from 1.4.4 to 1.4.8. This has been without any bother, but now when I start my app, I have this warning: 3544 -- 20051224-00:00:40 3 ACE_DLL::open failed for TAO_PI: Error: check log for details. 3544 -- 20051224-00:00:40 3 Unable to find service: ORBInitializer_Registry Aa far as I know, I'm not using portable interceptors, so why TAO tries to load this PI.dll ?? Here is the initialization parameters I use (unchanged since the 1.4.4 build): // Setup UTF16 translator for Sun's JDK ORB const char *directive="static UTF16_BOM_Factory \"-forceBE\" "; // Setup ORB const char *orbcfg=" \ dynamic Advanced_Resource_Factory Service_Object * TAO_Strategies:_make_TAO_Advanced_Resource_Factory () \"-ORBInputCDRAllocator null -ORBReactorMaskSignals 1 -ORBConnectionCacheLock null\" \ static Server_Strategy_Factory \"-ORBPOALock null -ORBAllowReactivationOfSystemids 0\" \ static Client_Strategy_Factory \"-ORBProfileLock null -ORBClientConnectionHandler RW -ORBTransportMuxStrategy EXCLUSIVE \""; if (ACE_Service_Config::process_directive (directive) != 0) ACE_ERROR ((LM_ERROR, ACE_TEXT ("ACECorbaTask::svc() - ") ACE_TEXT ("process_directive() failed for:\n") ACE_TEXT ("\"%s\""), directive)); if (ACE_Service_Config::process...

[tao-users] Re: tao naming service build problem (ACE-5.4.1+TAO-1.4.1)
Hi, This problem is fixed in the x.4.3 release you can obtain from http://deuce.doc.wustl.edu/Download.html Regards, Johnny Willemsen Remedy IT Leeghwaterstraat 25 2811 DT Reeuwijk The Netherlands www.theaceorb.nl / www.remedy.nl "serg" <serg@sigma.icmp.lviv.ua> wrote in message news:<opslmf7qgcpq42w9@shreck.lis.ua>... > Sorry but i haven't access to comp.object.corba.tao so i post the question > here. > > During build of orb services the following error occured: > > [...skipped...] > ... > make[3]: Leaving directory `/tao/tao/orbsvcs/orbsvcs' > make -f Makefile.CosNaming all > make[3]: Entering directory `/tao/tao/orbsvcs/orbsvcs' > > Makefile: /tao/tao/orbsvcs/orbsvcs/Makefile.CosNaming > > rm -f .shobj//libTAO_CosNaming.dll.def.old > .shobj//libTAO_CosNaming.dll.def; dll > tool --export-all --output-def .shobj//libTAO_CosNaming.dll.def --dllname > libTAO > _CosNaming.dll .shobj/Naming/Naming_Context_Interface.o > .shobj/Naming/Hash_Namin > g_Context.o .shobj/Naming/Persistent_Naming_Context.o > .shobj/Naming/Transient_Na > ming_Context.o .shobj/Naming/Persistent_Entries.o .shobj/Naming/Entries.o > .shobj > /Naming/Persistent_Context_Index.o .shobj/Naming/Naming_Utils.o > .shobj/Naming/Na > ming_Loader.o .shobj/Naming/Storable.o > .shobj/Naming/Storable_Naming_Context.o . > shobj/Naming/S...

[tao-users] Use of TAO_OutputCDR and ACE_Message_Block in CORBA::Any from TAO 1.4.1|ACE 5.4.1 to TAO2.2.0|ACE 6.2.0
This is a multipart message in MIME format. ------=_NextPart_000_00BF_01CEA8D4.9E005C80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable TAO VERSION: 2.2.0 ACE VERSION: 6.2.0 =20 HOST MACHINE and OPERATING SYSTEM: x86_64 and Red Hat - Linux 2.6.18-194.26.1.el5 =20 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: =20 COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc (GCC) 4.8.1 =20 THE $ACE_ROOT/ace/config.h FILE: config-linux.h =20 THE $ACE_ROOT/include/makeinclude/platform_macros.GNU FILE: platform_linux.GNU =20 CONTENTS OF $ACE_ROOT/bin/MakeProjectCreator/config/default.features (used by MPC when you generate your own makefiles): =20 AREA/CLASS/EXAMPLE AFFECTED: TAO_OutputCDR and ACE_Message_Block. =20 DOES THE PROBLEM AFFECT: EXECUTION. My application is affected. =20 SYNOPSIS: The code that extract data from CORBA::Any using TAO_OutputCDR and ACE_Message_Block for user defined types works properly in the old platform (TAO 1.4.1|ACE 5.4.1), but not in the new one(ACE 6.2.0). =20 DESCRIPTION: The code in the =93REPEAT BY=94 section works fine in the old platform = for user defined types, that is, the TAO_OutputCDR and ACE_Message_Block objects have the same length, but in the new platform th...

ACE 5.4.2 + TAO 1.4.2 client, ORBacus 4.1.2 NameService, and JACOrb 1.4.1 servants
Hi everyone, Background: ----------- I'm very new to CORBA, ACE & TAO. I'm trying to integrate with a 3rd party system which exposes a CORBA object model to clients. This system is composed of JACOrb 1.4.1 servers registering with an ORBacus 4.1.2 NameService. We've got existing software that uses ACE 5.4.2, and the 3rd party documentation mentions that people have used TAO (no version specified) previously to integrate with their system, so I'm trying out TAO 1.4.2 as a natural solution to the problem. Environment Specifics: ---------------------- - ACE 5.4.2 + TAO 1.4.2 clients - running on a variant of RedHat Enterprise Linux 4.x (x86 platform) - compiled with gcc-c++-3.4.3-22.1 - ORBacus 4.1.2 NameService, and JACorb 1.4.1 servants (the 3rd Party stuff) - running on SunOS 5.9 What I'm trying to do: ---------------------- To get started, I'm trying to create a simple "hi3rdParty" app which acquires a reference to the remote ORBacus NameService so that I can then get at the other services. Here's the code I'm using: try { // ------ begin common CORBA init -------- // First initialize the ORB - that will remove some arguments... // NOTE: we're gonna try and use "-ORBInitRef NameService=corbaloc:iiop:theServer:5000/NameService" // to find the naming service. CORBA::ORB_var orb = CORBA::ORB_init(argc, argv, "&quo...

[ace-users] Re: [tao-support] Has ACE 5.4.4/TAO 1.4.4 been built with gcc 4.0.0 yet
Hi Robert, > When building ACE 5.4.4/TAO 1.4.4 using gcc 4.0.0 under fedora core > 4 test 2 on an x86 platform I get a lot of errors mainly to do with > template instantiations. Has anyone successfully build TAO/ACE using > the latest gcc ? We just added GCC 4.0.0 support to ACE+TAO recently. The forthcoming x.4.5 beta should work nicely with GCC 4.0.0. We hope to have this available very shortly (there's just one remaining snag with typecodes that should be fixed in the next day or so). If you'd like to give things a try before we release x.4.5 please download the contents of ACE+TAO from our CVS repo at http://cvs.doc.wustl.edu/ and see if it works for you on your platform. If not, please let us know and we'll try to make sure that it's working before we put out the beta release. Thanks, Doug I've tried the CVS version on macosx 10.4, with gcc4.0 and still got the same intantiation problem. On 5/9/05, Douglas C. Schmidt <schmidt@cs.wustl.edu> wrote: > > Hi Robert, > > > When building ACE 5.4.4/TAO 1.4.4 using gcc 4.0.0 under fedora core > > 4 test 2 on an x86 platform I get a lot of errors mainly to do with > > template instantiations. Has anyone successfully build TAO/ACE using > > the latest gcc ? > > We just added GCC 4.0.0 support to ACE+TAO recently. The forthcoming > x.4.5 beta should work nicely with GCC 4.0.0. We hope to ha...

RE: [tao-users] Re: [ace-users] Re: Announcing the release of the new beta (ACE-5.4.10, TAO-1.4.10 and CIAO-0.4.10)
Hi, > > >> We encourage you to download the new beta, use it with your > > >> applications, and let us know soon if you encounter any problems > > >> since we plan to cut the x.5 release by February 28th. > > > > As per Wallace's comments, we have an aggressive schedule > for the x.5 > > release to meet the needs of some major sponsors. If > people can give > > x.4.10 a "test drive" in the next couple of days and report problems > > they encounter we'll try to ensure that we fix any > showstoppers before > > According to bugzilla bug 2323 is not fixed yet. > > http://deuce.doc.wustl.edu/bugzilla/show_bug.cgi?id=2323 > > For us it is a show stopper. We use the OCI version which does not > have problems related to this bug but it would be nice to be able to > use the latest version with more fixes. FYI, the reason that this test now fails is because Ossama added several new test cases which wheren't in the test in the past, this uncovered some bugs which according to our information where already there a long time. Johnny "Johnny Willemsen" <jwillemsen@remedy.nl> writes: > > > >> We encourage you to download the new beta, use it with your > > > >> applications, and let us know soon if you encounter any problems > > > >> sinc...

[ace-users] Re: a little bug of ACE-5.4.1+TAO-1.4.1+CIAO-0.4.1.tar.gz
Hi Adam, Please upgrade to ACE+TAO x.4.8, which you can download from http://deuce.doc.wustl.edu/Download.html under the heading "latest beta kit". The DOC groups at Washington University, UC Irvine, and Vanderbilt University only provide "best effort" support for non-sponsors for the latest beta kit, as described in http://www.cs.wustl.edu/~schmidt/ACE_wrappers/docs/ACE-bug-process.html Thus, if you need more "predictable" help for ACE 5.4.1, I recommend that you check out http://www.cs.wustl.edu/~schmidt/commercial-support.html for a list of companies that will provide you with ACE+TAO commercial support. Thanks, Doug >> When I compile this version, it prompts me the following errors that >> /*------ >> gmake[6]: *** No rule to make target `Client_Request_Interceptor.cpp', >> needed by `.obj/Client_Request_Interceptor.o'. Stop. >> ------*/ >> >> Then I find there is something wrong about the directory: >> /export/home/adam/ace.5.4.1.cc.64/TAO/tests/Portable_Interceptors/Request_Interceptor_Flow >> There are two files whose file names suffix are very strange. >> 1. Client_Request_Interceptor.cp >> 2. Server_Request_Interceptor.cp >> After I rename them from .cp to .cpp >> >> I wonder if this is a bug or some thing I configure wrong? >> >> Regards, >> Adam >> -...

[ace-bugs] Re: [tao-users] JDK 1.4.2 client with TAO 1.4 server
Hi Amir, Thanks for using the PRF. >> TAO VERSION: 1.4 >> ACE VERSION: 5.4 >> HOST MACHINE and OPERATING SYSTEM: >> Linux Red Hat 8 >> TARGET MACHINE and OPERATING SYSTEM, if different from HOST: >> Intel PC Windows 2000 >> COMPILER NAME AND VERSION (AND PATCHLEVEL): >> gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) >> javac (sun JDK 1.4.2) >> AREA/CLASS/EXAMPLE AFFECTED: >> DOES THE PROBLEM AFFECT: >> COMPILATION? >> no >> LINKING? >> no >> EXECUTION? >> yes ...

RE: [ace-users] segfault on linux x86-64 with ACE/TAO 5.4.4/1.4.4 #2
Hi, > Thanks for the reply. > The reason why I posted the stacktrace is that I have > currently no clue how to > reproduce a small testcase. But I will keep trying. > > I had the hope that someone familiar with ACE_Malloc_T<> > could shed light on > this subject. As I said the curious thing is that it works > with 32bit and > fails with 64bit. The only thing that I can imagine off is that somewhere a 64bit pointer is by accident handled as 32bit. Johnny ...

[tao-users] Announcing the release of the new beta (ACE-5.4.8, TAO-1.4.8 and CIAO-0.4.8)
[The following is on behalf of the PrismTech build-czars!] Hi, We are pleased to announce a new beta of ACE-5.4.8, TAO-1.4.8, and CIAO-0.4.8. We are currently working hard on the long-awaited x.5 release, which is slated to appear in early 2006. We therefore wanted to get this new beta out to fix several important bugs reported by our users, which we greatly appreciate as always. We've added a number of sub-setting improvements that reduce the static/dynamic footprint of ACE+TAO significantly (www.dre.vanderbilt.edu/Stats has all the details). We've also finally added support for Real-time CCM to CIAO and DAnCE. This beta is contains the results of our major footprint reduction effort that started in the summer of 2004. Between August 1st 2004 and October 14th 2005 the footprint reduction for the ORB_Init application has been 20%. Dependent on the parts of TAO you use the reduction can even be more. This reduction is inclusive all the extensions that have been made to TAO the last year. Interested users should check out http://www.dre.vanderbilt.edu/Stats/ for more details. Note that the footprint has increased slightly again due to emulated exceptions having been disabled in favour of native C++ exceptions in all stats builds. We have deprecated support for emulated exceptions since there are no sponsors for this configuration. If you require emulated exceptions please contact one of the companies listed in http://w...

RE: [tao-users] RE: [ace-users] XML service configuration no longer works with ACE/TAO 5.4.5/1.4.5
Hi, > > Hi Lothar > > > > > � � ACE VERSION: 5.4.5 > > > > Thanks for using the PRF form. Could you try to find the > problem and send > > us patches to fix this? > > > > Regards, > > > > Johnny Willemsen > > I have no problem committing some time to the problem. I do > however know as > much as nothing about the ACE XML parser and it's recent > changes. It seems to > me that (some) of the recent changes might have caused the > test failures. So > if someone working actively on ACEXML gives me directions I > am willing to > spend my time investigating the problem. I can't remember that work has been done the last months so I am also amazed things broke. Nobody is actively working on it, so I think there are not much directions at this moment. Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl On Wednesday 18 May 2005 11:01, Johnny Willemsen wrote: > Hi, > I can't remember that work has been done the last months so I am also > amazed things broke. Nobody is actively working on it, so I think there are > not much directions at this moment. Well, it did definiteley work with 5.4.4. So any changes that broke it must have been made between 5.4.4 and 5.4.5. I also read in the release email of 5.4.5 in the CIAO...

RE: [ace-users] segfault on linux x86-64 with ACE/TAO 5.4.4/1.4.4
Hi Lothar, Thanks for using the PRF form. It looks that one of the pointers to strcmp is zero, maybe that results in the crash. Could you post a small test app that reproduces the problem? Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl > ACE VERSION: 5.4.4 > > HOST MACHINE and OPERATING SYSTEM: > uname -a > Linux janus 2.6.11.4-20a-default #1 Wed Mar 23 21:52:37 UTC > 2005 x86_64 x86_64 > x86_64 GNU/Linux > > TARGET MACHINE and OPERATING SYSTEM, if different from HOST: > COMPILER NAME AND VERSION (AND PATCHLEVEL): > gcc-4.0.0 --version > gcc-4.0.0 (GCC) 4.0.0 > > CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to > a platform- > specific file, simply state which one]: > cat /opt2/linux/x86_64/ACE/1.4.4/ACE_wrappers/ace/config.h > #define ACE_HAS_XML_SVC_CONF > #include "ace/config-linux.h" > > CONTENTS OF > $ACE_ROOT/include/makeinclude/platform_macros.GNU (unless > this isn't used in this case, e.g., with Microsoft Visual C++): > cat > /opt2/linux/x86_64/ACE/1.4.4/ACE_wrappers/include/makeinclude/ > platform_macros.GNU > > # configure ACE/TAO for our use > > debug=1 > optimize=1 > exceptions=1 > threads=1 > inline=1 > rtti=1 > versioned_so=1 > interface_repo=1 > ssl=...

Re: [tao-users] ACE5.4.1+TAO1.4.1 compile fail under gcc3.4 #2
hello! i can not visit the cvs server for some limitation of here. does any web site provide cvs tar ball or just patch to 5.4.1? Or any one could send to me? Thanks very much! >From: Balachandran Natarajan <bala@cs.wustl.edu> >Reply-To: >To: yanyaqin97@mails.tsinghua.edu.cn >Subject: Re: [tao-users] ACE5.4.1+TAO1.4.1 compile fail under gcc3.4 > >Hi > > > ACE5.4.1+TAO1.4.1 compile fail under gcc3.4 > > Yes, a known issue. Ossama Othman hs been adding support in ACE+TAO > for gcc-3.4 with help from users like Oliver Kellog. Please try to > pull...

[ace-users] Announcing the release of the new beta (ACE-5.4.8, TAO-1.4.8 and CIAO-0.4.8)
[The following is on behalf of the PrismTech build-czars!] Hi, We are pleased to announce a new beta of ACE-5.4.8, TAO-1.4.8, and CIAO-0.4.8. We are currently working hard on the long-awaited x.5 release, which is slated to appear in early 2006. We therefore wanted to get this new beta out to fix several important bugs reported by our users, which we greatly appreciate as always. We've added a number of sub-setting improvements that reduce the static/dynamic footprint of ACE+TAO significantly (www.dre.vanderbilt.edu/Stats has all the details). We've also finally added support for Real-time CCM to CIAO and DAnCE. This beta is contains the results of our major footprint reduction effort that started in the summer of 2004. Between August 1st 2004 and October 14th 2005 the footprint reduction for the ORB_Init application has been 20%. Dependent on the parts of TAO you use the reduction can even be more. This reduction is inclusive all the extensions that have been made to TAO the last year. Interested users should check out http://www.dre.vanderbilt.edu/Stats/ for more details. Note that the footprint has increased slightly again due to emulated exceptions having been disabled in favour of native C++ exceptions in all stats builds. We have deprecated support for emulated exceptions since there are no sponsors for this configuration. If you require emulated exceptions please contact one of the companies listed in http://w...

Re: [tao-users] Problem with shmiop and large message size. TAO 1.4.2, 1.4.7,
Hi Nanbor, Can you please take a look at the question from Thaddeus Covert below and suggest a fix? Thaddeus, can you please explain the size of the buffer you're trying to pass? It's not in your posting below. Thanks, Doug In article <200512061457.45749.tcovert@tazznetworks.com> you write: >> New to CORBA and TAO. >> >> Problem: I have a program that works fine using iiop. Want to learn more about >> the pluggable protocols (ie colocation and shmiop). I've managed to figure >> out how to enable the shmiop and uiop. The uiop works fine, iiop works fine, >> but when I use shmiop my stress test fails with: >> >> FreeBSD 6.0, gcc 3.4.4, libACE 5.4.2, libTAO 1.4.2 >> >> TAO: (57262|134668288|SHMIOP_Transport.cpp|243) >> closing transport 11 after fault send_message () >> >> or >> Solaris 9, gcc 4.0.1, libACE 5.4.7, libTAO 1.4.7 >> >> TAO: (12580|1|Strategies/SHMIOP_Transport.cpp|238) closing transport 12 after >> fault send_message () >> : Not enough space >> >> The program works up till this point. The buffer size that is trying to be >> passed is: >> This is for the solaris 9 trace: >> >> Dec 5 18:18:29.050 2005@<local_host>@12580@LM_DEBUG@bin/tsserver|TAO (12580| >> 1) - GIOP_Message_Base::dump_msg, send GIOP >> v1.2 msg, 2800...

Re: [tao-users] ACE 5.4.0 TAO 1.4 build problems in orbsvcs #2
Sorry, forgot the attachment. Makefile: /export/home/bcassan/ACE_wrappers/TAO/orbsvcs/orbsvcs/Makefile.RTKokyuEvent g++ -W -Wall -Wpointer-arith -pipe -O3 -D_REENTRANT -I/export/home/bcassan/ACE_wrappers -I/export/home/bcassan/ACE_wrappers/TAO -DACE_NDEBUG -DACE_USE_RCSID=0 -DACE_HAS_EXCEPTIONS -D__ACE_INLINE__ -I/export/home/bcassan/ACE_wrappers/TAO -I/export/home/bcassan/ACE_wrappers/TAO/orbsvcs -I/export/home/bcassan/ACE_wrappers/TAO/orbsvcs/orbsvcs/ESF -DTAO_RTKOKYUEVENT_BUILD_DLL -c -fPIC -o .shobj/EC_Kokyu_Filter.o Event/EC_Kokyu_Filter.cpp g++ -W -Wall -Wpointer-arith -pipe -O...

[tao-users] US ECCN and EU-ECCN for TAO 1.4.1 + ACE 5.4.1
This is a multi-part message in MIME format. ------_=_NextPart_001_01C8CB97.492A7E73 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, We are using TAO 1.4.1 + ACE 5.4.1 in one of our products, and are now = in the process of collecting the information=20 needed to export it to other countries. Can you tell me what the U.S. Export Control Classification Number(ECCN) = for TAO 1.4.1 + ACE 5.4.1 is,=20 and whether a license exception may be used for it? If you don't know the US ECCN, can you tell me whether any US citizens or people living in the U.S.A. have contributed code to TAO 1.4.1 + ACE = 5.4.1 ? In addition to the U.S. ECCN, there is also a German "ECCN", which is called the AL Number or EU-ECCN. Can you tell me what the AL or EU-ECCN = Number is forTAO 1.4.1 + ACE 5.4.1 ? To better understand the meaning of the U.S. ECCN, please check the following webpage: http://www.bis.doc.gov/Licensing/Do_I_NeedAnECCN.html Many thanks, J=F6rg Rockel _______________________________________ www.nokiasiemensnetworks.com <http://www.nokiasiemensnetworks.com/>=20 Nokia Networks GmbH Heltorfer Str.1 D-40472 D=FCsseldorf Germany Mobile: +49(0)151 5515 3554 Direct: +49 (0)151 5515 3554 Fax: +49 (0) 211 9412 3383 email: J=F6rg Rockel@nsn.com <mailto:joerg.rockel@nsn.com>=20 J=F6rg Rockel=20 Senior Software Design Engi...

[tao-users] Re: ACE+TAO+CIAO
Hi folks, It's been a long time (5 months) since we put out the x.4.2 ACE+TAO+CIAO beta, and the current x.4.3 beta contains many improvements, fixes, and new features. It would be great if you could put this through its paces and let us know what problems you find so we can fix them ASAP. We plan to release the x.4.4 beta fairly soon (i.e., within a month), so your thorough testing will greatly improve its stability and portabilty! Thanks very much, Doug >> Since this is the season of giving, we are happy to announce a new beta >> of ACE-5....

[tao-users] RE: [tao-bugs] Problem on the reconnecting tests (TAO 1.4.4) #2
Hi, It looks the notification service does a call back and after that things just stop. Maybe the is_a fails and then things end. Johnny > -----Original Message----- > From: Andr� Cruz [mailto:andre.cruz@meteo.pt] > Sent: woensdag 16 maart 2005 10:49 > To: Johnny Willemsen; tao-users@cs.wustl.edu > Subject: RE: [tao-bugs] Problem on the reconnecting tests (TAO 1.4.4) > > Hello. Thanks for the help. > > I've ran the test with the debug flag but I can't find > anything in this > big log. Well, I don't even know what to look for. :) > > Maybe someone can take a look at it? > > Thanks. > Andr� > > > [root@saf144 Reconnecting]# ./run_test-debug.pl -v > TEST SCRIPT: Starting Notify Service on port 9889 > TEST > SCRIPT: > /usr/local/ACE_wrappers/TAO/orbsvcs/Notify_Service/./Notify_Se > rvice -ORBDebugLevel 5 -NoNameSvc -Boot -ORBSvcConf > ns_st_topo.conf -IORoutput > /usr/local/ACE_wrappers1.4.4/TAO/orbsvcs/tests/Notify/Reconnec > ting/notify.ior -ORBEndpoint iiop://:9889 > /usr/local/ACE_wrappers/TAO/orbsvcs/Notify_Service/./Notify_Service > -ORBDebugLevel 5 -NoNameSvc -Boot -ORBSvcConf ns_st_topo.conf > -IORoutput > /usr/local/ACE_wrappers1.4.4/TAO/orbsvcs/tests/Notify/Reconnec > ting/notify.ior -ORBEndpoint iiop://:9889 in TAO_Properties > ctos 93793cc > (10037|3085984416) Standard_Event_Persistence: -verbose ...

[tao-users] RE: [ace-users] XML service configuration no longer works with ACE/TAO 5.4.5/1.4.5
Hi Lothar > � � ACE VERSION: 5.4.5 Thanks for using the PRF form. Could you try to find the problem and send us patches to fix this? Regards, Johnny Willemsen Remedy IT Postbus 101 2650 AC Berkel en Rodenrijs The Netherlands www.theaceorb.nl / www.remedy.nl > > � � HOST MACHINE and OPERATING SYSTEM: > uname -a > Linux janus 2.6.11.4-20a-default #1 Wed Mar 23 21:52:37 UTC > 2005 x86_64 x86_64 > x86_64 GNU/Linux > > � � TARGET MACHINE and OPERATING SYSTEM, if different from HOST: > � � COMPILER NAME AND VERSION (AND PATCHLEVEL): > gcc-4.0.0 --version > gcc-4.0.0 (GCC) 4.0.0 > > � � CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to > a platform- > � � specific file, simply state which one]: > cat /opt2/linux/x86_64/ACE/1.4.4/ACE_wrappers/ace/config.h > #define ACE_HAS_XML_SVC_CONF > #include "ace/config-linux.h" > > � � CONTENTS OF > $ACE_ROOT/include/makeinclude/platform_macros.GNU (unless > � � this isn't used in this case, e.g., with Microsoft Visual C++): > cat > /opt2/linux/x86_64/ACE/1.4.4/ACE_wrappers/include/makeinclude/ > platform_macros.GNU > > # configure ACE/TAO for our use > > debug=1 > optimize=1 > exceptions=1 > threads=1 > inline=1 > rtti=1 > versioned_so=1 > interface_repo=1 > ssl=1 > > include $(ACE_ROOT)/include/makeinclude/platform_linux.GNU ...

[tao-bugs] Re: [tao-users] ACE 5.4.0 TAO 1.4 build problems in orbsvcs
Hi Bill, It looks to me like you haven't built Kokyu, which is in $ACE_ROOT/Kokyu/ Please try building this first and then build TAO. Chris/Venkita/Bala/Don, can we please figure out a way to keep the lack of Kokyu being built from causing the rest of orbsvcs from failing?! Thanks, Doug > Makefile: > /export/home/bcassan/ACE_wrappers/TAO/orbsvcs/orbsvcs/Makefile.RTKokyuEvent > > g++ -W -Wall -Wpointer-arith -pipe -O3 -D_REENTRANT > -I/export/home/bcassan/ACE_wrappers -I/export/home/bcassan/ACE_wrappers/TAO > -DACE_NDEBUG -DACE_USE_RCSID=0 -DACE...

[tao-users] JDK 1.4.2 client with TAO 1.4 server
TAO VERSION: 1.4 ACE VERSION: 5.4 HOST MACHINE and OPERATING SYSTEM: Linux Red Hat 8 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: Intel PC Windows 2000 COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) javac (sun JDK 1.4.2) AREA/CLASS/EXAMPLE AFFECTED: DOES THE PROBLEM AFFECT: COMPILATION? no LINKING? no EXECUTION? yes OTHER (please specify)? SYNOPSIS: I have a simple C++ server using TAO and running under linux and a simple java client using sun's build-in Java 2 ORB, which connects to the server using the cor...

[ciao-users] Utility library not being found on ACE/TAO/CIAO 5.4.2/1.4.2/0.4.2
Hello again, I am still attempting to install BBN's quo system and I was just informed that I should use ACE/TAO/CIAO 5.4.2/1.4.2/0.4.2. This is the reason for using an older version. CIAO VERSION: 0.4.2 TAO VERSION : 1.4.2 ACE VERSION : 5.4.2 HOST MACHINE and OPERATING SYSTEM: Dell Dimension 8100 w/ Gentoo Linux (2.6 kernel) TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): AREA/CLASS/EXAMPLE AFFECTED: CCF library DOES THE PROBLEM AFFECT: COMPILATION? If so, what do your $ACE_ROOT/ace/config.h: // -*- C++ -*- // // config-linux.h,v 4.41 2004/04/22 20:54:00 shuston Exp // The following configuration file is designed to work for Linux // platforms using GNU C++. #ifndef ACE_CONFIG_LINUX_H #define ACE_CONFIG_LINUX_H #include /**/ "ace/pre.h" #define ACE_PLATFORM_CONFIG config-linux.h #include "ace/config-linux-common.h" #define ACE_HAS_SVR4_DYNAMIC_LINKING #define ACE_HAS_AUTOMATIC_INIT_FINI #define ACE_HAS_DLSYM_SEGFAULT_ON_INVALID_HANDLE #if !defined (ACE_MT_SAFE) #define ACE_MT_SAFE 1 // JCEJ 12/22/96 #1 #endif #if ACE_MT_SAFE // Yes, we do have threads. #define ACE_HAS_THREADS // And they're even POSIX pthreads (LinuxThreads implementation) #define ACE_HAS_PTHREADS // ... and the final standard even! #define ACE_HAS_PTHREADS_STD ...

Web resources about - RE: [tao-users] Strange warning when updating from tao 1.4.4 to 1.4.8 #2 - comp.soft-sys.ace

Resources last updated: 3/5/2016 10:41:49 AM