Problem:
- Product Name: VisiBroker
- Product Version: 7.0/8.0
- Platform: All
- Component: Naming Service
When running VisiBroker 7.0/8.0 with Naming Service, application hangs up and Naming Service logs shows some "NotFound" and "markSuspect" GIOP logs on Sending and Received message. An example of the sending and received messages is as follows:
Application.orb_com.inprise.vbroker.orb.ORB@77d791ad.vbroker.log.default.filter.cdr - 010.161.121.145,00225438,
****** Sending Message *****
GIOP............
..........1IDL:o
mg.org/CosNaming
/NamingContext/N
otFound:1.0.....
...........RMI_M
atStatus.......
Application.orb_com.inprise.vbroker.orb.ORB@77d791ad.vbroker.log.default.filter.cdr - 010.161.121.145,00225438,
****** Received Message *****
GIOP............
.............PMC
......./CLUSTER_
POAPRDPRGSERVICE
.....76......mar
kSuspect........
................
.VIS............
.........-131416
2077x12264708061
48........
If you have the same reference name, doing multiple bind and/or unbind from the same cluster can result in missing references. For example, when two IORs are bound to the same reference name, sometimes, only 1 reference is displayed by list instead of 2. This problem may occur only on platforms with multiple CPUs.
Resolution:
This issue was fixed on CR8564. Visibroker 7.0 SP3 and 8.0 SP1 contain a fix on multiple bind and/or unbind sequence calls that can produce missing references if they have the same reference name.
#VisiBroker
#NamingService
#Security
#VisiNaming
