Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
Could we get a kernel release with this fixed?
On Sun, Aug 16, 2015 at 7:59 PM, Johann Nallathamby joh...@wso2.com wrote:
I have resolved CARBON-15265/IDENTITY-3511 as it seems to be related but
different. The current issue will be tracked in IDENTITY-3423.
On Fri, Aug 14, 2015 at 4:07 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Please find the attach files which contains stack trace separately.
Cheers!
On Fri, Aug 14, 2015 at 3:55 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Indika,
We are looking to identify the issue. Can you also send us the stack
trace of the two scenarios separately.
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 3:50 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Tharindu,
Above deadlock occurred when we remove topic subscription.
DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME =
'Q_tmp_192_168_1_21_41372_1' AND UM_TENANT_ID=-1234
We are getting another deadlock when we adding topic subscription also.
INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID,
UM_TENANT_ID, UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM
UM_HYBRID_ROLE WHERE UM_ROLE_NAME='Q_tmp_192_168_1_21_58252_1' AND
UM_TENANT_ID=-1234), -1234, (SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE
UM_TENANT_ID=-1234 AND UM_DOMAIN_NAME='PRIMARY'))
Please find the attached text file which contains output of SHOW ENGINE
INNODB STATUS;
Cheers!
On Fri, Aug 14, 2015 at 3:40 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Tharindu,
Please find the attach text file which contains output of above
command.
Cheers!
On Fri, Aug 14, 2015 at 1:03 PM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Ramith,
It seems this is not the exact same issue reported in [1]. For
investigating further can you connect to mysql database from
terminal/mysql
client and run the following command and share the output with us. We
should be able to see the database level errors caused from the output of
this command [2].
*SHOW ENGINE INNODB STATUS;*
[1] https://wso2.org/jira/browse/CARBON-15265
[2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe ram...@wso2.com
wrote:
$subject. Could we have a look?
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Thanks Regards,
*Johann Dilantha Nallathamby*
Technical Lead Product Lead of WSO2 Identity Server
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware
Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
I have resolved CARBON-15265/IDENTITY-3511 as it seems to be related but
different. The current issue will be tracked in IDENTITY-3423.
On Fri, Aug 14, 2015 at 4:07 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Please find the attach files which contains stack trace separately.
Cheers!
On Fri, Aug 14, 2015 at 3:55 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Indika,
We are looking to identify the issue. Can you also send us the stack
trace of the two scenarios separately.
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 3:50 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Above deadlock occurred when we remove topic subscription.
DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME =
'Q_tmp_192_168_1_21_41372_1' AND UM_TENANT_ID=-1234
We are getting another deadlock when we adding topic subscription also.
INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID, UM_TENANT_ID,
UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM UM_HYBRID_ROLE WHERE
UM_ROLE_NAME='Q_tmp_192_168_1_21_58252_1' AND UM_TENANT_ID=-1234), -1234,
(SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE UM_TENANT_ID=-1234 AND
UM_DOMAIN_NAME='PRIMARY'))
Please find the attached text file which contains output of SHOW ENGINE
INNODB STATUS;
Cheers!
On Fri, Aug 14, 2015 at 3:40 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Tharindu,
Please find the attach text file which contains output of above command.
Cheers!
On Fri, Aug 14, 2015 at 1:03 PM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Ramith,
It seems this is not the exact same issue reported in [1]. For
investigating further can you connect to mysql database from
terminal/mysql
client and run the following command and share the output with us. We
should be able to see the database level errors caused from the output of
this command [2].
*SHOW ENGINE INNODB STATUS;*
[1] https://wso2.org/jira/browse/CARBON-15265
[2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe ram...@wso2.com
wrote:
$subject. Could we have a look?
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Thanks Regards,
*Johann Dilantha Nallathamby*
Technical Lead Product Lead of WSO2 Identity Server
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware
Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
$subject. Could we have a look? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
Hi Ramith, It seems this is not the exact same issue reported in [1]. For investigating further can you connect to mysql database from terminal/mysql client and run the following command and share the output with us. We should be able to see the database level errors caused from the output of this command [2]. *SHOW ENGINE INNODB STATUS;* [1] https://wso2.org/jira/browse/CARBON-15265 [2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html Thanks, TharinduE On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe ram...@wso2.com wrote: $subject. Could we have a look? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- Tharindu Edirisinghe Software Engineer | WSO2 Inc Identity Server Team Blog : tharindue.blogspot.com mobile : +94 775 181586 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
Hi Tharindu,
Please find the attach files which contains stack trace separately.
Cheers!
On Fri, Aug 14, 2015 at 3:55 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Indika,
We are looking to identify the issue. Can you also send us the stack trace
of the two scenarios separately.
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 3:50 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Above deadlock occurred when we remove topic subscription.
DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME =
'Q_tmp_192_168_1_21_41372_1' AND UM_TENANT_ID=-1234
We are getting another deadlock when we adding topic subscription also.
INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID, UM_TENANT_ID,
UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM UM_HYBRID_ROLE WHERE
UM_ROLE_NAME='Q_tmp_192_168_1_21_58252_1' AND UM_TENANT_ID=-1234), -1234,
(SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE UM_TENANT_ID=-1234 AND
UM_DOMAIN_NAME='PRIMARY'))
Please find the attached text file which contains output of SHOW ENGINE
INNODB STATUS;
Cheers!
On Fri, Aug 14, 2015 at 3:40 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Please find the attach text file which contains output of above command.
Cheers!
On Fri, Aug 14, 2015 at 1:03 PM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Ramith,
It seems this is not the exact same issue reported in [1]. For
investigating further can you connect to mysql database from terminal/mysql
client and run the following command and share the output with us. We
should be able to see the database level errors caused from the output of
this command [2].
*SHOW ENGINE INNODB STATUS;*
[1] https://wso2.org/jira/browse/CARBON-15265
[2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe ram...@wso2.com
wrote:
$subject. Could we have a look?
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
add_subscription_stack_trace
Description: Binary data
remove_subscription_stack_trace
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
Hi Tharindu,
Above deadlock occurred when we remove topic subscription.
DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME =
'Q_tmp_192_168_1_21_41372_1' AND UM_TENANT_ID=-1234
We are getting another deadlock when we adding topic subscription also.
INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID, UM_TENANT_ID,
UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM UM_HYBRID_ROLE WHERE
UM_ROLE_NAME='Q_tmp_192_168_1_21_58252_1' AND UM_TENANT_ID=-1234), -1234,
(SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE UM_TENANT_ID=-1234 AND
UM_DOMAIN_NAME='PRIMARY'))
Please find the attached text file which contains output of SHOW ENGINE
INNODB STATUS;
Cheers!
On Fri, Aug 14, 2015 at 3:40 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Please find the attach text file which contains output of above command.
Cheers!
On Fri, Aug 14, 2015 at 1:03 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Ramith,
It seems this is not the exact same issue reported in [1]. For
investigating further can you connect to mysql database from terminal/mysql
client and run the following command and share the output with us. We
should be able to see the database level errors caused from the output of
this command [2].
*SHOW ENGINE INNODB STATUS;*
[1] https://wso2.org/jira/browse/CARBON-15265
[2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe ram...@wso2.com
wrote:
$subject. Could we have a look?
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
=
150814 15:45:59 INNODB MONITOR OUTPUT
=
Per second averages calculated from the last 1 seconds
-
BACKGROUND THREAD
-
srv_master_thread loops: 1669 1_second, 1669 sleeps, 156 10_second, 238
background, 238 flush
srv_master_thread log flush and writes: 2757
--
SEMAPHORES
--
OS WAIT ARRAY INFO: reservation count 1095210, signal count 634234
Mutex spin waits 6843782, rounds 34981966, OS waits 893336
RW-shared spins 594791, rounds 10468841, OS waits 156859
RW-excl spins 214480, rounds 2478214, OS waits 35428
Spin rounds per wait: 5.11 mutex, 17.60 RW-shared, 11.55 RW-excl
LATEST DETECTED DEADLOCK
150814 15:45:27
*** (1) TRANSACTION:
TRANSACTION 1FC44D6, ACTIVE 0 sec fetching rows
mysql tables in use 3, locked 3
LOCK WAIT 4 lock struct(s), heap size 1248, 2 row lock(s), undo log entries 1
MySQL thread id 285, OS thread handle 0x1664, query id 19128689 192.168.1.22
root Sending data
INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID, UM_TENANT_ID,
UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM UM_HYBRID_ROLE WHERE
UM_ROLE_NAME='Q_tmp_192_168_1_21_58252_1' AND UM_TENANT_ID=-1234), -1234,
(SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE UM_TENANT_ID=-1234 AND
UM_DOMAIN_NAME='PRIMARY'))
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 113 page no 3 n bits 168 index `PRIMARY` of table
`carbondb`.`um_hybrid_role` trx id 1FC44D6 lock mode S locks rec but not gap
waiting
Record lock, heap no 94 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
0: len 4; hex 8107; asc ;;
1: len 4; hex 7b2e; asc.;;
2: len 6; hex 01fc44d4; asc D ;;
3: len 7; hex de0005c0030110; asc;;
4: len 26; hex 515f746d705f3139325f3136385f315f32315f34313532385f31; asc
Q_tmp_192_168_1_21_41528_1;;
*** (2) TRANSACTION:
TRANSACTION 1FC44D4, ACTIVE 0 sec fetching rows, thread declared inside InnoDB
407
mysql tables in use 3, locked 3
4 lock struct(s), heap size 1248, 2 row lock(s), undo log entries 1
MySQL thread id 260, OS thread handle 0x168c, query id 19128690 192.168.1.20
root Sending data
INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID, UM_TENANT_ID,
UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM UM_HYBRID_ROLE WHERE
UM_ROLE_NAME='Q_tmp_192_168_1_21_41528_1' AND UM_TENANT_ID=-1234), -1234,
(SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE UM_TENANT_ID=-1234 AND
UM_DOMAIN_NAME='PRIMARY'))
*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 113 page no 3 n bits 168 index `PRIMARY` of table
`carbondb`.`um_hybrid_role` trx id 1FC44D4 lock_mode X locks rec but not gap
Record lock, heap no 94 PHYSICAL RECORD: n_fields 5; compact format; info bits 0
0: len
Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
Hi Indika,
We are looking to identify the issue. Can you also send us the stack trace
of the two scenarios separately.
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 3:50 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Above deadlock occurred when we remove topic subscription.
DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME =
'Q_tmp_192_168_1_21_41372_1' AND UM_TENANT_ID=-1234
We are getting another deadlock when we adding topic subscription also.
INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID, UM_TENANT_ID,
UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM UM_HYBRID_ROLE WHERE
UM_ROLE_NAME='Q_tmp_192_168_1_21_58252_1' AND UM_TENANT_ID=-1234), -1234,
(SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE UM_TENANT_ID=-1234 AND
UM_DOMAIN_NAME='PRIMARY'))
Please find the attached text file which contains output of SHOW ENGINE
INNODB STATUS;
Cheers!
On Fri, Aug 14, 2015 at 3:40 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Please find the attach text file which contains output of above command.
Cheers!
On Fri, Aug 14, 2015 at 1:03 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Ramith,
It seems this is not the exact same issue reported in [1]. For
investigating further can you connect to mysql database from terminal/mysql
client and run the following command and share the output with us. We
should be able to see the database level errors caused from the output of
this command [2].
*SHOW ENGINE INNODB STATUS;*
[1] https://wso2.org/jira/browse/CARBON-15265
[2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe ram...@wso2.com
wrote:
$subject. Could we have a look?
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
Hi Tharindu, Please find the attach text file which contains output of above command. Cheers! On Fri, Aug 14, 2015 at 1:03 PM, Tharindu Edirisinghe tharin...@wso2.com wrote: Hi Ramith, It seems this is not the exact same issue reported in [1]. For investigating further can you connect to mysql database from terminal/mysql client and run the following command and share the output with us. We should be able to see the database level errors caused from the output of this command [2]. *SHOW ENGINE INNODB STATUS;* [1] https://wso2.org/jira/browse/CARBON-15265 [2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html Thanks, TharinduE On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe ram...@wso2.com wrote: $subject. Could we have a look? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- Tharindu Edirisinghe Software Engineer | WSO2 Inc Identity Server Team Blog : tharindue.blogspot.com mobile : +94 775 181586 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Indika Sampath Senior Software Engineer WSO2 Inc. http://wso2.com Phone: +94 716 424 744 Blog: http://indikasampath.blogspot.com/ = 150814 15:36:05 INNODB MONITOR OUTPUT = Per second averages calculated from the last 8 seconds - BACKGROUND THREAD - srv_master_thread loops: 1596 1_second, 1596 sleeps, 149 10_second, 230 background, 230 flush srv_master_thread log flush and writes: 2684 -- SEMAPHORES -- OS WAIT ARRAY INFO: reservation count 1095161, signal count 634173 Mutex spin waits 6839180, rounds 34975078, OS waits 893318 RW-shared spins 594744, rounds 10468101, OS waits 156838 RW-excl spins 214442, rounds 2477679, OS waits 35423 Spin rounds per wait: 5.11 mutex, 17.60 RW-shared, 11.55 RW-excl LATEST DETECTED DEADLOCK 150814 15:05:40 *** (1) TRANSACTION: TRANSACTION 1FC34F9, ACTIVE 0 sec fetching rows mysql tables in use 1, locked 1 LOCK WAIT 10 lock struct(s), heap size 1248, 7 row lock(s), undo log entries 2 MySQL thread id 234, OS thread handle 0x9f4, query id 19097990 192.168.1.20 root updating DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME = 'Q_tmp_192_168_1_21_41372_1' AND UM_TENANT_ID=-1234 *** (1) WAITING FOR THIS LOCK TO BE GRANTED: RECORD LOCKS space id 113 page no 3 n bits 136 index `PRIMARY` of table `carbondb`.`um_hybrid_role` trx id 1FC34F9 lock_mode X locks rec but not gap waiting Record lock, heap no 47 PHYSICAL RECORD: n_fields 5; compact format; info bits 0 0: len 4; hex 8066; ascf;; 1: len 4; hex 7b2e; asc.;; 2: len 6; hex 01fc3174; asc 1t;; 3: len 7; hex a50e810110; asc;; 4: len 26; hex 515f746d705f3139325f3136385f315f32315f34313338325f31; asc Q_tmp_192_168_1_21_41382_1;; *** (2) TRANSACTION: TRANSACTION 1FC34FA, ACTIVE 0 sec fetching rows, thread declared inside InnoDB 484 mysql tables in use 1, locked 1 8 lock struct(s), heap size 1248, 4 row lock(s), undo log entries 1 MySQL thread id 205, OS thread handle 0x170c, query id 19097991 192.168.1.20 root updating DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME = 'Q_tmp_192_168_1_21_41382_1' AND UM_TENANT_ID=-1234 *** (2) HOLDS THE LOCK(S): RECORD LOCKS space id 113 page no 3 n bits 136 index `PRIMARY` of table `carbondb`.`um_hybrid_role` trx id 1FC34FA lock mode S locks rec but not gap Record lock, heap no 47 PHYSICAL RECORD: n_fields 5; compact format; info bits 0 0: len 4; hex 8066; ascf;; 1: len 4; hex 7b2e; asc.;; 2: len 6; hex 01fc3174; asc 1t;; 3: len 7; hex a50e810110; asc;; 4: len 26; hex 515f746d705f3139325f3136385f315f32315f34313338325f31; asc Q_tmp_192_168_1_21_41382_1;; *** (2) WAITING FOR THIS LOCK TO BE GRANTED: RECORD LOCKS space id 113 page no 3 n bits 136 index `PRIMARY` of table `carbondb`.`um_hybrid_role` trx id 1FC34FA lock_mode X locks rec but not gap waiting Record lock, heap no 34 PHYSICAL RECORD: n_fields 5; compact format; info bits 32 0: len 4; hex 805b; asc[;; 1: len 4; hex 7b2e; asc.;; 2: len 6; hex 01fc34f9; asc 4 ;; 3: len 7; hex 7d001c40080351; asc } @ Q;; 4: len 26; hex 515f746d705f3139325f3136385f315f32315f34313337325f31; asc Q_tmp_192_168_1_21_41372_1;; *** WE ROLL BACK TRANSACTION (2) TRANSACTIONS Trx id counter 1FC3744 Purge done for trx's n:o 1FC3739 undo n:o 0 History list length 768 LIST OF TRANSACTIONS FOR EACH SESSION: ---TRANSACTION 0, not started MySQL thread id 244, OS thread handle 0x12f0, query id 19102478 192.168.1.52 root checking query cache for query /* ApplicationName=DBeaver Enterprise 3.4.2 - Main */ SHOW ENGINE INNODB STATUS ---TRANSACTION 1FC34B3, not started MySQL thread id 240, OS thread handle
