July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-556) Complete support for Bundle uninstall

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-556?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened WFLY-556: --------------------------------- Assignee: (was: Thomas Diesler) > Complete support for Bundle uninstall > ------------------------------------- > > Key: WFLY-556 > URL: https://issues.jboss.org/browse/WFLY-556 > Project: WildFly > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > > Bundle uninstall only removes the BundleRevision from the runtime if it is no longer in use. The classloader associated with an uninstalled bundle that is still in use remains active. > Approach #1 - "in use" semantic specific to Bundle deployments > An undeploy management operation undeploys the bundle revision but holds in the MODULE phase when the revision is still in use > This is similar to deferred MODULE phase for deploy operation > in use is not respected for non-osgi deployments and hence breaks bundle deployments that depend on them > Approach #2 - "in use" semantic applies to all deployment types > Undeploy will only destroy the Module service if the Module is not in use by another deployment > When Module usage drops to zero, undeploy continues and removes the deployment from management > This approach would map cleanly - there is no cascading destroy effect. i.e. when you undeploy a jar that a webapp depends on > Services provided by the undeployed deployment would always go down, only classloader destruction is deferred -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-555) Complete support for Bundle start/stop

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-555?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened WFLY-555: --------------------------------- Assignee: (was: Thomas Diesler) > Complete support for Bundle start/stop > --------------------------------------- > > Key: WFLY-555 > URL: https://issues.jboss.org/browse/WFLY-555 > Project: WildFly > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > Labels: roadmap > > A Bundle start/stop operation activates/deactivates the bundle services. The associated class loader and wiring is unaffected. > Approach #1 - start/stop is not mapped to deployment operations > Bundle deploy installs the Bundle to the Framework > Bundle is not resolved/started as part of the deploy operation > No module/classloader is created during deployment > All deployment processing that needs load classes/resources is skipped > No service provided by the bundle deployment is created > Bundle needs to be started/stopped explicitly > Bundle start/stop management operations are specific to bundle deployments > The POST_MODULE processing for OSGi enabled deployments (e.g. webapp) would need to be executed in an OSGi specific processor chain > OSGi enabled POST_MODULE DUPs have their functionality externalised such that it can get reused for start/stop operations > The start/stop processing chain must be traversable in both directions repeatedly > Approach #2 - start/stop is mapped to deployment operations > Bundle deploy installs the Bundle to the Framework and attempts to resolve/start the Bundle > If the Bundle can get resolved, a module/classloader is created as part of the DU processing > In case the Bundle cannot get resolved, DUP processing is deferred and MODULE phase processing is reattempted later based on an external trigger > Has the benefit that any deployment type can also be a Bundle > Bundle stop must reverse work that is done in POST_MODULE DUPs > POST_MODULE DUPs must be traversable in both direction multiple times > Currently, we use approach #2 with limited support from POST_MODULE DUPs (i.e. they are not designed to be executed multiple times for the same deployment). There is also the cleanup phase which breaks multiple executions of POST_MODULE DUPs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-559) Support Bundle deploy/undeploy from management operation

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-559?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened WFLY-559: --------------------------------- Assignee: (was: Thomas Diesler) > Support Bundle deploy/undeploy from management operation > -------------------------------------------------------- > > Key: WFLY-559 > URL: https://issues.jboss.org/browse/WFLY-559 > Project: WildFly > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > > There is a requirement that a bundle can install/uninstall other bundles during start/stop. We support auto start/stop for bundle deployments and explicit start/stop as management operations. > In both cases this would trigger a management operation (i.e. deploy/undeploy) from within the another management operation, which currently not supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-540) OSGi requirements for AS9

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-540?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened WFLY-540: --------------------------------- Assignee: (was: Thomas Diesler) > OSGi requirements for AS9 > ------------------------- > > Key: WFLY-540 > URL: https://issues.jboss.org/browse/WFLY-540 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > [jboss-as7-dev] [Resolving AS8/OSGi deployment disconnects|http://lists.jboss.org/pipermail/jboss-as7-dev/2013-April/007...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1603) Remove OSGi subsystem

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1603?page=com.atlassian.jira.plugin.... ] Thomas Diesler commented on WFLY-1603: -------------------------------------- The OSGi subsystem is going to get moved to the JBOSGi umbrella project. Regular releases of the WildFly/OSGi integration will happen through JBOSGi. > Remove OSGi subsystem > --------------------- > > Key: WFLY-1603 > URL: https://issues.jboss.org/browse/WFLY-1603 > Project: WildFly > Issue Type: Task > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 8.0.0.Alpha3 > > > It has been decided to remove OSGi support from WF and EAP. OSGi will continue within the SOA/integration efforts via Karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBAS-8716) run.conf.bat options lost if JBoss run as a Windows Service

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/JBAS-8716?page=com.atlassian.jira.plugin.... ] Tom Fonteyne closed JBAS-8716. ------------------------------ Resolution: Done Resolved in: https://issues.jboss.org/browse/JBPAPP-8334 a "service.bat" can be downloaded from there. > run.conf.bat options lost if JBoss run as a Windows Service > ----------------------------------------------------------- > > Key: JBAS-8716 > URL: https://issues.jboss.org/browse/JBAS-8716 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Other, System service > Affects Versions: JBossAS-5.1.0.GA > Environment: Any Windows > Reporter: Vitaliy Tkachenko > Fix For: No Release > > > If the service is run by jbosssvc.exe then JAVA_OPTS is predefined and set to "-server". So if JBoss is run as a service the command "if not "x%JAVA_OPTS%" == "x" goto JAVA_OPTS_SET" in "run.conf.bat" never allows to continue and set all other options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-878) Message-Driven Beans doesn't support DeliveryActive activation config property

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-878?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated WFLY-878: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=981341 > Message-Driven Beans doesn't support DeliveryActive activation config property > ------------------------------------------------------------------------------ > > Key: WFLY-878 > URL: https://issues.jboss.org/browse/WFLY-878 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, JMS > Environment: Windows 64 bit > Reporter: Prasad Deshpande > Assignee: Jeff Mesnil > > I get this warning on AS7.1.1 console, seems that ActivationConfigProperty DeliveryActive is not implemented by hornetq-ra, could we please have it as earlier JMS implementation of JMS had it & application that were using it will fail with AS7 now..? > 16:04:30,794 WARN [org.jboss.ejb3] (MSC service thread 1-16) JBAS014105: ActivationConfigProperty DeliveryActive will be ignored since it is not allowed by resource adapter: hornetq-ra > Thanks, > Prasad -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-878) Message-Driven Beans doesn't support DeliveryActive activation config property

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-878?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-878: ---------------------------------------------- Ravi Bhardwaj <rbhardwa(a)redhat.com> made a comment on [bug 981341|https://bugzilla.redhat.com/show_bug.cgi?id=981341] Description of problem: startDelivery()/stopDelivery() missing in EAP 6 which were available using JMX in EAP 5.x. > Message-Driven Beans doesn't support DeliveryActive activation config property > ------------------------------------------------------------------------------ > > Key: WFLY-878 > URL: https://issues.jboss.org/browse/WFLY-878 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, JMS > Environment: Windows 64 bit > Reporter: Prasad Deshpande > Assignee: Jeff Mesnil > > I get this warning on AS7.1.1 console, seems that ActivationConfigProperty DeliveryActive is not implemented by hornetq-ra, could we please have it as earlier JMS implementation of JMS had it & application that were using it will fail with AS7 now..? > 16:04:30,794 WARN [org.jboss.ejb3] (MSC service thread 1-16) JBAS014105: ActivationConfigProperty DeliveryActive will be ignored since it is not allowed by resource adapter: hornetq-ra > Thanks, > Prasad -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBMETA-366) Update Java EE 7 schemas to the final releases

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/JBMETA-366?page=com.atlassian.jira.plugin... ] Eduardo Martins commented on JBMETA-366: ---------------------------------------- [~jfclere] can you pls review, and if ok merge and release? > Update Java EE 7 schemas to the final releases > ---------------------------------------------- > > Key: JBMETA-366 > URL: https://issues.jboss.org/browse/JBMETA-366 > Project: JBoss Metadata > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: client, common, ear, ejb, rar, web > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > The final release of the Java EE 7 schemas have changes with respect the ones currently in the Metadata project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBMETA-366) Update Java EE 7 schemas to the final releases

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/JBMETA-366?page=com.atlassian.jira.plugin... ] Eduardo Martins updated JBMETA-366: ----------------------------------- Git Pull Request: https://github.com/jboss/metadata/pull/48 > Update Java EE 7 schemas to the final releases > ---------------------------------------------- > > Key: JBMETA-366 > URL: https://issues.jboss.org/browse/JBMETA-366 > Project: JBoss Metadata > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: client, common, ear, ejb, rar, web > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > The final release of the Java EE 7 schemas have changes with respect the ones currently in the Metadata project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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 July 2013