For distributed platforms

Liberty profile: Developer Tools known restrictions

There are few known restrictions that apply when working with the WebSphere® Application Server Developer Tools for Eclipse.

See also Liberty profile: Runtime environment known restrictions.

List of known issues and restrictions:

Fix Pack 8550

EJB 3.1 restrictions

The tooling provides support for developing applications that use the full EJB 3.1 API. However, applications deployed on the Liberty profile should only use features included in EJB 3.1 Lite, which is a subset of the full specification. Applications deployed on the Liberty profile can also use features included in Message Driven Beans. See ejbLite-3.1 feature restrictions.

Projects that are required by web fragment projects are not automatically added to the Java build path

If you have a web application project that contains one or more web fragment projects, and the web application project has references in its deployment assembly page to projects that are required by the web fragment projects, then those dependent projects (such as the JPA and Utility projects) are not automatically added to the Java™ build path of the web fragment projects.

Manually add the dependent projects to the Java build path of the web fragment projects in order for them to compile.

Unable to interact with the Liberty profile server after modifying the console log level settings

There is a known limitation when the console log level is set to WARNING, ERROR, or OFF. The workbench has problems interacting with the Liberty profile server, such as cannot start, stop, or publish to the server. For example, the workbench is unable to start the Liberty profile server and the following timeout error message displays:
This is a screen capture of the server timeout error message: Server WebSphere Application Server V8.5 Liberty Profile at localhost was unable to start within 60 seconds. If the server requires more time, try increasing the timeout in the server editor.

The console log level (consoleLogLevel) is an attribute of the logging configuration element in the server configuration (server.xml) file with the following range options: INFO, AUDIT, WARNING, ERROR, and OFF. AUDIT is the default value for the console log level settings. For more details, search for the consoleLogLevel attribute in the For distributed platforms For IBM i platforms Liberty profile: Configuration elements in the server.xml topic.

To workaround this known limitation, specify INFO or use the default AUDIT setting for the console log level:
  1. In the Servers view, expand your Liberty Profile server.
  2. Right-click the Server Configuration[server.xml] node and select Open.
  3. In the Server Configuration editor and under the Configuration Structure section, expand Server Configuration node. The next step depends if the Logging element is available:
    • If the Logging element is available, select it and under the Logging section of the server configuration editor, use the drop-down menu for the Console log level field, and select either the AUDIT or INFO option. Type Ctrl + s to save your changes in the editor.
    • If the Logging element is not available, the workbench is already using the default AUDIT setting. As a result, you might be experiencing a different problem that is causing interaction failures between the workbench and the Liberty Profile server.
    .

For more information about limitations, see Known problems and limitations for WebSphere Application Server Developer Tools for Eclipse.


Icon that indicates the type of topic Reference topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Monday, 21 April 2014
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=r_limitations
File name: r_limitations.html