[jira] [Commented] (KARAF-3350) The log:display command fails with CNFE if the pax-logging-service bundle has been refreshed
[
https://issues.apache.org/jira/browse/KARAF-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220894#comment-14220894
]
Paolo Antinori commented on KARAF-3350:
---
https://issues.jboss.org/browse/ENTESB-2207
> The log:display command fails with CNFE if the pax-logging-service bundle has
> been refreshed
>
>
> Key: KARAF-3350
> URL: https://issues.apache.org/jira/browse/KARAF-3350
> Project: Karaf
> Issue Type: Bug
>Reporter: Guillaume Nodet
>
> {code}
> JBossFuse:karaf@root> fabric:create --wait-for-provisioning
> Waiting for container: root
> Waiting for container root to provision.
> Error executing command: Unable to create zookeeper server configuration
> JBossFuse:karaf@root> log:display
> Error executing command: org/ops4j/pax/logging/service/internal/PaxLevelImpl
> JBossFuse:karaf@root>
> JBossFuse:karaf@root> log:display-exception
> java.lang.NoClassDefFoundError:
> org/ops4j/pax/logging/service/internal/PaxLevelImpl
> at
> org.ops4j.pax.logging.service.internal.PaxLoggingEventImpl.getLevel(PaxLoggingEventImpl.java:92)[5:org.ops4j.pax.logging.pax-logging-service:1.8.0]
> at org.apache.karaf.shell.log.DisplayLog.getColor(DisplayLog.java:171)
> at org.apache.karaf.shell.log.DisplayLog.display(DisplayLog.java:143)
> at org.apache.karaf.shell.log.DisplayLog.doExecute(DisplayLog.java:135)
> at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
> at
> org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_55]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_55]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_55]
> at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_55]
> at org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:54)
> at org.apache.aries.proxy.impl.ProxyHandler.invoke(ProxyHandler.java:119)
> at
> org.apache.karaf.shell.console.commands.$BlueprintCommand272358056.execute(Unknown
> Source)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.karaf.shell.console.jline.Console.run(Console.java:196)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> at
> org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:79)[28:org.apache.karaf.shell.console:2.4.0.redhat-620042]
> Caused by: java.lang.ClassNotFoundException: Unable to load class
> 'org.ops4j.pax.logging.service.internal.PaxLevelImpl' because the bundle
> wiring for org.ops4j.pax.logging.pax-logging-service is no longer valid.
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1521)
> at
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:77)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1993)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)[:1.7.0_55]
> ... 22 more
> {code}
> This is caused by old events being kept in memory but the implementation
> classes aren't available anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3562) DefaultJDBCLock case sensitive issue
Paolo Antinori created KARAF-3562:
-
Summary: DefaultJDBCLock case sensitive issue
Key: KARAF-3562
URL: https://issues.apache.org/jira/browse/KARAF-3562
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 2.3.9
Reporter: Paolo Antinori
There's a possible issue with:
{code}
rs = getConnection().getMetaData().getTables(null, null, tableName, new
String[] {"TABLE"});
schemaExists = rs.next();
{code} in
https://github.com/apache/karaf/blob/master/main/src/main/java/org/apache/karaf/main/lock/DefaultJDBCLock.java#L165-L167
I'm using Postgres9.3 without any specific configuration.
I have configured the locking mechanism to use the property
{{karaf.lock.jdbc.table=KARAF_LOCK}}
but Postgres stores the table name in its catalog in lowercase, so the query
always returns a 0 length ResultSet.
I couldn't find a short form in the JDBC api to ignore the case.
I think this might be the default on Postgres, to convert it's catalog to
lowercase, but I learn that this depends on the db configuration usually.
So I suggest one of this possible options:
- try both upper and lower case
- improve logging to show which is table with the exact case that is checked
- specialize PostgresJDBCLock if we can make the assumption that's pg default.
And eventually improve Karaf docs to suggest trying to specify a lower case
name in case of errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3562) DefaultJDBCLock case sensitive issue
[
https://issues.apache.org/jira/browse/KARAF-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336547#comment-14336547
]
Paolo Antinori commented on KARAF-3562:
---
if it might be useful this is the Postegres instance I have used for the test:
{code}
#!/bin/sh
docker run -d --name="postgresql" \
-p 5432:5432 \
-v /tmp/postgresql:/data \
-e USER="super" \
-e DB="database_name" \
-e PASS="password" \
paintedfox/postgresql
{code}
> DefaultJDBCLock case sensitive issue
>
>
> Key: KARAF-3562
> URL: https://issues.apache.org/jira/browse/KARAF-3562
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 2.3.9
>Reporter: Paolo Antinori
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 2.4.2, 3.0.4, 2.3.11
>
>
> There's a possible issue with:
> {code}
> rs = getConnection().getMetaData().getTables(null, null, tableName, new
> String[] {"TABLE"});
> schemaExists = rs.next();
> {code} in
> https://github.com/apache/karaf/blob/master/main/src/main/java/org/apache/karaf/main/lock/DefaultJDBCLock.java#L165-L167
> I'm using Postgres9.3 without any specific configuration.
> I have configured the locking mechanism to use the property
> {{karaf.lock.jdbc.table=KARAF_LOCK}}
> but Postgres stores the table name in its catalog in lowercase, so the query
> always returns a 0 length ResultSet.
> I couldn't find a short form in the JDBC api to ignore the case.
> I think this might be the default on Postgres, to convert it's catalog to
> lowercase, but I learn that this depends on the db configuration usually.
> So I suggest one of this possible options:
> - try both upper and lower case
> - improve logging to show which is table with the exact case that is checked
> - specialize PostgresJDBCLock if we can make the assumption that's pg default.
> And eventually improve Karaf docs to suggest trying to specify a lower case
> name in case of errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3564) bin/stop fails for slave in case of Lock strategies
Paolo Antinori created KARAF-3564:
-
Summary: bin/stop fails for slave in case of Lock strategies
Key: KARAF-3564
URL: https://issues.apache.org/jira/browse/KARAF-3564
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 2.3.7
Reporter: Paolo Antinori
{{bin/stop}} invokes {{org.apache.karaf.main.Stop}}
https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Stop.java
{{Stop}} reads the socket port it has to connect to from a file: {{data/port}}
is the default.
But when a Lock strategy is in place, and the instance is the one that could
not obtain the lock, the shutdown socket is never started:
https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Main.java#L1411-L1415
{code}
if (lock.lock()) {
if (lockLogged) {
LOG.info("Lock acquired.");
}
setupShutdown(props);
{code}
and the Shutdown socket is created only in {{setupShutdown()}}
A workaround is to use {{bin/clien -u admin -p admin 'shutdown --force'}}
It should be safe to move the invocation of {{setupShutdown}} outside the
{{if(lock.lock())}} branch
cross reference: https://issues.jboss.org/browse/ENTESB-2417
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3564) bin/stop fails for slave in case of Lock strategies
[
https://issues.apache.org/jira/browse/KARAF-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-3564:
--
Description:
{{bin/stop}} invokes {{org.apache.karaf.main.Stop}}
https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Stop.java
{{Stop}} reads the socket port it has to connect to from a file: {{data/port}}
is the default.
But when a Lock strategy is in place, and the instance is the one that could
not obtain the lock, the shutdown socket is never started:
https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Main.java#L1411-L1415
{code}
if (lock.lock()) {
if (lockLogged) {
LOG.info("Lock acquired.");
}
setupShutdown(props);
{code}
and the Shutdown socket is created only in {{setupShutdown()}}
A workaround is to use {{bin/client -u admin -p admin 'shutdown --force'}}
It should be safe to move the invocation of {{setupShutdown}} outside the
{{if(lock.lock())}} branch
cross reference: https://issues.jboss.org/browse/ENTESB-2417
was:
{{bin/stop}} invokes {{org.apache.karaf.main.Stop}}
https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Stop.java
{{Stop}} reads the socket port it has to connect to from a file: {{data/port}}
is the default.
But when a Lock strategy is in place, and the instance is the one that could
not obtain the lock, the shutdown socket is never started:
https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Main.java#L1411-L1415
{code}
if (lock.lock()) {
if (lockLogged) {
LOG.info("Lock acquired.");
}
setupShutdown(props);
{code}
and the Shutdown socket is created only in {{setupShutdown()}}
A workaround is to use {{bin/clien -u admin -p admin 'shutdown --force'}}
It should be safe to move the invocation of {{setupShutdown}} outside the
{{if(lock.lock())}} branch
cross reference: https://issues.jboss.org/browse/ENTESB-2417
> bin/stop fails for slave in case of Lock strategies
> ---
>
> Key: KARAF-3564
> URL: https://issues.apache.org/jira/browse/KARAF-3564
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 2.3.7
>Reporter: Paolo Antinori
>
> {{bin/stop}} invokes {{org.apache.karaf.main.Stop}}
> https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Stop.java
> {{Stop}} reads the socket port it has to connect to from a file:
> {{data/port}} is the default.
> But when a Lock strategy is in place, and the instance is the one that could
> not obtain the lock, the shutdown socket is never started:
> https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Main.java#L1411-L1415
> {code}
> if (lock.lock()) {
> if (lockLogged) {
>LOG.info("Lock acquired.");
> }
> setupShutdown(props);
> {code}
> and the Shutdown socket is created only in {{setupShutdown()}}
> A workaround is to use {{bin/client -u admin -p admin 'shutdown --force'}}
> It should be safe to move the invocation of {{setupShutdown}} outside the
> {{if(lock.lock())}} branch
> cross reference: https://issues.jboss.org/browse/ENTESB-2417
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3857) Error with nested cfg folders and BndUtils
[
https://issues.apache.org/jira/browse/KARAF-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-3857:
--
Priority: Minor (was: Major)
> Error with nested cfg folders and BndUtils
> --
>
> Key: KARAF-3857
> URL: https://issues.apache.org/jira/browse/KARAF-3857
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.0
> Environment: Windows
>Reporter: Paolo Antinori
>Priority: Minor
>
> Windows only.
> Create a subfolder in {{etc/}}. Ex. {{etc/nested}}
> Put an empty {{test.cfg}} file in {{etc/nested}}
> You get this error:
> {code}
> 2015-07-15 17:04:18,911 | ERROR | 4.0.0\bin\..\etc | fileinstall
> | 4 - org.apache.felix.fileinstall - 3.5.0 | Failed to install
> artifact: H:\k2\apache-karaf-4.0.0\etc\nested
> java.net.MalformedURLException: Invalid syntax for instruction
> [Bundle-SymbolicName=H:\k2\apache-karaf]. Take a look at
> http://www.aqute.biz/Code/Bnd.
> at
> org.ops4j.pax.swissbox.bnd.BndUtils.parseInstructions(BndUtils.java:302)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Parser.(Parser.java:116)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Connection.(Connection.java:67)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:59)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:49)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.commons.handler.HandlerActivator$Handler.openConnection(HandlerActivator.java:222)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:271)[org.apache.felix.framework-5.0.1.jar:]
> at java.net.URL.openConnection(URL.java:971)[:1.7.0_79]
> at java.net.URL.openStream(URL.java:1037)[:1.7.0_79]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:943)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[4:org.apache.felix.fileinstall:3.5.0]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3856) FileNotFoundException: \x1\asf\karaf\k40x\target\checkout\assemblies\apache-karaf\target\assembly\system\org\apache\karaf\features\framework\4.0.0\framework-4.0.0-feature
Paolo Antinori created KARAF-3856:
-
Summary: FileNotFoundException:
\x1\asf\karaf\k40x\target\checkout\assemblies\apache-karaf\target\assembly\system\org\apache\karaf\features\framework\4.0.0\framework-4.0.0-features.xml
(The system cannot find the path specified)
Key: KARAF-3856
URL: https://issues.apache.org/jira/browse/KARAF-3856
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.0
Environment: Windows
Reporter: Paolo Antinori
On windows:
Error at boot, no custom modification at all.
{code}
2015-07-15 16:56:50,542 | INFO | FelixStartLevel | fileinstall
| 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from
org.apache.karaf.features.repos.cfg
2015-07-15 16:56:50,633 | ERROR | pool-1-thread-1 | BootFeaturesInstaller
| 8 - org.apache.karaf.features.core - 4.0.0 | Error installing boot
feature repository
file:/x1/asf/karaf/k40x/target/checkout/assemblies/apache-karaf/target/assembly/system/org/apache/karaf/features/framework/4.0.0/framework-4.0.0-features.xml
java.io.IOException:
\x1\asf\karaf\k40x\target\checkout\assemblies\apache-karaf\target\assembly\system\org\apache\karaf\features\framework\4.0.0\framework-4.0.0-features.xml
(The system cannot find the path specified) :
file:/x1/asf/karaf/k40x/target/checkout/assemblies/apache-karaf/target/assembly/system/org/apache/karaf/features/framework/4.0.0/framework-4.0.0-features.xml
at
org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:85)[8:org.apache.karaf.features.core:4.0.0]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.loadRepository(FeaturesServiceImpl.java:391)[8:org.apache.karaf.features.core:4.0.0]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:411)[8:org.apache.karaf.features.core:4.0.0]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:402)[8:org.apache.karaf.features.core:4.0.0]
at
org.apache.karaf.features.internal.service.BootFeaturesInstaller.installBootFeatures(BootFeaturesInstaller.java:86)[8:org.apache.karaf.features.core:4.0.0]
at
org.apache.karaf.features.internal.service.BootFeaturesInstaller.start(BootFeaturesInstaller.java:76)[8:org.apache.karaf.features.core:4.0.0]
at
org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:257)[8:org.apache.karaf.features.core:4.0.0]
at
org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:233)[8:org.apache.karaf.features.core:4.0.0]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_79]
at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_79]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_79]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_79]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_79]
Caused by: java.io.FileNotFoundException:
\x1\asf\karaf\k40x\target\checkout\assemblies\apache-karaf\target\assembly\system\org\apache\karaf\features\framework\4.0.0\framework-4.0.0-features.xml
(The system cannot find the path specified)
at java.io.FileInputStream.open(Native Method)[:1.7.0_79]
at java.io.FileInputStream.(FileInputStream.java:146)[:1.7.0_79]
at java.io.FileInputStream.(FileInputStream.java:101)[:1.7.0_79]
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)[:1.7.0_79]
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)[:1.7.0_79]
at java.net.URL.openStream(URL.java:1037)[:1.7.0_79]
at
org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:80)[8:org.apache.karaf.features.core:4.0.0]
... 12 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3857) Error with nested cfg folders and BndUtils
Paolo Antinori created KARAF-3857:
-
Summary: Error with nested cfg folders and BndUtils
Key: KARAF-3857
URL: https://issues.apache.org/jira/browse/KARAF-3857
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.0
Environment: Windows
Reporter: Paolo Antinori
Windows only.
Create a subfolder in {{etc/}}. Ex. {{etc/nested}}
Put an empty {{test.cfg}} file in {{etc/nested}}
You get this error:
{code}
2015-07-15 17:04:18,911 | ERROR | 4.0.0\bin\..\etc | fileinstall
| 4 - org.apache.felix.fileinstall - 3.5.0 | Failed to install artifact:
H:\k2\apache-karaf-4.0.0\etc\nested
java.net.MalformedURLException: Invalid syntax for instruction
[Bundle-SymbolicName=H:\k2\apache-karaf]. Take a look at
http://www.aqute.biz/Code/Bnd.
at
org.ops4j.pax.swissbox.bnd.BndUtils.parseInstructions(BndUtils.java:302)[50:org.ops4j.pax.url.wrap:2.4.1]
at
org.ops4j.pax.url.wrap.internal.Parser.(Parser.java:116)[50:org.ops4j.pax.url.wrap:2.4.1]
at
org.ops4j.pax.url.wrap.internal.Connection.(Connection.java:67)[50:org.ops4j.pax.url.wrap:2.4.1]
at
org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:59)[50:org.ops4j.pax.url.wrap:2.4.1]
at
org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:49)[50:org.ops4j.pax.url.wrap:2.4.1]
at
org.ops4j.pax.url.commons.handler.HandlerActivator$Handler.openConnection(HandlerActivator.java:222)[50:org.ops4j.pax.url.wrap:2.4.1]
at
org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:271)[org.apache.felix.framework-5.0.1.jar:]
at java.net.URL.openConnection(URL.java:971)[:1.7.0_79]
at java.net.URL.openStream(URL.java:1037)[:1.7.0_79]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:943)[4:org.apache.felix.fileinstall:3.5.0]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[4:org.apache.felix.fileinstall:3.5.0]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[4:org.apache.felix.fileinstall:3.5.0]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[4:org.apache.felix.fileinstall:3.5.0]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[4:org.apache.felix.fileinstall:3.5.0]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3649) "instance:list" causes IllegalStateException: No session available
[
https://issues.apache.org/jira/browse/KARAF-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642783#comment-14642783
]
Paolo Antinori commented on KARAF-3649:
---
I have seen this as well and I have also noticed that it goes away if you
upgrade to {{sshd-core/0.14.0}}
> "instance:list" causes IllegalStateException: No session available
> --
>
> Key: KARAF-3649
> URL: https://issues.apache.org/jira/browse/KARAF-3649
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 3.0.3
>Reporter: Martin Lichtin
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> Just executing "instance:list" causes following exception:
> {noformat}
> 2015-04-08 10:14:58,860 | INFO | 4]-nio2-thread-8 | ServerSession
> | 28 - org.apache.sshd.core - 0.12.0 | Server session created from
> /127.0.0.1:58539
> 2015-04-08 10:14:58,864 | INFO | 4]-nio2-thread-8 | Nio2Session
> | 28 - org.apache.sshd.core - 0.12.0 | Exception handler threw
> exception, closing the session
> java.lang.IllegalStateException: No session available
> at
> org.apache.sshd.common.AbstractSessionIoHandler.exceptionCaught(AbstractSessionIoHandler.java:49)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.io.nio2.Nio2Session.exceptionCaught(Nio2Session.java:126)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.io.nio2.Nio2Session.access$500(Nio2Session.java:47)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.io.nio2.Nio2Session$2.onFailed(Nio2Session.java:230)
> at
> org.apache.sshd.common.io.nio2.Nio2CompletionHandler$2.run(Nio2CompletionHandler.java:41)
> at java.security.AccessController.doPrivileged(Native
> Method)[:1.8.0_25]
> at
> org.apache.sshd.common.io.nio2.Nio2CompletionHandler.failed(Nio2CompletionHandler.java:39)[28:org.apache.sshd.core:0.12.0]
> at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:128)[:1.8.0_25]
> at sun.nio.ch.Invoker.invokeDirect(Invoker.java:157)[:1.8.0_25]
> at
> sun.nio.ch.UnixAsynchronousSocketChannelImpl.implWrite(UnixAsynchronousSocketChannelImpl.java:736)[:1.8.0_25]
> at
> sun.nio.ch.AsynchronousSocketChannelImpl.write(AsynchronousSocketChannelImpl.java:382)[:1.8.0_25]
> at
> sun.nio.ch.AsynchronousSocketChannelImpl.write(AsynchronousSocketChannelImpl.java:399)[:1.8.0_25]
> at
> java.nio.channels.AsynchronousSocketChannel.write(AsynchronousSocketChannel.java:577)[:1.8.0_25]
> at
> org.apache.sshd.common.io.nio2.Nio2Session.startWriting(Nio2Session.java:212)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.io.nio2.Nio2Session.write(Nio2Session.java:115)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.session.AbstractSession.doWritePacket(AbstractSession.java:508)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.session.AbstractSession.writePacket(AbstractSession.java:495)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.session.AbstractSession.sendKexInit(AbstractSession.java:856)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.server.session.ServerSession.sendKexInit(ServerSession.java:128)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.server.session.ServerSession.(ServerSession.java:60)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.server.session.SessionFactory.doCreateSession(SessionFactory.java:43)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.session.AbstractSessionFactory.createSession(AbstractSessionFactory.java:38)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.AbstractSessionIoHandler.sessionCreated(AbstractSessionIoHandler.java:36)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.io.nio2.Nio2Acceptor$AcceptCompletionHandler.onCompleted(Nio2Acceptor.java:127)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.io.nio2.Nio2Acceptor$AcceptCompletionHandler.onCompleted(Nio2Acceptor.java:108)[28:org.apache.sshd.core:0.12.0]
> at
> org.apache.sshd.common.io.nio2.Nio2CompletionHandler$1.run(Nio2CompletionHandler.java:32)
> at java.security.AccessController.doPrivileged(Native
> Method)[:1.8.0_25]
> at
> org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:30)[28:org.apache.sshd.core:0.12.0]
> at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)[:1.8.0_25]
> at sun.nio.ch.Invoker$2.run(Invoker.java:218)[:1.8.0_25]
> at
> sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)[:1.8.0_25]
> at
> java.util.concurrent.ThreadPo
[jira] [Commented] (KARAF-3857) Error with nested cfg folders and BndUtils
[
https://issues.apache.org/jira/browse/KARAF-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693419#comment-14693419
]
Paolo Antinori commented on KARAF-3857:
---
https://ops4j1.jira.com/browse/PAXSB-87
> Error with nested cfg folders and BndUtils
> --
>
> Key: KARAF-3857
> URL: https://issues.apache.org/jira/browse/KARAF-3857
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.0
> Environment: Windows
>Reporter: Paolo Antinori
>Priority: Minor
>
> Windows only.
> Create a subfolder in {{etc/}}. Ex. {{etc/nested}}
> Put an empty {{test.cfg}} file in {{etc/nested}}
> You get this error:
> {code}
> 2015-07-15 17:04:18,911 | ERROR | 4.0.0\bin\..\etc | fileinstall
> | 4 - org.apache.felix.fileinstall - 3.5.0 | Failed to install
> artifact: H:\k2\apache-karaf-4.0.0\etc\nested
> java.net.MalformedURLException: Invalid syntax for instruction
> [Bundle-SymbolicName=H:\k2\apache-karaf]. Take a look at
> http://www.aqute.biz/Code/Bnd.
> at
> org.ops4j.pax.swissbox.bnd.BndUtils.parseInstructions(BndUtils.java:302)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Parser.(Parser.java:116)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Connection.(Connection.java:67)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:59)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:49)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.commons.handler.HandlerActivator$Handler.openConnection(HandlerActivator.java:222)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:271)[org.apache.felix.framework-5.0.1.jar:]
> at java.net.URL.openConnection(URL.java:971)[:1.7.0_79]
> at java.net.URL.openStream(URL.java:1037)[:1.7.0_79]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:943)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[4:org.apache.felix.fileinstall:3.5.0]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3857) Error with nested cfg folders and BndUtils
[
https://issues.apache.org/jira/browse/KARAF-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936487#comment-14936487
]
Paolo Antinori commented on KARAF-3857:
---
Hi this is fixed in Pax Swissbox {{v1.8.2}}
> Error with nested cfg folders and BndUtils
> --
>
> Key: KARAF-3857
> URL: https://issues.apache.org/jira/browse/KARAF-3857
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.0
> Environment: Windows
>Reporter: Paolo Antinori
>Priority: Minor
>
> Windows only.
> Create a subfolder in {{etc/}}. Ex. {{etc/nested}}
> Put an empty {{test.cfg}} file in {{etc/nested}}
> You get this error:
> {code}
> 2015-07-15 17:04:18,911 | ERROR | 4.0.0\bin\..\etc | fileinstall
> | 4 - org.apache.felix.fileinstall - 3.5.0 | Failed to install
> artifact: H:\k2\apache-karaf-4.0.0\etc\nested
> java.net.MalformedURLException: Invalid syntax for instruction
> [Bundle-SymbolicName=H:\k2\apache-karaf]. Take a look at
> http://www.aqute.biz/Code/Bnd.
> at
> org.ops4j.pax.swissbox.bnd.BndUtils.parseInstructions(BndUtils.java:302)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Parser.(Parser.java:116)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Connection.(Connection.java:67)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:59)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:49)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.ops4j.pax.url.commons.handler.HandlerActivator$Handler.openConnection(HandlerActivator.java:222)[50:org.ops4j.pax.url.wrap:2.4.1]
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:271)[org.apache.felix.framework-5.0.1.jar:]
> at java.net.URL.openConnection(URL.java:971)[:1.7.0_79]
> at java.net.URL.openStream(URL.java:1037)[:1.7.0_79]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:943)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[4:org.apache.felix.fileinstall:3.5.0]
> at
> org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[4:org.apache.felix.fileinstall:3.5.0]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4128) client.bat lack bouncy-castle on its classpath
Paolo Antinori created KARAF-4128:
-
Summary: client.bat lack bouncy-castle on its classpath
Key: KARAF-4128
URL: https://issues.apache.org/jira/browse/KARAF-4128
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.4
Environment: Windows
Reporter: Paolo Antinori
{{bin/client.bat}} lacks this line:
{code}
# line 120
set
CLASSPATH=%CLASSPATH%;%KARAF_HOME%\system\org\bouncycastle\bcprov-jdk15on\1.52\bcprov-jdk15on-1.52.jar
{code}
that is present in
{{bin/client}} instead:
{code}
# line 260
CLASSPATH="$CLASSPATH:$KARAF_HOME/system/org/bouncycastle/bcprov-jdk15on/1.52/bcprov-jdk15on-1.52.jar"
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (KARAF-4128) client.bat lack bouncy-castle on its classpath
[
https://issues.apache.org/jira/browse/KARAF-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori closed KARAF-4128.
-
Resolution: Invalid
Sorry. Not relevant to karaf upstream.
> client.bat lack bouncy-castle on its classpath
> --
>
> Key: KARAF-4128
> URL: https://issues.apache.org/jira/browse/KARAF-4128
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.4
> Environment: Windows
>Reporter: Paolo Antinori
> Labels: windows
>
> {{bin/client.bat}} lacks this line:
> {code}
> # line 120
> set
> CLASSPATH=%CLASSPATH%;%KARAF_HOME%\system\org\bouncycastle\bcprov-jdk15on\1.52\bcprov-jdk15on-1.52.jar
> {code}
> that is present in
> {{bin/client}} instead:
> {code}
> # line 260
> CLASSPATH="$CLASSPATH:$KARAF_HOME/system/org/bouncycastle/bcprov-jdk15on/1.52/bcprov-jdk15on-1.52.jar"
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4477) Upgrade pax-url to version 2.4.7
Paolo Antinori created KARAF-4477:
-
Summary: Upgrade pax-url to version 2.4.7
Key: KARAF-4477
URL: https://issues.apache.org/jira/browse/KARAF-4477
Project: Karaf
Issue Type: Dependency upgrade
Affects Versions: 4.0.4
Reporter: Paolo Antinori
Upgrade of {{pax.url.version}} from {{2.4.6}} to {{2.4.7}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4511) grep leaves around Ansy reset char sequence
Paolo Antinori created KARAF-4511:
-
Summary: grep leaves around Ansy reset char sequence
Key: KARAF-4511
URL: https://issues.apache.org/jira/browse/KARAF-4511
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.5
Reporter: Paolo Antinori
{{grep}} command, injects an Ansi char sequence to close the
markup/highlighting of the found token.
It shouldn't do it when the command is invoked with the {{--color never}} flag.
The current erroneous behavior, produces this output:
{code}
echo abc | grep --color never
abXc
{code}
where {{X}} is the Ansi reset sequence, injected here:
https://github.com/jboss-fuse/karaf/blob/2e2b9324d4a65076b119239edc8920185914dc60/shell/commands/src/main/java/org/apache/karaf/shell/commands/impl/GrepAction.java#L144
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4511) grep leaves around Ansi reset char sequence
[
https://issues.apache.org/jira/browse/KARAF-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-4511:
--
Summary: grep leaves around Ansi reset char sequence (was: grep leaves
around Ansy reset char sequence)
> grep leaves around Ansi reset char sequence
> ---
>
> Key: KARAF-4511
> URL: https://issues.apache.org/jira/browse/KARAF-4511
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.5
>Reporter: Paolo Antinori
>
> {{grep}} command, injects an Ansi char sequence to close the
> markup/highlighting of the found token.
> It shouldn't do it when the command is invoked with the {{--color never}}
> flag.
> The current erroneous behavior, produces this output:
> {code}
> echo abc | grep --color never
> abXc
> {code}
> where {{X}} is the Ansi reset sequence, injected here:
> https://github.com/jboss-fuse/karaf/blob/2e2b9324d4a65076b119239edc8920185914dc60/shell/commands/src/main/java/org/apache/karaf/shell/commands/impl/GrepAction.java#L144
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4511) grep leaves around Ansi reset char sequence
[
https://issues.apache.org/jira/browse/KARAF-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264006#comment-15264006
]
Paolo Antinori commented on KARAF-4511:
---
PR Open here: https://github.com/apache/karaf/pull/180
> grep leaves around Ansi reset char sequence
> ---
>
> Key: KARAF-4511
> URL: https://issues.apache.org/jira/browse/KARAF-4511
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.5
>Reporter: Paolo Antinori
>
> {{grep}} command, injects an Ansi char sequence to close the
> markup/highlighting of the found token.
> It shouldn't do it when the command is invoked with the {{--color never}}
> flag.
> The current erroneous behavior, produces this output:
> {code}
> echo abc | grep --color never
> abXc
> {code}
> where {{X}} is the Ansi reset sequence, injected here:
> https://github.com/jboss-fuse/karaf/blob/2e2b9324d4a65076b119239edc8920185914dc60/shell/commands/src/main/java/org/apache/karaf/shell/commands/impl/GrepAction.java#L144
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4567) ENC( not working in ConfigAdmin
Paolo Antinori created KARAF-4567:
-
Summary: ENC( not working in ConfigAdmin
Key: KARAF-4567
URL: https://issues.apache.org/jira/browse/KARAF-4567
Project: Karaf
Issue Type: Bug
Affects Versions: 4.0.5, 2.4.4
Reporter: Paolo Antinori
I'm trying to make support for encrypted properties in in ConfigAdmin and I
cannot make it.
My suspect is that the functionality is not really working and that the unit
test is indeed not testing the functionality.
The test is
https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/java/org/apache/karaf/jaas/blueprint/jasypt/handler/EncryptableConfigAdminPropertyPlaceholderTest.java
and I think it should not assert for the correct value of {{foo}} but it
should check the correct value of {{encoded}}, coming from
https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/resources/org/apache/karaf/jaas/blueprint/jasypt/handler/configadmin-test.xml
I'm still on this and I might be wrong, but for what I can see, tokens like
{{ENC(${prop})}} fail to be replaced because
{{org.apache.karaf.jaas.jasypt.handler.EncryptablePropertyPlaceholder}} always
try to encrypt strings like {{${prop}}} that have not been correctly replaced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4567) ENC( not working in ConfigAdmin
[
https://issues.apache.org/jira/browse/KARAF-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-4567:
--
Description:
I'm trying to make support for encrypted properties in in ConfigAdmin and I
cannot make it.
My suspect is that the functionality is not really working and that the unit
test is indeed not testing the functionality.
The test is
https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/java/org/apache/karaf/jaas/blueprint/jasypt/handler/EncryptableConfigAdminPropertyPlaceholderTest.java
and I think it should not assert for the correct value of {{foo}} but it
should check the correct value of {{encoded}}, coming from
https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/resources/org/apache/karaf/jaas/blueprint/jasypt/handler/configadmin-test.xml
I'm still on this and I might be wrong, but for what I can see, tokens like
{{ENC($\{prop})}} fail to be replaced because
{{org.apache.karaf.jaas.jasypt.handler.EncryptablePropertyPlaceholder}} always
try to encrypt strings like {{$\{prop\}}} that have not been correctly replaced.
was:
I'm trying to make support for encrypted properties in in ConfigAdmin and I
cannot make it.
My suspect is that the functionality is not really working and that the unit
test is indeed not testing the functionality.
The test is
https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/java/org/apache/karaf/jaas/blueprint/jasypt/handler/EncryptableConfigAdminPropertyPlaceholderTest.java
and I think it should not assert for the correct value of {{foo}} but it
should check the correct value of {{encoded}}, coming from
https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/resources/org/apache/karaf/jaas/blueprint/jasypt/handler/configadmin-test.xml
I'm still on this and I might be wrong, but for what I can see, tokens like
{{ENC(${prop})}} fail to be replaced because
{{org.apache.karaf.jaas.jasypt.handler.EncryptablePropertyPlaceholder}} always
try to encrypt strings like {{${prop}}} that have not been correctly replaced.
> ENC( not working in ConfigAdmin
>
>
> Key: KARAF-4567
> URL: https://issues.apache.org/jira/browse/KARAF-4567
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.4, 4.0.5
>Reporter: Paolo Antinori
>
> I'm trying to make support for encrypted properties in in ConfigAdmin and I
> cannot make it.
> My suspect is that the functionality is not really working and that the unit
> test is indeed not testing the functionality.
> The test is
> https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/java/org/apache/karaf/jaas/blueprint/jasypt/handler/EncryptableConfigAdminPropertyPlaceholderTest.java
> and I think it should not assert for the correct value of {{foo}} but it
> should check the correct value of {{encoded}}, coming from
> https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/resources/org/apache/karaf/jaas/blueprint/jasypt/handler/configadmin-test.xml
> I'm still on this and I might be wrong, but for what I can see, tokens like
> {{ENC($\{prop})}} fail to be replaced because
> {{org.apache.karaf.jaas.jasypt.handler.EncryptablePropertyPlaceholder}}
> always try to encrypt strings like {{$\{prop\}}} that have not been correctly
> replaced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4567) ENC( not working in ConfigAdmin
[
https://issues.apache.org/jira/browse/KARAF-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-4567:
--
Priority: Minor (was: Major)
> ENC( not working in ConfigAdmin
>
>
> Key: KARAF-4567
> URL: https://issues.apache.org/jira/browse/KARAF-4567
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.4, 4.0.5
>Reporter: Paolo Antinori
>Priority: Minor
>
> I'm trying to make support for encrypted properties in in ConfigAdmin and I
> cannot make it.
> My suspect is that the functionality is not really working and that the unit
> test is indeed not testing the functionality.
> The test is
> https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/java/org/apache/karaf/jaas/blueprint/jasypt/handler/EncryptableConfigAdminPropertyPlaceholderTest.java
> and I think it should not assert for the correct value of {{foo}} but it
> should check the correct value of {{encoded}}, coming from
> https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/resources/org/apache/karaf/jaas/blueprint/jasypt/handler/configadmin-test.xml
> I'm still on this and I might be wrong, but for what I can see, tokens like
> {{ENC($\{prop})}} fail to be replaced because
> {{org.apache.karaf.jaas.jasypt.handler.EncryptablePropertyPlaceholder}}
> always try to encrypt strings like {{$\{prop\}}} that have not been correctly
> replaced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4567) ENC( not working in ConfigAdmin
[
https://issues.apache.org/jira/browse/KARAF-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344240#comment-15344240
]
Paolo Antinori commented on KARAF-4567:
---
I have spoken with Guillaume and it turned out that the issue was the order of
definition of my sibling nodes.
{{cm:}} node needs to be defined bedore {{enc:}} node, otherwise it won't
affect the behavior.
The unit test still looks to be wrong though, not really testing what is
supposed to test.
> ENC( not working in ConfigAdmin
>
>
> Key: KARAF-4567
> URL: https://issues.apache.org/jira/browse/KARAF-4567
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.4, 4.0.5
>Reporter: Paolo Antinori
>Priority: Minor
>
> I'm trying to make support for encrypted properties in in ConfigAdmin and I
> cannot make it.
> My suspect is that the functionality is not really working and that the unit
> test is indeed not testing the functionality.
> The test is
> https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/java/org/apache/karaf/jaas/blueprint/jasypt/handler/EncryptableConfigAdminPropertyPlaceholderTest.java
> and I think it should not assert for the correct value of {{foo}} but it
> should check the correct value of {{encoded}}, coming from
> https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/resources/org/apache/karaf/jaas/blueprint/jasypt/handler/configadmin-test.xml
> I'm still on this and I might be wrong, but for what I can see, tokens like
> {{ENC($\{prop})}} fail to be replaced because
> {{org.apache.karaf.jaas.jasypt.handler.EncryptablePropertyPlaceholder}}
> always try to encrypt strings like {{$\{prop\}}} that have not been correctly
> replaced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4567) ENC( logical error in unit test
[
https://issues.apache.org/jira/browse/KARAF-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-4567:
--
Summary: ENC( logical error in unit test (was: ENC( not working in
ConfigAdmin)
> ENC( logical error in unit test
>
>
> Key: KARAF-4567
> URL: https://issues.apache.org/jira/browse/KARAF-4567
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.4, 4.0.5
>Reporter: Paolo Antinori
>Priority: Minor
>
> I'm trying to make support for encrypted properties in in ConfigAdmin and I
> cannot make it.
> My suspect is that the functionality is not really working and that the unit
> test is indeed not testing the functionality.
> The test is
> https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/java/org/apache/karaf/jaas/blueprint/jasypt/handler/EncryptableConfigAdminPropertyPlaceholderTest.java
> and I think it should not assert for the correct value of {{foo}} but it
> should check the correct value of {{encoded}}, coming from
> https://github.com/apache/karaf/blob/master/jaas/blueprint/jasypt/src/test/resources/org/apache/karaf/jaas/blueprint/jasypt/handler/configadmin-test.xml
> I'm still on this and I might be wrong, but for what I can see, tokens like
> {{ENC($\{prop})}} fail to be replaced because
> {{org.apache.karaf.jaas.jasypt.handler.EncryptablePropertyPlaceholder}}
> always try to encrypt strings like {{$\{prop\}}} that have not been correctly
> replaced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4637) LDAPLoginModule - add "trim usernames" option
Paolo Antinori created KARAF-4637: - Summary: LDAPLoginModule - add "trim usernames" option Key: KARAF-4637 URL: https://issues.apache.org/jira/browse/KARAF-4637 Project: Karaf Issue Type: Improvement Affects Versions: 4.0.5 Reporter: Paolo Antinori It looks like that Active Directory accepts trailing white spaces at the end of username. Other LDAP providers instead discard eventual tralining spaces. Active Directory behavior is probably not standard, but adding an option to trim usernames could be useful to avoid risking to incur in problems hard to debug (as it just happened to us). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion
[
https://issues.apache.org/jira/browse/KARAF-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-4692:
--
Description:
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the
clause completely), {{bundle:install}} command succeeds, while
{{feature:install}}, while installing a feature containing a bundle with
manifest version set to 1, fails.
{code}
karaf@root()> feature:install ibm
Error executing command: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
org.osgi.framework.BundleException: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported
'Bundle-ManifestVersion' value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9 more
{code}
was:
In case of a bundle with `Bundle-ManifestVersion` set to 1 (or without the
clause completely), `bundle:install` command succeeds, while `feature:install`,
while installing a feature containing a bundle with manifest version set to 1,
fails.
```
karaf@root()> feature:install ibm
Error executing command: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
org.osgi.framework.BundleException: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported
'Bundle-ManifestVersion' value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9
[jira] [Created] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion
Paolo Antinori created KARAF-4692: - Summary: Inconsistent behavior towards Bundle-ManifestVersion Key: KARAF-4692 URL: https://issues.apache.org/jira/browse/KARAF-4692 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 4.0.6 Reporter: Paolo Antinori In case of a bundle with `Bundle-ManifestVersion` set to 1 (or without the clause completely), `bundle:install` command succeeds, while `feature:install`, while installing a feature containing a bundle with manifest version set to 1, fails. ``` karaf@root()> feature:install ibm Error executing command: Unable to build resource for mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' value: 1 2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while executing command org.osgi.framework.BundleException: Unable to build resource for mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' value: 1 at org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6] at org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6] at org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6] at org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102] at java.lang.Thread.run(Thread.java:745)[:1.8.0_102] Caused by: org.osgi.framework.BundleException: Unsupported 'Bundle-ManifestVersion' value: 1 at org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6] at org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6] ... 9 more ``` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion
[
https://issues.apache.org/jira/browse/KARAF-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-4692:
--
Description:
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the
clause completely), {{bundle:install}} command *succeeds*, while
{{feature:install}}, while installing a feature containing a bundle with
manifest version set to 1, *fails*.
{code}
karaf@root()> feature:install ibm
Error executing command: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
org.osgi.framework.BundleException: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported
'Bundle-ManifestVersion' value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9 more
{code}
was:
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the
clause completely), {{bundle:install}} command **succeeds**, while
{{feature:install}}, while installing a feature containing a bundle with
manifest version set to 1, **fails**.
{code}
karaf@root()> feature:install ibm
Error executing command: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
org.osgi.framework.BundleException: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported
'Bundle-ManifestVersion' value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:
[jira] [Updated] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion
[
https://issues.apache.org/jira/browse/KARAF-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-4692:
--
Description:
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the
clause completely), {{bundle:install}} command **succeeds**, while
{{feature:install}}, while installing a feature containing a bundle with
manifest version set to 1, **fails**.
{code}
karaf@root()> feature:install ibm
Error executing command: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
org.osgi.framework.BundleException: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported
'Bundle-ManifestVersion' value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9 more
{code}
was:
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the
clause completely), {{bundle:install}} command succeeds, while
{{feature:install}}, while installing a feature containing a bundle with
manifest version set to 1, fails.
{code}
karaf@root()> feature:install ibm
Error executing command: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
org.osgi.framework.BundleException: Unable to build resource for
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported
'Bundle-ManifestVersion' value: 1
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.
[jira] [Created] (KARAF-4693) shell:new issue with class wildcards
Paolo Antinori created KARAF-4693:
-
Summary: shell:new issue with class wildcards
Key: KARAF-4693
URL: https://issues.apache.org/jira/browse/KARAF-4693
Project: Karaf
Issue Type: Bug
Components: karaf-shell
Affects Versions: 4.0.6
Reporter: Paolo Antinori
Karaf shell fails if you run this command:
{code:a}=shell:new java.util.ArrayList 2
2016-09-02 11:15:51,525 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
java.lang.IllegalStateException
at
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:161)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:154)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.commands.impl.NewAction.findMatchingConstructors(NewAction.java:167)[41:org.apache.karaf.shell.commands:4.0.6]
at
org.apache.karaf.shell.commands.impl.NewAction.execute(NewAction.java:89)[41:org.apache.karaf.shell.commands:4.0.6]
at
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:274)[43:org.apache.karaf.shell.core:4.0.6]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
{code}
The reason for that is not really that it can't handle generics but it the
logic that probe for the best matching constructor, that at some point, in this
class:
https://github.com/apache/karaf/blob/68bef0ced72a3fe192cfe496b3fff654b49b2377/shell/core/src/main/java/org/apache/karaf/shell/support/converter/GenericType.java#L161-L161
sees {{type}} set to {{"? extends E"}} that is not able to handle, thus
throwing the blocking exception.
It's enough to replace that exception with an empty return, to bypass the
failing iteration and have the command to succeed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4693) shell:new issue with class wildcards
[
https://issues.apache.org/jira/browse/KARAF-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-4693:
--
Description:
Karaf shell fails if you run this command:
{code:none}a=shell:new java.util.ArrayList 2
2016-09-02 11:15:51,525 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
java.lang.IllegalStateException
at
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:161)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:154)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.commands.impl.NewAction.findMatchingConstructors(NewAction.java:167)[41:org.apache.karaf.shell.commands:4.0.6]
at
org.apache.karaf.shell.commands.impl.NewAction.execute(NewAction.java:89)[41:org.apache.karaf.shell.commands:4.0.6]
at
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:274)[43:org.apache.karaf.shell.core:4.0.6]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
{code}
The reason for that is not really that it can't handle generics but it the
logic that probe for the best matching constructor, that at some point, in this
class:
https://github.com/apache/karaf/blob/68bef0ced72a3fe192cfe496b3fff654b49b2377/shell/core/src/main/java/org/apache/karaf/shell/support/converter/GenericType.java#L161-L161
sees {{type}} set to {{"? extends E"}} that is not able to handle, thus
throwing the blocking exception.
It's enough to replace that exception with an empty return, to bypass the
failing iteration and have the command to succeed.
was:
Karaf shell fails if you run this command:
{code:a}=shell:new java.util.ArrayList 2
2016-09-02 11:15:51,525 | ERROR | nsole user karaf | ShellUtil
| 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
executing command
java.lang.IllegalStateException
at
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:161)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:154)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.commands.impl.NewAction.findMatchingConstructors(NewAction.java:167)[41:org.apache.karaf.shell.commands:4.0.6]
at
org.apache.karaf.shell.commands.impl.NewAction.execute(NewAction.java:89)[41:org.apache.karaf.shell.commands:4.0.6]
at
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.6]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.ka
[jira] [Commented] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion
[
https://issues.apache.org/jira/browse/KARAF-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467190#comment-15467190
]
Paolo Antinori commented on KARAF-4692:
---
Yes, that would give a predictable behavior to the whole platform.
Eventually with a platform level configuration flag to allow bundles with
version=1, but disabled by default.
> Inconsistent behavior towards Bundle-ManifestVersion
>
>
> Key: KARAF-4692
> URL: https://issues.apache.org/jira/browse/KARAF-4692
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.0.6
>Reporter: Paolo Antinori
>
> In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the
> clause completely), {{bundle:install}} command *succeeds*, while
> {{feature:install}}, while installing a feature containing a bundle with
> manifest version set to 1, *fails*.
> {code}
> karaf@root()> feature:install ibm
> Error executing command: Unable to build resource for
> mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
> value: 1
> 2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while
> executing command
> org.osgi.framework.BundleException: Unable to build resource for
> mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion'
> value: 1
> at
> org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
> Caused by: org.osgi.framework.BundleException: Unsupported
> 'Bundle-ManifestVersion' value: 1
> at
> org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
> ... 9 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3513) JMXConnectorServer should be able to pick up the new KeystoreInstance available in container
[
https://issues.apache.org/jira/browse/KARAF-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512886#comment-15512886
]
Paolo Antinori commented on KARAF-3513:
---
[~ffang] Hi, I don't see commits related to this JIRA
https://issues.apache.org/jira/browse/KARAF-3513 in current 4.x Master
Do you think this is correct?
I'd like to contribute on top of your commits, with this fix:
https://github.com/jboss-fuse/karaf/compare/2.4.0.redhat-6-3-x...paoloantinori:ENTESB-2192_picked?expand=1
that seems to have been already reported here:
https://issues.apache.org/jira/browse/KARAF-3887
Can I ask you to double check if anything is missing or if I'm looking at the
wrong place?
> JMXConnectorServer should be able to pick up the new KeystoreInstance
> available in container
>
>
> Key: KARAF-3513
> URL: https://issues.apache.org/jira/browse/KARAF-3513
> Project: Karaf
> Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 2.4.2, 3.0.4, 4.0.0.M3
>
>
> when we configure the JMX Connector with SSL enabled, if there's no valid
> keystore available in the first place when start the "Apache Karaf ::
> Management" bundle, that bundle can't pick up any KeystoreInstance available
> afterwards.
> For an instance, if we drop a keystore.xml file like
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
> xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0";>
> rank="1"
>path="..."
>keystorePassword="..."
>keyPasswords="..." />
>
> {code}
> into etc folder after we start karaf, a bundle created accordingly and a
> KeystoreInstance get published, however, the JMX Connector won't be able to
> pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf
> :: Management" bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-5404) CLI autocompletion issue
Paolo Antinori created KARAF-5404:
-
Summary: CLI autocompletion issue
Key: KARAF-5404
URL: https://issues.apache.org/jira/browse/KARAF-5404
Project: Karaf
Issue Type: Bug
Affects Versions: 4.1.2
Reporter: Paolo Antinori
Priority: Minor
In a freshly extracted Karaf 4.1.2, running on JDK9, hitting TAB just moves the
blinking cursor.
No autocompletion is triggered.
If I start typing any command instead, like pressing a single {{j}} and then
hit TAB, I get the correct suggestion.
I suspect this is either a bug or the help message at boot should be changed
from:
{code}
Apache Karaf (4.1.2)
Hit '' for a list of available commands
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KARAF-5405) Warning on shutdown on JDK9
Paolo Antinori created KARAF-5405:
-
Summary: Warning on shutdown on JDK9
Key: KARAF-5405
URL: https://issues.apache.org/jira/browse/KARAF-5405
Project: Karaf
Issue Type: Bug
Affects Versions: 4.1.2
Environment: Linux 64
Apache Karaf (4.1.2)
java -version
openjdk version "9"
OpenJDK Runtime Environment (build 9+181)
Reporter: Paolo Antinori
Priority: Minor
Upon logout a large warning message is in the output:
{code}
karaf@root()> logout
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.karaf.management.RmiRegistryFactory (jar:bundle://37.0:0/!/) to
field sun.rmi.transport.tcp.TCPEndpoint.localEndpoints
WARNING: Please consider reporting this to the maintainers of
org.apache.karaf.management.RmiRegistryFactory
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
{code}
Last lines in the logs:
{code}
017-10-04T11:03:55,615 | INFO | pipe-logout | LogoutAction
| 40 - org.apache.karaf.shell.commands - 4.1.2 | Disconnecting from
current session...
2017-10-04T11:03:55,620 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.8.2 | Destroying
BlueprintContainer for bundle org.apache.karaf.shell.core/4.1.2
2017-10-04T11:03:55,626 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.8.2 | Destroying
BlueprintContainer for bundle org.apache.karaf.jaas.blueprint.config/4.1.2
2017-10-04T11:03:55,630 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.8.2 | Destroying
BlueprintContainer for bundle org.apache.aries.blueprint.core/1.8.2
2017-10-04T11:03:55,641 | INFO | FelixShutdown| BlueprintExtender
| 12 - org.apache.aries.blueprint.core - 1.8.2 | Destroying
BlueprintContainer for bundle org.apache.aries.blueprint.cm/1.1.0
2017-10-04T11:03:55,652 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.event/4.1.2
2017-10-04T11:03:55,661 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.system.core/4.1.2
2017-10-04T11:03:55,664 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.shell.ssh/4.1.2
2017-10-04T11:03:55,672 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.jaas.command/4.1.2
2017-10-04T11:03:55,673 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.shell.commands/4.1.2
2017-10-04T11:03:55,673 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.service.core/4.1.2
2017-10-04T11:03:55,673 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.bundle.core/4.1.2
2017-10-04T11:03:55,674 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.package.core/4.1.2
2017-10-04T11:03:55,674 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.instance.core/4.1.2
2017-10-04T11:03:55,674 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.diagnostic.core/4.1.2
2017-10-04T11:03:55,675 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.kar.core/4.1.2
2017-10-04T11:03:55,675 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.config.core/4.1.2
2017-10-04T11:03:55,676 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.deployer.kar/4.1.2
2017-10-04T11:03:55,676 | INFO | FelixStartLevel | CommandExtension
| 42 - org.apache.karaf.shell.core - 4.1.2 | Unregistering commands for
bundle org.apache.karaf.l
[jira] [Created] (KARAF-5406) CLI error on window resize on Linux(Wayland)
Paolo Antinori created KARAF-5406: - Summary: CLI error on window resize on Linux(Wayland) Key: KARAF-5406 URL: https://issues.apache.org/jira/browse/KARAF-5406 Project: Karaf Issue Type: Bug Environment: Fedora 26 with Wayland JDK9 Karaf 4.1.2 Reporter: Paolo Antinori Priority: Minor This is interesting. It looks like `jline` is not silenced to ignore UI events it doesn't expects. If I minimize/maximize my Terminal, which corresponds to the linux package `terminator-1.91-2.fc26.noarch` I get this error spitted in the CLI console: ``` Exception in thread "SIGWINCH handler" java.lang.UnsupportedOperationException at org.jline.terminal.impl.NativeSignalHandler.handle(NativeSignalHandler.java:24) at org.apache.karaf.shell.impl.console.JLineTerminal.handle(JLineTerminal.java:280) at org.jline.terminal.impl.AbstractTerminal.raise(AbstractTerminal.java:65) at org.jline.terminal.impl.PosixSysTerminal.lambda$handle$1(PosixSysTerminal.java:65) at org.jline.utils.Signals.lambda$register$1(Signals.java:51) at com.sun.proxy.$Proxy31.handle(Unknown Source) at jdk.unsupported/sun.misc.Signal$InternalMiscHandler.handle(Signal.java:198) at java.base/jdk.internal.misc.Signal$1.run(Signal.java:220) at java.base/java.lang.Thread.run(Thread.java:844) ``` Nothing relevant in `karaf.log` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5406) CLI error on window resize on Linux(Wayland)
[
https://issues.apache.org/jira/browse/KARAF-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Antinori updated KARAF-5406:
--
Description:
This is interesting.
It looks like {{jline}} is not silenced to ignore UI events it doesn't expects.
If I minimize/maximize my Terminal, which corresponds to the linux package
{{terminator-1.91-2.fc26.noarch}}
I get this error spitted in the CLI console:
{code}
Exception in thread "SIGWINCH handler" java.lang.UnsupportedOperationException
at
org.jline.terminal.impl.NativeSignalHandler.handle(NativeSignalHandler.java:24)
at
org.apache.karaf.shell.impl.console.JLineTerminal.handle(JLineTerminal.java:280)
at
org.jline.terminal.impl.AbstractTerminal.raise(AbstractTerminal.java:65)
at
org.jline.terminal.impl.PosixSysTerminal.lambda$handle$1(PosixSysTerminal.java:65)
at org.jline.utils.Signals.lambda$register$1(Signals.java:51)
at com.sun.proxy.$Proxy31.handle(Unknown Source)
at
jdk.unsupported/sun.misc.Signal$InternalMiscHandler.handle(Signal.java:198)
at java.base/jdk.internal.misc.Signal$1.run(Signal.java:220)
at java.base/java.lang.Thread.run(Thread.java:844)
{code}
Nothing relevant in {{karaf.log}}
was:
This is interesting.
It looks like `jline` is not silenced to ignore UI events it doesn't expects.
If I minimize/maximize my Terminal, which corresponds to the linux package
`terminator-1.91-2.fc26.noarch`
I get this error spitted in the CLI console:
```
Exception in thread "SIGWINCH handler" java.lang.UnsupportedOperationException
at
org.jline.terminal.impl.NativeSignalHandler.handle(NativeSignalHandler.java:24)
at
org.apache.karaf.shell.impl.console.JLineTerminal.handle(JLineTerminal.java:280)
at
org.jline.terminal.impl.AbstractTerminal.raise(AbstractTerminal.java:65)
at
org.jline.terminal.impl.PosixSysTerminal.lambda$handle$1(PosixSysTerminal.java:65)
at org.jline.utils.Signals.lambda$register$1(Signals.java:51)
at com.sun.proxy.$Proxy31.handle(Unknown Source)
at
jdk.unsupported/sun.misc.Signal$InternalMiscHandler.handle(Signal.java:198)
at java.base/jdk.internal.misc.Signal$1.run(Signal.java:220)
at java.base/java.lang.Thread.run(Thread.java:844)
```
Nothing relevant in `karaf.log`
> CLI error on window resize on Linux(Wayland)
>
>
> Key: KARAF-5406
> URL: https://issues.apache.org/jira/browse/KARAF-5406
> Project: Karaf
> Issue Type: Bug
> Environment: Fedora 26 with Wayland
> JDK9
> Karaf 4.1.2
>Reporter: Paolo Antinori
>Priority: Minor
>
> This is interesting.
> It looks like {{jline}} is not silenced to ignore UI events it doesn't
> expects.
> If I minimize/maximize my Terminal, which corresponds to the linux package
> {{terminator-1.91-2.fc26.noarch}}
> I get this error spitted in the CLI console:
> {code}
> Exception in thread "SIGWINCH handler" java.lang.UnsupportedOperationException
> at
> org.jline.terminal.impl.NativeSignalHandler.handle(NativeSignalHandler.java:24)
> at
> org.apache.karaf.shell.impl.console.JLineTerminal.handle(JLineTerminal.java:280)
> at
> org.jline.terminal.impl.AbstractTerminal.raise(AbstractTerminal.java:65)
> at
> org.jline.terminal.impl.PosixSysTerminal.lambda$handle$1(PosixSysTerminal.java:65)
> at org.jline.utils.Signals.lambda$register$1(Signals.java:51)
> at com.sun.proxy.$Proxy31.handle(Unknown Source)
> at
> jdk.unsupported/sun.misc.Signal$InternalMiscHandler.handle(Signal.java:198)
> at java.base/jdk.internal.misc.Signal$1.run(Signal.java:220)
> at java.base/java.lang.Thread.run(Thread.java:844)
> {code}
> Nothing relevant in {{karaf.log}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5404) CLI autocompletion issue
[
https://issues.apache.org/jira/browse/KARAF-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191237#comment-16191237
]
Paolo Antinori commented on KARAF-5404:
---
Linux 64.
Same behavior with java8 and with different terminals.
{code}
$ echo $LANG
en_GB.utf8
{code}
{code}
karaf@root()> system:property
awt.toolkit=sun.awt.X11.XToolkit
com.sun.management.jmxremote=
file.encoding=UTF-8
file.encoding.pkg=sun.io
file.separator=/
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path=/data/software/redhat/fuse/apache-karaf-4.1.2/lib/boot/jna-4.4.0.jar:/data/software/redhat/fuse/apache-karaf-4.1.2/lib/boot/jna-platform-4.4.0.jar:/data/software/redhat/fuse/apache-karaf-4.1.2/lib/boot/org.apache.karaf.diagnostic.boot-4.1.2.jar:/data/software/redhat/fuse/apache-karaf-4.1.2/lib/boot/org.apache.karaf.jaas.boot-4.1.2.jar:/data/software/redhat/fuse/apache-karaf-4.1.2/lib/boot/org.apache.karaf.main-4.1.2.jar:/data/software/redhat/fuse/apache-karaf-4.1.2/lib/boot/org.osgi.core-6.0.0.jar
java.class.version=52.0
java.endorsed.dirs=/etc/alternatives/java_sdk_openjdk/jre/lib/endorsed:/etc/alternatives/java_sdk_openjdk/lib/endorsed:/data/software/redhat/fuse/apache-karaf-4.1.2/lib/endorsed
java.ext.dirs=/etc/alternatives/java_sdk_openjdk/jre/lib/ext:/etc/alternatives/java_sdk_openjdk/lib/ext:/data/software/redhat/fuse/apache-karaf-4.1.2/lib/ext
java.home=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.144-5.b01.fc26.x86_64/jre
java.io.tmpdir=/data/software/redhat/fuse/apache-karaf-4.1.2/data/tmp
java.library.path=:/data/software/redhat/fuse/apache-karaf-4.1.2/lib:/data/software/redhat/fuse/apache-karaf-4.1.2/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.rmi.server.randomIDs=true
java.runtime.name=OpenJDK Runtime Environment
java.runtime.version=1.8.0_144-b01
java.specification.name=Java Platform API Specification
java.specification.vendor=Oracle Corporation
java.specification.version=1.8
java.util.logging.config.file=/data/software/redhat/fuse/apache-karaf-4.1.2/etc/java.util.logging.properties
java.vendor=Oracle Corporation
java.vendor.url=http://java.oracle.com/
java.vendor.url.bug=http://bugreport.sun.com/bugreport/
java.version=1.8.0_144
java.vm.info=mixed mode
java.vm.name=OpenJDK 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Oracle Corporation
java.vm.specification.version=1.8
java.vm.vendor=Oracle Corporation
java.vm.version=25.144-b01
jna.loaded=true
jna.platform.library.path=/usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/xulrunner:/usr/lib64/atlas:/usr/lib64/dyninst:/usr/lib64/qt-3.3/lib:/usr/lib64/octave/4.2.1:/usr/lib64/mysql:/usr/lib64/iscsi:/usr/lib64/bind99:/usr/lib64/freetype-freeworld:/usr/lib64/tcl8.6
jnidispatch.path=/data/software/redhat/fuse/apache-karaf-4.1.2/data/tmp/jna-1074345407/jna929030919535504.tmp
karaf.base=/data/software/redhat/fuse/apache-karaf-4.1.2
karaf.clean.all=false
karaf.clean.cache=false
karaf.data=/data/software/redhat/fuse/apache-karaf-4.1.2/data
karaf.default.repository=system
karaf.delay.console=false
karaf.etc=/data/software/redhat/fuse/apache-karaf-4.1.2/etc
karaf.home=/data/software/redhat/fuse/apache-karaf-4.1.2
karaf.instances=/data/software/redhat/fuse/apache-karaf-4.1.2/instances
karaf.local.roles=admin,manager,viewer,systembundles
karaf.local.user=karaf
karaf.name=root
karaf.restart=false
karaf.restart.jvm=false
karaf.restart.jvm.supported=true
karaf.secured.services=(&(osgi.command.scope=*)(osgi.command.function=*))
karaf.shell.init.script=etc/shell.init.script,etc/scripts/*.script
karaf.shell.suppress.welcome=true
karaf.startLocalConsole=true
karaf.startRemoteShell=true
karaf.version=4.1.2
line.separator=
org.apache.aries.proxy.weaving.disabled=org.objectweb.asm.*,org.slf4j.*,org.apache.log4j.*,javax.*,org.apache.xerces.*
org.apache.aries.proxy.weaving.enabled=none
org.apache.servicemix.specs.debug=false
org.apache.servicemix.specs.timeout=0
org.ops4j.pax.logging.DefaultServiceLog.level=ERROR
org.osgi.framework.bootdelegation=com.sun.*, javax.transaction,
javax.transaction.*, javax.xml.crypto, javax.xml.crypto.*, jdk.nashorn.*,
sun.*, org.apache.html.dom, org.apache.wml.dom, org.apache.wml,
org.apache.xerces.xpointer, org.apache.xerces.xni.grammars,
org.apache.xerces.impl.xs.util, org.apache.xerces.jaxp.validation,
org.apache.xerces.impl.dtd.models, org.apache.xerces.impl.xpath,
org.apache.xerces.dom3.as, org.apache.xerces.impl.dv.xs,
org.apache.xerces.util, org.apache.xerces.impl.xs.opti,
org.apache.xerces.impl.xs.identity, org.apache.xerces.jaxp,
org.apache.xerces.impl.dv, org.apache.xerces.xs.datatypes,
org.apache.xerces.impl.msg, org.apache.xerces.dom.events,
org.apache.xerces.xni, org.apache.xerces.impl.xs, org.apache.xerces.impl,
org.apache.xerces.stax.events, org.apache.xerces.impl.io,
org.apache.xerces.xinclude, org.apache.xerc
[jira] [Created] (KARAF-5413) Missing explicit version in features
Paolo Antinori created KARAF-5413:
-
Summary: Missing explicit version in features
Key: KARAF-5413
URL: https://issues.apache.org/jira/browse/KARAF-5413
Project: Karaf
Issue Type: Bug
Reporter: Paolo Antinori
Priority: Minor
Explicit version is missing in a couple of features
{code}
/data/repositories/work/karaf [master_upstream|⚑ 3]
14:48 $ xmlstarlet sel -N ns=http://karaf.apache.org/xmlns/features/v1.3.0 -t
-v '/ns:features/ns:feature[not(@version)]/@name'
assemblies/features/standard/src/main/feature/feature.xml
jaas-boot
pax-http-service
wrap
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KARAF-5415) Issue with feature resolution (CXF related)
Paolo Antinori created KARAF-5415:
-
Summary: Issue with feature resolution (CXF related)
Key: KARAF-5415
URL: https://issues.apache.org/jira/browse/KARAF-5415
Project: Karaf
Issue Type: Bug
Affects Versions: 4.1.2
Reporter: Paolo Antinori
Hi, I am facing an odd behavior I cannot explain, with the feature resolution
logic.
I suspect a bug
In the scenario that I'm going to describe here, I end up with a version of
jetty that I wouldn't expect to see installed.
0. create a new features descriptor on the filesystem:
{code}
cat >> /tmp/features.xml <<"EOF"
http://karaf.apache.org/xmlns/features/v1.0.0"; name="cxf-test">
jetty
cxf-http
cxf-http
jetty
EOF
{code}
1. start a clean karaf 4.1.2
2. enable cxf repo: {{repo-add cxf 3.1.12}}
3. enable custom repo: {{feature:repo-add file:///tmp/features.xml}}
4. now the test, compare the outcome of the installation of the 3 features:
{code}
karaf@root()> feature:install test1
karaf@root()> la -l | grep -i jetty-all
# empty
karaf@root()> feature:uninstall test1
karaf@root()> feature:install test2
karaf@root()> la -l | grep -i jetty-all
# empty
karaf@root()> feature:uninstall test2
karaf@root()> feature:install test3
karaf@root()> la -l | grep -i jetty-all
142 │ Active │ 30 │ 8.1.14.v20131031 │
mvn:org.eclipse.jetty.aggregate/jetty-all-server/8.1.14.v20131031
# installs something from jetty 8 ???
{code}
So far I have not been able to understand in debug, where the error occurr or
what's causing it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5413) Missing explicit version in features
[
https://issues.apache.org/jira/browse/KARAF-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201623#comment-16201623
]
Paolo Antinori commented on KARAF-5413:
---
[~ffang] have you seen [~jbonofre] comments on github?
We probably need to bind 2 of those versions to other constants:
https://github.com/apache/karaf/pull/383/files
> Missing explicit version in features
>
>
> Key: KARAF-5413
> URL: https://issues.apache.org/jira/browse/KARAF-5413
> Project: Karaf
> Issue Type: Bug
>Reporter: Paolo Antinori
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 4.2.0
>
>
> Explicit version is missing in a couple of features
> {code}
> /data/repositories/work/karaf [master_upstream|⚑ 3]
> 14:48 $ xmlstarlet sel -N ns=http://karaf.apache.org/xmlns/features/v1.3.0
> -t -v '/ns:features/ns:feature[not(@version)]/@name'
> assemblies/features/standard/src/main/feature/feature.xml
> jaas-boot
> pax-http-service
> wrap
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KARAF-5421) Better error while installing non OSGi bundles
Paolo Antinori created KARAF-5421:
-
Summary: Better error while installing non OSGi bundles
Key: KARAF-5421
URL: https://issues.apache.org/jira/browse/KARAF-5421
Project: Karaf
Issue Type: Improvement
Affects Versions: 4.1.2
Reporter: Paolo Antinori
I understand installing a non OSGi bundle is wrong at a logical level, but the
error message when doing so, it's fairly cryptic:
{code}
karaf@root()> install mvn:org.keycloak/keycloak-undertow-adapter/3.3.0.CR2
Bundle IDs:
Error executing command: Error installing bundles:
Unable to install bundle
mvn:org.keycloak/keycloak-undertow-adapter/3.3.0.CR2:
org.osgi.framework.BundleException: OSGi R3 bundle not supported
{code}
Does it make sense for the error message to suggest checking it's a valid
bundle?
Manifest of the above file is:
{code}
14:21 $ unzip -c
~/.m2/repository/org/keycloak/keycloak-undertow-adapter/3.3.0.CR2/keycloak-undertow-adapter-3.3.0.CR2.jar
**MANIFEST.MF
Archive:
/home/pantinor/.m2/repository/org/keycloak/keycloak-undertow-adapter/3.3.0.CR2/keycloak-undertow-adapter-3.3.0.CR2.jar
inflating: META-INF/MANIFEST.MF
Manifest-Version: 1.0
Implementation-Title: Keycloak Undertow Integration
Implementation-Version: 3.3.0.CR2
Java-Version: 1.8.0_144
Built-By: pantinor
Scm-Connection: scm:git:git://github.com/keycloak/keycloak.git/keycloa
k-undertow-adapter
Specification-Vendor: JBoss by Red Hat
Os-Arch: amd64
Specification-Title: Keycloak Undertow Integration
Implementation-Vendor-Id: org.keycloak
Java-Vendor: Oracle Corporation
Os-Name: Linux
Scm-Url: https://github.com/keycloak/keycloak/tree/master/keycloak-und
ertow-adapter/
Implementation-Vendor: JBoss by Red Hat
Os-Version: 4.12.14-300.fc26.x86_64
Scm-Revision: 08d5a7a062fdbf8f2b63ca2a6e14e0fce2d3e3f1
Created-By: Apache Maven 3.5.0
Build-Jdk: 1.8.0_144
Specification-Version: 3.3
Implementation-URL: http://keycloak.org/keycloak-undertow-adapter
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5415) Issue with feature resolution (CXF related)
[
https://issues.apache.org/jira/browse/KARAF-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262204#comment-16262204
]
Paolo Antinori commented on KARAF-5415:
---
Thanks Guillaume for the explanation!
> Issue with feature resolution (CXF related)
> ---
>
> Key: KARAF-5415
> URL: https://issues.apache.org/jira/browse/KARAF-5415
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Paolo Antinori
>Assignee: Guillaume Nodet
>
> Hi, I am facing an odd behavior I cannot explain, with the feature resolution
> logic.
> I suspect a bug
> In the scenario that I'm going to describe here, I end up with a version of
> jetty that I wouldn't expect to see installed.
> 0. create a new features descriptor on the filesystem:
> {code}
> cat >> /tmp/features.xml <<"EOF"
>
> http://karaf.apache.org/xmlns/features/v1.0.0";
> name="cxf-test">
>
>jetty
>
>
>cxf-http
>
>
>
>cxf-http
>jetty
>
>
> EOF
> {code}
> 1. start a clean karaf 4.1.2
> 2. enable cxf repo: {{repo-add cxf 3.1.12}}
> 3. enable custom repo: {{feature:repo-add file:///tmp/features.xml}}
> 4. now the test, compare the outcome of the installation of the 3 features:
> {code}
> karaf@root()> feature:install test1
> karaf@root()> la -l | grep -i jetty-all
> # empty
> karaf@root()> feature:uninstall test1
> karaf@root()> feature:install test2
> karaf@root()> la -l | grep -i jetty-all
> # empty
> karaf@root()> feature:uninstall test2
> karaf@root()> feature:install test3
> karaf@root()> la -l | grep -i jetty-all
>
>
> 142 │ Active │ 30 │ 8.1.14.v20131031 │
> mvn:org.eclipse.jetty.aggregate/jetty-all-server/8.1.14.v20131031
> # installs something from jetty 8 ???
> {code}
> So far I have not been able to understand in debug, where the error occurr or
> what's causing it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
