May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBLOGGING-94) JBoss Logging does not detect log4j 2.0

by Nicholas Williams (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-94?page=com.atlassian.jira.plug... ] Nicholas Williams commented on JBLOGGING-94: -------------------------------------------- Can we get an update on this? I'd really like to see this fixed for 3.1.3. For that matter, what is the roadmap for 3.1.3? It has been almost a year since 3.1.2. It'd be nice to see this fixed and 3.1.3 released soon. > JBoss Logging does not detect log4j 2.0 > --------------------------------------- > > Key: JBLOGGING-94 > URL: https://issues.jboss.org/browse/JBLOGGING-94 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-logging-log4j > Affects Versions: 3.1.2.GA > Environment: Hibernate > Reporter: Henry Clout > Assignee: James Perkins > > The class org.jboss.logging.LoggerProviders checks for the presence of log4j using the code: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.Hierarchy", true, cl); > return new Log4jLoggerProvider(); > } > {code} > However, despite having the log4j-1.2-api-2.0.jar bridge included, this fails as the class org.apache.log4j.Hierarchy is not present in log4j 2.0. > I worked around this by forcing JBoss logging to use slf4j (which is then proxied to log4j) by setting the -Dorg.jboss.logging.provider=slf4j option. > As a proper fix, however, how about checking for a class that is included in log4j 1.2, 2.0 but not slf4j? org.apache.log4j.config.PropertySetter seems to tick the box. > I tested changing the afore mentioned method to: > {code} > private static LoggerProvider tryLog4j(final ClassLoader cl) throws ClassNotFoundException { > Class.forName("org.apache.log4j.LogManager", true, cl); > // JBLOGGING-65 - slf4j can disguise itself as log4j. Test for a class that slf4j doesn't provide. > Class.forName("org.apache.log4j.config.PropertySetter", true, cl); > return new Log4jLoggerProvider(); > } > {code} > And indeed I started receiving logging messages from Hibernate (via JBoss logging.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-23) Debugging rules impossible

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-23?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on DROOLS-23: ----------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> changed the Status of [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] from NEW to MODIFIED > Debugging rules impossible > -------------------------- > > Key: DROOLS-23 > URL: https://issues.jboss.org/browse/DROOLS-23 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Eclipse Juno, Windows 8 > Reporter: Marc Dzaebel > Assignee: Mark Proctor > > Create Drools Project, set breakpoint, debug as Drools Application > --> No debug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-23) Debugging rules impossible

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-23?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on DROOLS-23: ----------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> made a comment on [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] This works again in the latest Drools6 version of the Eclipse plugin > Debugging rules impossible > -------------------------- > > Key: DROOLS-23 > URL: https://issues.jboss.org/browse/DROOLS-23 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Eclipse Juno, Windows 8 > Reporter: Marc Dzaebel > Assignee: Mark Proctor > > Create Drools Project, set breakpoint, debug as Drools Application > --> No debug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3676) drl cann't debuging in Eclipse IDE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3676?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3676: -------------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> made a comment on [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] This works again in the latest Drools6 version of the Eclipse plugin > drl cann't debuging in Eclipse IDE > ---------------------------------- > > Key: JBRULES-3676 > URL: https://issues.jboss.org/browse/JBRULES-3676 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (expert) > Affects Versions: 5.5.0.CR1 > Environment: Eclipse 4.2，JDK1.7，Drools5.5CR1 > Reporter: hongkun an > Assignee: Mark Proctor > > i follow url content > http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html/... > I want debug drl example（HelloWord）in eclipse ide，but，only debug java file，cann't debug drl，why？ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3676) drl cann't debuging in Eclipse IDE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3676?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3676: -------------------------------------------------- Kris Verlaenen <kverlaen(a)redhat.com> changed the Status of [bug 958381|https://bugzilla.redhat.com/show_bug.cgi?id=958381] from NEW to MODIFIED > drl cann't debuging in Eclipse IDE > ---------------------------------- > > Key: JBRULES-3676 > URL: https://issues.jboss.org/browse/JBRULES-3676 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (expert) > Affects Versions: 5.5.0.CR1 > Environment: Eclipse 4.2，JDK1.7，Drools5.5CR1 > Reporter: hongkun an > Assignee: Mark Proctor > > i follow url content > http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html/... > I want debug drl example（HelloWord）in eclipse ide，but，only debug java file，cann't debug drl，why？ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-202) Set line number for newly created Methods

by John Doe (JIRA)

[ https://issues.jboss.org/browse/JASSIST-202?page=com.atlassian.jira.plugi... ] John Doe commented on JASSIST-202: ---------------------------------- If there is indeed a way to provide such metadata, this issue will automatically transform into a request for better documentation of the requested functionality :-) > Set line number for newly created Methods > ----------------------------------------- > > Key: JASSIST-202 > URL: https://issues.jboss.org/browse/JASSIST-202 > Project: Javassist > Issue Type: Feature Request > Affects Versions: 3.17.1-GA > Reporter: John Doe > Assignee: Shigeru Chiba > Priority: Minor > Labels: javassist > > As far as I could figure out, there is no way to provide line number information for newly created Methods. It would be nice if one could provide an start line at which the body starts, and Javassist would increment the line number at every line break in the body string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-202) Set line number for newly created Methods

by John Doe (JIRA)

John Doe created JASSIST-202: -------------------------------- Summary: Set line number for newly created Methods Key: JASSIST-202 URL: https://issues.jboss.org/browse/JASSIST-202 Project: Javassist Issue Type: Feature Request Affects Versions: 3.17.1-GA Reporter: John Doe Assignee: Shigeru Chiba Priority: Minor As far as I could figure out, there is no way to provide line number information for newly created Methods. It would be nice if one could provide an start line at which the body starts, and Javassist would increment the line number at every line break in the body string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1435) Modcluster subsystem startup missing required dependencies from JBoss Web

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1435?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-1435: ------------------------------------------- Probably need to replace with corresponding undertow components? > Modcluster subsystem startup missing required dependencies from JBoss Web > -------------------------------------------------------------------------- > > Key: WFLY-1435 > URL: https://issues.jboss.org/browse/WFLY-1435 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Alpha1 > Reporter: Richard Achmatowicz > Assignee: Paul Ferraro > > The mod cluster subsystem is not starting correctly due to missing (incorrect) dependencies on JBoss Web: > {noformat} > 16:59:36,549 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem. > 16:59:36,561 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem. > [snip] > 16:59:36,639 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Alpha15 starting > 16:59:36,654 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension > 16:59:36,657 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service > 16:59:36,661 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default] > 16:59:36,669 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 51) JBAS017502: Undertow 1.0.0.Alpha15 starting > 16:59:36,755 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Beta1 > 16:59:36,760 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 16:59:36,771 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010417: Started Driver service with driver-name = h2 > 16:59:36,816 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) Starting server server service: service jboss.undertow.server.default-server > 16:59:36,839 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) Starting host default-host > 16:59:36,891 INFO [io.undertow] (ServerService Thread Pool -- 51) Creating file handler for path /home/nrla/projects/wildfly-git-repo/testsuite/integration/clust/target/wildfly-clustering-xsite-LON-0/welcome-content > 16:59:36,904 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017525: Started http handler io.undertow.server.handlers.resource.ResourceHandler@26dce695. > 16:59:36,905 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) registering handler org.jboss.msc.value.InjectedValue@ab2d3a9 under path '/' > 16:59:36,927 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017519: Undertow AJP listener ajp-connector listening on /127.0.0.1:8009 > 16:59:36,926 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 > 16:59:37,252 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:59:37,262 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:59:37,291 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] > 16:59:37,478 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999 > 16:59:37,479 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/nrla/projects/wildfly-git-repo/testsuite/integration/clust/target/wildfly-clustering-xsite-LON-0/standalone/deployments > 16:59:37,478 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447 > 16:59:37,507 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.mod-cluster is missing [jboss.web, jboss.web.connector.ajp]"]} > 16:59:37,571 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.web (missing) dependents: [service jboss.mod-cluster] > service jboss.web.connector.ajp (missing) dependents: [service jboss.mod-cluster] > 16:59:37,706 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 16:59:37,707 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 16:59:37,707 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Alpha2-SNAPSHOT "WildFly" started (with errors) in 3027ms - Started 157 of 252 services (1 services failed or missing dependencies, 116 services are lazy, passive or on-demand) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1435) Modcluster subsystem startup missing required dependencies from JBoss Web

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created WFLY-1435: ----------------------------------------- Summary: Modcluster subsystem startup missing required dependencies from JBoss Web Key: WFLY-1435 URL: https://issues.jboss.org/browse/WFLY-1435 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 8.0.0.Alpha1 Reporter: Richard Achmatowicz Assignee: Paul Ferraro The mod cluster subsystem is not starting correctly due to missing (incorrect) dependencies on JBoss Web: {noformat} 16:59:36,549 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem. 16:59:36,561 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem. [snip] 16:59:36,639 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Alpha15 starting 16:59:36,654 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension 16:59:36,657 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service 16:59:36,661 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default] 16:59:36,669 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 51) JBAS017502: Undertow 1.0.0.Alpha15 starting 16:59:36,755 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Beta1 16:59:36,760 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 16:59:36,771 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010417: Started Driver service with driver-name = h2 16:59:36,816 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) Starting server server service: service jboss.undertow.server.default-server 16:59:36,839 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) Starting host default-host 16:59:36,891 INFO [io.undertow] (ServerService Thread Pool -- 51) Creating file handler for path /home/nrla/projects/wildfly-git-repo/testsuite/integration/clust/target/wildfly-clustering-xsite-LON-0/welcome-content 16:59:36,904 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017525: Started http handler io.undertow.server.handlers.resource.ResourceHandler@26dce695. 16:59:36,905 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) registering handler org.jboss.msc.value.InjectedValue@ab2d3a9 under path '/' 16:59:36,927 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017519: Undertow AJP listener ajp-connector listening on /127.0.0.1:8009 16:59:36,926 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 16:59:37,252 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 16:59:37,262 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 16:59:37,291 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 16:59:37,478 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999 16:59:37,479 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/nrla/projects/wildfly-git-repo/testsuite/integration/clust/target/wildfly-clustering-xsite-LON-0/standalone/deployments 16:59:37,478 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447 16:59:37,507 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.mod-cluster is missing [jboss.web, jboss.web.connector.ajp]"]} 16:59:37,571 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.web (missing) dependents: [service jboss.mod-cluster] service jboss.web.connector.ajp (missing) dependents: [service jboss.mod-cluster] 16:59:37,706 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 16:59:37,707 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 16:59:37,707 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Alpha2-SNAPSHOT "WildFly" started (with errors) in 3027ms - Started 157 of 252 services (1 services failed or missing dependencies, 116 services are lazy, passive or on-demand) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1434) Add support for loading groups for ManagementRealm

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-1434: -------------------------------------- Summary: Add support for loading groups for ManagementRealm Key: WFLY-1434 URL: https://issues.jboss.org/browse/WFLY-1434 Project: WildFly Issue Type: Feature Request Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Alpha2 Add default configuration to load groups from properties files for ManagementRealm. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 May 2013