[
https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-3380:
Affects Version/s: JCR Resource 2.2.8
Reduce memory footprint of JcrResourceListener
[
https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-3380:
Summary: Reduce memory footprint of JcrResourceListener (was: Reduce
memory footprint of)
[
https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-3380:
Fix Version/s: JCR Resource 2.3.2
Reduce memory footprint of JcrResourceListener
[
https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894311#comment-13894311
]
Robert Munteanu commented on SLING-2393:
[~alexander.klimetschek] - that would be
[
https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894320#comment-13894320
]
Carsten Ziegeler commented on SLING-3380:
-
To immediately free the event object,
Great news, yepp, I agree with Justin
2014-02-06 18:51 GMT+01:00 Justin Edelson jus...@justinedelson.com:
Hi Chetan,
Thanks for following through on this. I think the loss of messages
during initialization is less than ideal, but acceptable and certainly
understandable.
Justin
On Thu,
[
https://issues.apache.org/jira/browse/SLING-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-3366.
Resolution: Fixed
you can now configure connectionTimeout and soTimeout (both in seconds, both
[
https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894373#comment-13894373
]
Michael Dürig commented on SLING-3380:
--
bq. To immediately free the event object, we
[
https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-3380:
---
Assignee: Carsten Ziegeler
Reduce memory footprint of JcrResourceListener
The Buildbot has detected a new failure on builder sling-trunk-oak while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk-oak/builds/219
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: downstream
Build
[
https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894381#comment-13894381
]
Carsten Ziegeler commented on SLING-3380:
-
I've committed a first solution in rev
Stefan Egli created SLING-3382:
--
Summary: introduce back-off strategy for topology connector
frequency
Key: SLING-3382
URL: https://issues.apache.org/jira/browse/SLING-3382
Project: Sling
Hi,
During an offline discussion, Felix brought up the suggestion to lower the
topology connector's heartbeat frequency. Currently they are sent every 15 or
30 sec, which might seem a lot - especially as they were way too chatty (which
is fixed now with SLING-3377).
The main reason for having
Sounds like a good strategy to me
+1
Carsten
2014-02-07 11:38 GMT+01:00 Stefan Egli e...@adobe.com:
Hi,
During an offline discussion, Felix brought up the suggestion to lower the
topology connector's heartbeat frequency. Currently they are sent every 15
or 30 sec, which might seem a lot
[
https://issues.apache.org/jira/browse/SLING-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reassigned SLING-3375:
--
Assignee: Stefan Egli
HttpClient use in org.apache.sling.discovery.impl package does not
[
https://issues.apache.org/jira/browse/SLING-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3348:
---
Fix Version/s: Discovery Impl 1.0.4
fix sortable table headers in /system/console/topology
[
https://issues.apache.org/jira/browse/SLING-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3371:
---
Fix Version/s: Discovery Impl 1.0.4
provide more details in topology webconsole in error case
[
https://issues.apache.org/jira/browse/SLING-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3375:
---
Fix Version/s: Discovery Impl 1.0.4
HttpClient use in org.apache.sling.discovery.impl package does
[
https://issues.apache.org/jira/browse/SLING-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3377:
---
Fix Version/s: Discovery Impl 1.0.4
Make topology connector a plain HttpServlet instead of a
[
https://issues.apache.org/jira/browse/SLING-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3316:
---
Fix Version/s: Discovery Impl 1.0.4
Add auto-stop behavior to topology connector if pinging self
[
https://issues.apache.org/jira/browse/SLING-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3365:
---
Fix Version/s: Discovery Impl 1.0.4
HeartbeatHandler.deactivate() should not block
[
https://issues.apache.org/jira/browse/SLING-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3001:
---
Fix Version/s: Discovery Impl 1.0.4
Support wildcard (was: regular expressions) in IP whitelist for
[
https://issues.apache.org/jira/browse/SLING-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reassigned SLING-3296:
--
Assignee: Stefan Egli
Occasional NPE in EstablishedClusterView
[
https://issues.apache.org/jira/browse/SLING-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3366:
---
Fix Version/s: Discovery Impl 1.0.4
Allow to configure the heartbeat connection parameters
[
https://issues.apache.org/jira/browse/SLING-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-3367:
---
Fix Version/s: Discovery Impl 1.0.4
gzip topology announcements
---
The Buildbot has detected a new failure on builder sling-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk/builds/259
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
[
https://issues.apache.org/jira/browse/SLING-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reassigned SLING-3320:
--
Assignee: Bertrand Delacretaz
Execution order of BindingsValuesProvider
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria updated SLING-3352:
-
Attachment: SLING-3352.patch
I have implemented a full sync between osgi configs and jcr nodes
Hi,
I am thinking if we reduce the amount of data persisted in the repository
with every topology heartbeat.
For example we could just update the timestamp of the of announcement
hearbeat, if the topology hasn't changed at all (instead of writing the
complete announcement).
A more radical
[
https://issues.apache.org/jira/browse/SLING-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894565#comment-13894565
]
Radu Cotescu commented on SLING-3320:
-
Everything looks good to me. Can we also get a
[
https://issues.apache.org/jira/browse/SLING-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-3320.
Resolution: Fixed
Execution order of BindingsValuesProvider
[
https://issues.apache.org/jira/browse/SLING-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-3320:
---
Summary: Use service ranking to sort BindingsValuesProvider services (was:
What could be done for level 3:
a) at startup the behavior is as is today, cluster-ready, writing
repository-heartbeats as configured
b) this is done for a configured amount of time at least, eg for 5
minutes (exploring phase) - the idea of this being to avoid any
race-conditions of two nodes
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894597#comment-13894597
]
Tommaso Teofili commented on SLING-3352:
bq. So either do it the Sling way - or do
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894598#comment-13894598
]
Tommaso Teofili commented on SLING-3352:
bq. So either do it the Sling way - or do
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-3352:
---
Comment: was deleted
(was: bq. So either do it the Sling way - or do it the JCR way which is
Hi,
some ideas regarding the cluster detection:
* When a cluster node comes up, it writes it's intial I am here
annoucement to the repo.
* The node then comes to the listing mode, in which he listens if there's
any pong or if a new ping comes in, but here it doesn't write any cluster
heartbeat
I think this is basically what I proposed - except that I would be careful
to handle race-conditions with
startups/cluster-delays/observation-threading and thus propose to have a
period of a few minutes in which it assumes to be in a cluster, and only
afterwards switch back if that's not the case.
Hi,
Our recent builds [1] all hang at
org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest - I
don't have time to look right now, but if someone made changes in that
area recently please have a look.
-Bertrand
[1] http://ci.apache.org/builders/sling-trunk
If 1) and 2) are easily doable, I would start with them and see where it
leads us
Regards
Carsten
2014-02-07 16:04 GMT+01:00 Stefan Egli e...@adobe.com:
I think this is basically what I proposed - except that I would be careful
to handle race-conditions with
[
https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-2393:
-
Attachment: SLING-2393.patch
Attached a patch for the documentation.
Update
[
https://issues.apache.org/jira/browse/SLING-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-3320:
---
Component/s: Scripting
Affects Version/s: Scripting Core 2.0.24
Fix
[
https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-2393:
---
Component/s: (was: Servlets)
Documentation
Affects
[
https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-2393.
Resolution: Fixed
Patch applied in http://svn.apache.org/r1565846 , thanks!
The changes
44 matches
Mail list logo
