Resolution:
Description:
============
In the adb log file after seeing "Starting thread ", no more log messages were printed and the adapter hung. In administrator, the application is always showing "starting up".

-----------------------------------------------------
2010 Mar 24 11:20:16:361 GMT +1 COUNES_ADB.COUNES_ESB_NASAREPOSITORY_Publisher-COUNES_ADB_primary Info [Adapter] AEADB-700059

        Starting thread (name: COUNES_ESB_NASAREPOSITORY_Publisher-COUNES_ADB_primary.COMM.INTERFACE.1 , id: 4060060560)

2010 Mar 24 11:20:17:363 GMT +1 COUNES_ADB.COUNES_ESB_NASAREPOSITORY_Publisher-COUNES_ADB_primary Info [Adapter] AEADB-700059

        Starting thread (name: COUNES_ESB_NASAREPOSITORY_Publisher-COUNES_ADB_primary.DB.INTERFACE.1 , id: 4059007888)

2010 Mar 24 11:20:17:363 GMT +1 COUNES_ADB.COUNES_ESB_NASAREPOSITORY_Publisher-COUNES_ADB_primary Info [Adapter] AEADB-700059

        Starting thread (name: COUNES_ESB_NASAREPOSITORY_Publisher-COUNES_ADB_primary.PUB.MANAGER.1 , id: 4057955216)
-----------------------------------------------------

In the EMS console or the EMS log file, you could see "not allowed to create dynamic topic " messages.

For ADB6.0 you could see following log in adb log file:
-------------------------
ActiveDatabaseAdapterConfiguration.ActiveDatabaseAdapterConfiguration Error [Adapter] AEADB-910005
    Startup Error. SDK Exception Code = AESDKC-0151, Category = JmsComm, Severity = errorRole, Description = JMS Error: Failed to create Jms Subscriber DupDetectMessage : Invalid destination, File =
-------------------------


Environment:
===========
All

Cause:
=====
The adapter EMS user does not have privilege to create JMS topic/queue.

Resolution:
==========
Go to the EMS bin folder, open queues.conf file and topics.conf and add ">" into the files to allow dynamic queue/topic creation.

TIBCO Adapter for Activedatabase is not starting up and does not log any information even in debug mode.