[jira] [Created] (GERONIMO-6434) in-place deployment for OSGi applications
Jarek Gawor created GERONIMO-6434: - Summary: in-place deployment for OSGi applications Key: GERONIMO-6434 URL: https://issues.apache.org/jira/browse/GERONIMO-6434 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Add support for in-place deployment of OSGi applications. That is, the contents of the .eba archive and its bundles are expanded on disk. -- 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
[jira] [Resolved] (GERONIMODEVTOOLS-807) Handle updates to static and class resources at the same time
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-807. -- Resolution: Fixed Fix Version/s: 3.0.1 Handle updates to static and class resources at the same time - Key: GERONIMODEVTOOLS-807 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-807 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 When working with OSGi application and making changes to both static and class resources at the same time will cause the bundle to be automatically restarted. A bundle restart might be an expensive operation. However, in some cases it might be possible to just update the static resources on the server and perform hot code replace on the class files without restarting a bundle. -- 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
[jira] [Resolved] (GERONIMO-6427) Transport scheme NOT recognized: [tcp]
[ https://issues.apache.org/jira/browse/GERONIMO-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6427. --- Resolution: Fixed Fix Version/s: 3.0.1 Forgot to close. Transport scheme NOT recognized: [tcp] -- Key: GERONIMO-6427 URL: https://issues.apache.org/jira/browse/GERONIMO-6427 Project: Geronimo Issue Type: Bug Components: console Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 I ran into the following exception: 2013-01-03 19:25:20,497 ERROR [BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27) at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1656) at org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2099) at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2049) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:511) at org.apache.activemq.broker.BrokerService.autoStart(BrokerService.java:458) This happens if all the activemq modules are configured with load=false in config.xml and somebody tries to display all web applications using the admin console. -- 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
[jira] [Resolved] (GERONIMO-6393) javax.validation.Validator lookup improvement
[ https://issues.apache.org/jira/browse/GERONIMO-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6393. --- Resolution: Fixed Fix Version/s: 3.0.1 Forgot to close. javax.validation.Validator lookup improvement - Key: GERONIMO-6393 URL: https://issues.apache.org/jira/browse/GERONIMO-6393 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: general Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Each time the same application looks up javax.validation.Validator object in JNDI a completely new instance of the object is returned (as required per spec). However, with Apache Bean Validation implementation that means that expensive annotation scanning is done on each Validator.validate() call. Apache Bean Validation implementation maintains an annotation cache with each ValidatorContext. However, each ValidatorFactory.getValidator() call creates a new instance of ValidatorContext and that's why the cache is not reused and annotation scanning is done on each call. In Geronimo we can ensure that the same ValidatorContext is used for the given application and therefore, ensure that cache is reused and annotation scanning is only done one. -- 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
[jira] [Resolved] (GERONIMO-6385) Adjust default thread pool at runtime
[ https://issues.apache.org/jira/browse/GERONIMO-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6385. --- Resolution: Fixed Fix Version/s: 3.0.1 Forgot to close. Adjust default thread pool at runtime - Key: GERONIMO-6385 URL: https://issues.apache.org/jira/browse/GERONIMO-6385 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: core Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Right now the default thread pool size can only be adjusted while the server is not running. However, sometimes it might be desirable to adjust the thread pool size at runtime. -- 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
[jira] [Resolved] (GERONIMO-6374) Clear cache after unclean shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6374. --- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: viola.lu Clear cache after unclean shutdown -- Key: GERONIMO-6374 URL: https://issues.apache.org/jira/browse/GERONIMO-6374 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: kernel Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: viola.lu Fix For: 3.0.1 Clear caches on server start up after the server was forcibly killed. This is in case the cache got corrupted when the server was killed. -- 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
[jira] [Resolved] (GERONIMO-6370) Update static files without bundle restart
[ https://issues.apache.org/jira/browse/GERONIMO-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6370. --- Resolution: Fixed Closing as work for this issue is done. Update static files without bundle restart -- Key: GERONIMO-6370 URL: https://issues.apache.org/jira/browse/GERONIMO-6370 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: viola.lu Assignee: viola.lu Fix For: 3.0.1 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-796 have to extract bundles when install EBA and install it via reference: file -- 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
[jira] [Commented] (GERONIMO-6434) in-place deployment for OSGi applications
[ https://issues.apache.org/jira/browse/GERONIMO-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571526#comment-13571526 ] Jarek Gawor commented on GERONIMO-6434: --- I re-factored the code a bit to support in-place deployment for OSGi applications. Changes committed in revision 1442682. in-place deployment for OSGi applications - Key: GERONIMO-6434 URL: https://issues.apache.org/jira/browse/GERONIMO-6434 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Add support for in-place deployment of OSGi applications. That is, the contents of the .eba archive and its bundles are expanded on disk. -- 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
