home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 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 IT01133 Status: Closed

JSON LISTENER DOES NOT START ON WINDOWS

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
The start of the json listener fails since IDS 12.10.FC3. 
 
> EXECUTE FUNCTION task("start json listener"); 
returns 
> (expression)  Can not locate java 
(C:\PROGRA~1\IBM\IDS-12~1.FC3\extend\krakatoa\jre\bin\java) 
 
Running the same with "FUNCTION admin" fails too. 
 
The error message is quite clear. The fully qualified executable 
does not exist. The binary name has the file-type extension 
".EXE" and this file exists. The error is caused by the wrong 
call for the JAVA binary.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows users wanting to control the JSON Wire listener from * 
* the sysadmin database.                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IDS-12.10.xC5                                      * 
****************************************************************
Local Fix:
You can copy the existing file at the same location from 
java.exe to java and then the start of the json listener is 
successful.
Solution
Problem Fixed In IDS-12.10.xC5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.04.2014
16.10.2015
16.10.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC4.W1 FixList
12.10.xC5 FixList
12.10.xC5.W1 FixList