February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1312) connection-url is required when dataSourceClass is provided

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1312?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1312: ----------------------------------- Fix Version/s: WildFly/IronJacamar 1.3.3.Final 1.2.7.Final Affects Version/s: 1.2.6.Final > connection-url is required when dataSourceClass is provided > ----------------------------------------------------------- > > Key: JBJCA-1312 > URL: https://issues.jboss.org/browse/JBJCA-1312 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.2.Final, 1.2.6.Final > Reporter: Lin Gao > Assignee: Lin Gao > Fix For: WildFly/IronJacamar 1.3.3.Final, 1.2.7.Final > > > Method: {{LocalManagedConnectionFactory.createConnectionFactory}} requires connectionURL when dataSourceClass is specified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-232) Unclean shutdown of deployment scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-232?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-232: ----------------------------------------- [~ozizka] If you see this with WildFly 10.0.0.Final or the latest EAP 7 ER, please file a new JRIA with details. > Unclean shutdown of deployment scanner > -------------------------------------- > > Key: WFCORE-232 > URL: https://issues.jboss.org/browse/WFCORE-232 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha11 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.Beta4 > > > I happened to see this in a testsuite log file: > {code} > 2014-11-07 02:59:41,808 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0012: Scan of /opt/buildAgent/work/8feb0abb503148fe/testsuite/manualmode/target/deployment-test-bc636b67-df54-462d-9a13-3618a1755d3f threw Exception: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@146a4b2 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@e6cbcd[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 3] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) > at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:325) > at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:530) > at java.util.concurrent.ScheduledThreadPoolExecutor.execute(ScheduledThreadPoolExecutor.java:619) > at org.jboss.as.controller.ModelControllerImpl$3.executeAsync(ModelControllerImpl.java:669) > at org.jboss.as.controller.ModelControllerImpl$3.executeAsync(ModelControllerImpl.java:605) > at org.jboss.as.server.deployment.scanner.DefaultDeploymentOperations.deploy(DefaultDeploymentOperations.java:61) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:449) > at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$UndeployScanRunnable.run(FileSystemDeploymentService.java:538) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > 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:744) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} > DeploymentScannerService is calling stopScanner() on the scanner and then is shutting down the executor. But stopScanner does not wait for in progress tasks to complete, nor do the in-progress tasks recognize that shutdown is occurring and handle any problems differently (e.g. don't toss the above in the log.) > Waiting for tasks to complete could be tricky, e.g. imagine this race: > 1) Admin submits op to shutdown/reload, which has the controller lock and is now stopping services. > 2) Scan job kicks off, finds changes and wants to modify the model, so the task is blocking waiting for the controller lock. > Deadlock. > Now, this may not be a problem, as server reload tells MSC to remove the root service on the way out (i.e. after the bit where it blocks for stability) and then MSC threads take over, allowing the op thread to continue and release the lock. The shutdown handler spawns a thread to call System.exit. > But ^^^ is just a quick look, so be cautious! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6299) PostgreSQL Non-XA DS - relation does not exist

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6299?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved WFCORE-1416 to WFLY-6299: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-6299 (was: WFCORE-1416) > PostgreSQL Non-XA DS - relation does not exist > ---------------------------------------------- > > Key: WFLY-6299 > URL: https://issues.jboss.org/browse/WFLY-6299 > Project: WildFly > 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1074) Kie-spring read resources on EAP not working

by David virgil naranjo (JIRA)

David virgil naranjo created DROOLS-1074: -------------------------------------------- Summary: Kie-spring read resources on EAP not working Key: DROOLS-1074 URL: https://issues.jboss.org/browse/DROOLS-1074 Project: Drools Issue Type: Bug Affects Versions: 6.4.0.Beta2 Reporter: David virgil naranjo Assignee: Petr Široký had to touch little bit the Kie-Spring to get the resources correctly. This is the only class I had to touch: https://gist.github.com/dvirgiln/0f65d184c2004127b1db#file-gistfile1-txt-... getClass().getResource("/") is failing on EAP, it returns null This code needs to get the path of the kie-spring.jar. This is the only way I found to get the containing jar path. This code is working. Maybe you know another way. ClassLoader cl = getClass().getClassLoader(); URL url = getClass().getProtectionDomain().getCodeSource().getLocation(); configFilePath = url.getPath(); if (configFilePath.endsWith("!/")) { configFilePath = configFilePath.substring(0, configFilePath.length() - 2); } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[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)

8 years, 2 months

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)

8 years, 2 months

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)

8 years, 2 months

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)

8 years, 2 months

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)

8 years, 2 months

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)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2016