[jira] [Assigned] (KARAF-5233) LogService does not work with log4j2
[ https://issues.apache.org/jira/browse/KARAF-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5233: --- Assignee: Jean-Baptiste Onofré > LogService does not work with log4j2 > > > Key: KARAF-5233 > URL: https://issues.apache.org/jira/browse/KARAF-5233 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 >Reporter: Fabian Lange >Assignee: Jean-Baptiste Onofré > Fix For: 4.2.0, 4.1.2 > > > log:get / log:set and similar do not work with log4j2. > the reason is that the LogServiceImpl has hardcoded prefixes and assumes a > certain property name convention. > of course this totally changed with log4j2, making LogServiceImpl quite broken -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5023) The serviceUrl property is changed unexpected when edit the rmiServerPort/rmiRegistryPort properties
[
https://issues.apache.org/jira/browse/KARAF-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095772#comment-16095772
]
Jean-Baptiste Onofré commented on KARAF-5023:
-
The {{serviceUrl}} is constructed:
{code}
serviceUrl =
service:jmx:rmi://${rmiServerHost}:${rmiServerPort}/jndi/rmi://${rmiRegistryHost}:${rmiRegistryPort}/karaf-${karaf.name}
{code}
So, when you change one of the properties used in the {{serviceUrl}}, it's
re-evaluated and so it should be changed as well.
It's maybe a race condition or a "cascade" change not applied. Let me try.
> The serviceUrl property is changed unexpected when edit the
> rmiServerPort/rmiRegistryPort properties
>
>
> Key: KARAF-5023
> URL: https://issues.apache.org/jira/browse/KARAF-5023
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.2, 4.0.10
>
>
> karaf@root()> config:edit --force org.apache.karaf.management
> karaf@root()> config:property-set rmiRegistryPort 1100
> karaf@root()> config:property-set rmiServerPort 5
> karaf@root()> config:update
> karaf@root()> Exception in thread "JMX Connector Thread
> [service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-r
> oot]" java.lang.RuntimeException: Could not start JMX connector server
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:272)
> Caused by: java.io.IOException: Cannot bind to URL
> [rmi://127.0.0.1:1099/karaf-root]: javax.naming.CommunicationException
> [Root exception is java.rmi.NoSuchObjectException: no such object in table]
> at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432)
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:259)
> Caused by: javax.naming.CommunicationException [Root exception is
> java.rmi.NoSuchObjectException: no such object in tabl
> e]
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:161)
> at
> com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228)
> at javax.naming.InitialContext.bind(InitialContext.java:425)
> at
> javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
> ... 1 more
> Caused by: java.rmi.NoSuchObjectException: no such object in table
> at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379)
> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155)
> ... 5 more
> Looking into the etc/org.apache.karaf.management.cfg, the serviceUrl property
> is changed to:
> service:jmx:rmi://127.0.0.1:4/jndi/rmi://127.0.0.1:1099/karaf-root
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-4966) Provide a Update Note document
[ https://issues.apache.org/jira/browse/KARAF-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4966: Fix Version/s: (was: 4.1.2) 4.1.3 4.2.0 > Provide a Update Note document > -- > > Key: KARAF-4966 > URL: https://issues.apache.org/jira/browse/KARAF-4966 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.2.0, 4.1.3 > > > As we did for the update from Karaf 3.0.x to 4.0.x, we will provide a > documentation containing update notes. It should provide the key diff for > people upgrading to Karaf 4.1.x (location of the features, shell behavior, > ...). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4952) Provide features list on website
[
https://issues.apache.org/jira/browse/KARAF-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-4952:
Fix Version/s: (was: 4.1.2)
> Provide features list on website
>
>
> Key: KARAF-4952
> URL: https://issues.apache.org/jira/browse/KARAF-4952
> Project: Karaf
> Issue Type: Improvement
> Components: website
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>
> Even if the features repositories are already listed in
> {{etc/org.apache.karaf.features.repos.cfg}}, it could be interesting to
> provide the list on the website or user guide.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (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é updated KARAF-4188: Fix Version/s: (was: 4.1.2) 4.1.3 4.2.0 > Add support for Systemd's watchdog > -- > > Key: KARAF-4188 > URL: https://issues.apache.org/jira/browse/KARAF-4188 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Luca Burgazzoli >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.2.0, 4.0.10, 4.1.3 > > > 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.4.14#64029)
[jira] [Updated] (KARAF-3825) Add ability to shutdown Karaf with a disabled shutdown port
[ https://issues.apache.org/jira/browse/KARAF-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3825: Fix Version/s: (was: 3.0.9) 4.2.0 > Add ability to shutdown Karaf with a disabled shutdown port > --- > > Key: KARAF-3825 > URL: https://issues.apache.org/jira/browse/KARAF-3825 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Affects Versions: 3.0.3, 4.0.0 >Reporter: Dmitry Konstantinov >Assignee: Jean-Baptiste Onofré > Fix For: 4.2.0, 4.1.2, 4.0.10 > > > Sometimes by security reasons listen ports are asked to disable. It would be > nice to provide an alternative way to trigger Karaf shutdown by touching a > special file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-2511) Review and update documentation
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Fix Version/s: (was: 4.1.2) (was: 3.0.9) 4.1.3 4.2.0 > Review and update documentation > --- > > Key: KARAF-2511 > URL: https://issues.apache.org/jira/browse/KARAF-2511 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.2.0, 4.0.10, 4.1.3 > > > The documentation (manual) should be reviewed: > - The subshell part should be described (usage and configuration). > - The "code samples"/screenshots have to be updated with Karaf 3.0.0 use cases > - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-3976) Broken compatibility with 3.x jdbc DataSources
[
https://issues.apache.org/jira/browse/KARAF-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3976:
Fix Version/s: (was: 4.1.2)
4.1.3
4.2.0
> Broken compatibility with 3.x jdbc DataSources
> --
>
> Key: KARAF-3976
> URL: https://issues.apache.org/jira/browse/KARAF-3976
> Project: Karaf
> Issue Type: Bug
> Components: karaf-jdbc
>Affects Versions: 4.0.1
>Reporter: Sergey
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> 1st of all, current documentaion is wrong, because command names was changed
> to jdbc:ds-info, for example, but
> http://karaf.apache.org/manual/latest/users-guide/jdbc.html still contains
> jdbc:info command names.
> Most important compatibility breaking change was another one: in karaf 3.x I
> was able to deploy DataSource using spring-dm xml or blueprint, and it was
> registered as a service and in jndi, and was listed using jdbc:datasources
> command. Right now no datasources are listed.
> {code}
> karaf@root()> jndi:names
> JNDI Name | Class Name
> --
> osgi:service/jdbc/zeusDataSource |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/arenaDS |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/tomsDS |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/cofDS |
> com.sybase.jdbc3.jdbc.SybDataSource
> osgi:service/jdbc/fidbDataSource |
> net.sourceforge.jtds.jdbcx.JtdsDataSource
> osgi:service/jdbc/murexDS |
> com.sybase.jdbc3.jdbc.SybDataSource
> osgi:service/jdbc/gpDataSource|
> org.postgresql.ds.PGPoolingDataSource
> karaf@root()> jdbc:ds-info jdbc/fidbDataSource
> Property | Value
> -
> driver.version | 1.2.2
> db.version | 10.50.4000
> db.product | Microsoft SQL Server
> url| jdbc:jtds:sqlserver:
> driver.name| jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
> username | ...
> karaf@root()> jdbc:ds-list
> Name | Product | Version | URL | Status
> ---
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-3572) Override resources for instance:create in custom distributions
[
https://issues.apache.org/jira/browse/KARAF-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3572:
Fix Version/s: (was: 4.1.2)
4.2.0
4.1.3
> Override resources for instance:create in custom distributions
> --
>
> Key: KARAF-3572
> URL: https://issues.apache.org/jira/browse/KARAF-3572
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-instance
>Affects Versions: 3.0.3, 2.4.1, 4.0.0.M2
>Reporter: Krzysztof Sobkowiak
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> Currently the command {{instance:create}} creates a new instance using the
> resources included in {{org.apache.karaf.instance.core}} bundle. It would be
> resonable to allow people to override the resources in custom distributions,
> e.g. in the same way like branding bundles.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5260) log:tail default should start at the end of the file
[ https://issues.apache.org/jira/browse/KARAF-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095770#comment-16095770 ] Jean-Baptiste Onofré commented on KARAF-5260: - That's exactly what I was thinking ;). And my idea was actually to change the default to 1 number of entries instead of 0. [~ch...@die-schneider.net] [~gnt] thoughts ? > log:tail default should start at the end of the file > > > Key: KARAF-5260 > URL: https://issues.apache.org/jira/browse/KARAF-5260 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 > Environment: Windows 7 >Reporter: Scott Leschke >Assignee: Christian Schneider >Priority: Minor > Fix For: 4.2.0, 4.1.2 > > > I would suggest that the default for the log:tail command refrain from > dumping the entire contents of the log file to the console prior to tailing > and rather just start tailing at the end of the file. Given the general use > of the command, having all the prior log statements written to the console > every time the command is used is not helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5260) log:tail default should start at the end of the file
[ https://issues.apache.org/jira/browse/KARAF-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095290#comment-16095290 ] Scott Leschke commented on KARAF-5260: -- When I created the issue, I wasn't aware that it took the -n option. In retrospect, I would simply have suggested that the no option version of the command, log:tail, default to using -n 1 rather than -n 0 which tails the whole file. > log:tail default should start at the end of the file > > > Key: KARAF-5260 > URL: https://issues.apache.org/jira/browse/KARAF-5260 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 > Environment: Windows 7 >Reporter: Scott Leschke >Assignee: Christian Schneider >Priority: Minor > Fix For: 4.2.0, 4.1.2 > > > I would suggest that the default for the log:tail command refrain from > dumping the entire contents of the log file to the console prior to tailing > and rather just start tailing at the end of the file. Given the general use > of the command, having all the prior log statements written to the console > every time the command is used is not helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5260) log:tail default should start at the end of the file
[ https://issues.apache.org/jira/browse/KARAF-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved KARAF-5260. Resolution: Not A Bug Closing this issue as the current behaviour is working as designed. I will try to improve the behaviour in the linked issue. > log:tail default should start at the end of the file > > > Key: KARAF-5260 > URL: https://issues.apache.org/jira/browse/KARAF-5260 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 > Environment: Windows 7 >Reporter: Scott Leschke >Assignee: Christian Schneider >Priority: Minor > Fix For: 4.2.0, 4.1.2 > > > I would suggest that the default for the log:tail command refrain from > dumping the entire contents of the log file to the console prior to tailing > and rather just start tailing at the end of the file. Given the general use > of the command, having all the prior log statements written to the console > every time the command is used is not helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5260) log:tail default should start at the end of the file
[ https://issues.apache.org/jira/browse/KARAF-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094710#comment-16094710 ] Christian Schneider commented on KARAF-5260: I am opening a new issue for the change in the logging commands. As this title and description would be misleading. > log:tail default should start at the end of the file > > > Key: KARAF-5260 > URL: https://issues.apache.org/jira/browse/KARAF-5260 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 > Environment: Windows 7 >Reporter: Scott Leschke >Assignee: Christian Schneider >Priority: Minor > Fix For: 4.2.0, 4.1.2 > > > I would suggest that the default for the log:tail command refrain from > dumping the entire contents of the log file to the console prior to tailing > and rather just start tailing at the end of the file. Given the general use > of the command, having all the prior log statements written to the console > every time the command is used is not helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5266) log commands should limit number of lines printed instead of number of log entries
[ https://issues.apache.org/jira/browse/KARAF-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated KARAF-5266: --- Description: log:tail only shows the n last log entries. Still sometimes it looks like it shows masses of log data. This is when you have stack traces in the log. A full stack trace only counts as one line currently. I think a good enhancement would be to change the logic to really only show n lines instead of n log records. > log commands should limit number of lines printed instead of number of log > entries > -- > > Key: KARAF-5266 > URL: https://issues.apache.org/jira/browse/KARAF-5266 > Project: Karaf > Issue Type: Improvement >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: 4.2.0 > > > log:tail only shows the n last log entries. Still sometimes it looks like it > shows masses of log data. This is when you have stack traces in the log. A > full stack trace only counts as one line currently. I think a good > enhancement would be to change the logic to really only show n lines instead > of n log records. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5266) log commands should limit number of lines printed instead of number of log entries
[ https://issues.apache.org/jira/browse/KARAF-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094709#comment-16094709 ] Christian Schneider commented on KARAF-5266: log:tail only shows the n last log entries. Still sometimes it looks like it shows masses of log data. This is when you have stack traces in the log. A full stack trace only counts as one line currently. I think a good enhancement would be to change the logic to really only show n lines instead of n log records. I can look into that. > log commands should limit number of lines printed instead of number of log > entries > -- > > Key: KARAF-5266 > URL: https://issues.apache.org/jira/browse/KARAF-5266 > Project: Karaf > Issue Type: Improvement >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (KARAF-5266) log commands should limit number of lines printed instead of number of log entries
[ https://issues.apache.org/jira/browse/KARAF-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated KARAF-5266: --- Comment: was deleted (was: log:tail only shows the n last log entries. Still sometimes it looks like it shows masses of log data. This is when you have stack traces in the log. A full stack trace only counts as one line currently. I think a good enhancement would be to change the logic to really only show n lines instead of n log records. I can look into that.) > log commands should limit number of lines printed instead of number of log > entries > -- > > Key: KARAF-5266 > URL: https://issues.apache.org/jira/browse/KARAF-5266 > Project: Karaf > Issue Type: Improvement >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5266) log commands should limit number of lines printed instead of number of log entries
Christian Schneider created KARAF-5266: -- Summary: log commands should limit number of lines printed instead of number of log entries Key: KARAF-5266 URL: https://issues.apache.org/jira/browse/KARAF-5266 Project: Karaf Issue Type: Improvement Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 4.2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5260) log:tail default should start at the end of the file
[ https://issues.apache.org/jira/browse/KARAF-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider reassigned KARAF-5260: -- Assignee: Christian Schneider (was: Jean-Baptiste Onofré) > log:tail default should start at the end of the file > > > Key: KARAF-5260 > URL: https://issues.apache.org/jira/browse/KARAF-5260 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 > Environment: Windows 7 >Reporter: Scott Leschke >Assignee: Christian Schneider >Priority: Minor > Fix For: 4.2.0, 4.1.2 > > > I would suggest that the default for the log:tail command refrain from > dumping the entire contents of the log file to the console prior to tailing > and rather just start tailing at the end of the file. Given the general use > of the command, having all the prior log statements written to the console > every time the command is used is not helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5260) log:tail default should start at the end of the file
[ https://issues.apache.org/jira/browse/KARAF-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094645#comment-16094645 ] Christian Schneider commented on KARAF-5260: log:tail only shows the n last log entries. Still sometimes it looks like it shows masses of log data. This is when you have stack traces in the log. A full stack trace only counts as one line currently. I think a good enhancement would be to change the logic to really only show n lines instead of n log records. I can look into that. > log:tail default should start at the end of the file > > > Key: KARAF-5260 > URL: https://issues.apache.org/jira/browse/KARAF-5260 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 > Environment: Windows 7 >Reporter: Scott Leschke >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.2.0, 4.1.2 > > > I would suggest that the default for the log:tail command refrain from > dumping the entire contents of the log file to the console prior to tailing > and rather just start tailing at the end of the file. Given the general use > of the command, having all the prior log statements written to the console > every time the command is used is not helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5260) log:tail default should start at the end of the file
[ https://issues.apache.org/jira/browse/KARAF-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5260: --- Assignee: Jean-Baptiste Onofré > log:tail default should start at the end of the file > > > Key: KARAF-5260 > URL: https://issues.apache.org/jira/browse/KARAF-5260 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 > Environment: Windows 7 >Reporter: Scott Leschke >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.2.0, 4.1.2 > > > I would suggest that the default for the log:tail command refrain from > dumping the entire contents of the log file to the console prior to tailing > and rather just start tailing at the end of the file. Given the general use > of the command, having all the prior log statements written to the console > every time the command is used is not helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
