[JBoss JIRA] (WFLY-2906) WildFly 8.0.0 Final keeps lock on Manifest.mf files in exploded deployment
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2906?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2906:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1085294|https://bugzilla.redhat.com/show_bug.cgi?id=1085294] from VERIFIED to CLOSED
> WildFly 8.0.0 Final keeps lock on Manifest.mf files in exploded deployment
> --------------------------------------------------------------------------
>
> Key: WFLY-2906
> URL: https://issues.jboss.org/browse/WFLY-2906
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF, Web (Undertow)
> Affects Versions: 8.0.0.Final
> Environment: Windows7x64, Oracle Java 1.7.0_51
> Reporter: Wolfgang Knauf
> Assignee: Tomaz Cerar
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
>
> I have a small JSF web app. When performing exploded deployment, after a ".dodeploy"/."undeploy"/".dodeploy"/".undeploy" cycle, the manifest.mf files are locked (I cannot delete the files, Windows tells me that they are used by a Java process)
> A similar sample without JSF (and beans.xml) does not show this problem.
> See the forum post for more details and the zip file of the "to be deployed" app.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (WFLY-2696) management audit settings: syslog protocol is lowercase while uppercase is expected
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2696?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2696:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1047519|https://bugzilla.redhat.com/show_bug.cgi?id=1047519] from VERIFIED to CLOSED
> management audit settings: syslog protocol is lowercase while uppercase is expected
> -----------------------------------------------------------------------------------
>
> Key: WFLY-2696
> URL: https://issues.jboss.org/browse/WFLY-2696
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.CR1
> Environment: - 8.0.0 CR1 + latest code in master
> - domain mode
> Reporter: Tom Fonteyne
> Assignee: Tom Fonteyne
> Fix For: 8.0.0.Final
>
>
> Add a syslog handler to the audit settings of the management service of the domain controller, then start an instance. It fails to start with:
> JBAS014612: Operation ("register-server") failed - address: ([]): java.lang.IllegalArgumentException: No enum const class org.jboss.as.controller.audit.SyslogAuditLogHandler$Transport.udp
> at java.lang.Enum.valueOf(Enum.java:214)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (WFLY-3108) Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3108?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3108:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1076066|https://bugzilla.redhat.com/show_bug.cgi?id=1076066] from VERIFIED to CLOSED
> Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-3108
> URL: https://issues.jboss.org/browse/WFLY-3108
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
>
> The prescribed mechanism for converting a slave HC to master is to:
> 1) Start the slave with --backup so a local copy of the domain config is maintained (in file domain.cached-remote.xml).
> 2) Stop the existing master.
> 3) Use the cli to connect to the slave and
> /host=<slavename>:write-local-domain-controller
> 4) Then, in the CLI
> reload --host=<slavename>
> Problem is this fails because the HC expects to have a domain config file "domain.xml".
> 2014-03-13 09:54:04,829 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:514) [wildfly-host-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.io.FileNotFoundException: /Users/bstansberry/tmp/WF801/slave/domain/configuration/domain.xml (No such file or directory)
> at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_45]
> at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_45]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:100) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> ... 3 more
> Or, MUCH WORSE, there happens to be a random domain.xml in the filesystem, which has content that is out of sync with the correct domain config. This domain.xml config will be used.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months