July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3359) Transferring an operation attachments to slaves may lead to an OOM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3359?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3359: ----------------------------------------------- Emanuel Muckenhuber <emuckenh(a)redhat.com> changed the Status of [bug 1108952|https://bugzilla.redhat.com/show_bug.cgi?id=1108952] from MODIFIED to ON_QA > Transferring an operation attachments to slaves may lead to an OOM > ------------------------------------------------------------------ > > Key: WFLY-3359 > URL: https://issues.jboss.org/browse/WFLY-3359 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 9.0.0.Alpha1 > > > Transferring an operation attachment to a slave may lead to an OutOfMemoryError. > {code} > 19:44:47,794 ERROR [stderr] (domain-mgmt-handler-thread - 13) Exception in thread "domain-mgmt-handler-thread - 13" java.lang.OutOfMemoryError: Java heap space > 19:44:47,795 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.util.Arrays.copyOf(Arrays.java:2271) > 19:44:47,795 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.io.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java:178) > 19:44:47,795 ERROR [stderr] (domain-mgmt-handler-thread - 13) at org.jboss.as.controller.remote.TransactionalProtocolClientImpl$ReadAttachmentInputStreamRequestHandler$1.execute(TransactionalProtocolClientImpl.java:277) > 19:44:47,796 ERROR [stderr] (domain-mgmt-handler-thread - 13) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283) > 19:44:47,796 ERROR [stderr] (domain-mgmt-handler-thread - 13) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504) > 19:44:47,797 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > 19:44:47,797 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > 19:44:47,797 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.lang.Thread.run(Thread.java:724) > 19:44:47,798 ERROR [stderr] (domain-mgmt-handler-thread - 13) at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBEE-148?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on JBEE-148: ---------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1088423|https://bugzilla.redhat.com/show_bug.cgi?id=1088423] from MODIFIED to ON_QA > 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 > Security Level: Public(Everyone can see) > 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 > Fix For: jboss-jstl-api_1.2_spec-1.1.1.Final, jboss-jstl-api_1.2_spec-1.0.6.Final > > 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 was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3349) Pull cosmetic schema changes from EAP to WildFly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3349?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3349: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1097311|https://bugzilla.redhat.com/show_bug.cgi?id=1097311] from MODIFIED to ON_QA > Pull cosmetic schema changes from EAP to WildFly > ------------------------------------------------ > > Key: WFLY-3349 > URL: https://issues.jboss.org/browse/WFLY-3349 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3304) RemoteDomainConnectionService.fetchDomainWideConfiguration() isn't properly implemented

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3304?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3304: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1093866|https://bugzilla.redhat.com/show_bug.cgi?id=1093866] from MODIFIED to ON_QA > RemoteDomainConnectionService.fetchDomainWideConfiguration() isn't properly implemented > --------------------------------------------------------------------------------------- > > Key: WFLY-3304 > URL: https://issues.jboss.org/browse/WFLY-3304 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final, 8.1.0.CR1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.Alpha1 > > > The WFLY-2043 implementation is not working correctly because fetching the config from the master without fully registering is not properly implemented. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3570) I get NullPointerException when using ManagedScheduledExecutorService.scheduleAtFixedRate

by Pavel Abizyaev (JIRA)

Pavel Abizyaev created WFLY-3570: ------------------------------------ Summary: I get NullPointerException when using ManagedScheduledExecutorService.scheduleAtFixedRate Key: WFLY-3570 URL: https://issues.jboss.org/browse/WFLY-3570 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Pavel Abizyaev Assignee: Jason Greene When I try to run a task with a small period (1 second or less) using ManagedScheduledExecutorService.scheduleAtFixedRate sometimes I get NullPointerException at http://grepcode.com/file/repo1.maven.org/maven2/org.wildfly/wildfly-ee/8.... line 167 (resetHandles is null). I think it occurs when a next task has run before a previous finishes. On 8.1.0 I have the same problem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3569) DB2 jdbc driver and XA datasource

by Philippe Van Der Gucht (JIRA)

Philippe Van Der Gucht created WFLY-3569: -------------------------------------------- Summary: DB2 jdbc driver and XA datasource Key: WFLY-3569 URL: https://issues.jboss.org/browse/WFLY-3569 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.1.0.Final Reporter: Philippe Van Der Gucht Assignee: Jason Greene Our type 4 JDBC compliant driver has trouble when writing to two different xa-datasources. A write has been issued to the datasources but not committed (2 phase). Then, before the commit, a read is done from one of the datasources and this happens: {noformat} 2014-06-30 15:53:59,837 WARN [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (default task-2) IJ000305: Connection error occured: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@1de1a1e[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@187619 connection handles=0 lastUse=1404136358809 trackByTx=true pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@1d0f8a mcp=SemaphoreArrayListManagedConnectionPool@b559c4[pool=ourDS] xaResource=XAResourceWrapperImpl@1e747c0[xaResource=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection(a)187619 pad=false overrideRmValue=null productName=IDS/UNIX64 productVersion=IFX11700 jndiName=java:/ourDS] txSync=null]: com.ibm.db2.jcc.am.XaException: [jcc][t4][10401][12066][4.13.127] XA exception: XAER_NOTA ERRORCODE=-4228, SQLSTATE=null at com.ibm.db2.jcc.am.id.c(id.java:454) at com.ibm.db2.jcc.am.id.c(id.java:478) at com.ibm.db2.jcc.t4.bc.a(bc.java:2094) at com.ibm.db2.jcc.t4.bc.a(bc.java:2333) at com.ibm.db2.jcc.t4.bc.start(bc.java:1934) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.start(XAManagedConnection.java:259) at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.start(XAResourceWrapperImpl.java:203) {noformat} datasource configuration: {code:xml} <xa-datasource jndi-name="java:/ourDS" pool-name="ourDS" enabled="true"> <xa-datasource-property name="ServerName">127.0.0.1</xa-datasource-property> <xa-datasource-property name="PortNumber">9033</xa-datasource-property> <xa-datasource-property name="DatabaseName">ours</xa-datasource-property> <xa-datasource-property name="DriverType">4</xa-datasource-property> <xa-datasource-class>com.ibm.db2.jcc.DB2XADataSource</xa-datasource-class> <driver>com.informix</driver> <security> <user-name>user</user-name> <password>password</password> </security> </xa-datasource> {code:xml} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-226) automatical modification of class and method Annotation

by Paolo Paolo (JIRA)

[ https://issues.jboss.org/browse/JASSIST-226?page=com.atlassian.jira.plugi... ] Paolo Paolo commented on JASSIST-226: ------------------------------------- The created class works well if I don't use the RDFBeans library. Otherwise in another project the string "@RDFBean(value="http...")" works with the RDFBeans library. This is the console output: Exception in thread "main" java.lang.reflect.GenericSignatureFormatError at sun.reflect.generics.parser.SignatureParser.error(Unknown Source) at sun.reflect.generics.parser.SignatureParser.parsePackageNameAndSimpleClassTypeSignature(Unknown Source) at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignature(Unknown Source) at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(Unknown Source) at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(Unknown Source) at sun.reflect.generics.parser.SignatureParser.parseTypeSignature(Unknown Source) at sun.reflect.generics.parser.SignatureParser.parseTypeSig(Unknown Source) at sun.reflect.annotation.AnnotationParser.parseSig(Unknown Source) at sun.reflect.annotation.AnnotationParser.parseAnnotation(Unknown Source) at sun.reflect.annotation.AnnotationParser.parseAnnotations2(Unknown Source) at sun.reflect.annotation.AnnotationParser.parseAnnotations(Unknown Source) at java.lang.reflect.Method.declaredAnnotations(Unknown Source) at java.lang.reflect.Method.getAnnotation(Unknown Source) at java.beans.PropertyDescriptor.setReadMethod(Unknown Source) at java.beans.PropertyDescriptor.<init>(Unknown Source) at java.beans.Introspector.getTargetPropertyInfo(Unknown Source) at java.beans.Introspector.getBeanInfo(Unknown Source) at java.beans.Introspector.getBeanInfo(Unknown Source) at com.viceversatech.rdfbeans.reflect.RDFBeanInfo.<init>(RDFBeanInfo.java:85) at com.viceversatech.rdfbeans.reflect.RDFBeanInfo.get(RDFBeanInfo.java:56) at com.viceversatech.rdfbeans.RDFBeanManager.getAll(RDFBeanManager.java:305) at main.AAL_Test.main(AAL_Test.java:44) > automatical modification of class and method Annotation > ------------------------------------------------------- > > Key: JASSIST-226 > URL: https://issues.jboss.org/browse/JASSIST-226 > Project: Javassist > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.18.0-GA > Environment: JavaSE-1.7, Eclipse Kepler > Reporter: Paolo Paolo > Assignee: Shigeru Chiba > Labels: annotations > > I'm using Javassist to create .class file at runtime. Every method of the created class must have a Java Annotation ("@annotation example") with an URI. The problem is that the Annotation class modifies automatically the URI by substituting slashes with dots. > //the Annotation String that I need > @RDFBean('http://www.semanticweb.org/pi/2014/5/test#Test') > //the resulting String > @RDFBean('http:..www.semanticweb.org.pi.2014.5.test#Test') > Is there a way to prevent this String modification? > I suppose it's related to the different notation between a file path and a Java package. > This is the code: > ClassPool pool = ClassPool.getDefault(); > CtClass cc = pool.makeClass(className); > > ClassFile ccFile = cc.getClassFile(); > ConstPool constpool = ccFile.getConstPool(); > // create the annotation > AnnotationsAttribute attr = new AnnotationsAttribute(constpool, AnnotationsAttribute.visibleTag); > // classLocalName contains: http://www.semanticweb.org/pi/2014/5/test#Test > Annotation annot = new Annotation("RDFBean('" + classLocalName + "')", constpool); > attr.addAnnotation(annot); > ccFile.addAttribute(attr); -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3568) Not possible to use wrapped injectionTarget for some EE components

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-3568?page=com.atlassian.jira.plugin.... ] Jozef Hartinger moved WELD-1662 to WFLY-3568: --------------------------------------------- Project: WildFly (was: Weld) Key: WFLY-3568 (was: WELD-1662) Affects Version/s: 8.1.0.Final (was: 2.2.0.SP1) (was: 2.2.2.Final) Component/s: CDI / Weld (was: Extensions) > Not possible to use wrapped injectionTarget for some EE components > ------------------------------------------------------------------ > > Key: WFLY-3568 > URL: https://issues.jboss.org/browse/WFLY-3568 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.1.0.Final > Reporter: Tomas Remes > Assignee: Jozef Hartinger > > Using custom wrapped InjectionTarget should be available also for: > WS endpoint > EJB interceptor > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3414) moduleAlias should be optional in jboss-deployment-structure.xml

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFLY-3414?page=com.atlassian.jira.plugin.... ] Chao Wang reassigned WFLY-3414: ------------------------------- Assignee: Chao Wang (was: Jason Greene) > moduleAlias should be optional in jboss-deployment-structure.xml > ---------------------------------------------------------------- > > Key: WFLY-3414 > URL: https://issues.jboss.org/browse/WFLY-3414 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Harald Wellmann > Assignee: Chao Wang > > Very similar to WFLY-2851, there is still another issue where the schema {{jboss-deployment-structure-1_2.xsd}} expects a mandatory element {{moduleAlias}} in {{moduleType}}, which should be optional. > A module definition without {{moduleAlias}} works fine at runtime, but the {{jboss-deployment-structure.xml}} does not validate against the schema. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3567) Unchecked access to MSC Service Registry under JSM

by Dipak Kesarkar (JIRA)

Dipak Kesarkar created WFLY-3567: ------------------------------------ Summary: Unchecked access to MSC Service Registry under JSM Key: WFLY-3567 URL: https://issues.jboss.org/browse/WFLY-3567 Project: WildFly Issue Type: Support Request Security Level: Public (Everyone can see) Components: MSC Reporter: Dipak Kesarkar Assignee: David Lloyd When is the fix for this security issue https://access.redhat.com/security/cve/CVE-2014-0018 planned in Wildfly? In which version? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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