August 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5221) TimerServiceTimerService.getTimers() returns not only the associated timer entries for the current Bean

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5221?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-5221: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1257612 > TimerServiceTimerService.getTimers() returns not only the associated timer entries for the current Bean > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-5221 > URL: https://issues.jboss.org/browse/WFLY-5221 > Project: WildFly > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Blocker > > According to the spec [1] the getTimers() method must only return timers associated to the current EJB. > This is a huge issue if timers are cancled by this collection as it will remove all timers! > [1] https://docs.oracle.com/javaee/6/api/javax/ejb/TimerService.html#getTimer... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5221) TimerServiceTimerService.getTimers() returns not only the associated timer entries for the current Bean

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-5221: -------------------------------------- Summary: TimerServiceTimerService.getTimers() returns not only the associated timer entries for the current Bean Key: WFLY-5221 URL: https://issues.jboss.org/browse/WFLY-5221 Project: WildFly Issue Type: Bug Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink Priority: Blocker According to the spec [1] the getTimers() method must only return timers associated to the current EJB. This is a huge issue if timers are cancled by this collection as it will remove all timers! [1] https://docs.oracle.com/javaee/6/api/javax/ejb/TimerService.html#getTimer... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 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: -------------------------------------- There is a whole lot of new problems in the subsystem tests: remote servers changed types but are not transformed https://gist.github.com/rhusar/68a6e2a206f0ebab5539 jdbc store changed but is not transformed https://gist.github.com/rhusar/3328c813eea42db683e6 > 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: 10.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.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5219) Datasource transformer for EAP6.2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5219?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5219. ---------------------------- Resolution: Done > Datasource transformer for EAP6.2 > ---------------------------------- > > Key: WFLY-5219 > URL: https://issues.jboss.org/browse/WFLY-5219 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 10.0.0.Beta2 > Reporter: Hynek Švábek > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 10.0.0.CR1 > > > Datasource transformer for EAP6.2 work with wrong model version. > EAP 6.2 doesn't contain datasource model version 1.2, right version is 1.1 (jboss-as-datasources_1_1.xsd) > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > I execute this command over CLI > DomainController - EAP7 DR8 > Slave - EAP 6.2 > {code} > data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 > {code} > and get this output > {code} > Failed to execute line 'data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1': org.jboss.as.cli.CommandLineException: {"host-failure-descriptions" => {"slave" => "WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ], > \"operation\" => \"add\", > \"jndi-name\" => \"java:jboss/datasources/TestDS\", > \"driver-name\" => \"h2\", > \"connection-url\" => \"jdbc:h2:mem:test;DB_CLOSE_DELAY=-1\", > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"1dc420b4-d16f-4d0b-9cc5-3709939cff7d\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => 131382573 > } > } at resource [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ] to subsystem 'datasources' model version '1.2.0' -- attributes [statistics-enabled] WFLYJCA0088: Attributes [statistics-enabled] rejected. Must be true"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5219) Datasource transformer for EAP6.2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5219?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-5219: ---------------------------------- Since in 6.2.0 statistics enabled were not tweakable and always on, it means that the transformer is doing its job and making sure that only datasources with statistics-enabled=true (the default in the current version is false) can be used in profiles consumed by older slaves. If the data-source CLI command does not support setting statistics-enabled=true that is a different issue. > Datasource transformer for EAP6.2 > ---------------------------------- > > Key: WFLY-5219 > URL: https://issues.jboss.org/browse/WFLY-5219 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 10.0.0.Beta2 > Reporter: Hynek Švábek > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 10.0.0.CR1 > > > Datasource transformer for EAP6.2 work with wrong model version. > EAP 6.2 doesn't contain datasource model version 1.2, right version is 1.1 (jboss-as-datasources_1_1.xsd) > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > I execute this command over CLI > DomainController - EAP7 DR8 > Slave - EAP 6.2 > {code} > data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 > {code} > and get this output > {code} > Failed to execute line 'data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1': org.jboss.as.cli.CommandLineException: {"host-failure-descriptions" => {"slave" => "WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ], > \"operation\" => \"add\", > \"jndi-name\" => \"java:jboss/datasources/TestDS\", > \"driver-name\" => \"h2\", > \"connection-url\" => \"jdbc:h2:mem:test;DB_CLOSE_DELAY=-1\", > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"1dc420b4-d16f-4d0b-9cc5-3709939cff7d\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => 131382573 > } > } at resource [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ] to subsystem 'datasources' model version '1.2.0' -- attributes [statistics-enabled] WFLYJCA0088: Attributes [statistics-enabled] rejected. Must be true"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5219) Datasource transformer for EAP6.2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5219?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-5219: ---------------------------------- The xsd and the actual model version are independent. The model version is 1.2.0, see https://github.com/jbossas/jboss-eap/blob/EAP_6.2.0.GA/connector/src/main... > Datasource transformer for EAP6.2 > ---------------------------------- > > Key: WFLY-5219 > URL: https://issues.jboss.org/browse/WFLY-5219 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 10.0.0.Beta2 > Reporter: Hynek Švábek > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 10.0.0.CR1 > > > Datasource transformer for EAP6.2 work with wrong model version. > EAP 6.2 doesn't contain datasource model version 1.2, right version is 1.1 (jboss-as-datasources_1_1.xsd) > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > I execute this command over CLI > DomainController - EAP7 DR8 > Slave - EAP 6.2 > {code} > data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 > {code} > and get this output > {code} > Failed to execute line 'data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1': org.jboss.as.cli.CommandLineException: {"host-failure-descriptions" => {"slave" => "WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ], > \"operation\" => \"add\", > \"jndi-name\" => \"java:jboss/datasources/TestDS\", > \"driver-name\" => \"h2\", > \"connection-url\" => \"jdbc:h2:mem:test;DB_CLOSE_DELAY=-1\", > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"1dc420b4-d16f-4d0b-9cc5-3709939cff7d\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => 131382573 > } > } at resource [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ] to subsystem 'datasources' model version '1.2.0' -- attributes [statistics-enabled] WFLYJCA0088: Attributes [statistics-enabled] rejected. Must be true"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-925) Ability to use proxy in MavenUtil

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-925?page=com.atlassian.jira.plugin... ] Marek Kopecký moved JBEAP-902 to WFCORE-925: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-925 (was: JBEAP-902) Workflow: GIT Pull Request workflow (was: CDW v1) Affects Version/s: (was: 7.0.0.DR9) Component/s: Test Suite (was: Test Suite) Target Release: (was: 7.0.0.GA) > Ability to use proxy in MavenUtil > --------------------------------- > > Key: WFCORE-925 > URL: https://issues.jboss.org/browse/WFCORE-925 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Marek Kopecký > Assignee: Marek Kopecký > > WildFly Core testsuite can be run on pure-IPv6 machines. Proxy could be used in that case. > But some tests use MavenUtil class for download some dependencies. And this class can not use proxy server. > This MavenUtil should check "proxyHost" and "proxyPort" environment variables. If they are set, MavenUtil class should set proxy. If these variables are not set, proxy is not used. These variables are used by maven too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5219) Datasource transformer for EAP6.2

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-5219?page=com.atlassian.jira.plugin.... ] Hynek Švábek updated WFLY-5219: ------------------------------- Summary: Datasource transformer for EAP6.2 (was: Datasource transformer for EAP6.2 work with wrong model version.) > Datasource transformer for EAP6.2 > ---------------------------------- > > Key: WFLY-5219 > URL: https://issues.jboss.org/browse/WFLY-5219 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 10.0.0.Beta2 > Reporter: Hynek Švábek > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 10.0.0.CR1 > > > Datasource transformer for EAP6.2 work with wrong model version. > EAP 6.2 doesn't contain datasource model version 1.2, right version is 1.1 (jboss-as-datasources_1_1.xsd) > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > I execute this command over CLI > DomainController - EAP7 DR8 > Slave - EAP 6.2 > {code} > data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 > {code} > and get this output > {code} > Failed to execute line 'data-source add --profile=full-ha --jndi-name=java:jboss/datasources/TestDS --name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1': org.jboss.as.cli.CommandLineException: {"host-failure-descriptions" => {"slave" => "WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ], > \"operation\" => \"add\", > \"jndi-name\" => \"java:jboss/datasources/TestDS\", > \"driver-name\" => \"h2\", > \"connection-url\" => \"jdbc:h2:mem:test;DB_CLOSE_DELAY=-1\", > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"1dc420b4-d16f-4d0b-9cc5-3709939cff7d\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => 131382573 > } > } at resource [ > (\"profile\" => \"full-ha\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"java:jboss/datasources/TestDS\") > ] to subsystem 'datasources' model version '1.2.0' -- attributes [statistics-enabled] WFLYJCA0088: Attributes [statistics-enabled] rejected. Must be true"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-896) ClassObjectType deserialization doesn't work under OSGi

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-896?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-896. -------------------------------- Fix Version/s: 6.3.0.CR2 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/98523dd7b > ClassObjectType deserialization doesn't work under OSGi > ------------------------------------------------------- > > Key: DROOLS-896 > URL: https://issues.jboss.org/browse/DROOLS-896 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.3.0.CR2 > > > ClassObjectType deserialization don't use the ClassLoader stored in the DroolsObjectInput and then is not able to instance the right Class object under OSGi. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-896) ClassObjectType deserialization doesn't work under OSGi

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-896: ---------------------------------- Summary: ClassObjectType deserialization doesn't work under OSGi Key: DROOLS-896 URL: https://issues.jboss.org/browse/DROOLS-896 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco ClassObjectType deserialization don't use the ClassLoader stored in the DroolsObjectInput and then is not able to instance the right Class object under OSGi. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 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 August 2015