[tao-users] TAO 1.3.1 and TAO 1.2.0
Server:
TAO VERSION: 1.2.0
ACE VERSION: 5.2.0
HOST MACHINE and OPERATING SYSTEM:
- Compaq AU600, Tru64 Unix
COMPILER NAME AND VERSION (AND PATCHLEVEL): Compaq C++ V6.2 for
Tru64
Client:
TAO VERSION: 1.3.1
ACE VERSION: 5.3.1
HOST MACHINE and OPERATING SYSTEM:
- Win 2K Professional
COMPILER NAME AND VERSION (AND PATCHLEVEL): Visual C++ 6.0 SP 5
DOES THE PROBLEM AFFECT:
COMPILATION? No
LINKING? No
EXECUTION? Yes
AREA/CLASS/EXAMPLE AFFECTED:
Fails in _narrow()
OTHER (please specify)?
SYNOPSIS:
narrowing to an object interface throws exception
DESCRIPTION:
The server is running on Compaq, and the client is running on the
Windows. The client fails while narrowing an object reference. The
related codes are as follows:
try{
name.length(2);
name[0].id = CORBA::string_dup ("DF");
name[1].id = CORBA::string_dup ("NO_Ctrl");
obj=namingContext->resolve(name);
/******/ DF_Ctrl_var=NET_OPER::NO_Ctrl::_narrow(obj.in());
if (CORBA::is_nil(DF_Ctrl_var.in()))
ACE_ERROR_RETURN((LM_ERROR,
"could not resolve <%s>\n"),
-1);
}
catch (CORBA::Exception & ex)
{
return -1;
}
The client fails on the line marked by /******/.
Is there some incompatibility between TAO 1.2.0 and TAO 1.3.1?
I'm very new to ACE and TAO. Any help will be much appreciated
With regards,
Xiaolu Li
client.cpp
lixiaolu007
comp.soft-sys.ace
20326 articles. 
1 followers.
marlow.andrew
0 Replies
654 Views
Similar Artilces:
[tao-users] AMI from TAO 1.2 to TAO 1.3.1
This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C34181.E00841D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Server: TAO VERSION: 1.3.1 ACE VERSION: 5.3.1 HOST MACHINE and OPERATING SYSTEM: - Intel PIV 2.4GHz, Linux SuSe 8.0 COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc 2.95.3 Hello. I have a problem with AMI Callback. Some months ago I realized a data = distribution=20 application with Clients that attach() to Servers (with Threadpool, RT = CORBA 1) asynchronously.=20 The application was based on TAO 1.2 and it worked fine. Now with TAO 1.3.1, I had to add -lTAO_Messaging in the Makefiles and to = put a svc.conf file (with -ORBSchedPolicy definition) in the client's = directory.=20 Without changing the source code, Server and Client compiling is ok, = Server startup is ok, but Client execution stops (with "Aborted" = message) when data_distributor->sendc_attach(data_distributor_handler.in(), ...) is invoked. In particular, analyzing sendc_attch() in DDC.cpp (from DD.idl) I found = the client stops when _tao_call.start(ACE_ENV_SINGLE_ARG_PARAMETER); is reached. Help me, please! ------=_NextPart_000_001C_01C34181.E00841D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type c...
[tao-users] The differences between TAO 1.4.1.2 and 1.5.1.0 #2
This is a multi-part message in MIME format. ------_=_NextPart_001_01C74A75.80E5ABB0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello all, =20 Could someone tell me where can I find a document which describes about the differences between TAO 1.4.1.2 and 1.5.1.0? =20 Thanks with regards, Shi Lei ------_=_NextPart_001_01C74A75.80E5ABB0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD> <BODY> <DIV><FONT face=3DArial size=3D2><SPAN class=3D604250205-07022007>Hello=20 all,</SPAN></FONT></DIV> <DIV><FONT face=3DArial size=3D2><SPAN=20 class=3D604250205-07022007></SPAN></FONT> </DIV> <DIV><FONT face=3DArial size=3D2><SPAN class=3D604250205-07022007>Could = someone tell=20 me where can I find a document which describes about the differences = between TAO=20 1.4.1.2 and 1.5.1.0?</SPAN></FONT></DIV> <DIV><FONT face=3DArial size=3D2><SPAN=20 class=3D604250205-07022007></SPAN></FONT> </DIV> <DI...
Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released #2 #2
Hi Alex, > What are OCI's plan's for a supported TAO 1.4 release and developer > guide? Will this effect the release of the 1.3 guide? This is an excellent question - I'm sure Malcolm Spence will pitch in when he has a chance and I suspect that OCI will be supporting TAO 1.4 in due time. None of the changes in TAO 1.4 should affect the relevance of the info in the TAO 1.3 developer's guide - there's just more new stuff to document as time permits. Take care, Doug ...
Re: [tao-users] TAO 1.4 build v's TAO 1.3.5 build #2
Hi Joe, >> TAO VERSION: 1.3.5 & 1.4 >> ACE VERSION: 5.3.5 >> >> HOST MACHINE and OPERATING SYSTEM: >> Running on Windows 2000 Pro >> >> TAO 1.3.5 runtime >> >> Compiled using VC6 ( Release ) >> >> TARGET MACHINE and OPERATING SYSTEM, if different from HOST: >> COMPILER NAME AND VERSION (AND PATCHLEVEL): >> >> Windows 2000 >> Microsoft Visual C++ 6.00 >> >> >> AREA/CLASS/EXAMPLE AFFECTED: >> >> DOES THE PROBLEM AFFECT: >> I've been using TAO 1.3.5 for about a year now and was >> recently told to upgrade. I've decided to upgrade to TAO 1.4 and am >> having ALOT of build The DOC group's version of TAO 1.4 is obsolete. Please upgrade to ACE+TAO x.4.5, which you can download from http://deuce.doc.wustl.edu/Download.html under the heading "latest beta kit". Thanks, Doug >> issues. Everything worked fine with TAO 1.3.5 but since I installed >> TAO 1.4 , i started having problems compiling code. >> >> My main concern is that all my compiler problems are related >> directly to the TAO IDL generated code. Here are a sample of the many >> errors I am getting >> >> .. >> >> This error >> >> \ACE_wrappers\TAO\tao/DomainC.h(82) : e...
Re: [tao-users] TAO 1.4 build v's TAO 1.3.5 build #2
Hi Joe, >> Thanks for the reply Johnny but we are to go with 1.4 as its been >> released for a while and many of the bugs are already known. It has >> taken some time to get the premissions to move from 1.3.5 to 1.4 >> and now that progress has begun on the porting of code to the new >> runtime, we are seeing all the issue's listed below. If any help >> can be given on this , it would be greatly appreciated. If you want to use TAO 1.4 you need to contact one of the companies listed at http://www.cs.wustl.edu/~schmidt/commercial-support.html since the DOC group only provides "support" for the latest distribution, which happens to be x.4.5. Thanks, Doug -- Dr. Douglas C. Schmidt Professor and Associate Chair Electrical Engineering and Computer Science TEL: (615) 343-8197 Institute for Software Integrated Systems WEB: www.dre.vanderbilt.edu/~schmidt Vanderbilt University, Nashville TN, 37203 NET: d.schmidt@vanderbilt.edu ...
RE: [tao-users] TAO 1.4 build v's TAO 1.3.5 build #2
--0-694483482-1116417855=:96201 Content-Type: text/plain; charset=us-ascii Thanks for the reply Johnny but we are to go with 1.4 as its been released for a while and many of the bugs are already known. It has taken some time to get the premissions to move from 1.3.5 to 1.4 and now that progress has begun on the porting of code to the new runtime, we are seeing all the issue's listed below. If any help can be given on this , it would be greatly appreciated. Thanks for your time. Joe Goggins Johnny Willemsen <jwillemsen@remedy.nl> wrote: Hi, I would recommend you to use the x.4.5 release which you can obtain from http://deuce.doc.wustl.edu/Download.html. Make sure you build things in a clean tree and you get the new idl compiler. 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 Joe Goggins > Sent: woensdag 18 mei 2005 11:26 > To: joegoggins; tao-users@cs.wustl.edu > Subject: Re: [tao-users] TAO 1.4 build v's TAO 1.3.5 build > > Hi All, > > I've been working on this problem for quite a few days and > don't seem to...
Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released #2
Hi Tom, > We are currently arm-wrestling with TAO-1.3.3 on VxWorks-5.5/Tornado-2.2 > built with non-native exceptions and with implicit templates. Implicit > templates are desirable since we are now using STL and those nested > templates make explicit instantiation almost impossible. Non-native > exceptions are important since native exceptions lead to a factor of 4.5 > increase in code size (!!). > > Implicit templates cause trouble with singletons, since the VxWorks-2.x > loader does not respect weakly-defined symbols, so one can not load > multiple modules which reference the same templated singleton. Our > workaround involves using RTTI and implementing a "singleton registry" > to enable proper singleton behavior. This strategy works for our > production code based on TAO-1.2.1, and hopefully we'll finish off our > move to TAO-1.3.3 sometime soon. > > I've mentioned this on-list once or twice, and had positive feedback on > incorporating fixes or changes to move working code into the TAO tree. > We haven't until recently had time to consider moving away from > TAO-1.2.1, so patches would not have helped. I'd like to post (working) > patches to the list for feedback, and I'd like to do this in time for > consideration to move this code into the next TAO release if deemed > appropriate. Either way we should have something to contribute to our > VxWorks br...
[tao-users] performance degradation between TAO 1.2 and TAO 1.6.5
Hello, We have an application that was using TAO 1.2 and we decided to move to TAO 1.6.5. We use the CosEvent to push/pull events. We have noticed an important performance degradation in TAO 1.6.5: CPU utilization is higher in the process that push the event and in the CosEvent. Using a small test program that push 30 events per seconds, the CPU utilization of the CosEvent went from 1.5% (TAO 1.2) to 5.3% (TAO 1.6.5). The process that push the events went from 1.2% to 3.7%. The machine is a SunBlade 1500, with Solaris 10: SunOS 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Blade-1500. I will assume that such bad performance would have been noticed by someone else and so I am more willing to=20 suspect the way we use/configure TAO. So is someone aware of some new configuration parameters that are needed? The thing is, a truss output of the test program and CosEvent between the 2 versions of TAO does not show a lot of difference. The only main difference is that the client was using a writev(x,xxxxx,2), that is 2 chunks in TAO 122, and now is doing writev(x,xxxx,13) in TAO 1.6.5. The size of data actually transferred per event was around 7000 octets (most of it is TypeCode information as our event definition contains a 'union') I have also noticed that the generated code, and especially the typeCode information has changed between the 2 versions. And it seems to me that with TAO 1.2, the TypeCode info was pre-coded (I am talking of s...
[ace-users] Re: Memory leak, new(UNINT) in TAO(1.2.1) ACE (5.2.1) ?
Hi Ludovic, >> we face a memory leak detected by rationnal purify, using a server in >> tao 1.2.1 and ace 5.2.1 : new(UINT). To ensure that we have proper version/platform/compiler information, please make sure you fill out the appropriate problem report form (PRF), which is in $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM or in $ACE_ROOT/BUG-REPORT-FORM $TAO_ROOT/BUG-REPORT-FORM in older versions of ACE+TAO. Make sure to include this information when asking any questions about ACE+TAO since otherwise we have to "guess" what version/platform/compiler/options you've using, which is error-prone and slows down our responsiveness. >> Did anybody encouter this issue ? >> Is it solved in recent version of TAO/ACE ? The version of ACE+TAO you're using an ANCIENT. Please upgrade to TAO 1.4.4, which you can download from http://deuce.doc.wustl.edu/Download.html under the heading "latest beta kit". Thanks, Doug -- Dr. Douglas C. Schmidt Professor and Associate Chair Electrical Engineering and Computer Science TEL: (615) 343-8197 Institute for Software Integrated Systems WEB: www.dre.vanderbilt.edu/~schmidt Vanderbilt University, Nashville TN, 37203 NET: d.schmidt@vanderbilt.edu ...
[tao-users] Corba-Script 1.3.5 with TAO 1.2.7
TAO VERSION: 1.2.7 ACE VERSION: 5.2.7 HOST MACHINE and OPERATING SYSTEM: Redhat 8.0 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) AREA/CLASS/EXAMPLE AFFECTED: [What example failed? What module failed to compile?] DOES THE PROBLEM AFFECT: COMPILATION? If so, what do your $ACE_ROOT/ace/config.h and $ACE_ROOT/include/makeinclude/platform_macros.GNU contain? LINKING? On Unix systems, did you run make realclean first? EXECUTION? OTHER (please specify)? [Please indicate whether ACE/TAO, your application, or both are affected.] SYNOPSIS: My corbascript examples doesn't work with TAO 1.2.7. The invocation of a corbascript-service from a corbascript client terminates with the exception IDL:omg.org/CORBA/NO_IMPLEMENT:1.0. DESCRIPTION: We are using corbascript 1.3.5 from Phillipe Merle, Lille, France. After some adaptions - removing some ACE_TRY_ENV parameters - it works fine with TAO 1.2.0. After moving TAO to 1.2.7 we have to make some further adaptions with corbascript - again removing some ACE_TRY_ENV parameters. But now we have discovered some problems during the invocation of server requests. The request gets handled by the server successfully but at client side the invocation terminates with the exception NO_IMPLEMENT: Exception: system exception, ID '...
Re: [tao-users] Corba-Script 1.3.5 with TAO 1.2.7
Hi, The problem has to do with CorbaScript-1.3.5/src/cs_CorbaRequest.cpp, e.g. CS_Object* CS_CorbaRequest::invocation () { _request = CorbaTools::create_Request ( _object, _operation_name, Var2ptr(_nvlist), Var2ptr(_nvresult) ); try { _request->invoke (); throw_CORBA2_Exception (_request->env()->exception()); /*****/ } CATCH_ALL_CORBA_SYSTEM_EXCEPTIONS return CS_CorbaValue::create_value (_nvresult->value()); } The line marked /*****/ refers to the operation env() which is no longer available. Intuitively it would seem that just leaving away the try/catch and the throw_CORBA2_Exception() call should solve the problem. However, this may break other ORB configs (i.e. configs for emulated exceptions. Not sure whether there are any such?) Matthias, how did you change cs_CorbaRequest.cpp to get it to compile? --Oliver Matthias Oltmanns wrote: TAO VERSION: 1.2.7 ACE VERSION: 5.2.7 HOST MACHINE and OPERATING SYSTEM: Redhat 8.0 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) AREA/CLASS/EXAMPLE AFFECTED: [What example failed? What module failed to compile?] DOES THE PROBLEM AFFECT: COMPILATION? If so, what do your $ACE_ROOT/ace/config.h and $ACE_ROOT/include/makeinclu...
[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 >> -...
[tao-users] TAO 1.5.0 crashing while receiving IOR from TAO 2.0
Have you ever saw any patch between TAO versions 1.5 and 2.0 which can fix the crash below? It looks like it is inside SSLIOP. ----------------- lwp# 86 / thread# 86 -------------------- fb86add8 int TAO_SSLIOP_Profile::decode(TAO_InputCDR&) (1fbbfd0, eec78c08, 0, 286e08, 14e98, 1fbbfd0) + 590 fb850228 TAO_Profile*TAO::SSLIOP::Connector::create_profile(TAO_InputCDR&) (2dc080, eec78c08, e2, 1edb928, 1fbbfd0, 1fbbfd0) + 60 feb2f5f0 TAO_Profile*TAO_Connector_Registry::create_profile(TAO_InputCDR&) (2fd6f8, eec78f8c, 0, 1, 0, eec78dc8) + 2c0 feb9c15c bool operator>>(TA...
[tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released
Hi We are happy to announce a new beta of ACE-5.3.5, TAO-1.3.5 and CIAO-0.3.5. This beta comes with new ORB level services that were developed over the past few months by folks at Washington University and University of Rhode Island. Please see the release notes attached with this email for more information. As usual the latest release is available at: http://deuce.doc.wustl.edu/Download.html The doxygen documentation for the beta will be updated in the next few hours! We highly encourage you to download the present beta and use it with your applications and let us know if there are any problems. As always, please use the: $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM $CIAO_ROOT/PROBLEM-REPORT-FORM so that we have the version/platform/compiler/options you're using to report problems. We would also request that you take a look at $TAO_ROOT/docs/releasenotes $CIAO_ROOT/docs/releasenote.html for the status of various ongoing projects at the doc groups of WashU, UCI and Vanderbilt to move ACE+TAO+CIAO forward. In addition the following is a list of noteworthy changes since the last beta. Please refer to the ChangeLog for more details on the problem and the nature of fixes applied. --------------------------------------------------------------- IMPORTANT INFORMATION FOR UNIX and LINUX USERS ============================================== Please note that $ACE_ROOT/lib directory also has to be added to the LD_LIBRARY_PATH environment variab...
[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 >> 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 corbaloc format. >> The client gets org.omg.CORBA.OBJECT_NOT_EXIST exception. >> Here is the server's detailed log: >> TAO (21062|8192) - GIOP_Message_Base::dump_msg, recv GIOP v1.2 msg, 305 data bytes, other endian, Type Request[5] >> GIOP message - HEXDUMP 317 bytes >> 47 49 4f 50 01 02 00 00 00 00 01 31 00 00 00 05 GIOP.......1.... >> 03 00 00 00 00 00 00 00 00 00 00 25 00 00 00 00 ...........%.... >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ >> 00 00 00 00 00 55 73 65 72 5f 46 61 63 74 6f 72 .....User_Factor >> 79 00 00 00 00 00 00 06 5f 69 73 5f 61 00 00 00 ...
Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released
Hi Folks, It's been about a year since we released ACE 5.3 and TAO 1.3. We are therefore planning to release ACE 5.4 and TAO 1.4 by mid-December. The ACE+TAO x.3.5 beta that Venkita just announced will be the penultimate beta towards that goal. In addition to all the enhancements that he mentioned in the release notes, we also plan to add the following enhancements before the x.4 release: ---------------------------------------- .. ACE subsetting enhancements .. ORB footprint and compilation-time enhancements .. CORBA Security Service capabilities .. Load Balancing Service enhancements and bug fixes .. CIDL enhancements .. CIAO enhancements .. SCIOP fixes and enhancements .. Additional FT CORBA integration .. New Autoconf support .. Various fixes to parse-magic-bytes problems and problems with receiving GIOP message fragments. .. Impl Repo fixes ---------------------------------------- If there's something really important that you'd like to see go into the ACE+TAO x.4 release *and* you're willing to commit the time/resources necessary to ensure that this happens please let us know. Thanks, Doug A related question for OCI (and other companies supporting TAO I suppose): What are OCI's plan's for a supported TAO 1.4 release and developer guide? Will this effect the release of the 1.3 guide? Cheers, Alex. Douglas C. Schmidt wrote: >Hi Folks, > > It's been about a year since we rel...
Re: [tao-bugs] Increase in IFR Service footprint
Hello again, Something just occurred to me. Version 1.3.1 may have pre-dated some other changes to the IFR that would certainly explain the increase in runtime footprint you are referring to. Back in December, I changed the query dispatch mechanism in the IFR from servant locator to default servant, to optimize the performance. This new mechanism creates 30-odd servants and a POA for each at IFR startup time. This was done last December. Also, regarding the possible memory leaks - these servants and POAs have their lifetimes tied to the IFR, so any Purify checks must shut down the IFR gracefully to be accurate. Sorry for the confusion at first. Jeff "Simon McQueen" <sm@prismtechnologies.com> wrote in message news:<3F2656AB.2050208@prismtechnologies.com>... > TAO VERSION: 1.3.3 > ACE VERSION: 5.3.3 > > HOST MACHINE and OPERATING SYSTEM: > Win 2k > > COMPILER NAME AND VERSION (AND PATCHLEVEL): > Visual C++ 6 SP 5 dynamic debug build. > > AREA/CLASS/EXAMPLE AFFECTED: > Interface Repository > > DOES THE PROBLEM AFFECT: > COMPILATION? > No. > LINKING? > No. > EXECUTION? > Yes. > > SYNOPSIS: > I've been looking at a leak in 1.3.1 for a customer and whilst I was > checking against the latest CVS to see if the fix needed forward porting > I happened to notice that t...
[tao-users] Trying to migrate old TAO 1.4.4 code to 2.0.1 on Ubuntu 12.04 64bit
I'm having trouble porting some old ACE/TAO code to a new system running Ubunti 12.02 64 bit with TAO 2.0.1. using the following IDL: module Smrthm { interface Video { typedef sequence<octet> Picture; Picture TakeSnapshot(); }; }; The following code coredumps in the memcpy: Smrthm::Video::Picture_var theSnapshot = video->TakeSnapshot(); long pictureLength = theSnapshot->length(); cerr << "allocating buffer of size:" << pictureLength << "\n"; void *buffer = malloc(pictureLength); cerr << "allocated buffer\n"; memcpy(buffer, theSnapshot->get_buffer(1), pictureLength); cerr << "memcpy complete\n"; So I suspect I'm doing something wrong around theSnapshot->get_buffer(1), but I'm not sure what. Can someone point me to an example of how you're supposed to access the data of a sequence<octet>? Thanks Steve ...
[tao-users] RE: [ace-users] Re: How to use Any>>=OctetSeq in TAO 1.3.6? #2
Hi, > > Heiko, could you try to add TAO_Export to front of the operators in > > OctetSeqA.h and then rebuild TAO and you app. I think the linker > > errors should be gone. > > this is the solution! Thank you :-) Thanks for the feedback. I have just committed the fix into the repo and this will be in the 1.4 release. Regards, Johnny Willemsen Remedy IT Leeghwaterstraat 25 2811 DT Reeuwijk The Netherlands www.theaceorb.nl / www.remedy.nl ...
[tao-users] TAO 1.4.1?
Hi, I was just curious as to when you think TAO 1.4.1 will be released. Thanks. Scott ...
[tao-bugs] Compilation of TAO 1.3.1 with gcc3.3
TAO VERSION: 1.3.1 ACE VERSION: 5.3.1 HOST MACHINE and OPERATING SYSTEM: RS6000, AIX 5.1 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc 3.3 AREA/CLASS/EXAMPLE AFFECTED: Compiler Warning DOES THE PROBLEM AFFECT: COMPILATION? If so, what do your $ACE_ROOT/ace/config.h and $ACE_ROOT/include/makeinclude/platform_macros.GNU contain? config-aix5.1.h, platform_aix_g++.GNU LINKING? On Unix systems, did you run make realclean first? New Installation. EXECUTION? OTHER (please specify)? SYNOPSIS: Compiler warning about Singleton problem. DESCRIPTION: Compilation of ORB_Table.cpp results in the following Warning about Singleton-Problem g++ -pthread -W -Wall -mcpu=common -DACE_AIX_VERS=501 -fno-implicit-templates -fno-exceptions -fcheck-new -DACE_HAS_EXPLICIT_TEMPLATE_INSTANTIATION -I/corba/ACE_wrappers -I/corba/ACE_wrappers/TAO -DACE_NDEBUG -DACE_USE_RCSID=0 -DTAO_BUILD_DLL -c -o .shobj/ORB_Table.o ORB_Table.cpp /corba/ACE_wrappers/TAO/tao/TAO_Singleton.cpp: In static member function ` static TYPE* TAO_Singleton<TYPE, ACE_LOCK>::instance() [with TYPE = TAO_ORB_Table, ACE_LOCK = ACE_Thread_Mutex]': ORB_Table.cpp:132: instantiated from here /...
[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 corbaloc format. The client gets org.omg.CORBA.OBJECT_NOT_EXIST exception. Here is the server's detailed log: TAO (21062|8192) - GIOP_Message_Base::dump_msg, recv GIOP v1.2 msg, 305 data bytes, other endian, Type Request[5] GIOP message - HEXDUMP 317 bytes 47 49 4f 50 01 02 00 00 00 00 01 31 00 00 00 05 GIOP.......1.... 03 00 00 00 00 00 00 00 00 00 00 25 00 00 00 00 ...........%.... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 55 73 65 72 5f 46 61 63 74 6f 72 .....User_Factor 79 00 00 00 00 00 00 06 5f 69 73 5f 61 00 00 00 y......._is_a... 00 00 00 03 00 00 00 06 00 00 00 a0 00 00 00 00 ................ 00 00 00 28 49 44 4c 3a 6f 6d 67 2e 6f 72 67 2f ...(IDL:omg.org/ 53 65 6e 64 69 6e 67 43 6f 6e 74 65 78 74 2f 43 SendingContext/C 6f 64 65 42 61 73 65 3a 31 2e 30 00 00 00 00 01 odeBase:1.0..... 00 00 00 00 00 ...
Re: [tao-bugs] Increase in IFR Service footprint
Hi Simon, > Yes, I'm sure the footprint of the IFR has gone up, since I recently > added support for components, events, and valuetypes. However, I > haven't yet had time to do more than make sure it all builds ok - no > debugging or testing yet. I'm currently dividing my time between two > other projects, so I'd welcome fixes or patches from anyone who has > the time and inclination. This would something where PrismTech could really help us out by handling some of the QA and enhancements for the IFR! Thanks, Doug ...
tao naming service build problem (ACE-5.4.1+TAO-1.4.1)
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_...
This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C34181.E00841D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Server: TAO VERSION: 1.3.1 ACE VERSION: 5.3.1 HOST MACHINE and OPERATING SYSTEM: - Intel PIV 2.4GHz, Linux SuSe 8.0 COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc 2.95.3 Hello. I have a problem with AMI Callback. Some months ago I realized a data = distribution=20 application with Clients that attach() to Servers (with Threadpool, RT = CORBA 1) asynchronously.=20 The application was based on TAO 1.2 and it worked fine. Now with TAO 1.3.1, I had to add -lTAO_Messaging in the Makefiles and to = put a svc.conf file (with -ORBSchedPolicy definition) in the client's = directory.=20 Without changing the source code, Server and Client compiling is ok, = Server startup is ok, but Client execution stops (with "Aborted" = message) when data_distributor->sendc_attach(data_distributor_handler.in(), ...) is invoked. In particular, analyzing sendc_attch() in DDC.cpp (from DD.idl) I found = the client stops when _tao_call.start(ACE_ENV_SINGLE_ARG_PARAMETER); is reached. Help me, please! ------=_NextPart_000_001C_01C34181.E00841D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type c...
[tao-users] The differences between TAO 1.4.1.2 and 1.5.1.0 #2
This is a multi-part message in MIME format. ------_=_NextPart_001_01C74A75.80E5ABB0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello all, =20 Could someone tell me where can I find a document which describes about the differences between TAO 1.4.1.2 and 1.5.1.0? =20 Thanks with regards, Shi Lei ------_=_NextPart_001_01C74A75.80E5ABB0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD> <BODY> <DIV><FONT face=3DArial size=3D2><SPAN class=3D604250205-07022007>Hello=20 all,</SPAN></FONT></DIV> <DIV><FONT face=3DArial size=3D2><SPAN=20 class=3D604250205-07022007></SPAN></FONT> </DIV> <DIV><FONT face=3DArial size=3D2><SPAN class=3D604250205-07022007>Could = someone tell=20 me where can I find a document which describes about the differences = between TAO=20 1.4.1.2 and 1.5.1.0?</SPAN></FONT></DIV> <DIV><FONT face=3DArial size=3D2><SPAN=20 class=3D604250205-07022007></SPAN></FONT> </DIV> <DI...
Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released #2 #2
Hi Alex, > What are OCI's plan's for a supported TAO 1.4 release and developer > guide? Will this effect the release of the 1.3 guide? This is an excellent question - I'm sure Malcolm Spence will pitch in when he has a chance and I suspect that OCI will be supporting TAO 1.4 in due time. None of the changes in TAO 1.4 should affect the relevance of the info in the TAO 1.3 developer's guide - there's just more new stuff to document as time permits. Take care, Doug ...
Re: [tao-users] TAO 1.4 build v's TAO 1.3.5 build #2
Hi Joe, >> TAO VERSION: 1.3.5 & 1.4 >> ACE VERSION: 5.3.5 >> >> HOST MACHINE and OPERATING SYSTEM: >> Running on Windows 2000 Pro >> >> TAO 1.3.5 runtime >> >> Compiled using VC6 ( Release ) >> >> TARGET MACHINE and OPERATING SYSTEM, if different from HOST: >> COMPILER NAME AND VERSION (AND PATCHLEVEL): >> >> Windows 2000 >> Microsoft Visual C++ 6.00 >> >> >> AREA/CLASS/EXAMPLE AFFECTED: >> >> DOES THE PROBLEM AFFECT: >> I've been using TAO 1.3.5 for about a year now and was >> recently told to upgrade. I've decided to upgrade to TAO 1.4 and am >> having ALOT of build The DOC group's version of TAO 1.4 is obsolete. Please upgrade to ACE+TAO x.4.5, which you can download from http://deuce.doc.wustl.edu/Download.html under the heading "latest beta kit". Thanks, Doug >> issues. Everything worked fine with TAO 1.3.5 but since I installed >> TAO 1.4 , i started having problems compiling code. >> >> My main concern is that all my compiler problems are related >> directly to the TAO IDL generated code. Here are a sample of the many >> errors I am getting >> >> .. >> >> This error >> >> \ACE_wrappers\TAO\tao/DomainC.h(82) : e...
Re: [tao-users] TAO 1.4 build v's TAO 1.3.5 build #2
Hi Joe, >> Thanks for the reply Johnny but we are to go with 1.4 as its been >> released for a while and many of the bugs are already known. It has >> taken some time to get the premissions to move from 1.3.5 to 1.4 >> and now that progress has begun on the porting of code to the new >> runtime, we are seeing all the issue's listed below. If any help >> can be given on this , it would be greatly appreciated. If you want to use TAO 1.4 you need to contact one of the companies listed at http://www.cs.wustl.edu/~schmidt/commercial-support.html since the DOC group only provides "support" for the latest distribution, which happens to be x.4.5. Thanks, Doug -- Dr. Douglas C. Schmidt Professor and Associate Chair Electrical Engineering and Computer Science TEL: (615) 343-8197 Institute for Software Integrated Systems WEB: www.dre.vanderbilt.edu/~schmidt Vanderbilt University, Nashville TN, 37203 NET: d.schmidt@vanderbilt.edu ...
RE: [tao-users] TAO 1.4 build v's TAO 1.3.5 build #2
--0-694483482-1116417855=:96201 Content-Type: text/plain; charset=us-ascii Thanks for the reply Johnny but we are to go with 1.4 as its been released for a while and many of the bugs are already known. It has taken some time to get the premissions to move from 1.3.5 to 1.4 and now that progress has begun on the porting of code to the new runtime, we are seeing all the issue's listed below. If any help can be given on this , it would be greatly appreciated. Thanks for your time. Joe Goggins Johnny Willemsen <jwillemsen@remedy.nl> wrote: Hi, I would recommend you to use the x.4.5 release which you can obtain from http://deuce.doc.wustl.edu/Download.html. Make sure you build things in a clean tree and you get the new idl compiler. 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 Joe Goggins > Sent: woensdag 18 mei 2005 11:26 > To: joegoggins; tao-users@cs.wustl.edu > Subject: Re: [tao-users] TAO 1.4 build v's TAO 1.3.5 build > > Hi All, > > I've been working on this problem for quite a few days and > don't seem to...
Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released #2
Hi Tom, > We are currently arm-wrestling with TAO-1.3.3 on VxWorks-5.5/Tornado-2.2 > built with non-native exceptions and with implicit templates. Implicit > templates are desirable since we are now using STL and those nested > templates make explicit instantiation almost impossible. Non-native > exceptions are important since native exceptions lead to a factor of 4.5 > increase in code size (!!). > > Implicit templates cause trouble with singletons, since the VxWorks-2.x > loader does not respect weakly-defined symbols, so one can not load > multiple modules which reference the same templated singleton. Our > workaround involves using RTTI and implementing a "singleton registry" > to enable proper singleton behavior. This strategy works for our > production code based on TAO-1.2.1, and hopefully we'll finish off our > move to TAO-1.3.3 sometime soon. > > I've mentioned this on-list once or twice, and had positive feedback on > incorporating fixes or changes to move working code into the TAO tree. > We haven't until recently had time to consider moving away from > TAO-1.2.1, so patches would not have helped. I'd like to post (working) > patches to the list for feedback, and I'd like to do this in time for > consideration to move this code into the next TAO release if deemed > appropriate. Either way we should have something to contribute to our > VxWorks br...
[tao-users] performance degradation between TAO 1.2 and TAO 1.6.5
Hello, We have an application that was using TAO 1.2 and we decided to move to TAO 1.6.5. We use the CosEvent to push/pull events. We have noticed an important performance degradation in TAO 1.6.5: CPU utilization is higher in the process that push the event and in the CosEvent. Using a small test program that push 30 events per seconds, the CPU utilization of the CosEvent went from 1.5% (TAO 1.2) to 5.3% (TAO 1.6.5). The process that push the events went from 1.2% to 3.7%. The machine is a SunBlade 1500, with Solaris 10: SunOS 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Blade-1500. I will assume that such bad performance would have been noticed by someone else and so I am more willing to=20 suspect the way we use/configure TAO. So is someone aware of some new configuration parameters that are needed? The thing is, a truss output of the test program and CosEvent between the 2 versions of TAO does not show a lot of difference. The only main difference is that the client was using a writev(x,xxxxx,2), that is 2 chunks in TAO 122, and now is doing writev(x,xxxx,13) in TAO 1.6.5. The size of data actually transferred per event was around 7000 octets (most of it is TypeCode information as our event definition contains a 'union') I have also noticed that the generated code, and especially the typeCode information has changed between the 2 versions. And it seems to me that with TAO 1.2, the TypeCode info was pre-coded (I am talking of s...
[ace-users] Re: Memory leak, new(UNINT) in TAO(1.2.1) ACE (5.2.1) ?
Hi Ludovic, >> we face a memory leak detected by rationnal purify, using a server in >> tao 1.2.1 and ace 5.2.1 : new(UINT). To ensure that we have proper version/platform/compiler information, please make sure you fill out the appropriate problem report form (PRF), which is in $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM or in $ACE_ROOT/BUG-REPORT-FORM $TAO_ROOT/BUG-REPORT-FORM in older versions of ACE+TAO. Make sure to include this information when asking any questions about ACE+TAO since otherwise we have to "guess" what version/platform/compiler/options you've using, which is error-prone and slows down our responsiveness. >> Did anybody encouter this issue ? >> Is it solved in recent version of TAO/ACE ? The version of ACE+TAO you're using an ANCIENT. Please upgrade to TAO 1.4.4, which you can download from http://deuce.doc.wustl.edu/Download.html under the heading "latest beta kit". Thanks, Doug -- Dr. Douglas C. Schmidt Professor and Associate Chair Electrical Engineering and Computer Science TEL: (615) 343-8197 Institute for Software Integrated Systems WEB: www.dre.vanderbilt.edu/~schmidt Vanderbilt University, Nashville TN, 37203 NET: d.schmidt@vanderbilt.edu ...
[tao-users] Corba-Script 1.3.5 with TAO 1.2.7
TAO VERSION: 1.2.7 ACE VERSION: 5.2.7 HOST MACHINE and OPERATING SYSTEM: Redhat 8.0 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) AREA/CLASS/EXAMPLE AFFECTED: [What example failed? What module failed to compile?] DOES THE PROBLEM AFFECT: COMPILATION? If so, what do your $ACE_ROOT/ace/config.h and $ACE_ROOT/include/makeinclude/platform_macros.GNU contain? LINKING? On Unix systems, did you run make realclean first? EXECUTION? OTHER (please specify)? [Please indicate whether ACE/TAO, your application, or both are affected.] SYNOPSIS: My corbascript examples doesn't work with TAO 1.2.7. The invocation of a corbascript-service from a corbascript client terminates with the exception IDL:omg.org/CORBA/NO_IMPLEMENT:1.0. DESCRIPTION: We are using corbascript 1.3.5 from Phillipe Merle, Lille, France. After some adaptions - removing some ACE_TRY_ENV parameters - it works fine with TAO 1.2.0. After moving TAO to 1.2.7 we have to make some further adaptions with corbascript - again removing some ACE_TRY_ENV parameters. But now we have discovered some problems during the invocation of server requests. The request gets handled by the server successfully but at client side the invocation terminates with the exception NO_IMPLEMENT: Exception: system exception, ID '...
Re: [tao-users] Corba-Script 1.3.5 with TAO 1.2.7
Hi, The problem has to do with CorbaScript-1.3.5/src/cs_CorbaRequest.cpp, e.g. CS_Object* CS_CorbaRequest::invocation () { _request = CorbaTools::create_Request ( _object, _operation_name, Var2ptr(_nvlist), Var2ptr(_nvresult) ); try { _request->invoke (); throw_CORBA2_Exception (_request->env()->exception()); /*****/ } CATCH_ALL_CORBA_SYSTEM_EXCEPTIONS return CS_CorbaValue::create_value (_nvresult->value()); } The line marked /*****/ refers to the operation env() which is no longer available. Intuitively it would seem that just leaving away the try/catch and the throw_CORBA2_Exception() call should solve the problem. However, this may break other ORB configs (i.e. configs for emulated exceptions. Not sure whether there are any such?) Matthias, how did you change cs_CorbaRequest.cpp to get it to compile? --Oliver Matthias Oltmanns wrote: TAO VERSION: 1.2.7 ACE VERSION: 5.2.7 HOST MACHINE and OPERATING SYSTEM: Redhat 8.0 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) AREA/CLASS/EXAMPLE AFFECTED: [What example failed? What module failed to compile?] DOES THE PROBLEM AFFECT: COMPILATION? If so, what do your $ACE_ROOT/ace/config.h and $ACE_ROOT/include/makeinclu...
[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 >> -...
[tao-users] TAO 1.5.0 crashing while receiving IOR from TAO 2.0
Have you ever saw any patch between TAO versions 1.5 and 2.0 which can fix the crash below? It looks like it is inside SSLIOP. ----------------- lwp# 86 / thread# 86 -------------------- fb86add8 int TAO_SSLIOP_Profile::decode(TAO_InputCDR&) (1fbbfd0, eec78c08, 0, 286e08, 14e98, 1fbbfd0) + 590 fb850228 TAO_Profile*TAO::SSLIOP::Connector::create_profile(TAO_InputCDR&) (2dc080, eec78c08, e2, 1edb928, 1fbbfd0, 1fbbfd0) + 60 feb2f5f0 TAO_Profile*TAO_Connector_Registry::create_profile(TAO_InputCDR&) (2fd6f8, eec78f8c, 0, 1, 0, eec78dc8) + 2c0 feb9c15c bool operator>>(TA...
[tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released
Hi We are happy to announce a new beta of ACE-5.3.5, TAO-1.3.5 and CIAO-0.3.5. This beta comes with new ORB level services that were developed over the past few months by folks at Washington University and University of Rhode Island. Please see the release notes attached with this email for more information. As usual the latest release is available at: http://deuce.doc.wustl.edu/Download.html The doxygen documentation for the beta will be updated in the next few hours! We highly encourage you to download the present beta and use it with your applications and let us know if there are any problems. As always, please use the: $ACE_ROOT/PROBLEM-REPORT-FORM $TAO_ROOT/PROBLEM-REPORT-FORM $CIAO_ROOT/PROBLEM-REPORT-FORM so that we have the version/platform/compiler/options you're using to report problems. We would also request that you take a look at $TAO_ROOT/docs/releasenotes $CIAO_ROOT/docs/releasenote.html for the status of various ongoing projects at the doc groups of WashU, UCI and Vanderbilt to move ACE+TAO+CIAO forward. In addition the following is a list of noteworthy changes since the last beta. Please refer to the ChangeLog for more details on the problem and the nature of fixes applied. --------------------------------------------------------------- IMPORTANT INFORMATION FOR UNIX and LINUX USERS ============================================== Please note that $ACE_ROOT/lib directory also has to be added to the LD_LIBRARY_PATH environment variab...
[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 >> 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 corbaloc format. >> The client gets org.omg.CORBA.OBJECT_NOT_EXIST exception. >> Here is the server's detailed log: >> TAO (21062|8192) - GIOP_Message_Base::dump_msg, recv GIOP v1.2 msg, 305 data bytes, other endian, Type Request[5] >> GIOP message - HEXDUMP 317 bytes >> 47 49 4f 50 01 02 00 00 00 00 01 31 00 00 00 05 GIOP.......1.... >> 03 00 00 00 00 00 00 00 00 00 00 25 00 00 00 00 ...........%.... >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ >> 00 00 00 00 00 55 73 65 72 5f 46 61 63 74 6f 72 .....User_Factor >> 79 00 00 00 00 00 00 06 5f 69 73 5f 61 00 00 00 ...
Re: [tao-users] ACE 5.3.5 + TAO 1.3.5 + CIAO 0.3.5 beta released
Hi Folks, It's been about a year since we released ACE 5.3 and TAO 1.3. We are therefore planning to release ACE 5.4 and TAO 1.4 by mid-December. The ACE+TAO x.3.5 beta that Venkita just announced will be the penultimate beta towards that goal. In addition to all the enhancements that he mentioned in the release notes, we also plan to add the following enhancements before the x.4 release: ---------------------------------------- .. ACE subsetting enhancements .. ORB footprint and compilation-time enhancements .. CORBA Security Service capabilities .. Load Balancing Service enhancements and bug fixes .. CIDL enhancements .. CIAO enhancements .. SCIOP fixes and enhancements .. Additional FT CORBA integration .. New Autoconf support .. Various fixes to parse-magic-bytes problems and problems with receiving GIOP message fragments. .. Impl Repo fixes ---------------------------------------- If there's something really important that you'd like to see go into the ACE+TAO x.4 release *and* you're willing to commit the time/resources necessary to ensure that this happens please let us know. Thanks, Doug A related question for OCI (and other companies supporting TAO I suppose): What are OCI's plan's for a supported TAO 1.4 release and developer guide? Will this effect the release of the 1.3 guide? Cheers, Alex. Douglas C. Schmidt wrote: >Hi Folks, > > It's been about a year since we rel...
Re: [tao-bugs] Increase in IFR Service footprint
Hello again, Something just occurred to me. Version 1.3.1 may have pre-dated some other changes to the IFR that would certainly explain the increase in runtime footprint you are referring to. Back in December, I changed the query dispatch mechanism in the IFR from servant locator to default servant, to optimize the performance. This new mechanism creates 30-odd servants and a POA for each at IFR startup time. This was done last December. Also, regarding the possible memory leaks - these servants and POAs have their lifetimes tied to the IFR, so any Purify checks must shut down the IFR gracefully to be accurate. Sorry for the confusion at first. Jeff "Simon McQueen" <sm@prismtechnologies.com> wrote in message news:<3F2656AB.2050208@prismtechnologies.com>... > TAO VERSION: 1.3.3 > ACE VERSION: 5.3.3 > > HOST MACHINE and OPERATING SYSTEM: > Win 2k > > COMPILER NAME AND VERSION (AND PATCHLEVEL): > Visual C++ 6 SP 5 dynamic debug build. > > AREA/CLASS/EXAMPLE AFFECTED: > Interface Repository > > DOES THE PROBLEM AFFECT: > COMPILATION? > No. > LINKING? > No. > EXECUTION? > Yes. > > SYNOPSIS: > I've been looking at a leak in 1.3.1 for a customer and whilst I was > checking against the latest CVS to see if the fix needed forward porting > I happened to notice that t...
[tao-users] Trying to migrate old TAO 1.4.4 code to 2.0.1 on Ubuntu 12.04 64bit
I'm having trouble porting some old ACE/TAO code to a new system running Ubunti 12.02 64 bit with TAO 2.0.1. using the following IDL: module Smrthm { interface Video { typedef sequence<octet> Picture; Picture TakeSnapshot(); }; }; The following code coredumps in the memcpy: Smrthm::Video::Picture_var theSnapshot = video->TakeSnapshot(); long pictureLength = theSnapshot->length(); cerr << "allocating buffer of size:" << pictureLength << "\n"; void *buffer = malloc(pictureLength); cerr << "allocated buffer\n"; memcpy(buffer, theSnapshot->get_buffer(1), pictureLength); cerr << "memcpy complete\n"; So I suspect I'm doing something wrong around theSnapshot->get_buffer(1), but I'm not sure what. Can someone point me to an example of how you're supposed to access the data of a sequence<octet>? Thanks Steve ...
[tao-users] RE: [ace-users] Re: How to use Any>>=OctetSeq in TAO 1.3.6? #2
Hi, > > Heiko, could you try to add TAO_Export to front of the operators in > > OctetSeqA.h and then rebuild TAO and you app. I think the linker > > errors should be gone. > > this is the solution! Thank you :-) Thanks for the feedback. I have just committed the fix into the repo and this will be in the 1.4 release. Regards, Johnny Willemsen Remedy IT Leeghwaterstraat 25 2811 DT Reeuwijk The Netherlands www.theaceorb.nl / www.remedy.nl ...
[tao-users] TAO 1.4.1?
Hi, I was just curious as to when you think TAO 1.4.1 will be released. Thanks. Scott ...
[tao-bugs] Compilation of TAO 1.3.1 with gcc3.3
TAO VERSION: 1.3.1 ACE VERSION: 5.3.1 HOST MACHINE and OPERATING SYSTEM: RS6000, AIX 5.1 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc 3.3 AREA/CLASS/EXAMPLE AFFECTED: Compiler Warning DOES THE PROBLEM AFFECT: COMPILATION? If so, what do your $ACE_ROOT/ace/config.h and $ACE_ROOT/include/makeinclude/platform_macros.GNU contain? config-aix5.1.h, platform_aix_g++.GNU LINKING? On Unix systems, did you run make realclean first? New Installation. EXECUTION? OTHER (please specify)? SYNOPSIS: Compiler warning about Singleton problem. DESCRIPTION: Compilation of ORB_Table.cpp results in the following Warning about Singleton-Problem g++ -pthread -W -Wall -mcpu=common -DACE_AIX_VERS=501 -fno-implicit-templates -fno-exceptions -fcheck-new -DACE_HAS_EXPLICIT_TEMPLATE_INSTANTIATION -I/corba/ACE_wrappers -I/corba/ACE_wrappers/TAO -DACE_NDEBUG -DACE_USE_RCSID=0 -DTAO_BUILD_DLL -c -o .shobj/ORB_Table.o ORB_Table.cpp /corba/ACE_wrappers/TAO/tao/TAO_Singleton.cpp: In static member function ` static TYPE* TAO_Singleton<TYPE, ACE_LOCK>::instance() [with TYPE = TAO_ORB_Table, ACE_LOCK = ACE_Thread_Mutex]': ORB_Table.cpp:132: instantiated from here /...
[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 corbaloc format. The client gets org.omg.CORBA.OBJECT_NOT_EXIST exception. Here is the server's detailed log: TAO (21062|8192) - GIOP_Message_Base::dump_msg, recv GIOP v1.2 msg, 305 data bytes, other endian, Type Request[5] GIOP message - HEXDUMP 317 bytes 47 49 4f 50 01 02 00 00 00 00 01 31 00 00 00 05 GIOP.......1.... 03 00 00 00 00 00 00 00 00 00 00 25 00 00 00 00 ...........%.... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 55 73 65 72 5f 46 61 63 74 6f 72 .....User_Factor 79 00 00 00 00 00 00 06 5f 69 73 5f 61 00 00 00 y......._is_a... 00 00 00 03 00 00 00 06 00 00 00 a0 00 00 00 00 ................ 00 00 00 28 49 44 4c 3a 6f 6d 67 2e 6f 72 67 2f ...(IDL:omg.org/ 53 65 6e 64 69 6e 67 43 6f 6e 74 65 78 74 2f 43 SendingContext/C 6f 64 65 42 61 73 65 3a 31 2e 30 00 00 00 00 01 odeBase:1.0..... 00 00 00 00 00 ...
Re: [tao-bugs] Increase in IFR Service footprint
Hi Simon, > Yes, I'm sure the footprint of the IFR has gone up, since I recently > added support for components, events, and valuetypes. However, I > haven't yet had time to do more than make sure it all builds ok - no > debugging or testing yet. I'm currently dividing my time between two > other projects, so I'd welcome fixes or patches from anyone who has > the time and inclination. This would something where PrismTech could really help us out by handling some of the QA and enhancements for the IFR! Thanks, Doug ...
tao naming service build problem (ACE-5.4.1+TAO-1.4.1)
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_...
Web resources about - [tao-users] TAO 1.3.1 and TAO 1.2.0 - comp.soft-sys.aceResources last updated: 3/23/2016 12:28:46 AM