Hi Dan,
did you try both with Karaf 2.2.x and 2.3.x ?
did you see differences in the behavior ?
Regards
JB
On 01/16/2013 09:17 PM, Dan Tran wrote:
Hi I have a service's PreDestroy method which requires a service from
other bundle during shutdown. However at shutdown time, blueprint make
the re
Hi JB,
I only try 2.3, my new work does not work with 2.2
what is osgi/karaf shutdown sequencing flow? like it would shutdown
all bundles with the same start- level in the order from high to low ?
Thanks
-D
On Wed, Jan 16, 2013 at 12:18 PM, Jean-Baptiste Onofré
wrote:
> Hi Dan,
>
> did you
I fix a bunch of problems with blueprint shutting down recently, so could
you try with a recent blueprint snapshot and see if that helps ?
For now, blueprint bundles are shut down roughly according to their start
level. THere's something in blueprint which is supposed to better use the
bundle ser
Actually, I've raised and fixed
https://issues.apache.org/jira/browse/ARIES-1004
Can you see if the latest snapshots works better for you ?
On Fri, Jan 18, 2013 at 8:26 AM, Guillaume Nodet wrote:
> I fix a bunch of problems with blueprint shutting down recently, so could
> you try with a recent
cool, I will try to build my own version of karaf 2.3.1 snapshot to aries 1.0.2
Thanks
-Dan
On Fri, Jan 18, 2013 at 12:35 AM, Guillaume Nodet wrote:
> Actually, I've raised and fixed
> https://issues.apache.org/jira/browse/ARIES-1004
> Can you see if the latest snapshots works better for you ?
would it be possible to have aries blueprint 1.0.2-snashot deployed?
apache snapshot at
https://repository.apache.org/content/repositories/snapshots/org/apache/aries/blueprint/org.apache.aries.blueprint.core/1.0.2-SNAPSHOT/
is quite old
Thanks
-D
On Fri, Jan 18, 2013 at 9:09 AM, Dan Tran wrote
I checkout the blueprint-core from trunk, which is currently at
1.1.0-SNAPSHOT, it it right? ) and build with apache-karaf
2.3.1-snapshot
upon startup with karaf.bat i got the following stderr
ERROR: Bundle org.apache.aries.blueprint.cm [13] Error starting
mvn:org.apache.aries.blueprint/org.apach
You also need blueprint-cm in version 1.0.1-SNAPSHOT. The version-range
for blueprint-core has been increased there. That's all I had to do.
blueprint-core-1.1.0-SNAPSHOT and blueprint-cm-1.0.1-SNAPSHOT
kind regards,
christoph
On 2013-01-18 20:34, Dan Tran wrote:
I checkout the blueprint-cor
I now have my apache karaf 2.3.1-snapshot to pickup blueprint-core
1.1.0-SNAPSHOT and blueprint-cm 1.0.1-SNAPSHOT
my karaf.bat now hangs at startup
ERROR: Bundle org.apache.aries.blueprint.cm [8] Error starting
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.1-SNAPSHOT
(org.osgi.
Hi Dan,
yes, we are working on the Aries update (to fix the Blueprint issues).
I submitted a patch about to Aries, I gonna check if a new SNAPSHOT has
been deployed (at Aries) including the patch.
I keep you posted.
Regards
JB
On 01/18/2013 11:17 PM, Dan Tran wrote:
I now have my apache ka
also apache jenkens job for aries build also failing
https://builds.apache.org/job/AriesWithSnapshotDependencies/339/console
-D
On Fri, Jan 18, 2013 at 2:17 PM, Dan Tran wrote:
> I now have my apache karaf 2.3.1-snapshot to pickup blueprint-core
> 1.1.0-SNAPSHOT and blueprint-cm 1.0.1-SNAPSHOT
Thanks JB
-D
On Fri, Jan 18, 2013 at 2:19 PM, Jean-Baptiste Onofré wrote:
> Hi Dan,
>
> yes, we are working on the Aries update (to fix the Blueprint issues).
>
> I submitted a patch about to Aries, I gonna check if a new SNAPSHOT has been
> deployed (at Aries) including the patch.
>
> I keep yo
I am testing with the latest apache-karaf-2.3.1-SNAPSHOT with latest
aries blueprint. and still see this issue
where one of my blueprint's destroy method needs a service from
another bundle, however, that bundle's service is not longer
available. Is it bug from latest blueprint? Looks like bluepr
In 2.3.0, this issue is intermittent, I was able to twist start level,
and luckily it disappears. In 2.3.1-SNAPSHOT, it consistently happen,
In a way this is a good news since It is always reproducible.
-D
On Fri, Feb 8, 2013 at 1:52 PM, Dan Tran wrote:
> I am testing with the latest apache-kar
May be an upgrade to felix 4.2 is needed?
On Mon, Feb 11, 2013 at 8:56 AM, Dan Tran wrote:
> In 2.3.0, this issue is intermittent, I was able to twist start level,
> and luckily it disappears. In 2.3.1-SNAPSHOT, it consistently happen,
> In a way this is a good news since It is always reproducib
I created a Jira to update to Felix Framework 4.2.0 but only on trunk
and for Karaf 2.4.0.
I'm going to test if it helps for this issue, if so, I will upgrade for
Karaf 2.3.1 as well.
Did you notice this issue with Karaf 2.3.0 as well ?
Thanks
Regards
JB
On 02/17/2013 08:12 AM, Dan Tran wro
this issue also happens in karaf 2.3.0 but it is very intermittent, I
am able to play with start level, and with some luck, the problem went
away.
Only with 2.3.1-snapshot the issue is very repeatable.
I am going to build 2.3.1-snapshot with filix 4.2.0 to see if it helps.
for me both 2.3.0 and
It sounds like a bug in Aries Blueprint. Let me try to reproduce with a
simple test case.
Regards
JB
On 02/17/2013 08:21 AM, Dan Tran wrote:
this issue also happens in karaf 2.3.0 but it is very intermittent, I
am able to play with start level, and with some luck, the problem went
away.
Only
karf-2.3.1-snapshot with felix 4.2.0 does not help either.
Thanks your for looking into this issue
-D
On Sat, Feb 16, 2013 at 11:40 PM, Jean-Baptiste Onofré
wrote:
> It sounds like a bug in Aries Blueprint. Let me try to reproduce with a
> simple test case.
>
> Regards
> JB
>
>
> On 02/17/2013
Could you build something that we can reproduce ?
Ot at least give more details about what happens (services, start level,
etc..) ?
I've done an enhancement in blueprint so that when the extender detects
that the framework is stopping, it will preemptively shutdown all blueprint
containers.
So is
It my case, i have bundle with higher start level trying to access
service from lower start level at shutdown time ( ie blueprint
destroy-method ), it seems like the lower blueprint bundle service get
removed early, even thou the bundle is not stopped yet.
I will create a couple of simple of bundl
I am able to produce the issue with a couple of simple bundles.
However, setting
org.apache.aries.blueprint.preemptiveShutdown=false
at etc/config.properties
does not help.
For my case now, I currently swallow the exception. But I still think
the blueprint service should not disappear when i
It works!!!
I replace a latest copy of blueprint.core-1.1.1-SNAPSHOT at apache
jenkins and replaced the one at my 2.3.1 karaf ( ie
blueprint.core-1.1.0 )
Thanks
-D
On Thu, Mar 7, 2013 at 6:27 AM, Guillaume Nodet wrote:
> Dan, you may want to try building an aries snapshot of blueprint-core and
But the latest snapshot at apache snapshot repo does not have your change
Please please, help to push a new snapshot
Thanks
On Thu, Mar 7, 2013 at 8:13 AM, Dan Tran wrote:
> It works!!!
>
> I replace a latest copy of blueprint.core-1.1.1-SNAPSHOT at apache
> jenkins and replaced the one at my 2
Karaf 4.0.3 is not stable and where we need to investigate?
--
View this message in context:
http://karaf.922171.n3.nabble.com/Orderly-shutting-down-services-tp4027336p4045447.html
Sent from the Karaf - User mailing list archive at Nabble.com.
vetalok,
> Can one bundle that fails trigger whole framework to stop?
If it fails hard enough, yes. In fact even if it calls System.exit() ...
Suggest you first investigate this as a general Java-application-crashes
problem, e.g. collect and analyse heap dumps (hprof files), run whole
process i
26 matches
Mail list logo