[JBoss JIRA] (LOGMGR-124) Add marker support
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ]
James Perkins commented on LOGMGR-124:
--------------------------------------
I'm just a bit hesitant to add a new API to the JBoss Log Manager. Both slf4j and log4j2 seem to have their own marker API and I just don't love the idea of adding yet another to the mix. However, maybe people use markers more than I thought.
> Add marker support
> ------------------
>
> Key: LOGMGR-124
> URL: https://issues.jboss.org/browse/LOGMGR-124
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Components: core
> Affects Versions: 2.0.2.Final
> Reporter: Rob Heine
> Priority: Optional
>
> The logging engine currently (talking about the one included in WF-9) does not support Markers (like in implementations like "logback" and/or "log4j2").
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8660) Naming fix for jboss-seam-int
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8660?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-8660:
-----------------------------------
Description:
The rpm file "eap7-jboss-seam-int-0:7.0.0-1.GA_redhat_1.1.ep7.el6.noarch.rpm" contains jar named "jboss-seam-int-jbossas-7.0.0.GA-redhat-1.jar".
The corresponding file in the the zip in the location:
modules/system/layers/base/org/jboss/integration/ext-content/main/bundled/
has name jboss-seam-int.jar.
Fix is to add "-jbossas-" string to the jar file name in the dist.
was:
The rpm file "eap7-jboss-seam-int-0:7.0.0-1.GA_redhat_1.1.ep7.el6.noarch.rpm" contains jar named "jboss-seam-int-jbossas-7.0.0.GA-redhat-1.jar".
The corresponding file in the the zip in the location:
modules/system/layers/base/org/jboss/integration/ext-content/main/bundled/
has name jboss-seam-int.jar.
Either we remove the version part (7.0.0.GA-redhat-1), there is still difference in naming with "-jbossas-" string.
Desired change is to remove "-jbossas-" string from the jar file name.
> Naming fix for jboss-seam-int
> -----------------------------
>
> Key: WFLY-8660
> URL: https://issues.jboss.org/browse/WFLY-8660
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Katerina Novotna
> Assignee: Brian Stansberry
>
> The rpm file "eap7-jboss-seam-int-0:7.0.0-1.GA_redhat_1.1.ep7.el6.noarch.rpm" contains jar named "jboss-seam-int-jbossas-7.0.0.GA-redhat-1.jar".
> The corresponding file in the the zip in the location:
> modules/system/layers/base/org/jboss/integration/ext-content/main/bundled/
> has name jboss-seam-int.jar.
> Fix is to add "-jbossas-" string to the jar file name in the dist.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8660) Naming fix for jboss-seam-int
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8660?page=com.atlassian.jira.plugin.... ]
Brian Stansberry moved JBEAP-10599 to WFLY-8660:
------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8660 (was: JBEAP-10599)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Server
(was: RPM)
Affects Version/s: (was: 7.0.0.ER2 (Beta))
> Naming fix for jboss-seam-int
> -----------------------------
>
> Key: WFLY-8660
> URL: https://issues.jboss.org/browse/WFLY-8660
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Katerina Novotna
> Assignee: Brian Stansberry
>
> The rpm file "eap7-jboss-seam-int-0:7.0.0-1.GA_redhat_1.1.ep7.el6.noarch.rpm" contains jar named "jboss-seam-int-jbossas-7.0.0.GA-redhat-1.jar".
> The corresponding file in the the zip in the location:
> modules/system/layers/base/org/jboss/integration/ext-content/main/bundled/
> has name jboss-seam-int.jar.
> Either we remove the version part (7.0.0.GA-redhat-1), there is still difference in naming with "-jbossas-" string.
> Desired change is to remove "-jbossas-" string from the jar file name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2733) JBossAllXmlParserRegisteringProcessor leaks deployment unit attachments on undeploy
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2733?page=com.atlassian.jira.plugi... ]
Paul Ferraro moved JBEAP-10597 to WFCORE-2733:
----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2733 (was: JBEAP-10597)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Server
(was: Clustering)
Affects Version/s: 3.0.0.Beta16
(was: 7.1.0.DR17)
> JBossAllXmlParserRegisteringProcessor leaks deployment unit attachments on undeploy
> -----------------------------------------------------------------------------------
>
> Key: WFCORE-2733
> URL: https://issues.jboss.org/browse/WFCORE-2733
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 3.0.0.Beta16
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
>
> Seen in our clustering tests for singleton deployments.
> Timeline:
> Node1 elected as the singleton provider
> Some other node gets elected after topology change
> Node1 gets elected after another topology change and logs:
> {code}
> 13:08:42,248 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node1 elected as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
> 13:08:42,474 INFO [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
> 13:08:42,476 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "clusterbench-ee7-singleton-jbossall.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Root element supplier for {http://www.jboss.com/xml/ns/javaee}jboss-app already registered
> at org.jboss.staxmapper.XMLMapperImpl.registerRootElement(XMLMapperImpl.java:51)
> at org.jboss.staxmapper.XMLMapperImpl.registerRootElement(XMLMapperImpl.java:46)
> at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor.deploy(JBossAllXMLParsingProcessor.java:90)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years