Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
A user set up a JDBC connection to a group of two Connection Managers and asked how to make clients fail over when one CM is down. Art Kagel explained that connections to a downed CM time out and clients then try the other, with INFORMIXCONTIME and INFORMIXCONRETRY controlling retry/timeout behaviour. The poster still got random exceptions; Jinming Xiao spotted that his sqlhosts entries were wrong — the group name in the g= options (and the e= end entry) didn't match the group ifx_lab_ps. After correcting the sqlhosts definitions, the poster confirmed it was his mistake and the issue was resolved.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Thanks a lot, I managed to configure it.
Another question related to this. I created a group made of 2 connection
managers.
Is there a way to control the fail over of one of the conection managers in
the group so that people connecting to it won't end in the cm that is down?.
If one of the connection managers is down then connection attempts to it
will time out and your users will fail over to the other CM. The
environment variables INFORMIXCONTIME and INFORMIXCONRETRY control this
time out functionality. The client libraries will attempt to connect
INFORMIXCONRETRY times over INFORMIXCONTIME seconds so the longest time out
period is INFORMIXCONTIME/INFORMIXCONRETRY
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Mon, Apr 25, 2016 at 11:42 AM, JACOBO BALBUENA <jacobo.bc@gmail.com>
wrote:
> Thanks a lot, I managed to configure it.
> Another question related to this. I created a group made of 2 connection
> managers.
>
> Is there a way to control the fail over of one of the conection managers in
> the group so that people connecting to it won't end in the cm that is
> down?.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a11396814d69ed80531511454
I must be doing something wrong, with both cm up everything works ok always.
When I turn one cm down I get exceptions randomly. Am I missing something else
to force the swtich in case of failover?
jdbc:informix-sqli:informixserver=ifx_lab_ps;SQLH_TYPE=FILE;SQLH_FILE=/opt/infor
mix/etc/sqlhosts;INFORMIXCONTIME=5; INFORMIXCONRETRY=1;
sqlhost part :
ifx_lab_ps group - - c=1,e=ifx_proxy32
ifx_proxy_ps_1 onsoctcp lab-informix-0004.xunta.local 9095 g=ifx_proxy_ps
ifx_proxy_ps_2 onsoctcp lab-informix-0005.xunta.local 9095 g=ifx_proxy_ps
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.