[jira] [Updated] (FELIX-3317) Concurrency issue during Component Service registration

[ https://issues.apache.org/jira/browse/FELIX-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-3317: - Summary: Concurrency issue during Component Service registration (was: Potential concurr

Re: Weird problem with EventAdmin:blacklisting

Hi carsten thanks for the explanation I did not read the whole source codeunderstood The code works nice in equinox with the same eventadmin bundle deployed inside... I know this plugin and it s installed the event is on the correct topic and the servlet listens this topic but is never notif

Re: Weird problem with EventAdmin:blacklisting

Hi, for your previous question: the code is a little bit tricky. It's correct that just the sync handler gets the configuration. But the async handler does not deliver events by itself. It uses internally the async handler as well. Therefore timeout handling applies here as well. The blacklisting

[jira] [Commented] (FELIX-3317) Potential concurrency issue during Component Service registration

[ https://issues.apache.org/jira/browse/FELIX-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193043#comment-13193043 ] Felix Meschberger commented on FELIX-3317: -- There are multiple approaches to this

[jira] [Commented] (FELIX-3311) Cookie handling seems not to work anymore

[ https://issues.apache.org/jira/browse/FELIX-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193022#comment-13193022 ] Felix Meschberger commented on FELIX-3311: -- I recently (FELIX-3290) changed the c

[jira] [Created] (FELIX-3317) Potential concurrency issue during Component Service registration

Potential concurrency issue during Component Service registration - Key: FELIX-3317 URL: https://issues.apache.org/jira/browse/FELIX-3317 Project: Felix Issue Type: Bug

[jira] [Commented] (FELIX-3311) Cookie handling seems not to work anymore

[ https://issues.apache.org/jira/browse/FELIX-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193009#comment-13193009 ] Valentin Valchev commented on FELIX-3311: - Changing the language also doesn't work

[jira] [Updated] (FELIX-3316) Log plugin should provide more detailed exception column

[ https://issues.apache.org/jira/browse/FELIX-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-3316: Assignee: Felix Meschberger (was: Valentin Valchev) > Log plugin should provide more d

[jira] [Commented] (FELIX-3316) Log plugin should provide more detailed exception column

[ https://issues.apache.org/jira/browse/FELIX-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193006#comment-13193006 ] Valentin Valchev commented on FELIX-3316: - Fixed in rev.1235728 We need to add lo

[jira] [Resolved] (FELIX-3315) Log plugin does not show the bundle that has logged the event

[ https://issues.apache.org/jira/browse/FELIX-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-3315. - Resolution: Fixed > Log plugin does not show the bundle that has logged the event > -

[jira] [Created] (FELIX-3316) Log plugin should provide more detailed exception column

Log plugin should provide more detailed exception column Key: FELIX-3316 URL: https://issues.apache.org/jira/browse/FELIX-3316 Project: Felix Issue Type: Improvement Componen

[jira] [Created] (FELIX-3315) Log plugin does not show the bundle that has logged the event

Log plugin does not show the bundle that has logged the event - Key: FELIX-3315 URL: https://issues.apache.org/jira/browse/FELIX-3315 Project: Felix Issue Type: Improvement

Re: Weird problem with EventAdmin:blacklisting

My current problems are : - why such blacklisting ? - how this blacklisting may affect my communication because with the webconsole and log service I can see my message present in the right topic , but it's never dequeued ... it's stuck on the topic, handleEvent() callback is never invoked in my s

Re: Weird problem with EventAdmin:blacklisting

Hi once again, I just had a look to the source code and I'd like you to drop me a terrible confusion... In my code I am using the postEvent() method...This is the asynchronous sending of message isn't it ? But as far as I understand while reading the source ,timeouts are set for Synchronous deliver

Re: Weird problem with EventAdmin:blacklisting

Hi, by default the impl measures the time an event handler uses too handle this event. Once this is over the configured limit (in millisecs), this handler gets blacklisted - and stays there forever (unless you restart either the handler or the event admin). A usual trap here is debugging an event

Re: Weird problem with EventAdmin:blacklisting

Thanks for your help Carsten I'll do some tests I must read the source code to figure out with accuracy what kind of timeouts is used ... I don't see any valuable reason for my servlet not respond in 5seconds!!! It's present at startup with a runlevel 2 ... let me know more about the mechanism

Re: Weird problem with EventAdmin:blacklisting

Hi, the Felix event admin by default blacklists event handlers if they take more than 5 secs. With the setting you mentioned, you turn off the timeout for all event handlers. If you want a more fine grained setting, you can use the property org.apache.felix.eventadmin.IgnoreTimeout to disable tim

Re: Weird problem with EventAdmin:blacklisting

I'll try a test with the following property setted to 0 : org.apache.felix.eventadmin.Timeout I'll let you know results of such experiments regards J.MOLIERE - Mentor/J auteur Eyrolles blog: http://romjethoughts.blogspot.com 2012/1/25 jerome moliere : > Hi all, > I 've one part of my applicati

[jira] [Resolved] (FELIX-3314) Sort UPnP devices in alphabetical order

[ https://issues.apache.org/jira/browse/FELIX-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-3314. - Resolution: Fixed Fix Version/s: webconsole-upnp-plugin-1.0.2 fixed in SVN rev.123

[jira] [Created] (FELIX-3314) Sort UPnP devices in alphabetical order

Sort UPnP devices in alphabetical order --- Key: FELIX-3314 URL: https://issues.apache.org/jira/browse/FELIX-3314 Project: Felix Issue Type: Improvement Components: Web Console Affects Versio

Re: [VOTE] Release Service Diagnostics Plugin version 0.1.1

+1 Carsten 2012/1/20 Arjun Panday : > Hi everyone, > > Second attempt at releasing the Service Diagnostics WebConsole Plugin. > I've simply refactored the POMs by moving the parent role out of the reactor > POM. The directory structure seems cleaner. Let me know. > > Here's the staging repository

Re: [VOTE] Release Service Diagnostics Plugin version 0.1.1

2012/1/25 Arjun Panday : > Hi Carsten, > > Yes, I put it on hkp://pool.sks-keyservers.net, as recommended on this page: > https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven > > gpg --keyserver hkp://pool.sks-keyservers.net --recv-keys 9196890A > gpg: requesting k

Re: [VOTE] Release Service Diagnostics Plugin version 0.1.1

Hi Carsten, Yes, I put it on hkp://pool.sks-keyservers.net, as recommended on this page: https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven gpg --keyserver hkp://pool.sks-keyservers.net --recv-keys 9196890A gpg: requesting key 9196890A from hkp server pool.

Re: [VOTE] Release Service Diagnostics Plugin version 0.1.1

Hi Arjun, is your key on a public key server? Regards Carsten 2012/1/20 Arjun Panday : > Hi everyone, > > Second attempt at releasing the Service Diagnostics WebConsole Plugin. > I've simply refactored the POMs by moving the parent role out of the reactor > POM. The directory structure seems cle