[
https://issues.apache.org/jira/browse/FELIX-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-4941:
---
Assignee: Carsten Ziegeler
> Web console doesn't work with fileinstall
>
[
https://issues.apache.org/jira/browse/FELIX-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-4941:
Labels: (was: easyfix)
> Web console doesn't work with fileinstall
> -
[
https://issues.apache.org/jira/browse/FELIX-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-4941:
Summary: Configuration Properties not defined in Metatype are lost after
update (was: Web c
ping?
On 23/05/16 09:50, Ferry Huberts (JIRA) wrote:
Ferry Huberts created FELIX-5261:
Summary: FileInstall: allow comments in *.config files
Key: FELIX-5261
URL: https://issues.apache.org/jira/browse/FELIX-5261
[
https://issues.apache.org/jira/browse/FELIX-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-4941.
-
Resolution: Fixed
I've updated the web console to leave all properties not covered by meta
We solved three issues in this release:
http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.webconsole-4.2.16/changelog.txt
Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-1122/
You can use this UNIX script to download the release and verify th
+1 (non binding)
Tested on Karaf.
Regards
JB
On 05/31/2016 09:44 AM, Carsten Ziegeler wrote:
We solved three issues in this release:
http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.webconsole-4.2.16/changelog.txt
Staging repositories:
https://repository.apache.org/content/rep
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
+1
David
On 31 May 2016 at 09:44, Carsten Ziegeler wrote:
> We solved three issues in this release:
>
> http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.webconsole-4.2.16/changelog.txt
>
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix
+1 (non binding)
On 31.5.2016 г. 10:44 ч., Carsten Ziegeler wrote:
> We solved three issues in this release:
> http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.webconsole-4.2.16/changelog.txt
>
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapache
+1 (non-binding)
On Tue, May 31, 2016 at 6:32 AM, Valentin Valchev
wrote:
> +1 (non binding)
>
>
> On 31.5.2016 г. 10:44 ч., Carsten Ziegeler wrote:
>
> We solved three issues in this
> release:http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.webconsole-4.2.16/changelog.txt
>
>
>
[
https://issues.apache.org/jira/browse/FELIX-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308077#comment-15308077
]
Stefan Seifert commented on FELIX-4009:
---
thanks! - this should be all
> maven bundl
Hi all,
I am observing an issue in production which looks to me like a race
condition, but I am unable to reproduce it so far.
The exception is:
java.lang.IllegalStateException: Existing Configuration with pid
factoryPid.a5b6fe71-556c-4ce9-b09c-c19542586fc5 has had its properties set
to null and
You might know what’s in Karaf, but I don’t. What are the versions of config
admin and DS that you are using?
Since you say this is occurring in production it might not be possible, but if
you can get a log with debug trace on (setting ds.loglevel=debug) with the
trunk version of DS that would
Hi David,
some info is in the trace:
org.apache.felix.configadmin:1.8.8
org.apache.felix.scr:2.0.2
Unfortunately I cannot get the trunk version into production. but I can try
the debug log anyway. But first I need to figure out where I can set this
Fabian
On Tue, May 31, 2016 at 10:04 PM, David
Hi David,
I made some progress. I took the current trunk and changed version to 2.0.2
and compiled it, so i could just drop the dependency into my instances.
I added ds.loglevel=debug, but I am unsure if i capture the logs you might
be interested in. I see stuff like:
2016-05-31T23:01:48.530+0200
Hi Fabian,
That would be the good info in case it happens again :-)
Other than the logging changes, I don’t think anything has changed here since
2.0.2.
Meanwhile I will try to think about whether there can be a race condition we
don’t currently deal with. There might be, because we do a comb
[
https://issues.apache.org/jira/browse/FELIX-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Watson closed FELIX-5254.
> Improve structure of permutations to use unmodifiable capability lists
> -
[
https://issues.apache.org/jira/browse/FELIX-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Watson resolved FELIX-5254.
--
Resolution: Fixed
Assignee: Thomas Watson
I released a fix that introduced a class Candida
David Jencks created FELIX-5270:
---
Summary: [DS] Config race between update and delete
Key: FELIX-5270
URL: https://issues.apache.org/jira/browse/FELIX-5270
Project: Felix
Issue Type: Bug
Fabian sent me some logs off-list that helped me figure out what is going on.
I’ve opened https://issues.apache.org/jira/browse/FELIX-5270.
Meanwhile if it would not break the rest of your system I think you might avoid
triggering the problem by explicitly setting the bundle location, for insta
Hi David,
many thanks for your quick analysis!
Indeed changing bundle location to "?" makes the problem go away. It works
for this application because the configuration by design is anyway just
intended for a specific bundle. The factories use unique pids.
I will keep my reproduction scenario aliv
22 matches
Mail list logo
