Bug 781087 (SOA-3577) - Exception when Deploying ESB as archive through JON
Summary: Exception when Deploying ESB as archive through JON
Keywords:
Status: CLOSED UPSTREAM
Alias: SOA-3577
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Mark Little
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-11 16:23 UTC by David Tucker
Modified: 2025-02-10 03:14 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
JON 2.4.1, SOA-P 5.1, Fedora 15
Last Closed: 2025-02-10 03:14:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3577 0 Major Closed Exception when Deploying ESB as archive through JON 2013-01-17 16:25:38 UTC

Description David Tucker 2011-11-11 16:23:34 UTC
project_key: SOA

I am experiencing an issue when I try and deploy an ESB as a zipped archive through JON.  I get the following exception:

java.lang.Exception:Failed to distribute 'file:/opt/jboss-soa-p-5/jboss-as/server/demo/tmp/jopr-jbossas5-deploy-content3435882287890597057.tmp/esb-with-cxf-demo.esb' to 'esb-with-cxf-demo.esb' - cause: java.lang.RuntimeException:java.io.FileNotFoundException: /opt/jboss-soa-p-5/jboss-as/server/demo/deploy/esb-with-cxf-demo.esb (Is a directory) -> java.io.FileNotFoundException:/opt/jboss-soa-p-5/jboss-as/server/demo/deploy/esb-with-cxf-demo.esb (Is a directory)

Comment 1 Len DiMaggio 2011-11-11 18:39:28 UTC
Are you seeing the same issue as:  SOA-2970?

Comment 2 David Tucker 2011-11-11 19:01:19 UTC
No, the exception I get is the one listed in the description which I don't believe is the same thing as SOA-2970.  

Comment 4 Red Hat Bugzilla 2025-02-10 03:14:55 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.