June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1253) Multiple JDBC drivers versions - wrong driver is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1253?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1253: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1157649|https://bugzilla.redhat.com/show_bug.cgi?id=1157649] from MODIFIED to ON_QA > Multiple JDBC drivers versions - wrong driver is used > ----------------------------------------------------- > > Key: JBJCA-1253 > URL: https://issues.jboss.org/browse/JBJCA-1253 > Project: IronJacamar > Issue Type: Bug > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > > When multiple verions of the driver are being used only one is being used. the class driver is cached with the same string, i.e: "jdbc:mysql". This cache is shared among every mcf (the field LocalManagedConnectionFactory::driverCache is static). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1258) Remove driver cache

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1258?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1258: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1157649|https://bugzilla.redhat.com/show_bug.cgi?id=1157649] from MODIFIED to ON_QA > Remove driver cache > ------------------- > > Key: JBJCA-1258 > URL: https://issues.jboss.org/browse/JBJCA-1258 > Project: IronJacamar > Issue Type: Task > Components: JDBC > Reporter: Jesper Pedersen > Assignee: Lin Gao > Fix For: 1.0.32.Final, 1.2.4.Final > > > And interaction with DriverManager -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4496) Upgrade AESH from 0.33.14 to 0.33.15

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4496?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4496: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1210556|https://bugzilla.redhat.com/show_bug.cgi?id=1210556] from MODIFIED to ON_QA > Upgrade AESH from 0.33.14 to 0.33.15 > ------------------------------------ > > Key: WFLY-4496 > URL: https://issues.jboss.org/browse/WFLY-4496 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4487) Unable to inject Web Service Context into CDI Interceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4487?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4487: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1210328|https://bugzilla.redhat.com/show_bug.cgi?id=1210328] from MODIFIED to ON_QA > Unable to inject Web Service Context into CDI Interceptor > --------------------------------------------------------- > > Key: WFLY-4487 > URL: https://issues.jboss.org/browse/WFLY-4487 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Mustafa Musaji > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > Attachments: cdi-interceptors.zip > > > CDI Interceptor cannot inject Web Service context. > When trying to inject WebServiceContext in CDI Interceptor using @Resource annotation but it fails with: NameNotFoundException: env/org.example.MyInterceptor/webServiceContext -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1260) Allow System Property to override default First In First Out (FIFO) pooling behavior

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1260: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1210571|https://bugzilla.redhat.com/show_bug.cgi?id=1210571] from MODIFIED to ON_QA > Allow System Property to override default First In First Out (FIFO) pooling behavior > ------------------------------------------------------------------------------------ > > Key: JBJCA-1260 > URL: https://issues.jboss.org/browse/JBJCA-1260 > Project: IronJacamar > Issue Type: Support Patch > Components: Core > Affects Versions: 1.0.32.Final > Reporter: Johnathon Lee > Assignee: Johnathon Lee > Fix For: 1.0.32.Final > > > Introduce a system property "filo-pool-behavior" to override (revert) the changes introduced by JBJCA-1005. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2900: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1175982|https://bugzilla.redhat.com/show_bug.cgi?id=1175982] from MODIFIED to ON_QA > Performance issue with Xalan transformer and very large text nodes > ------------------------------------------------------------------ > > Key: WFLY-2900 > URL: https://issues.jboss.org/browse/WFLY-2900 > Project: WildFly > Issue Type: Bug > Components: XML Frameworks > Reporter: Kyle Lape > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.CR1 > > > It has been observed that when using the {{Transfomer}} to convert a {{StreamSource}} to {{DOMResult}}, the performance of Transform gets worse as the size of the > character data increases. If you have a 50MB text blob in XML, this will take a very long time to finish. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-117) Fork Log4J ConosleAppender to simply handling of calls to System.out

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-117?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on LOGMGR-117: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1196228|https://bugzilla.redhat.com/show_bug.cgi?id=1196228] from MODIFIED to ON_QA > Fork Log4J ConosleAppender to simply handling of calls to System.out > -------------------------------------------------------------------- > > Key: LOGMGR-117 > URL: https://issues.jboss.org/browse/LOGMGR-117 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: Kyle Lape > Assignee: Lin Gao > Fix For: 1.1.2.CR1 > > > While the use of {{ConsoleAppender}} in Log4J application logging configurations is discouraged, JBoss could probably do a better job of managing its use. > Currently it's possible to encounter a deadlock if thread A invokes {{System.out.println()}} and thread B invokes {{Logger.info()}}. Thread A will get the lock on {{System.out}} (a {{java.io.PrintWriter}}), but then thread B will get the lock on the {{org.apache.log4j.ConsoleAppender}}. Then each thread is waiting on the other's lock. > The suggested improvement (discussed with [~jamezp]) is to fork Log4J's {{ConsoleAppender}} so that instead of calling {{System.out.println}}, it calls the real {{stdout}}. > *Bonus enhancement*: Drop a {{WARN}} message to the system root logger discouraging the use of {{ConsoleAppender}} in application configurations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1252) MCPs can become detached

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1252?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1252: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1210570|https://bugzilla.redhat.com/show_bug.cgi?id=1210570] from MODIFIED to ON_QA > MCPs can become detached > ------------------------ > > Key: JBJCA-1252 > URL: https://issues.jboss.org/browse/JBJCA-1252 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.31.Final, 1.1.9.Final, 1.2.2.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.32.Final, 1.1.10.Final, 1.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1752) Concurrent message headers modification causes that message is never sent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1752?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1752: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1215786|https://bugzilla.redhat.com/show_bug.cgi?id=1215786] from MODIFIED to ON_QA > Concurrent message headers modification causes that message is never sent > ------------------------------------------------------------------------- > > Key: JGRP-1752 > URL: https://issues.jboss.org/browse/JGRP-1752 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.1 > Reporter: Radim Vansa > Assignee: Bela Ban > Labels: 621 > Fix For: 3.2.14, 3.4.2, 3.5 > > > Under some circumstances the TP protocol may try to add the TP header to message twice concurrently. > This happens for example when the stable message triggers retransmission while the message has been sent right now. > This may result in ArrayOutOfBoundException in Headers._putHeader and/or subsequent NullPointerException in Headers.size(). The retransmission attempt always fails, the message is never delivered. Moreover, keeping this (and possibly following) messages in the transmission table can lead to OOME. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-227) RejectedExecutionException when closing ModelControllerClient client

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-227?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-227: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1193926|https://bugzilla.redhat.com/show_bug.cgi?id=1193926] from MODIFIED to ON_QA > RejectedExecutionException when closing ModelControllerClient client > -------------------------------------------------------------------- > > Key: WFCORE-227 > URL: https://issues.jboss.org/browse/WFCORE-227 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Remoting > Affects Versions: 1.0.0.Alpha11 > Reporter: Alessio Soldano > Assignee: David Lloyd > Fix For: 1.0.0.Alpha15 > > > After wildfly-core 1.0.0.Alpha11 has been included in WFLY master, I'm seeing hundreds of the following exceptions in the logs when running the JBossWS-CXF testsuite: > {noformat} > Exception in thread "Remoting "management-client" task-4" java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.RemoteConnectionChannel$3@5651c0c2 rejected from org.xnio.XnioWorker$TaskPool@11462cd4[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 4] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372) > at org.xnio.XnioWorker.execute(XnioWorker.java:741) > at org.jboss.remoting3.remote.RemoteConnectionChannel.receiveMessage(RemoteConnectionChannel.java:363) > at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:107) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:451) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > {noformat} > The exception is logged just after the org.jboss.as.webservices.deployer.RemoteDeployer calls the RemotingModelControllerClient#close method. > The issue seems to be related to some kind of race condition, as trying to reproduce it with an attached debugger is not possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

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 June 2015