[jira] [Created] (KARAF-4188) Add support for Systemd's watchdog
Luca Burgazzoli created KARAF-4188: -- Summary: Add support for Systemd's watchdog Key: KARAF-4188 URL: https://issues.apache.org/jira/browse/KARAF-4188 Project: Karaf Issue Type: New Feature Reporter: Luca Burgazzoli Priority: Minor Systemd has a watchdog feature that could help detecting freeze jvm, integrating it in karaf would be possible via jna/jnr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4188) Add support for Systemd's watchdog
[ https://issues.apache.org/jira/browse/KARAF-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-4188: --- Assignee: Jean-Baptiste Onofré > Add support for Systemd's watchdog > -- > > Key: KARAF-4188 > URL: https://issues.apache.org/jira/browse/KARAF-4188 > Project: Karaf > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré >Priority: Minor > > Systemd has a watchdog feature that could help detecting freeze jvm, > integrating it in karaf would be possible via jna/jnr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4190) Upgrade to pax-logging 1.9
Guillaume Nodet created KARAF-4190: -- Summary: Upgrade to pax-logging 1.9 Key: KARAF-4190 URL: https://issues.apache.org/jira/browse/KARAF-4190 Project: Karaf Issue Type: Dependency upgrade Components: karaf-core Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4189) Switch to log4j v2 by default
[ https://issues.apache.org/jira/browse/KARAF-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-4189: --- Component/s: karaf-core > Switch to log4j v2 by default > - > > Key: KARAF-4189 > URL: https://issues.apache.org/jira/browse/KARAF-4189 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4189) Switch to log4j v2 by default
[ https://issues.apache.org/jira/browse/KARAF-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052963#comment-15052963 ] Jean-Baptiste Onofré commented on KARAF-4189: - +1 to do it for 4.1.0. By the way, I'm waiting for new Aries release to move forward on 4.0.4. > Switch to log4j v2 by default > - > > Key: KARAF-4189 > URL: https://issues.apache.org/jira/browse/KARAF-4189 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4189) Switch to log4j v2 by default
Guillaume Nodet created KARAF-4189: -- Summary: Switch to log4j v2 by default Key: KARAF-4189 URL: https://issues.apache.org/jira/browse/KARAF-4189 Project: Karaf Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4189) Switch to log4j v2 by default
[ https://issues.apache.org/jira/browse/KARAF-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052937#comment-15052937 ] Guillaume Nodet commented on KARAF-4189: PR at https://github.com/gnodet/karaf/tree/KARAF-4189 > Switch to log4j v2 by default > - > > Key: KARAF-4189 > URL: https://issues.apache.org/jira/browse/KARAF-4189 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4122) Custom interceptor prohibits declarative transactions
[ https://issues.apache.org/jira/browse/KARAF-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052388#comment-15052388 ] Christian Schneider commented on KARAF-4122: [~fwassmer] can you check if the pull request works for you? Btw. I also found some differences in the NameSpaceHandler. You should only return the xsd path for known namespace urls and you should return an empty collection for the managed classes. Not sure if these changes make a difference though. > Custom interceptor prohibits declarative transactions > - > > Key: KARAF-4122 > URL: https://issues.apache.org/jira/browse/KARAF-4122 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.3 > Environment: Karaf 4.0.2 + 4.0.3, Windows 7 x64, Oracle jdk 1.8 >Reporter: Felix Wassmer >Assignee: Christian Schneider > > When using declarative transactions in Karaf 4 (Aries transaction blueprint > 2.0.0), > adding a custom interceptor seems to conflict with the aries TxInterceptor. > Expected behavior > Interceptor enabled for service A > Service A with TxType.REQUIRED calls service B with TxType.MANDATORY and > service B will be executed in a transaction. > Actual behavior > Service B throws exception: No transaction present when calling method that > mandates a transaction. > (TxInterceptor was not registered for service A and therefore no tx started) > Disabling the interceptor (removing declaration in blueprint), > transactional behaviour works as expected (B is executed in a transaction). > Custom interceptor + tx behavior works as expected when using transaction > blueprint 1.1.1 and delcaring transactions in blueprint. > Example to reproduce the issue: > https://github.com/fwassmer/transaction-chain/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
