February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2022) XSD schemas do not properly validate

by Manuel Dominguez Sarmiento (JIRA)

Manuel Dominguez Sarmiento created JGRP-2022: ------------------------------------------------ Summary: XSD schemas do not properly validate Key: JGRP-2022 URL: https://issues.jboss.org/browse/JGRP-2022 Project: JGroups Issue Type: Bug Affects Versions: 3.6.8 Reporter: Manuel Dominguez Sarmiento Assignee: Bela Ban Priority: Minor Affected resources: - jgroups.xsd - relay.xsd - fork-stacks.xsd Paste these files into an Eclipse project, or run them through Oxygen XML or any other XML / XSD validator, you will get errors relating to src-resolve.4.1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6295) Wrong header comments on integration-tests.sh script

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6295?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-6295: -------------------------------------- Component/s: Test Suite (was: Documentation) Assignee: Eduardo Silva (was: Jason Greene) > Wrong header comments on integration-tests.sh script > ---------------------------------------------------- > > Key: WFLY-6295 > URL: https://issues.jboss.org/browse/WFLY-6295 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Eduardo Silva > Assignee: Eduardo Silva > Priority: Minor > > Wrong header comments on integration-tests.sh script, the header of integration-tests.sh script was copied of the build.sh script. > ### ====================================================================== ### > ## ## > ## This is the main entry point for the build system. ## > ## ## > ## Users should execute this file rather than 'mvn' to ensure ## > ## the correct version is being used with the correct configuration. ## > ## ## > ### ====================================================================== ### > # $Id: build.sh 105735 2010-06-04 19:45:13Z pgier $ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6298) Test suite crashes at : "jipijapa Hibernate 4.3.x (JPA 2.1) integration"

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6298?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-6298: ------------------------------------ Try using the "build.bat" command instead of directly using Maven. Try "build.bat clean install" > Test suite crashes at : "jipijapa Hibernate 4.3.x (JPA 2.1) integration" > ------------------------------------------------------------------------ > > Key: WFLY-6298 > URL: https://issues.jboss.org/browse/WFLY-6298 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.0.Final > Reporter: Shishir Subramanyam > Priority: Trivial > Attachments: Wildfly test suite error.JPG > > > The test suite fails at the step : "jipijapa Hibernate 4.3.x (JPA 2.1) integration". I did not make any changes to the code before running "mvn install" through cmd(windows) in the base directory -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1416) PostgreSQL Non-XA DS - relation does not exist

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1416?page=com.atlassian.jira.plugi... ] Jesper Pedersen closed WFCORE-1416. ----------------------------------- Resolution: Rejected Use the WildFly forum for questions > PostgreSQL Non-XA DS - relation does not exist > ---------------------------------------------- > > Key: WFCORE-1416 > URL: https://issues.jboss.org/browse/WFCORE-1416 > Project: WildFly Core > Issue Type: Bug > Environment: WildFly 10.0.0.Final, PostgreSQL 9.4, PostgreSQL JDBC Driver 9.3 and 9.4 > Reporter: Anton Saburov > Labels: datasource, postgresql > > I tried to check the same in WildFly 8.2.1 and 9.0.2 - everything is working > WildFly 10 - I get error. > Registered PostgreSQL JDBC driver as a module: > module add --name=org.postgresql --resources=postgresql-9.3-1102-jdbc41.jar --resource-delimiter=, --dependencies=javax.api,javax.transaction.api > Registered PostgreSQL JDBC driver: > /subsystem=datasources/jdbc-driver=postgresql:add(driver-name=postgresql, driver-module-name=org.postgresql, driver-class-name=org.postgresql.Driver, driver-datasource-class-name=org.postgresql.ds.PGSimpleDataSource, driver-xa-datasource-class-name=org.postgresql.xa.PGXADataSource) > Created Non-XA Datasource - MyDS and XA Datasource MyXADS > When I try to use Non-XA DS - I got error: relation "<table>" does not exist > When I try to use XA DS - all is OK. > I checked list of schema by SQL script: "select distinct table_schema from information_schema.tables" > For Non-XA I see only this: > - information_schema > - pg_default > For XA I see this: > - information_schema > - pg_default > - public > Maybe I have to make some additional options for DS ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5611) Change license of ejb3-ext-api to ASL

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5611?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-5611: ----------------------------------- Not whole ejb3 repo but just ejb3-ext-api part, https://github.com/wildfly/jboss-ejb3-ext-api which gives you for git log --format='%aE' | sort -u {noformat} arubinger(a)redhat.com cdewolf(a)redhat.com flavia.rainone(a)jboss.com jaikiran.pai(a)gmail.com jason.greene(a)redhat.com jmesnil(a)gmail.com jpai(a)redhat.com kkhan(a)redhat.com loubyansky(a)gmail.com paul.ferraro(a)redhat.com pgier(a)redhat.com sstark(a)redhat.com stuart.w.douglas(a)gmail.com wdecoste(a)redhat.com {noformat} Which are all RH employees or they ware at time of their contribution. > Change license of ejb3-ext-api to ASL > ------------------------------------- > > Key: WFLY-5611 > URL: https://issues.jboss.org/browse/WFLY-5611 > Project: WildFly > Issue Type: Task > Components: EJB > Reporter: David Lloyd > > Check commit history to ensure that all contributors to the current code base are within Red Hat or grant permission for the change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4840) Deprecated element cluster-passivation-store from ejb subsystem does not work

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-4840?page=com.atlassian.jira.plugin.... ] Dominik Pospisil reassigned WFLY-4840: -------------------------------------- Assignee: Dominik Pospisil (was: Radoslav Husar) > Deprecated element cluster-passivation-store from ejb subsystem does not work > ----------------------------------------------------------------------------- > > Key: WFLY-4840 > URL: https://issues.jboss.org/browse/WFLY-4840 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Ondřej Chaloupka > Assignee: Dominik Pospisil > Priority: Minor > > There is a mismatch in behaviour of deprecated element {{cluster-passivation-store}} under {{ejb}} subsystem. > When element is deprecated still it should work and only prints warning that it's deprecated. > {code} > [standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:read-resource() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"ejb3\"), > (\"cluster-passivation-store\" => \"infinispan\") > ]' not found", > "rolled-back" => true > } > {code} > but > {code} > [standalone@localhost:9990 /] /subsystem=ejb3/cluster-passivation-store=infinispan:add() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb.cache.factory.distributable.infinispan is already registered", > "rolled-back" => true > } > {code} > _A note:_ the element {{cluster-passivation-store}} was replaced by {{passivation-store}} which works fine -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6196) Tests fails in manualmode with security manager

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6196?page=com.atlassian.jira.plugin.... ] Fedor Gavrilov reassigned WFLY-6196: ------------------------------------ Assignee: Fedor Gavrilov > Tests fails in manualmode with security manager > ----------------------------------------------- > > Key: WFLY-6196 > URL: https://issues.jboss.org/browse/WFLY-6196 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Hynek Švábek > Assignee: Fedor Gavrilov > > *org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase#org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase* > *org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase#testTransactionJNDILookupDuringShutdownEvent* > {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.manualmode -Dts.noSmoke -Dtest=org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase > }} > Fail with: > {code} > ERROR [org.jboss.weld.Bootstrap] (MSC service thread 1-6) : java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "target" "read")" in code source "(vfs:/content/test.war/WEB-INF/classes <no signer certificates>)" of "null") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.SecurityManager.checkRead(SecurityManager.java:888) > at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:377) > at java.io.File.exists(File.java:814) > at org.jboss.as.test.manualmode.weld.extension.BeforeShutdownExtension.writeOutput(BeforeShutdownExtension.java:62) > at org.jboss.as.test.manualmode.weld.extension.BeforeShutdownExtension.lookupBeforeShutdown(BeforeShutdownExtension.java:37) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78) > at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:129) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:309) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:124) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:287) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:265) > at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:271) > at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:260) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:154) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:148) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53) > at org.jboss.weld.bootstrap.events.BeforeShutdownImpl.fire(BeforeShutdownImpl.java:41) > at org.jboss.weld.bootstrap.events.BeforeShutdownImpl.fire(BeforeShutdownImpl.java:32) > at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:72) > at org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113) > at org.jboss.as.weld.WeldStartService.stop(WeldStartService.java:128) > 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:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1073) Option to bypass start task operation in REST/JMS

by Ivo Bek (JIRA)

Ivo Bek created DROOLS-1073: ------------------------------- Summary: Option to bypass start task operation in REST/JMS Key: DROOLS-1073 URL: https://issues.jboss.org/browse/DROOLS-1073 Project: Drools Issue Type: Enhancement Components: kie server Affects Versions: 6.3.0.Final Reporter: Ivo Bek Assignee: Ivo Bek Today, it takes 2 requests to complete a task. In web development every request costs some time and in many scenarios it's enough to start and complete a task in one request without any delay. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6280) Can not call "visibility" bridged methods

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-6280?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-6280: ----------------------------- Component/s: (was: JSF) > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: WFLY-6280 > URL: https://issues.jboss.org/browse/WFLY-6280 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final, 10.0.0.Final > Reporter: Trond G. Ziarkowski > Assignee: Farah Juma > Labels: el > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6280) Can not call "visibility" bridged methods

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-6280?page=com.atlassian.jira.plugin.... ] Farah Juma reassigned WFLY-6280: -------------------------------- Assignee: Tomaz Cerar (was: Farah Juma) > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: WFLY-6280 > URL: https://issues.jboss.org/browse/WFLY-6280 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final, 10.0.0.Final > Reporter: Trond G. Ziarkowski > Assignee: Tomaz Cerar > Labels: el > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016