Hi Martin

 

It would be good if someone could look at the code that is causing the problem to see if it is possible to reduce or eliminate the cause. This is indeed a wide topic since improving your hardware could also eliminate the problem. I can testify to this since I have had personal experience with it.

 

You do not need to stop the AOS to clear the blocking. You can kill the process directly in your backend database. If you are using Microsoft SQL you can see the process that is causing the block in Enterprise Manager as shown below under the “Locks / Process ID” node.

 

 

No blocking process is shown here but the process that is causing the block usually has blocking in brackets as follows:

 

spid 98 (Blocking)

 

The process that is being directly blocked by spid 98 will appear as follows:

 

spid 74 (Blocked by 98)  

 

A blocking chain may then follow where another process is being blocked by spid 74 and so on.

 

Use the mouse to right click the blocking process and select properties from the context menu. The following screen will appear:

 

 

Select <Kill Process> to kill the process.

 

The only problem with using Enterprise Manager to view blocks is the fact that it may take forever to expand the nodes to see the blocking processes when there is a block. This is a result of the SQL service being busy as a result of the block. The alternative is to run the following query in Query Analyzer to see the blocking and blocked processes:

 

SELECT SPID, HOSTNAME, PROGRAM_NAME, BLOCKED, LOGINAME  FROM master..sysprocesses WHERE blocked <> 0

 

You may then kill the process that is causing the block in Query Analyzer as follows:

 

Kill 98

 

where 98 is the blocking spid.

 

 

Varden Morris

 

J. Wray & Nephew Ltd. - Group I.S.

234 Spanish Town Road

Kingston 11, Jamaica, W.I.

 

Phone:  (876) - 923 - 6141 Ext. 2226
Fax:      (876) - 923 - 5372

Cell:      (876) - 3833566
Email:   [EMAIL PROTECTED]

            [EMAIL PROTECTED]  



Martin <[EMAIL PROTECTED]> wrote:

Hi, All,

I was wondering if anybody knows how to solve session block problem.
When several online user do some posting process at the same time in Axapta, as we know if they use some common table, system will process one by one. So next user will be on waiting for table blocked release.
Sometime the posting session is blocked, then system began to slow. If i want to end and refresh the blocked session, i only can restart the AOS.
Is it the only way to solve this problem?

Thank you all in advance.

Best Regards

Martin Wei






Sharing the knowledge on Axapta.


Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!

Sharing the knowledge on Axapta.



Yahoo! Groups Links

Reply via email to