Bug 1275260 - NoSuchFileException when deleting a project for the first time
NoSuchFileException when deleting a project for the first time
Status: VERIFIED
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: Business Central (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity medium
: ER5
: 6.2.0
Assigned To: manstis
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-26 08:05 EDT by Zuzana Krejčová
Modified: 2016-07-31 21:19 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
server log from the moment of finished deployment (34.40 KB, text/plain)
2015-10-26 08:05 EDT, Zuzana Krejčová
no flags Details

  None (edit)
Description Zuzana Krejčová 2015-10-26 08:05:09 EDT
Created attachment 1086483 [details]
server log from the moment of finished deployment

Description of problem:
The first time user deletes a project, NoSuchFileException is logged into the server log. Any subsequent project deletions seem to be fine. The prject gets deleted anyway.
Full stacktrace is in the attachment.


Version-Release number of selected component (if applicable):
6.2 ER4


Steps to Reproduce:
1. Start up a clean installation of BRMS/BPM Suite.
2. If there is no example repostiory + project, create some.
3. Go to Project Authoring, open the project editor for the (example) project and delete the project.
4. Check the server log.


Actual results:
Project is deleted, but server log shows NoSuchFileException.


Expected results:
Project is deleted, server log is clean.
Comment 1 manstis 2015-10-26 08:12:58 EDT
Looking at the stack trace, this is exactly the same error as that in the referenced BZ. Setting to MODIFIED for QE to verify.

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