[jira] [Created] (KARAF-4941) Node is not fully sync when joining a group
Jean-Baptiste Onofré created KARAF-4941:
---
Summary: Node is not fully sync when joining a group
Key: KARAF-4941
URL: https://issues.apache.org/jira/browse/KARAF-4941
Project: Karaf
Issue Type: Bug
Components: cellar-config
Affects Versions: cellar-4.0.3
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: cellar-4.0.4
With a cluster group without any nodes, if we create a configuration (using
{{cluster:config-property-set}}), and then add a node in this group, the node
configurations are not updated and we don't see cluster group configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4194) Add a command (and MBean) to check the status of a node resource compare with the cluster
[ https://issues.apache.org/jira/browse/KARAF-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821727#comment-15821727 ] Jean-Baptiste Onofré commented on KARAF-4194: - Related to that, it would be great to have a status/progress bar when installing a resource on the cluster. > Add a command (and MBean) to check the status of a node resource compare with > the cluster > - > > Key: KARAF-4194 > URL: https://issues.apache.org/jira/browse/KARAF-4194 > Project: Karaf > Issue Type: New Feature > Components: cellar-bundle, cellar-config, cellar-features >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > > Even if we have cluster:sync command, it would be nice to have a command to > check if the resource is up to date on the node with the cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4940) Add a cluster:shutdown command
Jean-Baptiste Onofré created KARAF-4940:
---
Summary: Add a cluster:shutdown command
Key: KARAF-4940
URL: https://issues.apache.org/jira/browse/KARAF-4940
Project: Karaf
Issue Type: Improvement
Components: cellar-core
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: cellar-4.0.4
To be able to easily shutdown a cluster (for a cluster with large number of
nodes), it would be great to provide a {{cluster:shutdown}} command that:
* uninstall the Cellar feature from the nodes
* with {{-f}} also shutdown the Karaf nodes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4931) Static Profile generation fails if configfile element contains a placeholder
[
https://issues.apache.org/jira/browse/KARAF-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Nierbeck resolved KARAF-4931.
---
Resolution: Fixed
Assignee: Achim Nierbeck
Fix Version/s: 4.1.0
fixed with:
http://git-wip-us.apache.org/repos/asf/karaf/commit/e6e0928b
> Static Profile generation fails if configfile element contains a placeholder
>
>
> Key: KARAF-4931
> URL: https://issues.apache.org/jira/browse/KARAF-4931
> Project: Karaf
> Issue Type: Bug
> Components: karaf-profile
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Achim Nierbeck
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
>
> The demo/profiles/static fails in case of a feature file containing a
> placeholder for a file location
> karaf.etc in this sample
> {code}
> ...
>
> finalname="${karaf.etc}/jetty.xml">mvn:org.ops4j.pax.web/pax-web-features/${project.version}/xml/jettyconfig
>
> org.osgi.service.http.port=8181
> javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
> org.ops4j.pax.web.config.file=${karaf.etc}/jetty.xml
>
> ...
> {code}
> see also:
> https://ops4j1.jira.com/browse/PAXWEB-999
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4939) Be able to use Unix /etc/passwd directly in the PropertiesLoginModule
[
https://issues.apache.org/jira/browse/KARAF-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4939:
Fix Version/s: 4.0.9
4.1.0
> Be able to use Unix /etc/passwd directly in the PropertiesLoginModule
> -
>
> Key: KARAF-4939
> URL: https://issues.apache.org/jira/browse/KARAF-4939
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-security
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.9
>
>
> It would be great to be able to directly use an Unix {{/etc/passwd}} in the
> {{PropertiesLoginModule}} to authenticate Karaf users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4939) Be able to use Unix /etc/passwd directly in the PropertiesLoginModule
Jean-Baptiste Onofré created KARAF-4939:
---
Summary: Be able to use Unix /etc/passwd directly in the
PropertiesLoginModule
Key: KARAF-4939
URL: https://issues.apache.org/jira/browse/KARAF-4939
Project: Karaf
Issue Type: Improvement
Components: karaf-security
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
It would be great to be able to directly use an Unix {{/etc/passwd}} in the
{{PropertiesLoginModule}} to authenticate Karaf users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4938) HTTP session replication broken because Hazelcast dependency
[ https://issues.apache.org/jira/browse/KARAF-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roland Hauser updated KARAF-4938: - Description: Starting with Cellar 4.0.2, the dependency to Hazelcast has changed from "hazelcast-all" to "hazelcast". This change breaks session failover (as documented here: https://karaf.apache.org/manual/cellar/latest-4/#_enable_cluster_http_session_replication) because the newly used artifact "hazelcast" does not contain the "com.hazelcast.web" package. I checked hazelcast-all/3.7.4 and it exports the package necessary. Please use this as Hazelcast dependency. was: Starting with Cellar 4.0.2, the dependency to Hazelcast has changed from "hazelcast-all" to "hazelcast". This change breaks session failover because the newly used artifact "hazelcast" does not contain the "com.hazelcast.web" package. This breaks session failover documented here: https://karaf.apache.org/manual/cellar/latest-4/#_enable_cluster_http_session_replication I checked hazelcast-all/3.7.4 and it exports the package necessary. Please use this as Hazelcast dependency. > HTTP session replication broken because Hazelcast dependency > - > > Key: KARAF-4938 > URL: https://issues.apache.org/jira/browse/KARAF-4938 > Project: Karaf > Issue Type: Bug > Components: cellar-hazelcast >Affects Versions: cellar-4.0.2, cellar-4.0.3 >Reporter: Roland Hauser >Priority: Blocker > > Starting with Cellar 4.0.2, the dependency to Hazelcast has changed from > "hazelcast-all" to "hazelcast". This change breaks session failover (as > documented here: > https://karaf.apache.org/manual/cellar/latest-4/#_enable_cluster_http_session_replication) > because the newly used artifact "hazelcast" does not contain the > "com.hazelcast.web" package. > I checked hazelcast-all/3.7.4 and it exports the package necessary. Please > use this as Hazelcast dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4938) HTTP session replication broken because Hazelcast dependency
Roland Hauser created KARAF-4938: Summary: HTTP session replication broken because Hazelcast dependency Key: KARAF-4938 URL: https://issues.apache.org/jira/browse/KARAF-4938 Project: Karaf Issue Type: Bug Components: cellar-hazelcast Affects Versions: cellar-4.0.3, cellar-4.0.2 Reporter: Roland Hauser Priority: Blocker Starting with Cellar 4.0.2, the dependency to Hazelcast has changed from "hazelcast-all" to "hazelcast". This change breaks session failover because the newly used artifact "hazelcast" does not contain the "com.hazelcast.web" package. This breaks session failover documented here: https://karaf.apache.org/manual/cellar/latest-4/#_enable_cluster_http_session_replication I checked hazelcast-all/3.7.4 and it exports the package necessary. Please use this as Hazelcast dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
