November 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-46) Unnecessary Locking in WrappedConnection and WrappedPreparedStatement

by Deyan Bektchiev (JIRA)

Unnecessary Locking in WrappedConnection and WrappedPreparedStatement --------------------------------------------------------------------- Key: JBJCA-46 URL: https://jira.jboss.org/jira/browse/JBJCA-46 Project: JBoss JCA Issue Type: Bug Components: JDBC Environment: Windows Sun JDK 1.6 Reporter: Deyan Bektchiev Assignee: Jesper Pedersen The JBoss JDBC Connection and PreparedStatement wrapper classes all acquire and release a lock when entering and exiting most of their methods. JDBC connections are not supposed to be thread safe and even if you coded your wrapper this way there is no guarantee that the underlying Connection would behave properly if accessed by multiple threads concurrently. In one particular use case when profiling obtaining the locks for Statements (that obtain the Connection locks) took 5% of the total time. I can provide a YourKit CPU profiler snapshot. Regards, Deyan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JGRP-1095) MPING: doesn't work with IPv6

by Bela Ban (JIRA)

MPING: doesn't work with IPv6 ----------------------------- Key: JGRP-1095 URL: https://jira.jboss.org/jira/browse/JGRP-1095 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 Running MPING with TCP works with IPv4, but not with IPv6 (members don't find each other). The config is <MPING mcast_addr="ff0e::8:8:5" mcast_port="7200" num_ping_requests="1" timeout="3000" num_initial_members="3"/> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBLOGGING-31) Add ability to specify a date pattern with a specific time zone

by David Lloyd (JIRA)

Add ability to specify a date pattern with a specific time zone --------------------------------------------------------------- Key: JBLOGGING-31 URL: https://jira.jboss.org/jira/browse/JBLOGGING-31 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jboss-logmanager Affects Versions: 1.1.0.GA-jboss-logmanager Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Fix For: 1.1.1.CR1-jboss-logmanager, 1.2.0.CR1-jboss-logmanager The date format would work like this: %z{America/Chicago}%d{dd MMM yyyy HH:mm:ss,SSS} Any %d string appearing after a %z would then have that time zone. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-441) Release JBoss Security 2.0.4.SP2

by Anil Saldhana (JIRA)

Release JBoss Security 2.0.4.SP2 -------------------------------- Key: SECURITY-441 URL: https://jira.jboss.org/jira/browse/SECURITY-441 Project: JBoss Security and Identity Management Issue Type: Release Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: JBossSecurity_2.0.4.SP1 Reporter: Anil Saldhana Assignee: Stefan Guilhen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7416) Create a Maven Artifact for snmp-adaptor.sar

by Andrew Lee Rubinger (JIRA)

Create a Maven Artifact for snmp-adaptor.sar -------------------------------------------- Key: JBAS-7416 URL: https://jira.jboss.org/jira/browse/JBAS-7416 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Andrew Lee Rubinger Assignee: Paul Gier Fix For: JBossAS-5.2.0.Beta1 AS trunk has a Maven2 artifact for the SNMP Adaptor SAR: http://snapshots.jboss.org/maven2/org/jboss/jbossas/jboss-as-varia/6.0.0-... ...We'll need a corollary for Branch_5_x as well. :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (SECURITY-426) DecodeAction is not correctly using information of the JaasSecurityDomain bean

by Marcus Moyses (JIRA)

DecodeAction is not correctly using information of the JaasSecurityDomain bean ------------------------------------------------------------------------------ Key: SECURITY-426 URL: https://jira.jboss.org/jira/browse/SECURITY-426 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: JBossSecurity_2.0.3.SP2 Reporter: Marcus Moyses Assignee: Anil Saldhana Fix For: JBossSecurity_2.0.4 When encrypting the bindCredential of LdapExtLoginModule, DecodeAction is not correctly using the information set in the JaasSecurityDomain bean, thus decryption fails. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBXB-230) Switch to NoopRepeatableParticleHandler as the default RepeatableParticleHandler

by Alexey Loubyansky (JIRA)

Switch to NoopRepeatableParticleHandler as the default RepeatableParticleHandler -------------------------------------------------------------------------------- Key: JBXB-230 URL: https://jira.jboss.org/jira/browse/JBXB-230 Project: JBoss XML Binding (JBossXB) Issue Type: Task Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA The default impl currently is based on ValueList container. While originally it's meant to be an optimization in collecting repeated term values, in JBossXBBuilder-based impl it actually has the opposite effect. So, the default for JBossXBBuilder-based impl should be an impl of RepeatableParticleHandler which does nothing. For the XsdBinder-based impl with RtElementHandler, RtCharactersHandler, RtAttributeHandler the default may still remain ValueList-based. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-229) Add RepeatableParticleHandler to TermBinding

by Alexey Loubyansky (JIRA)

Add RepeatableParticleHandler to TermBinding -------------------------------------------- Key: JBXB-229 URL: https://jira.jboss.org/jira/browse/JBXB-229 Project: JBoss XML Binding (JBossXB) Issue Type: Task Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA This task is a refactoring to add RepeatableParticleHandler to TermBinding instead of having a global default impl of RepeatableParticleHandler for all the terms in SundayContentHandler. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1094) BindInterface converter: check if it assigns correct bind_addr

by Bela Ban (JIRA)

BindInterface converter: check if it assigns correct bind_addr -------------------------------------------------------------- Key: JGRP-1094 URL: https://jira.jboss.org/jira/browse/JGRP-1094 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.8 When bind_addr is null and bind_interface is non-null, the BinterInterface property converter should grab a non-loopback address on the interface defined by bind_interface and assign it to bind_addr. Check if this works, both for IPv4 and IPv6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1096) IPv6: test TCPGOSSIP

by Bela Ban (JIRA)

IPv6: test TCPGOSSIP -------------------- Key: JGRP-1096 URL: https://jira.jboss.org/jira/browse/JGRP-1096 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.8 - TCP:TCPGOSSIP (start GossipRouter with IPv6 bind address) - TCP:TCPPING: OK, works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
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 November 2009