March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3175) Create non-clustered implementations of org.wildfly.clustering.api services

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-3175: ---------------------------------- Summary: Create non-clustered implementations of org.wildfly.clustering.api services Key: WFLY-3175 URL: https://issues.jboss.org/browse/WFLY-3175 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 8.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 9.0.0.CR1 There are several reasons to do this: * The implementations are very simple * An application that uses the public clustering api will can still deploy and function in a non-clustered environment * We no longer need to use OPTIONAL dependencies in the web and ejb clustering layers The clustering services would now be installed from a DUP within the infinispan subsystem instead of the jgroups subsystem. If a cache container defines a transport, then the clustered version of the channel-based service is installed, otherwise the local version will be installed. If a cache is clustered, then the clustered version of the cache-based services is installed, otherwise a local version will be installed. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3150) component upgrade to Hibernate ORM 4.3.5

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3150?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-3150: ------------------------------- Summary: component upgrade to Hibernate ORM 4.3.5 (was: component upgrade to Hibernate next ORM 4.3.x release ) > component upgrade to Hibernate ORM 4.3.5 > ---------------------------------------- > > Key: WFLY-3150 > URL: https://issues.jboss.org/browse/WFLY-3150 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Affects Versions: 8.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Fix For: 8.0.1.Final > > > Need the https://hibernate.atlassian.net/browse/HHH-9073 change to pass the TCK. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-150) The jboss-jstl-api_1.2_spec artifact depends on xalan artifact that is not present in Maven Central

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-150?page=com.atlassian.jira.plugin.s... ] Shelly McGowan reassigned JBEE-150: ----------------------------------- Assignee: Tomaz Cerar (was: Shelly McGowan) > The jboss-jstl-api_1.2_spec artifact depends on xalan artifact that is not present in Maven Central > --------------------------------------------------------------------------------------------------- > > Key: JBEE-150 > URL: https://issues.jboss.org/browse/JBEE-150 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Tomas Repel > Assignee: Tomaz Cerar > > The org.jboss.spec.javax.servlet.jstl:jboss-jstl-api_1.2_spec:1.1.0.Final depends on xalan:xalan:2.7.1.jbossorg-2 artifact, this one is not present in Maven Central. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-148) Unbounded ELEvaluator cache can cause OOMEs

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-148?page=com.atlassian.jira.plugin.s... ] Shelly McGowan reassigned JBEE-148: ----------------------------------- Assignee: Tomaz Cerar (was: Shelly McGowan) > Unbounded ELEvaluator cache can cause OOMEs > ------------------------------------------- > > Key: JBEE-148 > URL: https://issues.jboss.org/browse/JBEE-148 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jstl-api > Affects Versions: jboss-jstl-api_1.2_spec-1.0.5.Final, jboss-jstl-api_1.2_spec-1.1.0.Final > Reporter: Aaron Ogburn > Assignee: Tomaz Cerar > Attachments: diff.out > > > Unbounded jstl ELEvaluator cache can cause OOMEs. > Related community issue: > https://issues.apache.org/bugzilla/show_bug.cgi?id=31789 > This was fixed in 1.0 and 1.1 but never got added to 1.2 so we missed this here too. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-149) Patch Taglibs Bug 33934

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-149?page=com.atlassian.jira.plugin.s... ] Shelly McGowan reassigned JBEE-149: ----------------------------------- Assignee: Tomaz Cerar (was: Shelly McGowan) > Patch Taglibs Bug 33934 > ----------------------- > > Key: JBEE-149 > URL: https://issues.jboss.org/browse/JBEE-149 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jstl-api > Affects Versions: jboss-jstl-api_1.2_spec-1.0.5.Final > Reporter: Kevin Formsma > Assignee: Tomaz Cerar > > Taglibs fixed a bug where SetTag would retain references to the target object, causing pooled SetTag instances to have much higher memory usage when the target object is large. When using many web threads in JBoss 7.2.2, our heap grows due to these objects being associated to pooled SetTags. > https://issues.apache.org/bugzilla/show_bug.cgi?id=33934 > Can this patch be fixed in the jboss fork of taglibs as well? -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-220) Java 8 & Streams/Consumers - javassist.bytecode.InterfaceMethodrefInfo cannot be cast to javassist.bytecode.MethodrefInfo

by Stefan Hendriks (JIRA)

Stefan Hendriks created JASSIST-220: --------------------------------------- Summary: Java 8 & Streams/Consumers - javassist.bytecode.InterfaceMethodrefInfo cannot be cast to javassist.bytecode.MethodrefInfo Key: JASSIST-220 URL: https://issues.jboss.org/browse/JASSIST-220 Project: Javassist Issue Type: Bug Affects Versions: 3.18.1-GA Environment: OS X Reporter: Stefan Hendriks Assignee: Shigeru Chiba This is a bug report - which also exists on the powermock issue tracker at https://code.google.com/p/powermock/issues/detail?id=490 --- The problem is that an exception is thrown (see below how to reproduce) Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/bin/java -ea -Didea.launcher.port=7543 "-Didea.launcher.bin.path=/Applications/IntelliJ IDEA 13.app/bin" -Dfile.encoding=UTF-8 -classpath "/Applications/IntelliJ IDEA 13.app/lib/idea_rt.jar:/Applications/IntelliJ IDEA 13.app/plugins/junit/lib/junit-rt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/lib/ant-javafx.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/lib/dt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/lib/javafx-mx.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/lib/jconsole.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/lib/sa-jdi.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/lib/tools.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/charsets.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/deploy.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/htmlconverter.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/javaws.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/jce.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/jfr.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/jfxswt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/jsse.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/management-agent.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/plugin.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/resources.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/rt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/cldrdata.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/jfxrt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/nashorn.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/Users/shendriks/projects/katas/fizzbuzz/java/target/test-classes:/Users/shendriks/projects/katas/fizzbuzz/java/target/classes:/Users/shendriks/.m2/repository/junit/junit/4.8.2/junit-4.8.2.jar:/Users/shendriks/.m2/repository/org/hamcrest/hamcrest-all/1.3/hamcrest-all-1.3.jar:/Users/shendriks/.m2/repository/org/mockito/mockito-all/1.9.5/mockito-all-1.9.5.jar:/Users/shendriks/.m2/repository/org/powermock/powermock-module-junit4/1.5.4/powermock-module-junit4-1.5.4.jar:/Users/shendriks/.m2/repository/org/powermock/powermock-module-junit4-common/1.5.4/powermock-module-junit4-common-1.5.4.jar:/Users/shendriks/.m2/repository/org/powermock/powermock-core/1.5.4/powermock-core-1.5.4.jar:/Users/shendriks/.m2/repository/org/powermock/powermock-reflect/1.5.4/powermock-reflect-1.5.4.jar:/Users/shendriks/.m2/repository/org/objenesis/objenesis/2.1/objenesis-2.1.jar:/Users/shendriks/.m2/repository/org/javassist/javassist/3.18.1-GA/javassist-3.18.1-GA.jar:/Users/shendriks/.m2/repository/org/powermock/powermock-api-mockito/1.5.4/powermock-api-mockito-1.5.4.jar:/Users/shendriks/.m2/repository/org/powermock/powermock-api-support/1.5.4/powermock-api-support-1.5.4.jar" com.intellij.rt.execution.application.AppMain com.intellij.rt.execution.junit.JUnitStarter -ideVersion5 com.fundynamic.katas.FizzBuzzTest Internal Error occured. java.lang.IllegalStateException: Failed to transform class with name com.fundynamic.katas.FizzBuzz. Reason: javassist.bytecode.InterfaceMethodrefInfo cannot be cast to javassist.bytecode.MethodrefInfo at org.powermock.core.classloader.MockClassLoader.loadMockClass(MockClassLoader.java:214) at org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:144) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:67) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:340) at sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:114) at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:125) at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49) at sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:439) at sun.reflect.annotation.AnnotationParser.parseClassValue(AnnotationParser.java:420) at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724) at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531) at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355) at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286) at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120) at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72) at java.lang.Class.createAnnotationData(Class.java:3410) at java.lang.Class.annotationData(Class.java:3399) at java.lang.Class.getAnnotations(Class.java:3335) -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3174) Add view of batch jobs with ability to view, restart and stop

by James Perkins (JIRA)

James Perkins created WFLY-3174: ----------------------------------- Summary: Add view of batch jobs with ability to view, restart and stop Key: WFLY-3174 URL: https://issues.jboss.org/browse/WFLY-3174 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Batch Reporter: James Perkins Assignee: James Perkins Currently there is no way to view batch jobs for a deployment with in the batch subsystem management. There should be a way to view the batch jobs that have run on various deployments. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3115) JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources

by Thomas Kriechbaum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3115?page=com.atlassian.jira.plugin.... ] Thomas Kriechbaum commented on WFLY-3115: ----------------------------------------- I have tested this scenario with wildfly 8.0.1 SNAPSHOT Build #1040 (25.3.2014 - https://ci.jboss.org/hudson/job/WildFly-latest-master/1040/) With this build @Resource(lookup="java:app/url/Configuration") and the following entry in jboss-web.xml resolves an URL defined within standalone.xml <resource-ref> <res-ref-name>java:app/url/Configuration</res-ref-name> <jndi-name>java:jboss/url/Configuration</jndi-name> </resource-ref> see WFLY-2423 that covers the appropriate fix. > JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources > ----------------------------------------------------------------------------------------- > > Key: WFLY-3115 > URL: https://issues.jboss.org/browse/WFLY-3115 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Thomas Kriechbaum > > When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported. > When defining JNDI-names (e.g. java:jboss/url/Configuration) instead of concrete URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml). > see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952 -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3114) @Resource(lookup="java:...") causes an exception for URL resources

by Thomas Kriechbaum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3114?page=com.atlassian.jira.plugin.... ] Thomas Kriechbaum commented on WFLY-3114: ----------------------------------------- I have tested this scenario with wildfly 8.0.1 SNAPSHOT Build #1040 (25.3.2014 - https://ci.jboss.org/hudson/job/WildFly-latest-master/1040/) With this build @Resource(lookup="java:...") does not throw an exception any more! see WFLY-2423 that covers the appropriate fix. > @Resource(lookup="java:...") causes an exception for URL resources > ------------------------------------------------------------------- > > Key: WFLY-3114 > URL: https://issues.jboss.org/browse/WFLY-3114 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Thomas Kriechbaum > > When referencing an URL resource via @Resource the lookup-property only supports a valid URLs (e.g. http://www.jboss.org). A JNDI-Name causes an exception (e.g. java:global/url/Configuration or java:app/url/Configuration) > Issue has been discussed in the user form. > Note: > @Resource(name="java:global/url/Configuration") works. > From my point of view, the javadoc of @Resource is not very easy to understand. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3164) Create customized Audit Logger

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3164?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-3164: ---------------------------------- One issue is that we currently only handle two kinds of 'events': -controller audit events -jmx audit events There is talk of supporting more events like authorization done, connection opened etc. so what we come up with needs to be flexible enough to handle those, and possibly more events like that in the future. The concern being if a user implements a custom formatter for 9.0.0, and we add some more events for 9.1.0 their custom formatter should still work although more events were added for 9.1.0. A half-baked idea, take with a pinch of salt, is that perhaps for the custom formatter we could have a reference back to one of the WF provided handler types as a 'fallback' for events not handled by the custom formatter. > Create customized Audit Logger > ------------------------------ > > Key: WFLY-3164 > URL: https://issues.jboss.org/browse/WFLY-3164 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Labels: EAP > Fix For: 9.0.0.CR1 > > > Some users want to have a single line audit log formatter. I think it would be better to have the ability to add your own formatter from a module, something along the lines of: > {code} > <custom-formatter code="org.blah.MyCustomFormatter" module="org.blah/mymodule"> > <property name="layout">...</property> > <property name="propB">...</property> > </custom-formatter> > {code} > We'd need an SPI, and a slight reworking of the audit log internals. In any case doing this will put us in a better position to provide the single line logger if this proposal is not acceptable to our users. -- 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

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