home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC10 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT40991 Status: Closed

CUSTOMERS USING THREAD CLASS SETNAME() CAN CAUSE CONNECTION ISSUES -908 ON
CLIENT / -408 ON SERVER

product:
IBM CSDK / 5724C2381 / 450 - CSDK 4.50
Problem description:
The JDBC driver gathers information about the Application with
this call:
AppName = "Thread[id:" + Thread.currentThread().getId() + ",
name:" + Thread.currentThread().getName()
+ ", path:" +
getClass().getProtectionDomain().getCodeSource().getLocation().g
etPath() + ']';

In case setName() is used with special characters and spaces,
server may reject the connection.

14:28:23  listener-thread@asfpfutl.c:1503: err = -408: oserr =
0: errstr = from machine1 to server server1 : Invalid message
type received from the sqlexec process.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix JDBC prior to 4.50.JC9.                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description.                                       *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix JDBC 4.50.JC9.                           *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix JDBC prior to 4.50.JC9.                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description.                                       *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix JDBC 4.50.JC9.                           *
****************************************************************
Comment
Fixed in Informix JDBC 4.50.JC9.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.05.2022
05.10.2022
05.10.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)