IBM Support

Synchronization problems in WebSphere Integration Developer V6 test environment servers

Technote (troubleshooting)


In WebSphere Integration Developer V6, you might find that a test environment server (such as WebSphere Process Server) occasionally experiences one or more of the following symptoms.


  • The message "Publishing failed" is displayed when attempting to start the server.

  • The server status remains at "Stopped" when an application is republished and a "Publishing (100%)" message might be displayed indefinitely.

  • The server status remains at "Stopped" when the workbench is shut down and restarted without first stopping the server.

  • The server status remains at "Starting" indefinitely and might never change to "Started".


Regardless of the server status that is displayed, the preceding problems are all related to the fact that there are one or more rogue java.exe server processes still running that are preventing the server from starting or restarting.

Resolving the problem

Restarting WebSphere Integration Developer will not terminate the rogue server processes. To terminate the processes, you must complete the following steps:

  1. Close WebSphere Integration Developer.

  2. Using Task Manager or a similar mechanism, locate any java.exe server processes and terminate them.

  3. Open WebSphere Integration Developer.

  4. Start the server as usual.

Generally, this approach will resolve many of the synchronization problems that you might experience when working with test environment servers.

If you are still experiencing problems with the test environment servers, you can also try changing the server connection type from RMI to SOAP. Although RMI is intended to provide improved communication with the server, SOAP is designed to be more compatible with firewalls and it is more tolerant of security settings. As a result, SOAP is often a better choice if you are experiencing server problems that you cannot seem to resolve. To change the server connection type, complete the following steps:
  1. In the Servers view of WebSphere Integration Developer, double-click your server top open the server configuration editor.

  2. In the Server section of the editor, select the SOAP radio button.

  3. Press Ctrl-S to save your changes and close the editor.

  4. Start the server (or restart the server if it is already running).
You might be able to resolve certain problems by simply upgrading to the latest fixes for WebSphere Integration Developer and WebSphere Process Server using the Rational Product Updater (RPU). The latest fixes can be found at the following sites:
The remainder of this technote presents several detailed solutions to the specific problem of the server status remaining "Starting" indefinitely. However, many of the solutions might also apply to the other server synchronization problems listed at the beginning of this technote.

There are potentially many causes for the problem of the server status remaining "Starting..." indefinitely. Below is a list of a few of the most common potential causes, with the solution or workaround for each one:
  • Cause: Either the SOAP connector port or the ORB bootstrap port specified in the server configuration editor of the Servers view differs from the port values specified in the test environment server.

    Solution: When you create a new version 6 server profile, the profile creation wizard automatically assigns new port values for this new server profile. The SOAP connector port and the ORB bootstrap port (that is, RMI) are important to WebSphere Integration Developer, because either one of these ports are used for communicating with version 6 servers.

    You must ensure that the port specified in the WebSphere Integration Developer server configuration editor matches the corresponding port that the profile creation wizard generated. The default ORB bootstrap port is 2809 while the default SOAP connector port is 8880.

    It has been observed that in general, RMI does not work well when security is enabled, or even at times when security is not enabled. It is best to use SOAP if you encounter any problems. This is due to version 6 server limitations that are under investigation for future releases and are not discussed in this technote. See the following related information
    RMI option in WebSphere Test Environment 6.0. fails to start server

    Note: If you cannot recall the SOAP and RMI port numbers for "your profile", and you are not familiar with using the administrative console and starting the server from the command line, the port numbers can be found in the following file:

    <WID Install Dir>\bi_v6\profiles\<myprofile>\


    <Some other myprofile location>\config\cells

    The corresponding RMI and SOAP port number elements in serverindex.xml should be similar to:

    . . .
    <specialEndpoints  xmi:id="NamedEndPoint_1146785522658" endPointName="BOOTSTRAP_ADDRESS">
    <endPoint xmi:id="EndPoint_1146785522658"
    host="" port="
    <endPoint xmi:id="EndPoint_1146785522659"
    host="" port="
    . . .

    Ensure that you have upgraded to the latest fixes for WebSphere Integration Developer and WebSphere Process Server using the Rational Product Updater (RPU). These fixes can be found at:
    To make sure the runtime update succeeded, check the following directory:

    update directory>\

    If security is not enabled and you experience problems, especially after an update, go to section "Delete and replace the profile" provided further down in this technote.

  • Cause: Global security has been enabled in the server but not in the Servers view.

    Solution: When you enable global security on a version 6 server, you also need to put that information into WebSphere Integration Developer so that WebSphere Integration Developer is able to securely communicate with the server. You can do this by entering the username and password in the Security section of the server configuration editor. Also see the document, Console output fails to display in the v6 WebSphere Test Environment when global security is enabled.

  • Cause: Multiple version 6 test environment servers started on the same machine all use the same JVM debug port (7777).

    Solution: Change the server's JVM debug port, as documented in Starting multiple v6 WebSphere Test Environment servers in debugging mode.

  • Cause: The test environment does not work if the Proxy settings option is enabled in the Preferences window. If proxy authentication is enabled, the console window needs to authenticate to the proxy server in order to read from the version 6 server logs. Currently, the server architecture does not enable it to authenticate.

    Solution: To work around this issue, you can do one of the following:
    • Disable proxy authentication if it is not needed:
      1. Go to Window > Preferences > Internet > Proxy settings.

      2. If you have any settings there:
        1. Temporarily remove those settings.

        2. Restart WebSphere Integration Developer.

        3. Start the server to see that it starts and that you receive the console messages.

      This action should be enough on its own if you do not need proxy authentication (that is, you are not behind a firewall).

    • Keep Proxy settings enabled and go to:
      1. Windows > Preferences > Install/Update

      2. Click OK or Cancel.

      You do not need to enter any information or change any settings. The OK/Cancel action loads the Update Manager plug-ins so that a becomes available to the WebSphere Integration Developer JVM. This causes a dialog prompt to be displayed the first time that authentication is required. Now, whenever it tries to authenticate, you will receive an authentication window and it should allow you to receive console output and the server should finish starting.

      This would need to be done every time WebSphere Integration Developer is started.

    Note: This is a known problem with the WebSphere Integration Developer version 6 server tooling integration. The way that the server tooling receives the console information is by a servlet that is running on the version 6 test environment (the file is called Transfer.ear and TransferSecure.ear, depending on whether security is enabled). The server tools request the SystemOut.log and SystemErr.log files by composing an HTTP request using this servlet. If a proxy has been configured for the WebSphere Integration Developer JVM (by way of the Proxy Settings page), then anytime the console information is requested, it will try to go through this proxy. Normally this would not be a problem, but if proxy authentication is required, the server does not know how to handle this challenge (as a has not been implemented), and therefore, the request for the console is not fulfilled. This is an architectural limitation for version 6 servers at this time.

  • Cause: Some version 6 issues related to server profiles can leave the server in the "Starting. . ." state:
    1. If the computer name was changed, the default or any other existing profile will still use the old computer name. The solution is to delete the existing profiles (see step 2), and create a new profile. See also the Related Information items for creating and deleting a profile.

    2. A profile can only be removed or deleted using the command:

      wasprofile.bat -delete -profileName {your profile name}

      For example, at the command prompt, from <WID_install_dir>\runtimes\bi_v6\bin\

      wasprofile.bat -delete -profileName AppSrv01

      Note: The following user scenario illustrates what occurs when an incorrect method of deleting the profile is attempted:

      The following directory for the profile AppSrv01 was deleted in an attempt to remove the profile:


      A new profile behAppSrv was created, making sure to not specify the profile to run as a Windows service. Next, the server configuration in WebSphere Integration Developer was configured to run profile behAppSrv. On server Start, the following wsadmin server trace showed:

      . . .
      WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: Failed to get a connection with IP address associated with hostname localhost
      WASX7213I: This scripting client is not connected to a server process;please refer to the log file {WID Install Dir}\runtimes\bi_v6\profiles\AppSrv01\logs\wsadmin.traceout for additional information.
      WASX8011W: AdminTask object is not available.
      Uninstall filetransfer -cell VFEL07L1D521Node05Cell -node VFEL07L1D521Node05 -server server1 Operation FAILED!
      WASX7206W: The application management service is not running. Application management commands will not run.
      . . .

      Version 6 servers keep a reference to profiles, so it is not possible to delete a profile by deleting the directory. You must use the wasprofile.bat command as shown in Step 2 above.

  • Delete and replace the profile. If the server still does not work, and especially if security is not enabled, it is possible that you have a bad profile. The profile might sometimes not be useable after updating version 6 servers.

    Note: The v6 server update installer updates the core product files in a WebSphere server product. Service in a maintenance package might update the Profile templates. Some maintenance packages provide required service for existing profiles in addition to service for the core product files. Each maintenance package that has profile maintenance provides a script that changes the profile. The update installer prompts you to back up your configuration when installing a maintenance package that has required maintenance for profiles. This might be missed in a silent or automated install such as using the WebSphere Integration Developer version 6 Rational Product Updater (RPU). Consult the actual version 6 update readmes and install instructions for the test environment servers, and version 6 server support, if in doubt.

    If the profile does not have too much critical information, it is often easier or faster to delete the profile and create a new one.

    Delete the profile per the instructions WebSphere Application Server: Deleting a profile.

    The full option command:

    wasprofile.bat -delete -profile {Name profile_name}

    Can be run from:


    Or from the profile itself:

    <WID_install_dir>\runtimes\bi_v6\profiles\profile_name\bin: wasprofile.bat -delete

    After deleting the profile, make sure you also delete the profile directory:


    Then create a new profile using the following information:
    Note: record the SOAP and RMI port numbers when creating the new profile. RMI is not recommended for starting the server.

  • A re-install might sometimes be necessary if the server cannot start; for example, if none of the above applies or have not helped, and you see the error message: serverlaunch but failed initialization. To re-install, consult the following document, Install of the Rational Application Developer 6.x WebSphere Test Environment 6.0 server failed on Windows Operating System.

  • Contact WebSphere Integration Developer V6 support if these suggestions do not help.

Related information
The following related information mainly applies to Rational Application Developer (on which WebSphere Integration Developer is built), but the related information is still relevant and helpful to users of WebSphere Integration Developer and WebSphere Process Server.

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational Software Architect V7 Integrated WebSphere Test Environment Linux, Windows 6.0,, 6.0.1,
Software Development Rational Web Developer for WebSphere Software Integrated Test Environment Windows, Linux 6.0,,,
Software Development Rational Application Developer for WebSphere Software Integrated Test Environment Windows, Linux 6.0,, 6.0.1,

Document information

More support for: WebSphere Integration Developer
Test and deployment tools

Software version: 6.1, 6.1.2, 6.2

Operating system(s): Linux, Windows

Reference #: 1264397

Modified date: 04 October 2007

Translate this page: