December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4141) MySQLConnector/J version 5.1.34 not working on Wildfly8.2.final

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4141?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-4141: ----------------------------------- Where is this? in CLI or just in Console? > MySQLConnector/J version 5.1.34 not working on Wildfly8.2.final > --------------------------------------------------------------- > > Key: WFLY-4141 > URL: https://issues.jboss.org/browse/WFLY-4141 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.2.0.Final > Environment: Ubuntu 14.04.1, Oracle Java 8 update 25, Wildfly 8.2.final > Reporter: Mukund Rajamannar > Assignee: Brian Stansberry > > In Wildfly 8.2 domain mode, I am not able to use MySQL Connector/J as a JDBC driver. This works on 8.1.final and it appears to be a regression introduced in 8.2. Please see the section on reproducing the bug for details. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-99) Infinite recursion when exception stack frame class lookup fails

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-99?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on LOGMGR-99: ----------------------------------------------- Nikoleta Ziakova <nziakova(a)redhat.com> changed the Status of [bug 1071695|https://bugzilla.redhat.com/show_bug.cgi?id=1071695] from ON_QA to VERIFIED > Infinite recursion when exception stack frame class lookup fails > ---------------------------------------------------------------- > > Key: LOGMGR-99 > URL: https://issues.jboss.org/browse/LOGMGR-99 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 1.5.1.Final > Reporter: James Livingston > Assignee: James Perkins > Priority: Critical > Fix For: 1.3.3.Final, 1.4.4.Final, 1.5.4.Final, 2.0.0.Beta2 > > Attachments: logmgr99.war > > > To print out the jar information in exception stack traces, the log manager needs to resolve the class name from StackTraceElement to the Class object. Since the log manager cannot know which classloader was used, guessClass() tries the TCCL, the logmanager's classloader and finally the system classloader. > It is possible that the TCCL contains a class of the same name as the one in the stack frame, but it not the same class. This can easily happen if the application packages a jar that is also used by the container. In this situation, the class may not be able to be loaded, such as if the application-packages class is missing it's dependencies. > If Class.forName() would throw a NoClassDefFoundError or similar, JBoss Modules (or other classloader implementation) may attempt to log this using java.util.logging API. This can result in infinite recursion, for example > {code} > ... > at org.jboss.logmanager.Logger.log(Logger.java:367) > at org.jboss.modules.log.JDKModuleLogger.doLog(JDKModuleLogger.java:109) > at org.jboss.modules.log.JDKModuleLogger.classDefineFailed(JDKModuleLogger.java:194) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:401) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73) > at org.jboss.modules.Module.loadModuleClass(Module.java:527) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:266) > at org.jboss.logmanager.formatters.Formatters$12.guessClass(Formatters.java:578) > at org.jboss.logmanager.formatters.Formatters$12.renderExtended(Formatters.java:421) > at org.jboss.logmanager.formatters.Formatters$12.renderRaw(Formatters.java:388) > at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:150) > at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86) > at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35) > at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49) > at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:76) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:290) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298) > at org.jboss.logmanager.Logger.logRaw(Logger.java:721) > at org.jboss.logmanager.Logger.logRaw(Logger.java:731) > at org.jboss.logmanager.Logger.log(Logger.java:367) > ... > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4142) ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml

by Gabriele Garuglieri (JIRA)

[ https://issues.jboss.org/browse/WFLY-4142?page=com.atlassian.jira.plugin.... ] Gabriele Garuglieri updated WFLY-4142: -------------------------------------- Fix Version/s: (was: 8.1.0.Final) (was: 8.1.0.CR2) > ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml > --------------------------------------------------------------------------------- > > Key: WFLY-4142 > URL: https://issues.jboss.org/browse/WFLY-4142 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: Gabriele Garuglieri > Assignee: Stuart Douglas > > The default processor runs later, and overwrites the value provided by this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-354) Support EJB 2.0 dtd descriptors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-354?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-354: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1057835|https://bugzilla.redhat.com/show_bug.cgi?id=1057835] from NEW to ASSIGNED > Support EJB 2.0 dtd descriptors > ------------------------------- > > Key: JBMETA-354 > URL: https://issues.jboss.org/browse/JBMETA-354 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Affects Versions: 7.0.0.Final > Reporter: Carlo de Wolf > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4142) ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml

by Gabriele Garuglieri (JIRA)

[ https://issues.jboss.org/browse/WFLY-4142?page=com.atlassian.jira.plugin.... ] Gabriele Garuglieri commented on WFLY-4142: ------------------------------------------- The referred bug was closed as solved and apparently it is included in fixes list for 8.1.0 final, but the pull [https://github.com/wildfly/wildfly/pull/6172] that should have solved it was marked as reverted few days after merging and indeed 8.1.0 final still has the very same problem. > ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml > --------------------------------------------------------------------------------- > > Key: WFLY-4142 > URL: https://issues.jboss.org/browse/WFLY-4142 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: Gabriele Garuglieri > Assignee: Stuart Douglas > Fix For: 8.1.0.CR2, 8.1.0.Final > > > The default processor runs later, and overwrites the value provided by this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4142) ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml

by Gabriele Garuglieri (JIRA)

[ https://issues.jboss.org/browse/WFLY-4142?page=com.atlassian.jira.plugin.... ] Gabriele Garuglieri updated WFLY-4142: -------------------------------------- Summary: ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml (was: ear-sub-deployments-isolated is ignored from jboss-deployment-structure.xml) > ear-sub-deployments-isolated is still ignored from jboss-deployment-structure.xml > --------------------------------------------------------------------------------- > > Key: WFLY-4142 > URL: https://issues.jboss.org/browse/WFLY-4142 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: Gabriele Garuglieri > Assignee: Stuart Douglas > Fix For: 8.1.0.CR2, 8.1.0.Final > > > The default processor runs later, and overwrites the value provided by this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4142) ear-sub-deployments-isolated is ignored from jboss-deployment-structure.xml

by Gabriele Garuglieri (JIRA)

Gabriele Garuglieri created WFLY-4142: ----------------------------------------- Summary: ear-sub-deployments-isolated is ignored from jboss-deployment-structure.xml Key: WFLY-4142 URL: https://issues.jboss.org/browse/WFLY-4142 Project: WildFly Issue Type: Bug Components: EE Reporter: Gabriele Garuglieri Assignee: Stuart Douglas Fix For: 8.1.0.CR2, 8.1.0.Final The default processor runs later, and overwrites the value provided by this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-119) Add resolve-expressions param to operation read-resource

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-119?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-119: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1079197 > Add resolve-expressions param to operation read-resource > -------------------------------------------------------- > > Key: WFCORE-119 > URL: https://issues.jboss.org/browse/WFCORE-119 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Michael Voegele > Assignee: Joe Wertz > Labels: expression, read-resource > Fix For: 1.0.0.Alpha9 > > > When reading a resource remotely, it would be nice to have the possibility to have expressions resolved. > Following does of course not work, as the code runs in a separate jvm. > {code:java} > private void readRecursive(ModelNode modelNode, String modelNodeName, Map<String, Object> map) { > switch (modelNode.getType()) { > ... > case EXPRESSION: > // this would be great but won't work as it runs in a different jvm > // ModelNode expression = modelNode.resolve(); > // readRecursive(expression, modelNodeName, map); > map.put(modelNodeName, modelNode.asString()); > break; > ... > } > {code} > Therefore a param resolve-expressions for the read-resource operation would be good. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-269) CLI freezes and it's not possible to terminate it (using Ctrl-C) in some cases

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-269?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-269: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1149099|https://bugzilla.redhat.com/show_bug.cgi?id=1149099] from ON_QA to VERIFIED > CLI freezes and it's not possible to terminate it (using Ctrl-C) in some cases > ------------------------------------------------------------------------------- > > Key: WFCORE-269 > URL: https://issues.jboss.org/browse/WFCORE-269 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: 1.0.0.Alpha14 > > > This is copy of https://bugzilla.redhat.com/show_bug.cgi?id=1149099 > Description: > The CLI freezes in phase of requesting username/password in some cases. > Reproducer > ========== > Run following command: > ./jboss-cli.sh -c << EOF > /core-service=management/security-realm=ManagementRealm/authentication=local:remove > reload > EOF -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-269) CLI freezes and it's not possible to terminate it (using Ctrl-C) in some cases

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-269?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-269: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1149099|https://bugzilla.redhat.com/show_bug.cgi?id=1149099] from ASSIGNED to ON_QA > CLI freezes and it's not possible to terminate it (using Ctrl-C) in some cases > ------------------------------------------------------------------------------- > > Key: WFCORE-269 > URL: https://issues.jboss.org/browse/WFCORE-269 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: 1.0.0.Alpha14 > > > This is copy of https://bugzilla.redhat.com/show_bug.cgi?id=1149099 > Description: > The CLI freezes in phase of requesting username/password in some cases. > Reproducer > ========== > Run following command: > ./jboss-cli.sh -c << EOF > /core-service=management/security-realm=ManagementRealm/authentication=local:remove > reload > EOF -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 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 2014