Bug 913560 - [EAP 6.1] Updating periodic file handler fails: JBAS014746: file may not be null
Summary: [EAP 6.1] Updating periodic file handler fails: JBAS014746: file may not be null
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 6
Version: JON 3.1.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: JON 3.2.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 911633 915469 948264
TreeView+ depends on / blocked
 
Reported: 2013-02-21 13:33 UTC by Radim Hatlapatka
Modified: 2013-04-04 12:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 948264 (view as bug list)
Environment:
Last Closed: 2013-04-04 12:57:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Radim Hatlapatka 2013-02-21 13:33:23 UTC
Description of problem:

When trying to change logging level of periodic file handler via JON, it fails with:
{JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-3=JBAS014746: file may not be null}}, rolled-back=true
Version-Release number of selected component (if applicable):


Version-Release number of selected component (if applicable):
EAP 6.1.0.DR4 and JON 3.1.2


How reproducible: always


Steps to Reproduce:
1. import EAP 6.1 standalone
2. create Periodic File Handler resource under logging subsystem
3. Configure this new resource (try updating logging level for example)
  
Actual results:
Configuration update fails with: {JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-3=JBAS014746: file may not be null}}, rolled-back=true


Expected results:
successfully changed configuration level


Additional info:
I have no problem to change the attribute level via EAP 6.1 cli

Comment 1 Charles Crouch 2013-03-04 23:17:02 UTC
I wonder if this changed between EAP6.0 and 6.1

Comment 2 Radim Hatlapatka 2013-03-05 09:14:00 UTC
I've just tried it with EAP 6.0.1 and it works as expected => it has to be caused by some change between EAP 6.0 and EAP 6.1

Comment 3 Radim Hatlapatka 2013-04-04 12:57:21 UTC
This is actually a bug in EAP 6.1 and is fixed in EAP 6.1.0.ER4 (https://bugzilla.redhat.com/show_bug.cgi?id=948264)


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