Resolution:
This behaviour is observed especially when the datastore is located on un-supported shared devices (like NFS). As per TIBCO Enterprise Message Service (TIBCO EMS) User's Guide, most of NFS implementations are not supported. One of the reasons is issues with file lock manager.

That being said, if you are testing EMS server by locating the datastore files on a NFS mounted drive, and the server hangs, here are some tips to figure out if the problem is due to the file lock manager.

1. You should first make sure that the current login id has enough permission to access/create/modify files on this NFS storage. Also check if that same login id is also used to start the EMS Server.

2. Check if EMS process (tibemsd(64)) is hanging on a lock request to the datastore files. On Solaris, you can use tools like pstack and truss to verify that the process is hanging in a lock request:

First run a ps -eaf on the process name, get the pid

host1% ps -eaf | grep tibemsd
     tibco 43797 10031  0 12:10:29 pts/6    0:00 tibemsd

Then use the pid and get the following outputs.

host1% pstack 43797

host1% truss -p 43797

Also the pfiles on this process id would say what is actually going on...

host1% pfiles 43797

Once you get the output, if you see that the server is trying to get a lock on the files but it is unable to do so then it is surely a problem with the File Lock Manager. In this case, there is little that can be done from an EMS perspective, and this is why, among other things, NFS is not supported.
If you are not able to find further details, please send the output from above commands to TIBCO Support so we can assist you further.

We strongly recommend you to consider moving away from NFS. Please refer to the Support Criteria for implementing the shared storage in the EMS User's Guide, chapter Fault Tolerance.