September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-254) logging-profiles doesn't work with Apache Common Logging

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-254?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-254: -------------------------------------- I've got a local implementation of this with just implementing the {{org.apache.commons.logging.Log}} and {{org.apache.commons.logging.LogFactory}}. I need to test it with WildFly and decide the level the project should be compiled to. Currently WildFly uses jboss-logmanager 2.0.4.Final which targets Java 7. If this project will be required for JBoss EAP 6 then it will need to work with Java 6 as well. > logging-profiles doesn't work with Apache Common Logging > -------------------------------------------------------- > > Key: WFCORE-254 > URL: https://issues.jboss.org/browse/WFCORE-254 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Anders Welen > Assignee: James Perkins > Priority: Minor > Attachments: 87905.tar > > > The logging for one logging-profile ends up in another logging-profile from time to time. It's not sporadic as all logging will end up in the wrong place when things go wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7077) logging profile with apache commons does not work

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-7077?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-7077. ------------------------------- Resolution: Duplicate Issue > logging profile with apache commons does not work > -------------------------------------------------- > > Key: WFLY-7077 > URL: https://issues.jboss.org/browse/WFLY-7077 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: Brad Maxwell > Assignee: James Perkins > > All entry logs go to the log file of the first accessed application logging profile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7077) logging profile with apache commons does not work

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-7077?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-7077: ------------------------------------- I've been a bit hesitant to add yet another logging project, but now that this issue is coming up again I think it might be time. See the details on WFCORE-254 for more information. > logging profile with apache commons does not work > -------------------------------------------------- > > Key: WFLY-7077 > URL: https://issues.jboss.org/browse/WFLY-7077 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: Brad Maxwell > Assignee: James Perkins > > All entry logs go to the log file of the first accessed application logging profile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1780) Imprecise messages related to slave HC being unable to connect to master

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1780?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1780: ------------------------------------- Description: If a slave fails to connect to the master it logs "Could not connect to master. Aborting. Error was: %s" but since WFCORE-316 it no longer always aborts. Plus when it does abort it uses the deprecated SystemExiter.exit method. So we should change the first message to drop the bit about aborting and then if we do really abort pass an abort message to SystemExiter. was: If a slave fails to connect to the master it logs "Could not connect to master. Aborting. Error was: %s" but since WFCORE-316 it no longer always aborts. Plus when it does abort it uses the deprecated SystemExiter.exit method. So we should change the first message to drop the bit abort aborting and then if we do really abort pass an abort message to SystemExiter. > Imprecise messages related to slave HC being unable to connect to master > ------------------------------------------------------------------------ > > Key: WFCORE-1780 > URL: https://issues.jboss.org/browse/WFCORE-1780 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > If a slave fails to connect to the master it logs "Could not connect to master. Aborting. Error was: %s" but since WFCORE-316 it no longer always aborts. > Plus when it does abort it uses the deprecated SystemExiter.exit method. > So we should change the first message to drop the bit about aborting and then if we do really abort pass an abort message to SystemExiter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1780) Imprecise messages related to slave HC being unable to connect to master

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1780: ---------------------------------------- Summary: Imprecise messages related to slave HC being unable to connect to master Key: WFCORE-1780 URL: https://issues.jboss.org/browse/WFCORE-1780 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor If a slave fails to connect to the master it logs "Could not connect to master. Aborting. Error was: %s" but since WFCORE-316 it no longer always aborts. Plus when it does abort it uses the deprecated SystemExiter.exit method. So we should change the first message to drop the bit abort aborting and then if we do really abort pass an abort message to SystemExiter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7088) Resource adapter subsystem configuration descriptions: connection-definitions

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7088?page=com.atlassian.jira.plugin.... ] Ilia Vassilev updated WFLY-7088: -------------------------------- Affects Version/s: 10.1.0.Final > Resource adapter subsystem configuration descriptions: connection-definitions > ----------------------------------------------------------------------------- > > Key: WFLY-7088 > URL: https://issues.jboss.org/browse/WFLY-7088 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.1.0.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Trivial > > Multiple typos and grammar issues with the descriptions. > I will create a diff with the issues, and suggested fixes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7083) Resource adapter subsystem configuration descriptions: wm-security

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7083?page=com.atlassian.jira.plugin.... ] Ilia Vassilev updated WFLY-7083: -------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/9182) > Resource adapter subsystem configuration descriptions: wm-security > ------------------------------------------------------------------ > > Key: WFLY-7083 > URL: https://issues.jboss.org/browse/WFLY-7083 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.1.0.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Trivial > > These descriptions of wm-security may want to be reviewed. > * There is a typo in the resource description of {{wm-security}}: > bq. Toggle on/off wm.security for this resource-adapter. In case of false all wm-security-* parameters are ignored, even thei defaults. > * For {{wm-security-mapping-required}}, the description seems to refer to documentation sections: > bq. Defines if a mapping is required for security credentials. A value of false means Case 1 as defined in section 16.4.3, and a value of true means Case 2 as defined in section 16.4.4. > However these sections can me moved or removed, and the numbers will often change. I'm not even sure what content this refers to. We shouldn't hard-code documentation references. > * Ending the description with a full stop is also missing on many descriptions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7088) Resource adapter subsystem configuration descriptions: connection-definitions

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-7088?page=com.atlassian.jira.plugin.... ] Ilia Vassilev moved JBEAP-5949 to WFLY-7088: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7088 (was: JBEAP-5949) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) (was: User Experience) Affects Version/s: (was: 7.0.0.GA) > Resource adapter subsystem configuration descriptions: connection-definitions > ----------------------------------------------------------------------------- > > Key: WFLY-7088 > URL: https://issues.jboss.org/browse/WFLY-7088 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Trivial > > Multiple typos and grammar issues with the descriptions. > I will create a diff with the issues, and suggested fixes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1250) Drools Sample.drl is broken

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1250?page=com.atlassian.jira.plugi... ] Robert (Bob) Brodt commented on DROOLS-1250: -------------------------------------------- See https://github.com/droolsjbpm/drools/pull/912 > Drools Sample.drl is broken > --------------------------- > > Key: DROOLS-1250 > URL: https://issues.jboss.org/browse/DROOLS-1250 > Project: Drools > Issue Type: Feature Request > Components: eclipse plugin > Affects Versions: 6.4.0.Final > Reporter: Tianwei Chen > Assignee: Robert (Bob) Brodt > > Hello, I use drools plugin (6.4.0.Final) in Eclipse Neon. I followed the wizard to create a drools project with some example files. After the step were done, Eclipse highlighted errors at the two rules in the Sample.drl file. Here is one of the errors: > Multiple markers at this line > - com.sample.DroolsTest.Message cannot be resolved to a type > - org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type > - Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > - org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > - KnowledgeHelper cannot be resolved to a type > - Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > - Message.GOODBYE cannot be resolved to a type > - org.kie.api.runtime.rule.RuleContext cannot be resolved to a type > - java.lang.Exception cannot be resolved to a type > When I ran DroolsTest.java, I got the following error: > java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0 > text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > KnowledgeHelper cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > java.lang.Exception cannot be resolved to a type > org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0 > text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > KnowledgeHelper cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > java.lang.Exception cannot be resolved to a type > org.kie.api.runtime.rule.RuleContext cannot be resolved to a type > Message.GOODBYE cannot be resolved to a type > org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type]] > at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575) > It seems like an library path issue. Please help! > Thank you very much! > Tianwei Chen -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6965) Audit @Ignore-d clustering integration tests

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6965?page=com.atlassian.jira.plugin.... ] Radoslav Husar edited comment on WFLY-6965 at 9/9/16 12:48 PM: --------------------------------------------------------------- Analyzed and enabled 4 cases in a PR https://github.com/wildfly/wildfly/pull/9131 -RemoteFailoverTestCase already has PR submitted since 2015.- Status: merged. Fine/CoarseSessionPassivationTestCase fail intermittently probably due to Infinispan issue, traced under WFLY-6624. -WFLY-835 is being fixed by Mike M.- Status: merged. was (Author: rhusar): Analyzed and enabled 4 cases in a PR https://github.com/wildfly/wildfly/pull/9131 RemoteFailoverTestCase already has PR submitted since 2015. Fine/CoarseSessionPassivationTestCase fail intermittently probably due to Infinispan issue. WFLY-835 is being fixed by Mike M. > Audit @Ignore-d clustering integration tests > -------------------------------------------- > > Key: WFLY-6965 > URL: https://issues.jboss.org/browse/WFLY-6965 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 10.1.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 11.0.0.Alpha1 > > > Recently stumbling upon an @Ignore-d test which would have caught a regression, we need to audit ignored clustering tests, e.g. some are referencing already fixed issues. > {noformat} > [rhusar@syrah clustering]$ git grep @Ignore > src/test/java/org/jboss/as/test/clustering/cluster/ejb/remote/RemoteFailoverTestCase.java: @Ignore("WFLY-3532") > src/test/java/org/jboss/as/test/clustering/cluster/ejb/stateful/StatefulFailoverTestCase.java: @Ignore("WFLY-835 @Resource UserTransaction error when file passivation store is selected") > src/test/java/org/jboss/as/test/clustering/cluster/web/passivation/CoarseSessionPassivationTestCase.java:@Ignore("WFLY-6624") > src/test/java/org/jboss/as/test/clustering/cluster/web/passivation/FineSessionPassivationTestCase.java:@Ignore("WFLY-6624") > src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/passivation/ClusterPassivationTestCase.java: @Ignore("JBPAPP-8774") > src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/dd/RemoteEJB2ClientStatefulBeanFailoverDDTestCase.java: @Ignore("JBPAPP-8726") > src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/dd/RemoteEJB2ClientStatefulBeanFailoverDDTestCase.java: @Ignore("JBPAPP-8726") > src/test/java/org/jboss/as/test/clustering/single/jdbcstore/TransactionalJdbcStoreTestCase.java:@Ignore("https://issues.jboss.org/browse/ISPN-604") > src/test/java/org/jboss/as/test/clustering/xsite/XSiteSimpleTestCase.java: @Ignore("https://issues.jboss.org/browse/WFLY-5239") > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016