It's all about the answers!

Ask a question

[closed] Jazz SCM being too slow


Marc Tolentino (164) | asked Nov 18 '08, 12:54 p.m.
edited Oct 10 '17, 2:39 p.m. by David Lafreniere (4.3k7)

hi,

after a 4 months, it is now taking my team (3/4 developers) in average 2 to 5mins to deliver change-sets to our main stream as opposed to 2/5 seconds.

And sometimes we are even having errors like:
<i:a4cf4e4c0f> Deliver Failed
Transaction rollback
Lock Details:
SQL: select ce.ITEM_ID from SCM.COMPONENT_ENTRY ce where
(ce.WORKSPACE_ITEM_ID=&quot;_rM3YMLSOEd2a4aLeUTwOHQ' and...
...
SQL Exception #1
SQL Message: A lock could not be obtained within the time requested
SQL State 40XL1
Error Code: 30000 </i:a4cf4e4c0f>

We have checked the Jazz server and its hard disk usage is still 50% of full capacity.

Do you have any ideas to improve this performance issue? Any work around?

Many thanks.
Marc

The question has been closed for the following reason: "Problem is not reproducible or outdated" by daviddl Oct 10 '17, 2:39 p.m.

One answer



permanent link
Dmitry Karasik (1.8k11) | answered Nov 18 '08, 12:54 p.m.
JAZZ DEVELOPER
after a 4 months, it is now taking my team (3/4 developers) in average 2
to 5mins to deliver change-sets to our main stream as opposed to 2/5
seconds.

And sometimes we are even having errors like: Deliver Failed
Transaction rollback
Lock Details:
SQL: select ce.ITEM_ID from SCM.COMPONENT_ENTRY ce where
(ce.WORKSPACE_ITEM_ID=&quot;_rM3YMLSOEd2a4aLeUTwOHQ' and... ..
SQL Exception #1
SQL Message: A lock could not be obtained within the time requested SQL
State 40XL1
Error Code: 30000

We have checked the Jazz server and its hard disk usage is still 50% of
full capacity.

Do you have any ideas to improve this performance issue? Any work
around?

This error means that your operation was waiting for another operation
that was being performed on the same stream and timed out. If you can
post a snapshot of all the operations running on the server at the time
it will give us a better understanding of what the problem might be.

- Dmitry