[MCOL-1746] Error while connecting to the MariadDB maxscale with tx Created: 2018-09-20  Updated: 2023-10-26  Resolved: 2019-01-21

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.1.6
Fix Version/s: 1.1.7

Type: Bug Priority: Major
Reporter: Abirlal Adhikari Assignee: Andrew Hutchings (Inactive)
Resolution: Fixed Votes: 0
Labels: connect-engine, upstream
Environment:

Centos 7

Epic/Theme: server

 Description   

While I tried connecting my Mariadb-TX server from AX using mxs_adapter and cdc connectors I get the following error:

2018-09-20 16:12:38 [cdc_test.cdc_tab] MaxScale connection could not be
created: Exception caught: basic_string::_S_create
2018-09-20 16:12:38 [cdc_test.cdc_tab] Received fatal signal 11
mxs_adapter[0x42bfd5]
/lib64/libpthread.so.0(+0xf6d0)[0x7f4081ba96d0]
mxs_adapter(mysql_close+0x12)[0x434b02]
mxs_adapter(_Z11streamTableSsSs+0x26a)[0x41d89a]
mxs_adapter(_ZNSt6thread5_ImplISt12_Bind_simpleIFPFvSsSsESsSsEEE6
_M_runEv+0x37)[0x41eeb7]
/lib64/libstdc++.so.6(+0xb5070)[0x7f4080e5b070]
/lib64/libpthread.so.0(+0x7e25)[0x7f4081ba1e25]
/lib64/libc.so.6(clone+0x6d)[0x7f40805bfbad]
Segmentation fault (core dumped)

How to resolve this?

 Comments   
Comment by markus makela [ 2018-09-21 ]

What version of mxs_adapter were you using?

Comment by Abirlal Adhikari [ 2018-09-24 ]

my mxs_adapter version is 1.1.6

Comment by Andrew Hutchings (Inactive) [ 2018-09-24 ]

Fix merged as part of https://github.com/mariadb-corporation/mariadb-columnstore-data-adapters/pull/64

Comment by Abirlal Adhikari [ 2018-09-24 ]

pardon me, but I am not understanding the solution totally so please can you walk me through it?

Comment by Elena Kotsinova (Inactive) [ 2018-09-25 ]

abir_gozo it is expected that fix will be included in v.1.1.7
Could you please give us more detailed information about your environment and configuration you prepared.
Also command you run will be helpful.
This is to be sure that we are fixing the correct issue.

Comment by Andrew Hutchings (Inactive) [ 2019-01-21 ]

The problem is due to a library linking problem in previous versions which has since been fixed

Generated at Thu Feb 08 02:31:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.