October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7395) Allow to provide deployment dependency to JNDI resource

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-7395?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-7395: --------------------------------- Description: For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly 10.x For example if EJB contains dependency to queue registered in JNDI: {code} @Resource(mappedName = "java:/jms/queue/OutQueue") private Queue outQueue; {code} then it would not get deployed when OutQueue is not present. Purpose of this feature request is to add possibility to provide such dependency in the way as @org.jboss.annotation.ejb.Depends did. was: For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly 10.x For example if EJB contains dependency to queue registered in JNDI: {code} @Resource(mappedName = "java:/jms/queue/OutQueue") private Queue outQueue; {code} then it would not get deployed when OutQueue is not present. > Allow to provide deployment dependency to JNDI resource > ------------------------------------------------------- > > Key: WFLY-7395 > URL: https://issues.jboss.org/browse/WFLY-7395 > Project: WildFly > Issue Type: Feature Request > Components: Server > Affects Versions: 10.1.0.Final > Reporter: Miroslav Novak > Assignee: Jason Greene > > For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly 10.x > For example if EJB contains dependency to queue registered in JNDI: > {code} > @Resource(mappedName = "java:/jms/queue/OutQueue") > private Queue outQueue; > {code} > then it would not get deployed when OutQueue is not present. Purpose of this feature request is to add possibility to provide such dependency in the way as @org.jboss.annotation.ejb.Depends did. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7395) Allow to provide deployment dependency to JNDI resource

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-7395: ------------------------------------ Summary: Allow to provide deployment dependency to JNDI resource Key: WFLY-7395 URL: https://issues.jboss.org/browse/WFLY-7395 Project: WildFly Issue Type: Feature Request Components: Server Affects Versions: 10.1.0.Final Reporter: Miroslav Novak Assignee: Jason Greene For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly 10.x For example if EJB contains dependency to queue registered in JNDI: {code} @Resource(mappedName = "java:/jms/queue/OutQueue") private Queue outQueue; {code} then it would not get deployed when OutQueue is not present. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7394) Redeploy deployment if all missing dependencies for deployment are corrected

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-7394: ------------------------------------ Summary: Redeploy deployment if all missing dependencies for deployment are corrected Key: WFLY-7394 URL: https://issues.jboss.org/browse/WFLY-7394 Project: WildFly Issue Type: Enhancement Components: Server Affects Versions: 10.1.0.Final Reporter: Miroslav Novak Assignee: Jason Greene If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. This behavior could be configurable. For example if you deploy EJB which injects queue like: {code} @Resource(mappedName = "java:/jms/queue/OutQueue") private Queue outQueue; {code} and administrator deploys queue later then EJB would automatically get redeployed. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5703) Add an IBM ORB configuration to WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5703?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-5703: ------------------------------------- When I originally raised it it was specifically about transactions but I remember now I reshaped it to be about the ORB in its entirety. > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: WFLY-5703 > URL: https://issues.jboss.org/browse/WFLY-5703 > Project: WildFly > Issue Type: Feature Request > Components: IIOP > Reporter: Tom Jenkinson > Priority: Optional > > Placeholder to be moved to WFLY > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5703) Add an IBM ORB configuration to WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5703?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5703: -------------------------------- Component/s: (was: Transactions) > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: WFLY-5703 > URL: https://issues.jboss.org/browse/WFLY-5703 > Project: WildFly > Issue Type: Feature Request > Components: IIOP > Reporter: Tom Jenkinson > Priority: Optional > > Placeholder to be moved to WFLY > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5703) Add an IBM ORB configuration to WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5703?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-5703: ------------------------------------- Sorry, you are right. I will remove the Transactions component. Note I am the original reporter. > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: WFLY-5703 > URL: https://issues.jboss.org/browse/WFLY-5703 > Project: WildFly > Issue Type: Feature Request > Components: IIOP, Transactions > Reporter: Tom Jenkinson > Priority: Optional > > Placeholder to be moved to WFLY > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5703) Add an IBM ORB configuration to WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5703?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened WFLY-5703: --------------------------------- > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: WFLY-5703 > URL: https://issues.jboss.org/browse/WFLY-5703 > Project: WildFly > Issue Type: Feature Request > Components: IIOP, Transactions > Reporter: Tom Jenkinson > Priority: Optional > > Placeholder to be moved to WFLY > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6966) FatalError on Transaction Expired Entry Monitor during server shutdown

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6966?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-6966: ------------------------------------- It is not a consistent error. Unless something special is done in WFLY with the logger I expect other components could be coerced to emit a warn/error during shutdown. > FatalError on Transaction Expired Entry Monitor during server shutdown > ---------------------------------------------------------------------- > > Key: WFLY-6966 > URL: https://issues.jboss.org/browse/WFLY-6966 > Project: WildFly > Issue Type: Enhancement > Components: IIOP, Transactions > Affects Versions: 10.1.0.CR1 > Reporter: Ondra Chaloupka > Assignee: Tomasz Adamski > Priority: Minor > > I do experience intermittent errors being shown in server log during server shutdown. It happens time to time for server configured to use {{JTS}} transaction that {{Transaction Expired Entry Monitor}} shows {{FatalError}} during container shutdown. > I do experience this failure when jdbc object store is used. > The shutdown log looks > {code} > 2016-08-16 07:07:46,900 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment wmq.jmsra.rar (runtime-name: wmq.jmsra.rar) in 132ms > 2016-08-16 07:07:46,914 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 2016-08-16 07:07:46,914 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 2016-08-16 07:07:46,915 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 2016-08-16 07:07:46,921 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 2016-08-16 07:07:46,924 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment crashrecovery-jms-stateless-cmt.jar (runtime-name: crashrecovery-jms-stateless-cmt.jar) in 156ms > 2016-08-16 07:07:46,947 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 16) WFLYCLINF0003: Stopped client-mappings cache from ejb container > 2016-08-16 07:07:46,952 TRACE [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) InputObjectState::InputObjectState(0:ffff7f000001:55f44a88:57b2ec0b:8, Recovery/FactoryContact) > 2016-08-16 07:07:46,959 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 32) AMQ151003: resource adaptor stopped > 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) ORB::shutdown () > 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) OA::destroyRootPOA () > 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) RootOA::shutdownObject (Servant) > 2016-08-16 07:07:46,962 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA032018: Destroying TransactionManagerService > 2016-08-16 07:07:46,963 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA032014: Stopping transaction recovery manager > 2016-08-16 07:07:47,000 FATAL [com.arjuna.ats.jts] (Transaction Expired Entry Monitor) ARJUNA022006: The ORB has not been initialized yet > 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) Exception in thread "Transaction Expired Entry Monitor" com.arjuna.ats.arjuna.exceptions.FatalError > 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.ORBManager.getORB(ORBManager.java:56) > 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.restore_state(FactoryContactItem.java:264) > 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.restoreMe(FactoryContactItem.java:320) > 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.recreate(FactoryContactItem.java:100) > 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.ExpiredContactScanner.scan(ExpiredContactScanner.java:99) > 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:171) > 2016-08-16 07:07:47,001 DEBUG [com.arjuna.ats.arjuna] (Listener:4712) Recovery listener existing com.arjuna.ats.internal.arjuna.recovery.WorkerService > 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: Mode <== TERMINATED > 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: shutdown waiting for scan to end > 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: scan TERMINATED at phase 1 > 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread Status <== INACTIVE > 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread exiting > 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: shutdown scan wait complete > 2016-08-16 07:07:47,003 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0010: Unbound data source [java:jboss/datasources/jdbc-store] > 2016-08-16 07:07:47,006 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Stopped Driver service with driver-name = module_postgresql-9.4.1207.jar > 2016-08-16 07:07:47,012 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 32) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.SP16-redhat-1 [023d1e88-638c-11e6-927a-a180c25082cf] stopped > 2016-08-16 07:07:47,012 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP listener default suspending > 2016-08-16 07:07:47,013 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 2016-08-16 07:07:47,013 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0004: Undertow 1.3.21.Final-redhat-1 stopping > 2016-08-16 07:07:47,018 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) stopped in 250ms > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1033) Enhance XTS AS7 configuration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-1033?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-1033: ------------------------------------- There are things that could be done and I would note that Paul moved it from its original issues tracker (JBTM) based on my direction. > Enhance XTS AS7 configuration > ----------------------------- > > Key: WFLY-1033 > URL: https://issues.jboss.org/browse/WFLY-1033 > Project: WildFly > Issue Type: Enhancement > Components: XTS > Reporter: Andrew Dinn > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > The current integration of XTS into AS7 as an AS7 extension allows optional configuration of the coordinator URL from the <xts/> element in the AS7 standalone configuration file. No other configuration options are currently supported. > XTS ought to support more precise configuration. IN particular, it ought to be possible to enable or disable deployment of coordinator, participant or client services independently and also to choose whether to deploy WS-AT or WS-BA services or both. This requires selectively deploying only the required web service endpoints, selectively executing the required initialization routines and selectively loading the required high level service implementations and context factory implementations. > The XTS implementation has already been factored so as to to support such discriminated bootstrapping. So this task only requires modifying the AS7 extension code to manage the relevant configuration information and install the relevant values into the XTS environment configuration beans before starting the XTS service. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.3

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-6854: --------------------------------------- Hibernate ORM {{5.1.4.Final}} should be the target now. > Upgrade Hibernate ORM to 5.1.3 > ------------------------------- > > Key: WFLY-6854 > URL: https://issues.jboss.org/browse/WFLY-6854 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Emmanuel Bernard > Assignee: Scott Marlow > Fix For: 11.0.0.Alpha1 > > > This is a follow up on WFLY-6682. > After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users. > We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it. > PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

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