Studio throws "An existing instance of BWAppNode is already running. Please terminate the Java process before relaunching the Debugger" warning while launching the Studio debugger.

Studio throws "An existing instance of BWAppNode is already running. Please terminate the Java process before relaunching the Debugger" warning while launching the Studio debugger.

book

Article ID: KB0074546

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks -
Not Applicable -

Description

Resolution:

If you check Run configuration > Arguments > VM Arguments in Eclipse business studio, you can see that there exists a VM argument named '-Dorg.osgi.service.http.port=8090'. This parameter specifies BW AppNode's HTTP port. The port specified for this argument is used by the BW Management APIs to communicate with the AppNode i.e JVM OS process. If the port specified in this argument is already in use by any other appnode or any other OS process, Business Studio cannot launch the appnode and present this warning message. You can use "netstat -an" or external tool such as 'Cports' to check if the port that you want to use in Business Studio is being used by another process. You can then either free up that port or assign a new one in Studio.

One of the common cases this warning can be seen is BusinessStudio crash while the application is running or being debugged. In such cases, the eclipse process is crashed, however; the appnode's OS process still runs in the background, still occupying the port. In such cases, if the workspace is restarted and the user tries to start/debug the application, they will see this warning. In such cases, the user can simply search the existing running appnode process and kill it to re-launch the application.

Issue/Introduction

Studio throws "An existing instance of BWAppNode is already running. Please terminate the Java process before relaunching the Debugger" warning while launching the Studio debugger.