[jira] [Assigned] (KARAF-5069) Support include/exclude filter for topic for appenders
[ https://issues.apache.org/jira/browse/KARAF-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5069: --- Assignee: Jean-Baptiste Onofré > Support include/exclude filter for topic for appenders > -- > > Key: KARAF-5069 > URL: https://issues.apache.org/jira/browse/KARAF-5069 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Oliver Wulff >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.4.0 > > > Some collector events should be sent to one appender (ex. kafka) whereas > other events to another appender (ex. camel) for custom enrichement of the > event. > Implementation proposal: > Every appender could provide an exclude and include property to configure to > which appender the events should be sent to. The exclude/include condition > could be based on the topic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5069) Support include/exclude filter for topic for appenders
[ https://issues.apache.org/jira/browse/KARAF-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5069: Fix Version/s: decanter-1.4.0 > Support include/exclude filter for topic for appenders > -- > > Key: KARAF-5069 > URL: https://issues.apache.org/jira/browse/KARAF-5069 > Project: Karaf > Issue Type: New Feature > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Oliver Wulff >Assignee: Jean-Baptiste Onofré > Fix For: decanter-1.4.0 > > > Some collector events should be sent to one appender (ex. kafka) whereas > other events to another appender (ex. camel) for custom enrichement of the > event. > Implementation proposal: > Every appender could provide an exclude and include property to configure to > which appender the events should be sent to. The exclude/include condition > could be based on the topic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-5085) Upgrade to Aries JPA 2.6.1
Jean-Baptiste Onofré created KARAF-5085: --- Summary: Upgrade to Aries JPA 2.6.1 Key: KARAF-5085 URL: https://issues.apache.org/jira/browse/KARAF-5085 Project: Karaf Issue Type: Dependency upgrade Components: karaf-feature Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.1.2, 4.0.10 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5074) Support for typed config files (as in Felix ConfigAdmin config files) in features
[ https://issues.apache.org/jira/browse/KARAF-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960911#comment-15960911 ] Guillaume Nodet commented on KARAF-5074: I pushed a branch https://github.com/gnodet/karaf/tree/KARAF-5074 > Support for typed config files (as in Felix ConfigAdmin config files) in > features > - > > Key: KARAF-5074 > URL: https://issues.apache.org/jira/browse/KARAF-5074 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KARAF-5082) add "location" attribute to config feature tag
[ https://issues.apache.org/jira/browse/KARAF-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned KARAF-5082: -- Assignee: Guillaume Nodet > add "location" attribute to config feature tag > -- > > Key: KARAF-5082 > URL: https://issues.apache.org/jira/browse/KARAF-5082 > Project: Karaf > Issue Type: New Feature >Affects Versions: 4.1.1 >Reporter: Jean-Philippe CLEMENT >Assignee: Guillaume Nodet > Fix For: 4.2.0 > > > This addition follows KARAF-4829. In order to get synchronous configuration > file, the tag should be used instead of . > At present time does not allow to use external files as > does. Using several external files might be more handy (and short) than > inlining the configuration in the tag. > I would be a real nice addition to add a location attribute to , for > instance: > > Thank you! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5082) add "location" attribute to config feature tag
[ https://issues.apache.org/jira/browse/KARAF-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-5082: --- External issue URL: (was: https://issues.apache.org/jira/browse/KARAF-4829) > add "location" attribute to config feature tag > -- > > Key: KARAF-5082 > URL: https://issues.apache.org/jira/browse/KARAF-5082 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.1.1 >Reporter: Jean-Philippe CLEMENT > Fix For: 4.2.0 > > > This addition follows KARAF-4829. In order to get synchronous configuration > file, the tag should be used instead of . > At present time does not allow to use external files as > does. Using several external files might be more handy (and short) than > inlining the configuration in the tag. > I would be a real nice addition to add a location attribute to , for > instance: > > Thank you! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5082) add "location" attribute to config feature tag
[ https://issues.apache.org/jira/browse/KARAF-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-5082: --- Fix Version/s: 4.2.0 > add "location" attribute to config feature tag > -- > > Key: KARAF-5082 > URL: https://issues.apache.org/jira/browse/KARAF-5082 > Project: Karaf > Issue Type: New Feature >Affects Versions: 4.1.1 >Reporter: Jean-Philippe CLEMENT > Fix For: 4.2.0 > > > This addition follows KARAF-4829. In order to get synchronous configuration > file, the tag should be used instead of . > At present time does not allow to use external files as > does. Using several external files might be more handy (and short) than > inlining the configuration in the tag. > I would be a real nice addition to add a location attribute to , for > instance: > > Thank you! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5082) add "location" attribute to config feature tag
[ https://issues.apache.org/jira/browse/KARAF-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-5082: --- Issue Type: New Feature (was: Improvement) > add "location" attribute to config feature tag > -- > > Key: KARAF-5082 > URL: https://issues.apache.org/jira/browse/KARAF-5082 > Project: Karaf > Issue Type: New Feature >Affects Versions: 4.1.1 >Reporter: Jean-Philippe CLEMENT > Fix For: 4.2.0 > > > This addition follows KARAF-4829. In order to get synchronous configuration > file, the tag should be used instead of . > At present time does not allow to use external files as > does. Using several external files might be more handy (and short) than > inlining the configuration in the tag. > I would be a real nice addition to add a location attribute to , for > instance: > > Thank you! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-4676) Karaf does not reapply the wiring when rebooting
[
https://issues.apache.org/jira/browse/KARAF-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated KARAF-4676:
---
Fix Version/s: 4.1.0
> Karaf does not reapply the wiring when rebooting
>
>
> Key: KARAF-4676
> URL: https://issues.apache.org/jira/browse/KARAF-4676
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.6
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> The features service is smart and apply it's computed wiring to the bundles
> when features are installed.
> However, after restarting Karaf from scratch, the previous wiring is not used
> which can lead to problems:
> {code}
> karaf@root()> repo-add pax-cdi 1.0.0-SNAPSHOT ; feature:install pax-cdi-weld
> karaf@root()> bundle:list --no-format | grep -v Active
> START LEVEL 100 , List Threshold: 50
> karaf@root()> system:shutdown --reboot
> Confirm: reboot instance root (yes/no): yes
> karaf@root()>
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> bundle:list --no-format | grep -v Active
> START LEVEL 100 , List Threshold: 50
> 51Installed80 2.3.3.Final Weld OSGi Bundle
> 53Waiting 80 1.0.0.SNAPSHOT OPS4J Pax CDI Extender for Bean
> Bundles
> 56Installed80 1.0.0.SNAPSHOT OPS4J Pax CDI Weld Adapter
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (KARAF-4697) Infinite error loop on F24
[
https://issues.apache.org/jira/browse/KARAF-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved KARAF-4697.
Resolution: Fixed
Fix Version/s: 4.1.0
> Infinite error loop on F24
> --
>
> Key: KARAF-4697
> URL: https://issues.apache.org/jira/browse/KARAF-4697
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: John Poth
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Since
> [KARAF-4188|https://github.com/apache/karaf/commit/12fdb85f3afb34b9cbd3207aa405a3036ce27913],
> KARAF will use the JnaNativePty by default which causes the following
> infinite error loop on F24: {code} 2016-09-02T13:30:49,505 | ERROR | Karaf
> local console user karaf | ShellUtil | 43 - org.apache.karaf.shell.core -
> 4.1.0.SNAPSHOT | Exception caught while executing command
> com.sun.jna.LastErrorException: [22] at com.sun.jna.Native.invokeVoid(Native
> Method) ~[?:?] at com.sun.jna.Function.invoke(Function.java:367) [?:?] at
> com.sun.jna.Function.invoke(Function.java:315) [?:?] at
> com.sun.jna.Library$Handler.invoke(Library.java:212) [?:?] at
> com.sun.proxy.$Proxy33.tcsetattr(Unknown Source) [9:jline:3.0.0.M1] at
> org.jline.terminal.impl.jna.linux.LinuxNativePty.setAttr(LinuxNativePty.java:71)
> [9:jline:3.0.0.M1] at
> org.jline.terminal.impl.AbstractPosixTerminal.setAttributes(AbstractPosixTerminal.java:36)
> [9:jline:3.0.0.M1] at
> org.jline.terminal.impl.AbstractTerminal.enterRawMode(AbstractTerminal.java:94)
> [9:jline:3.0.0.M1] at
> org.apache.karaf.shell.impl.console.JLineTerminal.enterRawMode(JLineTerminal.java:138)
> [43:org.apache.karaf.shell.core:4.1.0.SNAPSHOT] at
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:444)
> [9:jline:3.0.0.M1] at
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:390)
> [9:jline:3.0.0.M1] {code} I created an
> [issue|https://github.com/jline/jline3/issues/11] and
> [PR|https://github.com/jline/jline3/pull/12] in JLine3 to resolve this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (KARAF-4264) Upgrade to pax-web 6
[ https://issues.apache.org/jira/browse/KARAF-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed KARAF-4264. -- Resolution: Fixed Fix Version/s: (was: 4.2.0) > Upgrade to pax-web 6 > > > Key: KARAF-4264 > URL: https://issues.apache.org/jira/browse/KARAF-4264 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (KARAF-4676) Karaf does not reapply the wiring when rebooting
[
https://issues.apache.org/jira/browse/KARAF-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed KARAF-4676.
--
Resolution: Duplicate
> Karaf does not reapply the wiring when rebooting
>
>
> Key: KARAF-4676
> URL: https://issues.apache.org/jira/browse/KARAF-4676
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.6
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> The features service is smart and apply it's computed wiring to the bundles
> when features are installed.
> However, after restarting Karaf from scratch, the previous wiring is not used
> which can lead to problems:
> {code}
> karaf@root()> repo-add pax-cdi 1.0.0-SNAPSHOT ; feature:install pax-cdi-weld
> karaf@root()> bundle:list --no-format | grep -v Active
> START LEVEL 100 , List Threshold: 50
> karaf@root()> system:shutdown --reboot
> Confirm: reboot instance root (yes/no): yes
> karaf@root()>
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.1.0-SNAPSHOT)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> bundle:list --no-format | grep -v Active
> START LEVEL 100 , List Threshold: 50
> 51Installed80 2.3.3.Final Weld OSGi Bundle
> 53Waiting 80 1.0.0.SNAPSHOT OPS4J Pax CDI Extender for Bean
> Bundles
> 56Installed80 1.0.0.SNAPSHOT OPS4J Pax CDI Weld Adapter
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (KARAF-5016) Possible NPE while running "log:tail" in Karaf console
[ https://issues.apache.org/jira/browse/KARAF-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-5016. Resolution: Fixed Fix Version/s: (was: 4.1.1) 4.1.2 > Possible NPE while running "log:tail" in Karaf console > -- > > Key: KARAF-5016 > URL: https://issues.apache.org/jira/browse/KARAF-5016 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.1.0 >Reporter: Richard Kosegi >Assignee: Guillaume Nodet >Priority: Trivial > Fix For: 4.1.2 > > > There is occasional NPE while running "log:tail" in Karaf console. > This occurs few times per day, it has no real impact other then tailing of > log is stopped (and must be restarted by CTRL+C, log:tail) > Exception in thread "pool-51-thread-1" java.lang.NullPointerException > at > org.apache.karaf.log.core.internal.layout.PatternParser$MDCPatternConverter.convert(PatternParser.java:551) > at > org.apache.karaf.log.core.internal.layout.PatternConverter.format(PatternConverter.java:63) > at > org.apache.karaf.log.core.internal.LogEventFormatterImpl.format(LogEventFormatterImpl.java:117) > at org.apache.karaf.log.command.DisplayLog.printEvent(DisplayLog.java:121) > at org.apache.karaf.log.command.DisplayLog.printEvent(DisplayLog.java:105) > at > org.apache.karaf.log.command.LogTail$PrintEventThread.run(LogTail.java:113) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5074) Support for typed config files (as in Felix ConfigAdmin config files) in features
[ https://issues.apache.org/jira/browse/KARAF-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960944#comment-15960944 ] ASF subversion and git services commented on KARAF-5074: Commit 3cd6866bf9eb8d19b186441390d1e6d8719e652a in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=3cd6866 ] [KARAF-5074] Upgrade to Felix Utils 1.10, FileInstall 3.6 and use the new TypedProperties > Support for typed config files (as in Felix ConfigAdmin config files) in > features > - > > Key: KARAF-5074 > URL: https://issues.apache.org/jira/browse/KARAF-5074 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KARAF-5074) Support for typed config files (as in Felix ConfigAdmin config files) in features
[ https://issues.apache.org/jira/browse/KARAF-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-5074. Resolution: Fixed https://github.com/apache/karaf/commit/3cd6866bf9eb8d19b186441390d1e6d8719e652a > Support for typed config files (as in Felix ConfigAdmin config files) in > features > - > > Key: KARAF-5074 > URL: https://issues.apache.org/jira/browse/KARAF-5074 > Project: Karaf > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5074) Support for typed config files (as in Felix ConfigAdmin config files) in features
[
https://issues.apache.org/jira/browse/KARAF-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961012#comment-15961012
]
Oliver Lietz commented on KARAF-5074:
-
[~gnt], it seems like configurations in files with extension {{.config}} are
not supported, but {{.cfg}} only, right?
> Support for typed config files (as in Felix ConfigAdmin config files) in
> features
> -
>
> Key: KARAF-5074
> URL: https://issues.apache.org/jira/browse/KARAF-5074
> Project: Karaf
> Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5084) Use of LocateRegistry in RmiRegistryFactory problematic due to InetAddress.getLocalHost().getHostAddress()
[
https://issues.apache.org/jira/browse/KARAF-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961400#comment-15961400
]
Michael Vorburger commented on KARAF-5084:
--
http://blog2.vorburger.ch/2017/04/java-local-rmi-using-jdks-inetaddress.html
describes more background about what's going on here.
It turns out that I slightly confused two things: There are two strictly
speaking separate problems in the log above - the first exception, from
org.apache.karaf.management.ConnectorServerFactory, is a actually not directly
impacting Pax Exam - it just means that Karaf Management JMX server hits a
similar issue. Unless you need to use JMX, that is not a problem at least for
running tests. The second exception is
https://ops4j1.jira.com/browse/PAXEXAM-740, and fixing that required no
changes in Karaf, just in Pax Exam, after all.
I'll close this issue as my interest was to get PAXEXAM-740 resolved. If
someone else is bothered by the NoRouteToHostException from Karaf JMX, then
feel free to re-open. The big difference though is that one may WANT the Karaf
JMX RMI server to be accessible on non-loopback network interfaces too, for
remote monitoring & administration; contrary to Pax Exam's RMI which is always
strictly local. So e.g. programmatically in Karaf code forcing
System.setProperty("java.rmi.server.hostname",
InetAddress.getLoopbackAddress().getHostAddress()) is most probably Not a Good
Idea... you may want to simply set java.rmi.server.hostname to a "suitable"
hostname for your system in your Karaf start-up script?
> Use of LocateRegistry in RmiRegistryFactory problematic due to
> InetAddress.getLocalHost().getHostAddress()
> --
>
> Key: KARAF-5084
> URL: https://issues.apache.org/jira/browse/KARAF-5084
> Project: Karaf
> Issue Type: Bug
> Components: karaf-management
>Affects Versions: 4.1.1
>Reporter: Michael Vorburger
>
> I'm hitting this error e.g. from the
> KarafTestContainerITest.checkKarafSystemService in the
> org.ops4j.pax.exam2/containers/pax-exam-container-karaf :
> {code}Exception in thread "JMX Connector Thread
> [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]"
> java.lang.RuntimeException: Could not start JMX connector server
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:258)
> Caused by: java.io.IOException: Cannot bind to URL
> [rmi://0.0.0.0:1099/karaf-root]: javax.naming.CommunicationException [Root
> exception is java.rmi.ConnectIOException: Exception creating connection to:
> 0.0.0.0; nested exception is:
> java.net.NoRouteToHostException: No route to host (Host unreachable)]
> 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:245)
> Caused by: javax.naming.CommunicationException [Root exception is
> java.rmi.ConnectIOException: Exception creating connection to: 0.0.0.0;
> nested exception is:
> java.net.NoRouteToHostException: No route to host (Host unreachable)]
> 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.ConnectIOException: Exception creating connection to:
> 0.0.0.0; nested exception is:
> java.net.NoRouteToHostException: No route to host (Host unreachable)
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)
> at
> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:342)
> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155)
> ... 5 more
> Caused by: java.net.NoRouteToHostException: No route to host (Host
> unreachable)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:204)
> at
> java.net.AbstractPlainSocketImpl.connect(Abstra
[jira] [Work started] (KARAF-5082) add "location" attribute to config feature tag
[ https://issues.apache.org/jira/browse/KARAF-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5082 started by Guillaume Nodet. -- > add "location" attribute to config feature tag > -- > > Key: KARAF-5082 > URL: https://issues.apache.org/jira/browse/KARAF-5082 > Project: Karaf > Issue Type: New Feature >Affects Versions: 4.1.1 >Reporter: Jean-Philippe CLEMENT >Assignee: Guillaume Nodet > Fix For: 4.2.0 > > > This addition follows KARAF-4829. In order to get synchronous configuration > file, the tag should be used instead of . > At present time does not allow to use external files as > does. Using several external files might be more handy (and short) than > inlining the configuration in the tag. > I would be a real nice addition to add a location attribute to , for > instance: > > Thank you! -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5082) add "location" attribute to config feature tag
[
https://issues.apache.org/jira/browse/KARAF-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961422#comment-15961422
]
Guillaume Nodet commented on KARAF-5082:
Rather than
{code}
{code}
I'm going to use:
{code}
mvn:some.groupid/1.0.0/cfg
{code}
This will be closer to the {{}} element.
> add "location" attribute to config feature tag
> --
>
> Key: KARAF-5082
> URL: https://issues.apache.org/jira/browse/KARAF-5082
> Project: Karaf
> Issue Type: New Feature
>Affects Versions: 4.1.1
>Reporter: Jean-Philippe CLEMENT
>Assignee: Guillaume Nodet
> Fix For: 4.2.0
>
>
> This addition follows KARAF-4829. In order to get synchronous configuration
> file, the tag should be used instead of .
> At present time does not allow to use external files as
> does. Using several external files might be more handy (and short) than
> inlining the configuration in the tag.
> I would be a real nice addition to add a location attribute to , for
> instance:
>
> Thank you!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (KARAF-5084) Use of LocateRegistry in RmiRegistryFactory problematic due to InetAddress.getLocalHost().getHostAddress()
[
https://issues.apache.org/jira/browse/KARAF-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Vorburger closed KARAF-5084.
Resolution: Later
> Use of LocateRegistry in RmiRegistryFactory problematic due to
> InetAddress.getLocalHost().getHostAddress()
> --
>
> Key: KARAF-5084
> URL: https://issues.apache.org/jira/browse/KARAF-5084
> Project: Karaf
> Issue Type: Bug
> Components: karaf-management
>Affects Versions: 4.1.1
>Reporter: Michael Vorburger
>
> I'm hitting this error e.g. from the
> KarafTestContainerITest.checkKarafSystemService in the
> org.ops4j.pax.exam2/containers/pax-exam-container-karaf :
> {code}Exception in thread "JMX Connector Thread
> [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-root]"
> java.lang.RuntimeException: Could not start JMX connector server
> at
> org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:258)
> Caused by: java.io.IOException: Cannot bind to URL
> [rmi://0.0.0.0:1099/karaf-root]: javax.naming.CommunicationException [Root
> exception is java.rmi.ConnectIOException: Exception creating connection to:
> 0.0.0.0; nested exception is:
> java.net.NoRouteToHostException: No route to host (Host unreachable)]
> 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:245)
> Caused by: javax.naming.CommunicationException [Root exception is
> java.rmi.ConnectIOException: Exception creating connection to: 0.0.0.0;
> nested exception is:
> java.net.NoRouteToHostException: No route to host (Host unreachable)]
> 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.ConnectIOException: Exception creating connection to:
> 0.0.0.0; nested exception is:
> java.net.NoRouteToHostException: No route to host (Host unreachable)
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)
> at
> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:342)
> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:155)
> ... 5 more
> Caused by: java.net.NoRouteToHostException: No route to host (Host
> unreachable)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:204)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at java.net.Socket.connect(Socket.java:538)
> at java.net.Socket.(Socket.java:434)
> at java.net.Socket.(Socket.java:211)
> at
> sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
> at
> sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
> ... 10 more
> 02:33:50.966 [main] INFO o.o.p.e.spi.reactors.ReactorManager - suite finished
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 182.081 sec
> <<< FAILURE! - in org.ops4j.pax.exam.karaf.container.KarafTestContainerITest
> checkKarafSystemService(org.ops4j.pax.exam.karaf.container.KarafTestContainerITest)
> Time elapsed: 182.074 sec <<< ERROR!
> java.net.NoRouteToHostException: No route to host (Host unreachable)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(S
[jira] [Commented] (KARAF-5074) Support for typed config files (as in Felix ConfigAdmin config files) in features
[
https://issues.apache.org/jira/browse/KARAF-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961424#comment-15961424
]
Guillaume Nodet commented on KARAF-5074:
Where do you see that ? Afaik, I've removed any different between {{.config}}
and {{.cfg}} so both are handled the same way and can be either typed or
untyped configurations.
> Support for typed config files (as in Felix ConfigAdmin config files) in
> features
> -
>
> Key: KARAF-5074
> URL: https://issues.apache.org/jira/browse/KARAF-5074
> Project: Karaf
> Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
