![]() Using MQ to store and randomly access large quantities of data is not generally recommended.Ģ. MQ is primarily a transport, not a database. FDC files IBM recommended us to follow one of the below to resolve the issueġ. We used to run linear log clean up script with rcdimg job every 30min, and used to get the same kind of FDC files when the queue depth is high.Īs per our MQ Semaphores busy alerts and. We had the same kind of problem couple of months back, We had the exatly same FDC's were created like what you have right now. so, I am stilll not convinced tha the problem was due to physical memory. When the queue manager was stopped, the memory released was 3.5 GB. | Probe Description :- AMQ6150: WebSphere MQ semaphore is busy. | Major Errorcode :- xecL_W_LONG_LOCK_WAIT | | Product Long Name :- WebSphere MQ for AIX | | Date/Time :- Sunday November 15 23:29: | | WebSphere MQ First Failure Symptom Report | If it truely was a memory problem there should also have been an FDC cut. Last edited by jeevan on Tue 12:35 pm edited 2 times in total But I am not convinced but I do not have an alternative explanation. Many think it is memory problem as the error log has semaphonre busy error. What could have been happned so that the cluster repository manager did not get an access to a semaphore? could a semaphone be overwritten by another process so that first process loose track of it and error out? My manager asked me to come up with some action for avoiding such problem in future. Then he shut down the queue manager, clean the semaphore and restarted. ![]() when he tried to suspend the queue manager for maintenance, the command were not being processed. According to my friend who attended the problem, he saw that some of the store registers were disconnected( alert by a script). We had this problem in one of our gateway queue managers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |