April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-434) Fix AuditLogFieldsOfLogTestCase

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-434?page=com.atlassian.jira.plugin... ] Tomaz Cerar resolved WFCORE-434. -------------------------------- Fix Version/s: 1.0.0.Alpha19 Resolution: Done > Fix AuditLogFieldsOfLogTestCase > ------------------------------- > > Key: WFCORE-434 > URL: https://issues.jboss.org/browse/WFCORE-434 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 1.0.0.Alpha19 > > > Test started to fail with: > {noformat} > java.lang.IllegalArgumentException: Invalid character: - > at org.jboss.dmr.JSONParserImpl.invalid(JSONParserImpl.java:136) > at org.jboss.dmr.JSONParser.yyLex(JSONParser.java:596) > at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:662) > at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1390) > at org.jboss.as.test.manualmode.auditlog.AuditLogFieldsOfLogTestCase.testAuditLoggingFields(AuditLogFieldsOfLogTestCase.java:106) > {noformat} > message was (notice the extra "-" in front) > {noformat} > - { > "type" : "core", > "r/o" : false, > "booting" : false, > "version" : "9.0.0.Alpha1", > "user" : "IAmAdmin", > "domainUUID" : null, > "access" : "NATIVE", > "remote-address" : "127.0.0.1/127.0.0.1", > "success" : true, > "ops" : [{ > "operation" : "write-attribute", > "address" : [ > { > "core-service" : "management" > }, > { > "access" : "audit" > }, > { > "logger" : "audit-log" > } > ], > "name" : "log-boot", > "value" : true, > "operation-headers" : { > "caller-type" : "user", > "access-mechanism" : "NATIVE" > } > }] > } > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-626) Global list-get operation can inadvertently create list elements

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-626?page=com.atlassian.jira.plugin... ] Tomaz Cerar resolved WFCORE-626. -------------------------------- Assignee: Paul Ferraro (was: Tomaz Cerar) Resolution: Done > Global list-get operation can inadvertently create list elements > ---------------------------------------------------------------- > > Key: WFCORE-626 > URL: https://issues.jboss.org/browse/WFCORE-626 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.0.0.CR1 > > > Consider the following sequence of operations: > # :list-clear(name=attribute) > # :list-get(name=attribute, index=0) > # :list-add(name=attribute, value=test) > # :list-get(name=attribute, index=0) > #2 will return <undefined> as expected. The expected result of #4 is "test". However, it returns <undefined>. This is because #2 will create the missing element at index 0 causing #3 to operate on index 1. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-159) PropertyNotFoundException when the property is a JDK8 defender method

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBEE-159?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar moved WFLY-3687 to JBEE-159: ---------------------------------------- Project: JBoss JavaEE Spec APIs (was: WildFly) Key: JBEE-159 (was: WFLY-3687) Workflow: classic default workflow (was: GIT Pull Request workflow ) Affects Version/s: jboss-el-api_3.0_spec-1.0.2.Final (was: 8.1.0.Final) Component/s: jboss-el-api (was: EE) > PropertyNotFoundException when the property is a JDK8 defender method > --------------------------------------------------------------------- > > Key: JBEE-159 > URL: https://issues.jboss.org/browse/JBEE-159 > Project: JBoss JavaEE Spec APIs > Issue Type: Enhancement > Components: jboss-el-api > Affects Versions: jboss-el-api_3.0_spec-1.0.2.Final > Reporter: Rich DiCroce > Assignee: Tomaz Cerar > Priority: Minor > Labels: java8 > > I have a class that implements an interface that uses Java 8's new defender methods feature. Some getters on the interface have default implementations, and the concrete classes don't override them. > If I try to refer to one of these getters as a property like so: > {code:xml} > value="#{cc.filter.filter.valueChoices}" > {code} > Then I get this exception: > {noformat} > Caused by: javax.el.PropertyNotFoundException: The class 'com.lapis.jsf.framework.dao.search.DefaultEntityFilter' does not have the property 'valueChoices'. > at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:731) [jboss-el-api_3.0_spec-1.0.3.Final.jar:1.0.3.Final] > at javax.el.BeanELResolver.getValue(BeanELResolver.java:351) [jboss-el-api_3.0_spec-1.0.3.Final.jar:1.0.3.Final] > at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.2.6-jbossorg-4.jar:] > at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.2.6-jbossorg-4.jar:] > at com.sun.el.parser.AstValue.getValue(AstValue.java:140) [javax.el-3.0.0.jar:] > at com.sun.el.parser.AstValue.getValue(AstValue.java:204) [javax.el-3.0.0.jar:] > at com.sun.el.parser.AstEmpty.getValue(AstEmpty.java:66) [javax.el-3.0.0.jar:] > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:226) [javax.el-3.0.0.jar:] > at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] > at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] > at com.sun.faces.facelets.el.ContextualCompositeValueExpression.getValue(ContextualCompositeValueExpression.java:158) [jsf-impl-2.2.6-jbossorg-4.jar:] > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.2.6-jbossorg-4.jar:] > ... 68 more > {noformat} > Two workarounds exist. One: you can override the default method in a concrete class and have it just call the default super method. Two: you can call the getter using a method expression instead of a value expression. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-511) KieContainerImpl.updateResourcesIncrementally throws NullPointerException when a package doesn't exist

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-511?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-511: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1195464|https://bugzilla.redhat.com/show_bug.cgi?id=1195464] from MODIFIED to ON_QA > KieContainerImpl.updateResourcesIncrementally throws NullPointerException when a package doesn't exist > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-511 > URL: https://issues.jboss.org/browse/DROOLS-511 > Project: Drools > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Mike Wilson > Assignee: Mario Fusco > Labels: backport-to-6.0.x > Fix For: 6.2.0.CR1 > > > When calling KieContainerImpl.updateToVersion(ReleaseId), we sometimes experience a NullPointerException during a chained set of method calls that try to obtain a package, and then a rule within it. > If the package is null, a NullPointerException is thrown, because there is no check in place before that call to get the rule from the package. > To prevent this, a null check should be added to the package before trying to get the rule from it. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3549) Deadlock during shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3549?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3549: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1184532|https://bugzilla.redhat.com/show_bug.cgi?id=1184532] from ASSIGNED to MODIFIED > Deadlock during shutdown > ------------------------ > > Key: WFLY-3549 > URL: https://issues.jboss.org/browse/WFLY-3549 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: David Lloyd > Fix For: 8.2.0.Final > > > This deadlock appeared in an Arquillian test: > {noformat} > Found one Java-level deadlock: > ============================= > "undefined": > waiting to lock monitor 0x00007f67a421bfa8 (object 0x00000000e0700480, a org.jboss.as.threads.ScheduledThreadPoolService), > which is held by "MSC service thread 1-2" > "MSC service thread 1-2": > waiting for ownable synchronizer 0x00000000e0700618, (a java.util.concurrent.locks.ReentrantLock$NonfairSync), > which is held by "undefined" > Java stack information for the threads listed above: > =================================================== > "undefined": > at org.jboss.as.threads.ScheduledThreadPoolService$ExecutorImpl.terminated(ScheduledThreadPoolService.java:121) > - waiting to lock <0x00000000e0700480> (a org.jboss.as.threads.ScheduledThreadPoolService) > at java.util.concurrent.ThreadPoolExecutor.tryTerminate(ThreadPoolExecutor.java:704) > at java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1006) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1163) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > "MSC service thread 1-2": > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000e0700618> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197) > at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214) > at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290) > at java.util.concurrent.ThreadPoolExecutor.interruptIdleWorkers(ThreadPoolExecutor.java:781) > at java.util.concurrent.ThreadPoolExecutor.tryTerminate(ThreadPoolExecutor.java:695) > at java.util.concurrent.ThreadPoolExecutor.shutdown(ThreadPoolExecutor.java:1397) > at java.util.concurrent.ScheduledThreadPoolExecutor.shutdown(ScheduledThreadPoolExecutor.java:759) > at org.jboss.as.threads.ManagedScheduledExecutorService.internalShutdown(ManagedScheduledExecutorService.java:53) > at org.jboss.as.threads.ScheduledThreadPoolService.stop(ScheduledThreadPoolService.java:67) > - locked <0x00000000e0700480> (a org.jboss.as.threads.ScheduledThreadPoolService) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > 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:724) > Found 1 deadlock. > {noformat} > Looks like two MSC service threads exited and tried to terminate the thread pool at the same time. And because the MSC threads are not daemon threads, the entire JVM hangs and blocks the Arquillian test that was waiting for the container to shut down. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-579) ProxyMetadataSource does not return JDK8 'default' methods from interfaces

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFCORE-579?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFCORE-579: ----------------------------------- Summary: ProxyMetadataSource does not return JDK8 'default' methods from interfaces (was: ProxyMetadataSource does not return JDK8 'default' methods fro minterfaces) > ProxyMetadataSource does not return JDK8 'default' methods from interfaces > -------------------------------------------------------------------------- > > Key: WFCORE-579 > URL: https://issues.jboss.org/browse/WFCORE-579 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha19 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4515) Fix clustering transformers and reenable in mixed-domain tests

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4515?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-4515: -------------------------------------- The problem with 6.3.0 seem to be different though, i.e. {noformat}ERROR: JBAS014612: Operation ("add") failed - address: ([ ("subsystem" => "infinispan"), ("cache-container" => "maximal"), ("invalidation-cache" => "invalid"), ("remote-store" => "REMOTE_STORE") ]){noformat} > Fix clustering transformers and reenable in mixed-domain tests > -------------------------------------------------------------- > > Key: WFLY-4515 > URL: https://issues.jboss.org/browse/WFLY-4515 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 9.0.0.Beta2 > Reporter: Kabir Khan > Assignee: Radoslav Husar > Priority: Critical > Fix For: 9.0.0.CR1 > > > When running the jgroups and infinispan subsystem tests with -Djboss.test.transformers.eap there are some failures in the transformers tests. > Also, in the mixed domain tests it is not possible to enable these subsystems, so I have removed them from DomainAdjuster620 in https://github.com/wildfly/wildfly/pull/7350. They should be reenabled again as part of this Jira. > Some info from private mail: > {quote} > However, when transforming that to 7.2.0 by running: > mvn clean install -DallTests -Djboss.test.mixed.domain.dir=/Users/kabir/old-as7-releases/ -pl testsuite/mixed-domain/ -Dtest=MixedDomain_7_2_0_Final_TestSuite > I get the following error: > 11:59:43,682 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.io.IOException: 1-$-WFLYCTL0300: Transforming resource [ > ("profile" => "full-ha"), > ("subsystem" => "infinispan"), > ("cache-container" => "server"), > ("transport" => "TRANSPORT") > ] for host controller 'slave' to subsystem 'infinispan' model version '1.4.0' --there were problems with some of the attributes and this resource will need to be ignored on that host. Details of problems: [WFLYCLINF0027: Could not determine 'stack' attribute from JGroups subsystem] > I am not totally sure if this is the right solution, but I attempted to add a stack attribute to the transport, but it does not seem to get persisted so it goes away after reloading the DC (out of admin-only to normal mode). I also tried in standalone mode, and executing > /subsystem=infinispan/cache-container=server/transport=TRANSPORT:write-attribute(name=stack, value=udp) > and the stack does not get persisted. > It is probably a simple fix, but since I am not sure if it is the right fix or not, especially since adding this to the writer it also seems to be ignored by the parser. Perhaps this is a candidate for something along the lines of https://github.com/wildfly/wildfly/blob/master/clustering/jgroups/extensi... so that we can support old configs, but not actually use it on a server using the current version? > {quote} > Note that the above is when I was working on this, the 7.2.0 test has been removed. We now test EAP 6.2.0 and 6.3.0 compatibility. I believe the problem is similar there although I have not dug in very deeply. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-783) Deployment scanner service should use a separate operation for each deployment

by Jive JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-783?page=com.atlassian.jira.plugin.sy... ] Jive JIRA Integration updated AS7-783: -------------------------------------- Forum Reference: https://developer.jboss.org/message/925570#925570 > Deployment scanner service should use a separate operation for each deployment > ------------------------------------------------------------------------------ > > Key: AS7-783 > URL: https://issues.jboss.org/browse/AS7-783 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: No Release > > > The scanner is creating a single composite op for all deployments encountered in a scan, rather than individual ops. The effect is failures in on deployment results in rolling back the others. > This makes some sense when users change things after startup, since multiple changes within one scan are probably related to each other. But it's not the correct behavior at startup, since multiple apps may not be interrelated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-177) Add support for Base32 encoding and decoding

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-177?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-177: --------------------------- Description: Add support for Base32 encoding of ByteIterators and support for Base32 decoding of CodePointIterators. (was: Add Base32 encoding of ByteIterators and Base32 decoding of CodePointIterators.) > Add support for Base32 encoding and decoding > -------------------------------------------- > > Key: ELY-177 > URL: https://issues.jboss.org/browse/ELY-177 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: Farah Juma > Assignee: Farah Juma > > Add support for Base32 encoding of ByteIterators and support for Base32 decoding of CodePointIterators. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-177) Add support for Base32 encoding and decoding

by Farah Juma (JIRA)

Farah Juma created ELY-177: ------------------------------ Summary: Add support for Base32 encoding and decoding Key: ELY-177 URL: https://issues.jboss.org/browse/ELY-177 Project: WildFly Elytron Issue Type: Feature Request Components: Utils Reporter: Farah Juma Assignee: Farah Juma Add Base32 encoding of ByteIterators and Base32 decoding of CodePointIterators. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015