Server cores when migrated to Visibroker 5.2.1 from 4.5

Server cores when migrated to Visibroker 5.2.1 from 4.5

Post by grajes » Sun, 09 May 2004 01:18:26


Server program working perfectly fine with Visibroker 4.5 crashes when
migrated to BES 5.2.1. NO code change has been made. Server code is
BOA implemented.
The server runs good if doesn't make multiple server to server calls.
When it does, it hangs for some time and then cores. Stack trace says
it cores when it tries to connect to database. I had big problems
when I try to start the server itself. It has been resolved by
increasing the
threadStackSize to 256000. Had anyone come across simillar isses, pls
help me out! Is there any other properties to be set to make this code
work, like threadMax, threadMaxIdle or related. And disturbing fact is
that, most of the time (95%) it works fine the first time, but sure to
core next time!


1. Server connections - Visibroker 4.5

2. [OT] OTL (was Visibroker for C++ 4.5 and Orcale Pro*C)

"William Cai" < XXXX@XXXXX.COM > wrote in

I haven't done any benchmarks but OTL is simply a C++ header file that you include in
your code and compile them alltogether. OTL just wraps either ODBC or OCI calls using
some #ifdefs and C++ templates so there should be no noticeable performance degradation
in comparison to using ODBC/OCI directly. For example, if you want to connect to some
Oracle 9i database you just include this in your code:

#define OTL_ORA9I
#include "otlv4.h"

If instead you prefer using ODBC you give:

#define OTL_ODBC
#include "otlv4.h"

(Of course you can have the preprocessor definition of OTL_* in the makefile so that no
source code change is needed if you want to change the library used, i.e. ODBC or OCI)

Using ODBC you can connect to a large collection of databases (any db that there exists
an ODBC driver for) but there are also some support for "native" protocols like OCI for
Oracle and DB2 CLI

I have not used OCCI myself. I used to code with the Rogue Wave DBTools but switched to
OTL as soon as I learnt about it and I haven't really missed them. :-)


Stelios G. Sfakianakis | Center of Medical Informatics
Voice: +30-2810-391650 | Institute of Computer Science
PGP Key ID: 0x5F30AAC2 | FORTH,

3. visibroker 4.5 generated code bug

4. Visibroker for C++ 4.5 and Orcale Pro*C

5. Accesing CORBA Objects created by a POA object in Visibroker 4.5

6. timeouts ... visibroker 4.5

7. visibroker 4.5 bug/memory leak

8. Visibroker 4.5 and VC++ .Net 2003

9. Migrating SBS 4.5 to Win2k server only(not SBS2000)

10. Migrating SBS 4.5 Domain to Windows 2003 Server.

11. Migrating from SBS 4.5 to Windows SERVER 2003

12. migrating SBS 4.5 to SBS 2003 keeping the server on the same hardware

13. Migrating from SBS 4.5 and Exchange 5.5 to standard Windows Server 2003 and Exch

14. Migrating SBS 4.5 to Windows 2000 Server using Windows NT 4 full version

15. Best Practices to migrate or upgrade SBS 4.5 to Win 2K3 Standard Server