A fix is available
APAR status
Closed as program error.
Error description
The problem occurs when a worklight runtime has applications deployed and the WebSphere Application Server is restarted When the Worklight console is launched, after selecting the runtime, the error "FWLSE0023E: application 'xxx' not found,please redeploy.[project xxxx]' appears. In the WAS log file the following exception is emitted: StatusMessage E StatusMessage createStatusMessage Preparation to deploy 'xxxxxx' failed java.io.IOException: Connection to <url> refused while accessing Worklight artifact URL. The exception is due to the WebSphere Application Server startup order. The TCP listeners are started after all applications have started do the HTTP and HTTPS ports are not avaible to the applications when they execute code at the startup.
Local fix
Disable the automatic startup of the Worklight runtimes application in the WebSphere Application Server console and start them after the application server is completely started.
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of the Worklight console running on Websphere * * Application Server * **************************************************************** * PROBLEM DESCRIPTION: * * After starting the WAS server, when connecting to the * * Worklight console and selecting the runtime, the following * * error is displayed : * * Will give the error "FWLSE0023E:application '<application * * name>' not found,please redeploy.[project <prohect name>]' * * In the WAS SytemOut.log the following exception is emitted : * * * * 0000000a StatusMessage E StatusMessage createStatusMessage * * Preparation to deploy 'xxxxxx' failed * * java.io.IOException: * * Connection to <host> refused while accessing Worklight * * artifact URL: <url> * * * * The error occurs when there is one or more applications * * deployed in the runtime. * **************************************************************** * RECOMMENDATION: * * - * ****************************************************************
Problem conclusion
This problem occurs during the start of the runtime when it synchronizes the applications. The runtime needs to invoke a REST service but in WebSphere Application Server the TCP listeners are only started after all applications have started. It means that the HTTP(s) port is not available when code is executed during the startup of the application.
Temporary fix
Comments
APAR Information
APAR number
PI25268
Reported component name
WORKLIGHT CONSU
Reported component ID
5725I4301
Reported release
620
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-09-08
Closed date
2014-09-17
Last modified date
2014-09-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WORKLIGHT CONSU
Fixed component ID
5725I4301
Applicable component levels
R620 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSZH4A","label":"IBM Worklight"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
17 October 2021