BW Startup Error

Sometime we might get this error while starting up a BW application. This is very common error in tibco space.


java.lang.UnsatisfiedLinkError: Library not found: tibrvnativesd
at com.tibco.tibrv.Tibrv.loadNativeLibrary(Tibrv.java:388)
at com.tibco.tibrv.Tibrv.(Tibrv.java:79)
at com.tibco.sdk.m.byte(MAppImpl.java:700)
at com.tibco.sdk.m.v(MAppImpl.java:478)
at com.tibco.sdk.m.(MAppImpl.java:95)
at com.tibco.sdk.a.(MThinAppImpl.java:21)
at com.tibco.sdk.MApp.(MApp.java:149)
at com.tibco.share.util.TraceApp.(Unknown Source)
at com.tibco.share.util.Trace.if(Unknown Source)
at com.tibco.share.util.Trace.a(Unknown Source)
at com.tibco.share.util.Trace.(Unknown Source)
at com.tibco.pe.core.JobPoolCreator.createTrace(Unknown Source)
at com.tibco.pe.PEMain.a(Unknown Source)
at com.tibco.pe.PEMain.do(Unknown Source)
at com.tibco.pe.PEMain.a(Unknown Source)
at com.tibco.pe.PEMain.(Unknown Source)
at com.tibco.pe.PEMain.main(Unknown Source)
Caused by: java.lang.UnsatisfiedLinkError: /export/home/tibco/tibrv/8.3/lib/libtibrvnativesd.so: ld.so.1: bwengine: fatal: /export/home/tibco/tibrv/8.3/lib/libtibrvnativesd.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1803)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1728)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1028)
at com.tibco.tibrv.Tibrv.loadNativeLibrary(Tibrv.java:385)
... 16 more

To resolve this error, you can change the %RV_HOME%/lib with %RV_HOME%/lib/tibrvj.jar in the property tibco.env.STD_EXT_CP in application tra and start the BW application. if this is common error with all you BW applications running on a host, then you can change the bwengin.tra file itself so that when applications are deployed they have this property set in their tra.

 

How to browse message in TIBCO EMS?

There was API available which can help in browsing data on EMS destinations but there was out of box tools also available in market which provide easy way to browse messages/data on EMS destinations. One of widely used tools that I personally use is GEMS. You can download the tool from tibcommunity. 

Connect to the desired EMS instance.

Click on Queues on left hand side of the GEMS tools.

Right Click on the queue/topic which you want to browse. You should get option to browse. There is browse option in main menu option also. Note that for topic, you will get Monitor Topic option, for queue it will be Browse Queue

After clicking on browse queue, you will get below window.  By default it will list down only 10 messages, by checking on  'No limit' option, you can get all the messages sitting on the queue.

Browse Result

You can double click on any message to see it content.

Ranjeet Singh.

TIBCO Deployment-Internal error: Subscription context is null

You might get this error while doing deploying using AppManage utility. To resolve the issue, just rerun the deployment script one more time, it just goes away !!!. 

TIBCO Admin -Server Plugin Failed

Error appearing in TIBCO Administrator UserInterface: Server Plugin Failed **********************                                                                                               

Error log in Administrator log file : tibco.objectrepo.OperationFailedException: Error retrieving stream for VFile CriticalCellCalculation.process URI= at com.tibco.archive.impl.filevff.FileVFileStream.getInputStream(FileVFileStream.java:32) at"

Resolution
--------------

1. Stop hawk agent on the BW machine and  admin machine. If this solve the problem, then no need to perform other steps.

2. On BW machine, At the path /var/tmp OR   /tmp, there will be .tmp files related to admin domain which should be deleted.

E.g., At path /tmp/tibco_####_TIBCO_QA2_Administrator_tparhetibq017.####.com_tibco, remove all .tmp files.

[tibco@tparhetibq017 tibco_####_TIBCO_QA2_Administrator_tparhetibq017.####.com_tibco]$
ll *.tmp
-rw-r--r-- 1 tibco tibco 9911 Oct 12 11:14 tibco_####_TIBCO_QA2_Administrator_tparhetibq017.####.com59169.tmp
-rw-r--r-- 1 tibco tibco 9965 Oct 12 11:44 tibco_####_TIBCO_QA2_Administrator_tparhetibq017.####.com59179.tmp

4.Restart the hawk agent on BW machine.

3.If above steps does not solve the issue, just restart the administrator server & finally start the hawk agent on admin machine.

TIBCO EMS Issue- Zone Error

Error : SEVERE ERROR: Zone 'PL.RPTEXP.CREATE_Q.1HZONE01' is defined as type 'mhop' in configuration but also is defined as type '1hop' in meta.db

I got above error in one of EMS server and it prevented EMS to come up properly. EMS used DB as data store. First thing that we should try when we get this kind of error [which indicate a EMS database store corruptions] is to start EMS instance with '-forceStart' command like tibemsd.exe -forceStart. If this does not solve the problem, then we can go to the EMS database and remove the problematic zone records from ZONE_RECS table. In our case due to some reason , ZONE_RECS have more than 100 records for same zone with 1hop or mhop property set  which confused the EMS instance somehow.

TIBCO EMS Troubleshooting-How to find consumer and producers for EMS destinations?

1.    Based on queue name, find the consumer id and connection id.
show  consumers queue=TEST.CIB.1LST.LTD.RequestReply.ReferenceData.2 full

                                                                                            
      Id   Conn     Sess User      T Queue                                             
53675650 383273 55949126 1lst_lstm Q TEST.CIB.1LST.LTD.RequestReply.ReferenceData.2
53675651 383273 55949127 1lst_lstm Q TEST.CIB.1LST.LTD.RequestReply.ReferenceData.2

2.    Based on ‘Conn’ – connection id, we can find host from where connection is being made. Take out all the connections either based on user or if user not know, take all and then search the connection id from the list.
3.    Third column in above statement output is session ID. We can also use Gems tool to find above details from consumers section. In Gems tool, go to consumers and sort the queue name, it list down connection id and session id for each connection/consumer id.
4.    To find the producer for a given destination, best way to find the details is to use Gems tool. Gems tool provides the producer column as well for each destination.

TIBCO EMS Troubleshooting-How to find the receiver for a given EMS Durable ?

To find which host is acting as receiver for a given durable, we need to find the details of the durable.
show durable <durableName>

Get the consumer ID and do ‘show consumer <consumerID>’
Get the connection ID and find the host which is having this connection ID. There is no command to check this so we first get all the connections on the server using ‘show connections’ and try to serch connection ID.

tcp://test-uatems01:7222> show durable CDS2BBG_sit1_1
 Durable Subscriber:  CDS2BBG_sit1_1
 Subscription name:   CDS2BBG_sit1_1
 Client ID:
 Topic:               test.cib.tro.reportserver.event
 Type:                dynamic
 Status:              online
 Username:            cib_1tro_test
 Consumer ID:         577675554
 No Local:            disabled

tcp://test-uatems01:7222> show consumer 577675554
 Consumer:                  id=577675554, user durable topic subscriber
 Connection:                id=23375853, started
 Session:                   id=429355973, acknowledgement: client acknowledge
 User name:                 "cib_1tro_test"
 Topic:                     test.cib.tro.reportserver.event
 Durable name:              "CDS2BBG_sit1_1"


To narrow down the list of connection , we can take only a subset of connection by filtering by user if we know the user.

show connections user=<userName>