December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3934) Provide modcluster runtime operation within console

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-3934?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-3934: ----------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Provide modcluster runtime operation within console > --------------------------------------------------- > > Key: AS7-3934 > URL: https://issues.jboss.org/browse/AS7-3934 > Project: Application Server 7 > Issue Type: Task > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 7.3.0.Alpha1 > > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-84) Configurable default Locale for Logger#getMessageLogger()

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-84?page=com.atlassian.jira.plug... ] Claudio Miranda commented on JBLOGGING-84: ------------------------------------------ I believe this RFE is related to the case I will describe, if not I will open a new RFE. Having come from a JBoss AS background, so it is more related to it. The needs come to have a property to set the default locale of jboss logging, and not depend upon default locale (-Duser.country=BR and -Duser.language=pt). However I see from the current code, it is not possible. org.jboss.logging.Messages.java public static <T> T getBundle(Class<T> type, Locale locale) { String language = locale.getLanguage(); String country = locale.getCountry(); String variant = locale.getVariant(); The simplest case to solve it to create a property at jvm level and in the describing code above, check for that property and use it, using as fallback the current implementation, what do you think ? Why I ask that ? >From a application server point of view. 1. Its kind of weird to deal with some translations for technical terms, they just don't sound right. I am not blaming the translation text, only that it doesn't fit in the technical view to analyze logs and messages. 2. Not all messages are localized, so printing only english messages looks more consistent [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Iniciando o Serviço de Nomeação [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Implantação do driver compatível-JDBC class org.h2.Driver (versão 1.3) [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Ativação da Extensão WebServices [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Sessão de correio limitado [java:jboss/mail/Default] [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.4.GA-redhat-1 [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080 [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Limite da fonte de dados [java:jboss/datasources/ExampleDS] [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Limite da fonte de dados [java:jboss/datasources/KitchensinkQuickstartSSO] [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Iniciando a implantação do "jboss-as-cdi-injection.war" [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Escutando no 127.0.0.1:9999 [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Escutando no 127.0.0.1:4447 3. If the user wants to search in the internet for help, it is not going to have success with this term "Sessão de correio limitado" 4. The user who uses an application servers is expected to understand many technical terms in english language, so he already understand relevant english terms to read the english log messages. 5. There are accents in many translated words, when they are displayed in terminal consoles (with different charset encoding), it only show a binary character instead of the accented char. > Configurable default Locale for Logger#getMessageLogger() > --------------------------------------------------------- > > Key: JBLOGGING-84 > URL: https://issues.jboss.org/browse/JBLOGGING-84 > Project: JBoss Logging > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Michael Locher > Assignee: David Lloyd > > Please make the Locale for org.jboss.logging.Logger#getMessageLogger configurable (e.g. via a system property). > Use Case: > Having different locales for 'application code' which is deployed in JBAPP (specified as JVM default at startup and available via Locale.getDefault()) and the locale for logging of JBAPP. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2152) WSDL URL should be anchor

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-2152?page=com.atlassian.jira.plugin.s... ] Heiko Braun reassigned AS7-2152: -------------------------------- Assignee: Harald Pehl (was: Heiko Braun) harald, can you fix this while adding the deployment browser? > WSDL URL should be anchor > ------------------------- > > Key: AS7-2152 > URL: https://issues.jboss.org/browse/AS7-2152 > Project: Application Server 7 > Issue Type: Enhancement > Components: Console > Reporter: Richard Opalka > Assignee: Harald Pehl > Fix For: 7.2.0.CR1 > > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2751) Manage modcluster through console

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-2751?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-2751. ------------------------------ Fix Version/s: 7.2.0.CR1 (was: No Release) Resolution: Done > Manage modcluster through console > --------------------------------- > > Key: AS7-2751 > URL: https://issues.jboss.org/browse/AS7-2751 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: eap6_prd_req > Fix For: 7.2.0.CR1 > > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5736) Console: unable to change default-cache

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-5736?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-5736. ------------------------------ Resolution: Done > Console: unable to change default-cache > --------------------------------------- > > Key: AS7-5736 > URL: https://issues.jboss.org/browse/AS7-5736 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5399) Ability to flush queues/topics, etc

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-5399?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-5399. ------------------------------ Resolution: Done > Ability to flush queues/topics, etc > ------------------------------------ > > Key: AS7-5399 > URL: https://issues.jboss.org/browse/AS7-5399 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Reporter: Heiko Braun > Assignee: Jeff Mesnil > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2371) Ability to flush queues & topics from the console

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-2371?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-2371. ------------------------------ Resolution: Done > Ability to flush queues & topics from the console > ------------------------------------------------- > > Key: AS7-2371 > URL: https://issues.jboss.org/browse/AS7-2371 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Jim Tyrrell > Assignee: Heiko Braun > Labels: eap6-ux > Fix For: 7.2.0.CR1 > > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6111) Clarify analytics usage

by Heiko Braun (JIRA)

Heiko Braun created AS7-6111: -------------------------------- Summary: Clarify analytics usage Key: AS7-6111 URL: https://issues.jboss.org/browse/AS7-6111 Project: Application Server 7 Issue Type: Clarification Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5399) Ability to flush queues/topics, etc

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/AS7-5399?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on AS7-5399: ---------------------------------- both queues and jms-topics have a :remove-messages operation that can be used to flush their messages. If the filter parameter is null, all their messages are removed. > Ability to flush queues/topics, etc > ------------------------------------ > > Key: AS7-5399 > URL: https://issues.jboss.org/browse/AS7-5399 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Reporter: Heiko Braun > Assignee: Jeff Mesnil > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3700) Deadlock between AbstractWorkingMemory and DefaultAgenda in Fusion

by Winfried Umbrath (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3700?page=com.atlassian.jira.plug... ] Winfried Umbrath updated JBRULES-3700: -------------------------------------- Attachment: jbrules-3700-test.tgz Attached a failing unit test reproducing the deadlock > Deadlock between AbstractWorkingMemory and DefaultAgenda in Fusion > ------------------------------------------------------------------ > > Key: JBRULES-3700 > URL: https://issues.jboss.org/browse/JBRULES-3700 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (fusion) > Affects Versions: 5.5.0.Final > Reporter: Winfried Umbrath > Assignee: Mark Proctor > Attachments: jbrules-3700-test.tgz > > > I experienced a deadlock when running in STREAM mode and using negative patterns with temporal constraints. > When the rule gets fired by the installed timer job and at the same time another thread is firing rules, a deadlock can occur: > 1. [rule firing thread] StatefulKnowledgeSessionImpl.execute(StatefulKnowledgeSessionImpl.java:820) > acquires lock in AbstractWorkingMemory > 2. [timer-thread] DefaultAgenda.fireActivation() > call of synchronized method > 3. [rule firing thread] DefaultAgenda.fireActivation() > synchronized method, wait for other thread to exit synchornized method > 4. [timer-thread] AbstractWorkingMemory.getGlobal() > tries to access a global, tries to acquire lock in AbstractWorkingMemory which is held by the other thread > --> Deadlock > Excerpt from thread dump: > "http-thread-pool-8082(374)": > at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1264) > - waiting to lock <0x00007f50407e4950> (a org.drools.common.DefaultAgenda) > at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1221) > at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1456) > at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:710) > at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:679) > at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:234) > at org.drools.command.runtime.rule.FireAllRulesCommand.execute(FireAllRulesCommand.java:102) > at org.drools.command.runtime.rule.FireAllRulesCommand.execute(FireAllRulesCommand.java:32) > at org.drools.command.runtime.BatchExecutionCommandImpl.execute(BatchExecutionCommandImpl.java:155) > at org.drools.command.runtime.BatchExecutionCommandImpl.execute(BatchExecutionCommandImpl.java:76) > at org.drools.impl.StatefulKnowledgeSessionImpl.execute(StatefulKnowledgeSessionImpl.java:821) > "pool-4251-thread-1": > at sun.misc.Unsafe.park(Native Method) > - parking to wait for 0x00007f503fc71a20> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:778) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1114) > at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:186) > at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:262) > at org.drools.common.AbstractWorkingMemory.getGlobal(AbstractWorkingMemory.java:634) > at myrules.Rule_ruleWithTimeout_ece4a3c9fc2741a4ab97a92b77611203DefaultConsequenceInvokerGenerated.evaluate(Unknown Source) > at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1287) > - locked <0x00007f50407e4950> (a org.drools.common.DefaultAgenda) > at org.drools.common.DefaultAgenda.fireTimedActivation(DefaultAgenda.java:1344) > - locked <0x00007f50407e4950> (a org.drools.common.DefaultAgenda) > at org.drools.common.Scheduler$ActivationTimerJob.execute(Scheduler.java:83) -- 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

13 years, 7 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 December 2012