| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2424.1 | | SEND::SLAVIN | | Fri Jan 24 1997 12:57 | 7 |
|
> Incedently, will he have to upgrade FBE if he upgrades ObjectBroker
> to V2.7 ?
You need to ask Fbe. I do not think they have a new version for
ObjectBroker V2.7, but I do not know if one of the older versions
would work with it.
|
| 2424.2 | | REQUE::BOWER | Peter Bower, ObjectBroker | Tue Jan 28 1997 06:40 | 2 |
| See also note 2355 and 2331.
|
| 2424.3 | Auto server start QAR'd ? | KERNEL::SMITH | | Fri Jan 31 1997 11:48 | 15 |
| Ok, thanks for tips, I should have mentioned that has already been
tried.
I believe this problem was QAR'd back somewhere between Dec 95 and
Jun 96. Specically it was with OBB V2.5A-06 on NT V3.5.
Only I cannot gain access to the QAR database to check ..
2.490 (CAL911) 41.40
$ set host CAL911
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
Is the QAR database still available?
thanks ewan.
|
| 2424.4 | | RECV::SLAVIN | | Fri Jan 31 1997 12:31 | 3 |
| The old QAR system has been replaced with the new PTR database.
The old QARs are still available on the SEND:: cluster for viewing -
they are write locked.
|
| 2424.5 | | REQUE::BOWER | Peter Bower, ObjectBroker | Sat Feb 01 1997 17:33 | 4 |
|
What errors is the user getting on the autostartup ? Is the user
proxying into an account in the system administrator group ?
|
| 2424.6 | FBE_GetInitialNamingContext failed | KERNEL::SMITH | | Tue Feb 11 1997 11:58 | 13 |
|
This is still dragging on but we may be getting somewhere.
The error on autostart is
FBE_TEST_ENABLE = FALSE
Register Context and Implementations to FBE Name Server
Call error OBB_ORB_rundown
Call error_exit: CORBA_exception_free
FBE_GetInitialNamingContext failed
|
| 2424.7 | Looks like FBE error | REQUE::ctxobj.zko.dec.com::Patrick | ObjectBroker Engineering | Tue Feb 11 1997 13:22 | 8 |
| Looks as if FBE code is failing some place. You need to investigate
why this is occuring. Could it be that there is an environment variable
that needs to be propagated or setup for the FBE Name Server to
work?
Paul Patrick
|
| 2424.8 | Some suggestions | HOUBA::BOUCHET | | Wed Feb 12 1997 03:44 | 57 |
| The FBE naming service is not supported on WNT. If the FBE naming
service is running on another node (e.g. VMS or Digital Unix) try
to add the node name in the OBB_DEFAULT_NODES property. The method
resolution algorithm should select the remote running FBE naming
service. The problems you may encounter are related to the way
that FBE use the naming service to store its own information.
For your information, FBE use the naming service for several
purposes:
(a) Provide an object references for object implementation(s)
supported by the adapters. This is used by the test client
automatically used by FBE.
/<project-name>.context/<object-type-name>
(b) Provide FBE Agent hosts information.
/fbe_workbench.private/_<hostname>.host
There is an object reference for the FBE Agent
running on this node.
(c) Provide FBE project client/server information.
/fbe_workbench.private/<project-name>.project
<node-name>.s_<adapter>
Installed server adapters.
<node-name>.c_<adapter>
Installed client addapters.
This structure may cause trouble in your case if your client
application uses the object references for the test client (point
a). In case where two instances of the same adapters would run
on different machines, all new client programs will use the last
started adapter (FYI: object references have static binding and
stubs have been generated with static method map).
The FBE agent is also not supported on WNT. This means that you
cannot use:
(a) the FBE trace facility. This is not a big problem as the server
adapters will only report an error message indicating that it
cannot initialize the Tracing Facility.
(b) the FBE workbench start/stop commmand. They don't directly
register the project object implementation(s) but dummy ones
(I didn't remember such design motivations). If you want your
server to be started automatically, you need to generate a
registration file and load it in the implementation registery
manually.
I hope this will help you.
Cheers.
Frederic
|
| 2424.9 | NS and Name Context support | EMNTAL::STADELMANN | Sepp @ZUO 760-2609 | Thu Feb 13 1997 04:14 | 17 |
| I havent read all, but be aware that you need OBB 2.5A to work with FBE
(the old version) or maybe 2.5B with the lates greates version of FBE
of which I dont have a kit. ... objectreferences among objectbroker
versions migth be a problem as well.
My question, as we're here in a name server topic
Is a COSS compliant name server required to support Naming Context such
as the FBE Name Server does ?
If yes; how can we then call NS of OBB 2.6 and greater COSS compliant
(do we)?
Given a name context (not only the default one) is required when will
OBB 2.7-xyz support name context's
Sepp,
|