December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-942) Unlock thread in case of a SQLException

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-942: ------------------------------------- Summary: Unlock thread in case of a SQLException Key: JBJCA-942 URL: https://issues.jboss.org/browse/JBJCA-942 Project: IronJacamar Issue Type: Bug Components: JDBC Affects Versions: 1.1.0.Beta3, 1.0.13.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.14.Final, 1.1.0.Beta4 -- 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-6114) lower messaging's min-large-message-size value in standalone-full.xml

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/AS7-6114?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil updated AS7-6114: ----------------------------- Description: AS7's messaging subsystem defines 2 attributes: journal-file-size => 10MiB min-large-message-size => 100KiB However, for startup performance issue, the standalone-full.xml sets the journal-file-size at 1OOKiB. This leads to issues since it's the same value than the min-large-message-size. If we want to keep a low journal-file-size value in standalone-full.xml, the min-large-message-size must also bet set appropriately (eg 75KiB?) For production use, however, we should suggest to the users to remove the journal-file-size and min-large-message-size from standalone-full.xml to use the default values (resp. 10MiB & 100KiB) was: AS7's messaging subsystem defines 2 attributes: journal-file-size => 10MiB min-large-message-size => 100KiB However, for startup performance issue, the standalone-full.xml sets the journal-file-size at 1OOKiB. This leads to issues since it's the same value than the min-large-message-size. If we want to keep a low journal-file-size value in standalone-full.xml, the min-large-message-size must also bet set appropriately (eg 75KiB?) For production use, however, we should suggest to the users to remove the journal-file-size and min-large-message-size from standalone-full.xml to use the default values (resp. 100MiB & 100KiB) > lower messaging's min-large-message-size value in standalone-full.xml > --------------------------------------------------------------------- > > Key: AS7-6114 > URL: https://issues.jboss.org/browse/AS7-6114 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 7.2.0.Alpha1 > > > AS7's messaging subsystem defines 2 attributes: > journal-file-size => 10MiB > min-large-message-size => 100KiB > However, for startup performance issue, the standalone-full.xml sets the journal-file-size at 1OOKiB. This leads to issues since it's the same value than the min-large-message-size. > If we want to keep a low journal-file-size value in standalone-full.xml, the min-large-message-size must also bet set appropriately (eg 75KiB?) > For production use, however, we should suggest to the users to remove the journal-file-size and min-large-message-size from standalone-full.xml to use the default values (resp. 10MiB & 100KiB) -- 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] (JBWEB-258) DigestAuthenticator generates duplicate nonces

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/JBWEB-258?page=com.atlassian.jira.plugin.... ] Aaron Ogburn updated JBWEB-258: ------------------------------- Affects Version/s: JBossWeb-7.2.0.Alpha3 > DigestAuthenticator generates duplicate nonces > ---------------------------------------------- > > Key: JBWEB-258 > URL: https://issues.jboss.org/browse/JBWEB-258 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossWeb-2.1.12.GA, JBossWeb-7.0.16.GA, JBossWeb-7.2.0.Alpha3 > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > > DigestAuthenticator currently generates nonces as a hash of the client's remote ip, the current time at generation time, and an internal server key. With high concurrent load in a scenario where many clients show a single ip (such as behind a loadbalancer/proxy), then it is very easy for DigestAuthenticator to give out duplicate nonces when they are generated at the same time. > This then leads to authentication failues as counts for the duplicate nonces get out of whack. -- 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-5733) Domain "Runtime" navigation (LHS) not refreshed when the number of server configurations is changed

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-5733?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-5733: ---------------------------------- same applies to topology view > Domain "Runtime" navigation (LHS) not refreshed when the number of server configurations is changed > --------------------------------------------------------------------------------------------------- > > Key: AS7-5733 > URL: https://issues.jboss.org/browse/AS7-5733 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > > Remove all server configurations on a host to see what I mean -- 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-6026) Cannot add jgroups transport property

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6026?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-6026. ------------------------------ Resolution: Cannot Reproduce Bug > Cannot add jgroups transport property > ------------------------------------- > > Key: AS7-6026 > URL: https://issues.jboss.org/browse/AS7-6026 > 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-6096) Allow changing of pool attributes w/o disabling a datasource

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6096?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-6096. ------------------------------ Resolution: Done > Allow changing of pool attributes w/o disabling a datasource > ------------------------------------------------------------ > > Key: AS7-6096 > URL: https://issues.jboss.org/browse/AS7-6096 > 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-4694) JBAS014478: Could not find timeout method

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/AS7-4694?page=com.atlassian.jira.plugin.s... ] jaikiran pai reassigned AS7-4694: --------------------------------- Assignee: Stephen Coy (was: jaikiran pai) Steve has expressed interest in looking into this. Assigning this to him. > JBAS014478: Could not find timeout method > ----------------------------------------- > > Key: AS7-4694 > URL: https://issues.jboss.org/browse/AS7-4694 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final > Environment: ubuntu 11.04, x32, oracle jdk_1.6.0_27, AS 7.1.1.Final > Reporter: Franck Garcia > Assignee: Stephen Coy > Labels: serialization, timers > > I've added a timer service in one of my ejb of a specific module inside my ear application through the @Schedule annotation. > I then removed the method annotated with the Schedule annotation and redeploy. > The AS refuses to deploy my module (and my entire ear as a consequence) ended up with the following exception: > Caused by: java.lang.IllegalStateException: JBAS014478: Could not find timeout method: com.acme.AppLogger.processSend(javax.ejb.Timer) > at org.jboss.as.ejb3.timerservice.CalendarTimer.<init>(CalendarTimer.java:138) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl.getActivePersistentTimers(TimerServiceImpl.java:906) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:633) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl.start(TimerServiceImpl.java:190) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > I add to get rid of the $JBOSS_DIR$standalone/data/timer-service-data folder to be able to properly redeploy. -- 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-6115) CLONE - In security domain, in the mapping settings, the "module" attribute is not fully implemented

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-6115: --------------------------------- Summary: CLONE - In security domain, in the mapping settings, the "module" attribute is not fully implemented Key: AS7-6115 URL: https://issues.jboss.org/browse/AS7-6115 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.1.3.Final (EAP) Reporter: Tom Fonteyne Assignee: Tom Fonteyne In security domain, in the mapping settings, the "module" attribute is not fully implemented -- 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-6101) In security domain, in the mapping settings, the "module" attribute is not fully implemented

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/AS7-6101?page=com.atlassian.jira.plugin.s... ] Tom Fonteyne updated AS7-6101: ------------------------------ Git Pull Request: https://github.com/jbossas/jboss-as/pull/3600 > In security domain, in the mapping settings, the "module" attribute is not fully implemented > -------------------------------------------------------------------------------------------- > > Key: AS7-6101 > URL: https://issues.jboss.org/browse/AS7-6101 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > In security domain, in the mapping settings, the "module" attribute is not fully implemented -- 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 David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-84?page=com.atlassian.jira.plug... ] David Lloyd commented on JBLOGGING-84: -------------------------------------- That is true, however in practice it is much simpler to configure your application locale. Especially when you consider that an application may often support multiple locales depending on the geographical location of the user. > 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

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