KB-1756 Plugin fails to deploy with "Cannot open JAR file for reading" error in app server log

Jordan Horwat — Wed, 24 Oct 2018 14:49:19 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 10/24/2018 2:49:19 PM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Cause

The above error is caused by one of the following:

The plugin does not have the correct permissions or ownership to be executed by the user running Appian.
The plugin files are corrupt.

Action

Based on the determined cause above, proceed with one of the following actions, respectively:

Ensure that the plugin has plugin the correct permissions and ownership to be executed by the user running Appian.
Redeploy the original plugin into Appian.
- If deploying fails again, the plugin may still be corrupt. Rebuild the plugin JAR and redeploy to resolve.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: plug-ins, plugins

DRAFT KB-XXXX Plugin fails to deploy with error in app server log with "Cannot open JAR file for reading" error

Daniel DeVeau — Wed, 24 Oct 2018 10:36:57 GMT

Revision 11 posted to Appian Knowledge Base by Daniel DeVeau on 10/24/2018 10:36:57 AM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Cause

The above error is caused by one of the following:

The plugin does not have the correct permissions or ownership to be executed by the user running Appian.
The plugin files are corrupt.

Action

Based on the determined cause above, proceed with one of the following actions, respectively:

Ensure that the plugin has plugin the correct permissions and ownership to be executed by the user running Appian.
Redeploy the original plugin into Appian.
- If deploying fails again, the plugin may still be corrupt. Rebuild the plugin JAR and redeploy to resolve.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: shared components, plugins

DRAFT KB-XXXX Plugin fails to deploy with error in app server log with "Cannot open JAR file for reading" error

Daniel DeVeau — Wed, 24 Oct 2018 10:35:58 GMT

Revision 10 posted to Appian Knowledge Base by Daniel DeVeau on 10/24/2018 10:35:58 AM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Cause

The above error is caused by one of the following:

The plugin does not have the correct permissions or ownership to be executed by the user running Appian.
The plugin files are corrupt.

Action

Based on the determined cause above, proceed with one of the following actions, respectively:

Ensure that the plugin has plugin the correct permissions and ownership to be executed by the user running Appian.
Re-deploy the original plugin into Appian.
- If deploying fails again, the plugin may still be corrupt. Rebuild the plugin JAR and re-deploy to resolve.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: shared components, plugins

DRAFT KB-XXXX Plugin fails to deploy with error in app server log with "Cannot open JAR file for reading" error

Daniel DeVeau — Wed, 24 Oct 2018 10:35:21 GMT

Revision 9 posted to Appian Knowledge Base by Daniel DeVeau on 10/24/2018 10:35:21 AM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Cause

The above error is caused by one of the following:

The plugin does not have the correct permissions or ownership to be executed by the user running Appian.
The plugin files are corrupt.

Action

Based on the determined cause above, proceed with one of the following actions, respectively:

Ensure that the plugin has plugin the correct permissions and ownership to be executed by the user running Appian.
Re-deploy the original plugin into Appian.
- If re-deploying fails to resolve the issue, the plugin may still be corrupt. Rebuild the plugin JAR and deploy again to resolve.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: shared components, plugins

DRAFT KB-XXXX Plugin fails to deploy with error in app server log with "Cannot open JAR file for reading" error

Jordan Horwat — Wed, 24 Oct 2018 09:48:02 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 10/24/2018 9:48:02 AM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Cause

The above error is caused by one of the following:

The plugin does not have the correct permissions or ownership to be executed by the user running Appian.
The plugin files are corrupt.

Action

Based on the determined cause above, proceed with one of the following actions, respectively:

Ensure that the plugin has plugin the correct permissions and ownership to be executed by the user running Appian.
Re-import the original plugin into Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: shared components, plugins

DRAFT KB-XXXX Plugin fails to deploy with error in app server log with "Cannot open JAR file for reading" error

Jordan Horwat — Wed, 24 Oct 2018 09:47:16 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 10/24/2018 9:47:16 AM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Cause

The above error is caused by one of the following:

The plugin does not have the correct permissions or ownership to be executed by the user running Appian.
The plugin files are corrupt.

Action

Based on the determined cause above, proceed with the following actions, respectively:

Ensure that the plugin has plugin the correct permissions and ownership to be executed by the user running Appian.
Re-import the original plugin into Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: shared components, plugins

KB-XXXX Plugin fails to deploy with error in app server log, "Cannot open JAR file for reading"

Jordan Horwat — Wed, 24 Oct 2018 09:46:48 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 10/24/2018 9:46:48 AM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Cause

The above error is caused by one of the following:

The plugin does not have the correct permissions or ownership to be executed by the user running Appian.
The plugin files are corrupt.

Action

Based on the determined cause above, proceed with the following actions, respectively:

Ensure that the plugin has plugin the correct permissions and ownership to be executed by the user running Appian.
Re-import the original plugin into Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: shared components, plugins

KB-XXXX Plugin fails to deploy with error in app server log, "Cannot open JAR file for reading"

Daniel DeVeau — Tue, 23 Oct 2018 18:05:16 GMT

Revision 5 posted to Appian Knowledge Base by Daniel DeVeau on 10/23/2018 6:05:16 PM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Causes

Cause 1

The plugin does not have the correct permissions or ownership to be executed by the user running Appian.

Cause 2

The plugin files are corrupt.

Actions

For cause 1

Ensure that the plugin has plugin the correct permissions and ownership to be executed by the user running Appian.

For cause 2

Re-import the original plugin into Appian.

Affected Versions

This article applies to all versions of Appian.

Tags: shared components, plugins

Plugin fails to deploy with error in app server log, "Cannot open JAR file for reading"

Daniel DeVeau — Tue, 23 Oct 2018 17:48:24 GMT

Revision 4 posted to Appian Knowledge Base by Daniel DeVeau on 10/23/2018 5:48:24 PM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Causes

Cause 1

Cause 2

Action

Affected Versions

This article applies to all versions of Appian.

Tags: shared components, plugins

Plugin fails to deploy with error in app server log, "Cannot open JAR file for reading"

Daniel DeVeau — Tue, 23 Oct 2018 17:47:22 GMT

Revision 3 posted to Appian Knowledge Base by Daniel DeVeau on 10/23/2018 5:47:22 PM

Symptoms

A plugin fails to deploy, and the application server log shows the following error:

[Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Plug-in '<Plugin Name>.jar' (<Plugin Name>.jar) version 0.0: 'Cannot open JAR file for reading: <Path to plugin>/<Plugin name>.jar'

Causes

Cause 1

Cause 2

Action

Affected Versions

This article applies to all versions of Appian.

Tags: shared components, plugins

Some plugins fail to deploy with error in app server log, "Cannot open JAR file for reading"

Daniel DeVeau — Thu, 18 Oct 2018 18:38:08 GMT

Revision 2 posted to Appian Knowledge Base by Daniel DeVeau on 10/18/2018 6:38:08 PM

Symptoms

Causes

Cause 1

Cause 2

Action

Affected Versions

This article applies to all versions of Appian.

Tags: shared components, plugins

Some plugins fail to deploy with error in app server log, "Cannot open JAR file for reading"

Daniel DeVeau — Wed, 17 Oct 2018 21:53:38 GMT

Revision 1 posted to Appian Knowledge Base by Daniel DeVeau on 10/17/2018 9:53:38 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been addressed via AN-XXXXX in Appian X.X Hotfix Package X.
This issue has been addressed via AN-XXXXX in the following hotfixes/versions:
- List each specific hotfix package/version in ascending order by version.
This use case has been incorporated in Appian X.X Hotfix Package X.
This use case has been incorporated in the following versions/hotfixes:
- List each specific hotfix package/version in ascending order by version.

Note: When listing hotfixes, add a hyperlink to the Hotfix documentation for that version.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

Apply the latest hotfix to your Appian installation.
Upgrade to the latest version of Appian.
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

Affected Versions

This article applies to all versions of Appian.

Tags: shared components, plugins