July 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4056) Graceful shutdown for JMS

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4056?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4056: ------------------------------- Parent: (was: WFLY-1247) Issue Type: Feature Request (was: Sub-task) > Graceful shutdown for JMS > ------------------------- > > Key: WFLY-4056 > URL: https://issues.jboss.org/browse/WFLY-4056 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Stuart Douglas > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4056) Graceful shutdown for JMS

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4056?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4056: ------------------------------- Fix Version/s: 11.0.0.Alpha1 > Graceful shutdown for JMS > ------------------------- > > Key: WFLY-4056 > URL: https://issues.jboss.org/browse/WFLY-4056 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Stuart Douglas > Assignee: Jeff Mesnil > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4634) Cannot start JDBC storage for Batch subsystem with the Driver in a deployment

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4634?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-4634. ------------------------------- Resolution: Out of Date This now works as part of WFLY-4811. > Cannot start JDBC storage for Batch subsystem with the Driver in a deployment > ----------------------------------------------------------------------------- > > Key: WFLY-4634 > URL: https://issues.jboss.org/browse/WFLY-4634 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.0.CR1 > Reporter: Jan Martiska > Assignee: James Perkins > Priority: Critical > > Steps to reproduce: > {noformat} > - deploy JDBC driver as a deployment (postgresql93.jar in this case) > - /subsystem=datasources/data-source=BatchProcessingDS:add(driver-name=postgresql93.jar, jndi-name="java:jboss/datasources/BatchProcessingDS", connection-url="some-url") > - /subsystem=batch/job-repository=jdbc:write-attribute(name=jndi-name,value="java:jboss/datasources/BatchProcessingDS") > - /subsystem=batch:write-attribute(name=job-repository-type,value=jdbc) > - :reload > {noformat} > The reload fails with: > {noformat} > 11:45:44,391 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."postgresql93.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."postgresql93.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "postgresql93.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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) > Caused by: javax.batch.operations.BatchRuntimeException: JBERET000621: Failed to look up datasource by jndi name java:jboss/datasources/BatchProcessingDS. > at org.jberet.repository.JdbcRepository.<init>(JdbcRepository.java:128) > at org.jberet.repository.JdbcRepository.create(JdbcRepository.java:109) > at org.wildfly.extension.batch.job.repository.JobRepositoryFactory.getJobRepository(JobRepositoryFactory.java:63) > at org.wildfly.extension.batch.deployment.BatchEnvironmentProcessor.deploy(BatchEnvironmentProcessor.java:71) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: javax.naming.NameNotFoundException: datasources/BatchProcessingDS [Root exception is java.lang.IllegalStateException] > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.doLookup(InitialContext.java:290) > at org.jberet.repository.JdbcRepository.<init>(JdbcRepository.java:126) > ... 9 more > Caused by: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) > at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:138) > at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46) > at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131) > ... 19 more > 11:45:44,396 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "postgresql93.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"postgresql93.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"postgresql93.jar\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"postgresql93.jar\" > Caused by: javax.batch.operations.BatchRuntimeException: JBERET000621: Failed to look up datasource by jndi name java:jboss/datasources/BatchProcessingDS. > Caused by: javax.naming.NameNotFoundException: datasources/BatchProcessingDS [Root exception is java.lang.IllegalStateException] > Caused by: java.lang.IllegalStateException"}} > 11:45:44,397 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "BatchProcessingDS") > ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.driver-demander.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]", > "jboss.data-source.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]" > ]} > 11:45:44,398 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "BatchProcessingDS") > ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.driver-demander.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]", > "jboss.data-source.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]", > "jboss.data-source.java:jboss/datasources/BatchProcessingDS is missing [jboss.jdbc-driver.postgresql93_jar]" > ]} > {noformat} > From reading the log, it looks to me like some sort of circular dependency problem: the JDBC driver won't start because there is a dependency on the datasource, but the datasource won't start because it has a dependency on the JDBC driver. > This doesn't seem to happen when the JDBC driver is deployed as a module, only as a deployment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5028) component upgrade to Hibernate ORM 5.0.0.CR4

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-5028?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-5028: ------------------------------- Priority: Blocker (was: Major) > component upgrade to Hibernate ORM 5.0.0.CR4 > -------------------------------------------- > > Key: WFLY-5028 > URL: https://issues.jboss.org/browse/WFLY-5028 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5028) component upgrade to Hibernate ORM 5.0.0.CR4

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-5028?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-5028: ------------------------------- Summary: component upgrade to Hibernate ORM 5.0.0.CR4 (was: component upgrade to Hibernate ORM 5.0.0.CR3) > component upgrade to Hibernate ORM 5.0.0.CR4 > -------------------------------------------- > > Key: WFLY-5028 > URL: https://issues.jboss.org/browse/WFLY-5028 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-853) Simplify the remote-outbound connections

by Tomasz Adamski (JIRA)

Tomasz Adamski created WFCORE-853: ------------------------------------- Summary: Simplify the remote-outbound connections Key: WFCORE-853 URL: https://issues.jboss.org/browse/WFCORE-853 Project: WildFly Core Issue Type: Feature Request Components: Remoting Affects Versions: 2.0.0.Alpha11 Reporter: Tomasz Adamski Assignee: Tomasz Adamski Create remote-outbound-group element in remoting configuration which gather connections that share the same configuration. http://lists.jboss.org/pipermail/wildfly-dev/2015-July/004235.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-852) add Hibernate Search deployment processor

by Scott Marlow (JIRA)

Scott Marlow created WFCORE-852: ----------------------------------- Summary: add Hibernate Search deployment processor Key: WFCORE-852 URL: https://issues.jboss.org/browse/WFCORE-852 Project: WildFly Core Issue Type: Task Components: Server Reporter: Scott Marlow Assignee: Jason Greene Fix For: 2.0.0.Alpha12 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-852) add Hibernate Search deployment processor

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFCORE-852?page=com.atlassian.jira.plugin... ] Scott Marlow reassigned WFCORE-852: ----------------------------------- Assignee: Scott Marlow (was: Jason Greene) > add Hibernate Search deployment processor > ----------------------------------------- > > Key: WFCORE-852 > URL: https://issues.jboss.org/browse/WFCORE-852 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 2.0.0.Alpha12 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5039) Batch JobXmlResolverService should safe copy values from the maps

by James Perkins (JIRA)

James Perkins created WFLY-5039: ----------------------------------- Summary: Batch JobXmlResolverService should safe copy values from the maps Key: WFLY-5039 URL: https://issues.jboss.org/browse/WFLY-5039 Project: WildFly Issue Type: Bug Components: Batch Reporter: James Perkins Assignee: James Perkins {code} 2015-07-30 12:37:31,658 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."jslxml_ejb_vehicle.ear"."jslxml_ejb_vehicle_client.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."jslxml_ejb_vehicle.ear"."jslxml_ejb_vehicle_client.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "jslxml_ejb_vehicle_client.jar" of deployment "jslxml_ejb_vehicle.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.0.0.Alpha11.jar:2.0.0.Alpha11] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40] Caused by: java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:711) [rt.jar:1.8.0_40] at java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:734) [rt.jar:1.8.0_40] at org.wildfly.extension.batch.jberet.deployment.BatchDeploymentResourceProcessor.deploy(BatchDeploymentResourceProcessor.java:60) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.0.0.Alpha11.jar:2.0.0.Alpha11] ... 5 more {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1285) rar-info: CCI interface information missing

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1285?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1285: ----------------------------------- Fix Version/s: 1.2.6.Final (was: 1.26) > rar-info: CCI interface information missing > ------------------------------------------- > > Key: JBJCA-1285 > URL: https://issues.jboss.org/browse/JBJCA-1285 > Project: IronJacamar > Issue Type: Bug > Components: AS > Reporter: Jesper Pedersen > Assignee: Johnathon Lee > Fix For: 1.2.6.Final > > > If a resource adapter is using CCI then the ConnectionFactory and Connection information isn't included in the report. > The information should be based directly on the actual interface classes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 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 July 2015