Category Archives: Tibco RV Interview Questions

BLOG NAME CHANGE on Sunday (Aug 31,2014) :- Please update book mark with NEW one (TIBCOWITHSIVA.WORDPRESS.COM)

30 Aug

I am planning to change blog name this Sunday (Aug 31st,2014) ..

thanks for all 100000 views and followers.

New blog name will be much easier :- TIBCOWITHSIVA.WORDPRESS.COM

 

tibcowithsiva.wordpress.com- ====> TIBCOWITHSIVA.WORDPRESS.COM

 Leave a comment

Posted by siva@21five77 on August 30, 2014 in FAQ's, Linux system admin, Tibco AdapterS, Tibco Admin, Tibco Business Works, TIBCO BusinessConnect, Tibco BW Interview Questions, TIBCO cim, Tibco EMS, Tibco EMS Interview Questions, Tibco HAWK, Tibco Hawk interview questions, Tibco Interview Questions, TIBCO jobs db, TIBCO Messaging, TIBCO Rendezvous, Tibco Repository VIDEOS, Tibco RV Interview Questions, Tibco Training details, Unix support issues, Useful handy

 

TIBCO RV/RVRD Http   Interface

05 Jun

We can check RVS status and each tibco rvd is running expose on HTTP interface , with this we can get many useful information about RVD /RVRD.

E.g:-

General information(version,host name,store file,process id, ip add..) client details services has been subscribed by rvd XML Configuration- it gives subject a particular service is using and what are

those etc. Current Log

Which services has been subscribed by rvd

to check on which Http port your rvd is publishing information do this in your linux/windows host where rvd/rvrd  is running

In UNIX :–> ps -ef | grep ‘rvd|rvrd’  | grep -v grep

this will show rvd/rvrd  process with parameters used for starting “-http 7580″ shows that http interface is on port 7582now just type this in your browser.

http://hostname:7580/

Best Regards,Siva.

If you guys are looking for online Tibco Training  /Learn TIBCO instantly through video tutorials , do please reach me Root2Node@gmail.com

 

 Leave a comment

Posted by siva@21five77 on June 5, 2013 in TIBCO Messaging, TIBCO Rendezvous, Tibco RV Interview Questions

 

Tibrv Errors and Exceptions with   resolutions

03 Sep

While working with TIBCO_RV during many years I found that tibco errors are mysteriously difficult to diagnose for a newcomer and minor difference between syntax and semantics along with network specifics lead some strange error.here I am putting most common error which I have faced mainly because of some silly mistake in syntax and spent hours to figure out exact cause during my initial days.

This list is by no means complete and I would encourage to put any other error you have encountered to make this list more useful.

any suggestion, input feedback always welcome.

1) Error: Failed to initialize transport: Could not resolve network specification

This error comes when your rvd tries to creates tibco transport and failed to created it , it could come in your Java program which is trying to establish tibco transport or while using

tibrvsend or tibrvlisten command . recently I have encountered when I am trying to listen on a particular topic (subject) by using tibrvlisten command in my windows machine.

C:\>tibrvlisten -service “5420” -network “190.231.54.20” -daemon “tcp:7500″ TEST.REPLY

Cause: It was not working because of missing “;” before network value , when I modified network string as below it working.

C:\>tibrvlisten -service “5420” -network “;190.231.54.20″ -daemon “tcp:7500″ TEST.REPLY

2) Not able to receive message between two host .This is another classic error which I have faced many times , it always look something is wrong on my side but many times it comesbecause of network filtering where they allow/disallow passing message between two based on service or topic.

generally prod and non production servers reside on different multicast network so if a configuration working for non production it may not work on production environment if network is different. you will have to change the network parameter and use the one which is assigned for production.

3) Failed to initialize transport: Arguments conflictAnother classic error which has manifests itself in different form and can magically puzzle you but I have already said looking and focusing on error message is most important point, here its simply trying to say I am trying to create tibco rvd transport for your but the arguments (which could be either service, network or daemon) is conflicting with something already running on that box, service or network.

I have recently faced issue with two different reason let’s see where are those.

C:\>tibrvlisten -service “5420” -network “;190.231.54.20″ -daemon “tcp:7500″ TEST.REPLYtibrvlisten: Failed to initialize transport: Arguments conflict

Here I was trying to listen on above tibco transport but it always failing later I discovered that service “5420” was already bounded to some other network “”;200.231.54.20″ and some other process was already using that. when I shutdown the process and restart my tibrvlisten it started working.

Cause: If a service is already bounded to a network , trying to bound with another network will fail.

The reason for this failure is that since rvd associates the port , specified by service number with the interface/address specified by the network parameter and hence not able to associate two or more networks/interfaces with same UDP port (remember service denotes UDP port)

Second time also manifestation was same but actual cause was not with the service name but was with the network interface.

I was again trying to listen this time using remote daemon

C:\>tibrvlisten -service “5420” -network “;190.231.54.20″ -daemon “tcp:10.230.23.65:7500″ TEST.REPLYtibrvlisten: Failed to initialize transport: Arguments conflict

Cause :Here on host 10.230.23.65 we had two NIC (Network Interface Card) and this network “190.231.54.20” was already bound to NIC card “eth1″ and here I am trying to binding this with eth0 (default one) and due to this it was failing.

Solution : when I changed the command to use “eth1″ it started working.C:\>tibrvlisten -service “5420” -network “eth1;190.231.54.20″ -daemon “tcp:10.230.23.65:7500″ TEST.REPLYtibrvlisten: Listening to subject TEST.REPLY

Conclusion: you can not associate same service with two different network or same network with two different NIC cards.

4)TibrvException[error=67,message=Socket limit reached] at com.tibco.tibrv.TibrvImplTPortC.natCreate(Native Method) at com.tibco.tibrv.TibrvImplTPortC.create(TibrvImplTP ortC.java:40) at com.tibco.tibrv.TibrvRvdTransport.init(TibrvRvdTra nsport.java:77

Cause: your rvd (Rendezvous daemon) is creating so many tibco transport that eventually it exhausts Socket limit available for any process in windows.

Diagnosis: to find out the culprit you need to find out on which process is creating so many transport first.

netstat -nap | grep “processid | wc -l

run this multiple time with different suspected process to identify the process which is culprit.

Now if your process is publishing/subscribing on multiple service you need to find on which service this is happening to find out use netstat command again with different service your process is using.

netstat -a | grep “service” | wc -l

Now you know exact culprit process id and service , first stop the process and figure out why exactly so many transports are getting created.

5) Name collision on Certified messaging.You can not have two connection with same name if you are using Certified messaging. you will get below error.ADV_CLASS=ERROR ADV_SOURCE=RVCM ADV_NAME=REGISTRATION.COLLSION.NAME.TestClient

it means some one has alrady registered with name “TestClient” in this certified transport.UHF32WN5SUQZ

6) Exception while confirming message in tibco rv certified messaging.TibrvException[error=27,message=Not permitted]

This error comes if you try to confirm the message two times.

Cheers,Siva,For TIBCO training please reach me at :Root2node@gmail.com

 

 Leave a comment

Posted by siva@21five77 on September 3, 2012 in TIBCO Rendezvous, Tibco RV Interview Questions

 

Ledger file in Tibco Certified   Messaging

28 Aug

TIBCO ledger file is used in case of certified messaging to store unresolved message. When you use certified messaging using CMTransport then rendezvous process will store of each message in a ledger which could be either in Memory or File based.You can either opt for In Memory or Process based ledger or File based ledger both approaches has there advantage and disadvantages .In case if you are going to use In Memory or process based ledger than all unconsumed messages will be lost if process shutdown or crashed. so it only make sense to opt for Process based ledger if certification is required only on process duration if you would like to have recording after  process duration then file based ledger should be used.

TIBCO rendezvous Process keeps every outbound message in ledger either in Process memory or in persistent File based upon its configuration until it’s consumed by the entire certified subscriber or until specified expiry times got elapsed.

Advantage of File based ledger is that storage extends beyond process duration so message will be available even in case of process died which is..to know more indepth on RV ..touch base on root2node@gmail.com

Cheers,Siva.

 Leave a comment

Posted by siva@21five77 on August 28, 2012 in TIBCO Rendezvous, Tibco RV Interview Questions

 

RVD (Rendezvous daemon) vs RVRD (Rendezvous Routing   Daemon)

28 Aug

RVRD (Rendezvous Routing Daemon) are simply process owned by middleware or network teams which listens multicast traffic locally and transmit it to another RVRD counter part (another host) using TCP. This remote host than re multicast this traffic to there own network. So essentially it used to bridge two different regional network e.g. London and Newyork etc.

RVRD is multicast in one end and unicast on other end so it receives messages from multiple RVD (Rendezvous Daemon) and send via TCP to another RVRD which distributes messages on different RVD (Rendezvous Daemon) on there own network e.g. say on NY network.

Control of RVRD (Rendezvous Routing Daemon) resides on middleware/network team and they decide which topics/subject is allowed for RVRD (Rendezvous Routing Daemon)  traffic. So if you send message on a topic which is not configured on RVRD and subscriber for that service is on some another physical network it will not receive those messages until that topic is enabled on RVRD (Rendezvous Routing Daemon) front.

On the other hand RVD (Rendezvous Daemon) is a background process runs on every host which wants to send or receive message from tibco multicast network. Your process depends upon this for reliable and efficient network communication. all messages goes via rvd before it enters or leaves host on a multicast network and RVD (Rendezvous Daemon) is responsible for creating packets or assembling packets to and from the network.

On points— RVD transmit outbound message from your program to network.— RVD delivers inbound message from network to your process.— RVD takes care of Operating system specifics and encapsulates those leaving your process independent of such low level details.— RVD daemon can be start automatically if its not running already ,may exit after some specified period of inactivity.