You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Gert Vanthienen <ge...@gmail.com> on 2011/12/15 22:21:17 UTC
[VOTE] Release ServiceMix 4.4.0 (take 2)
L.S.,
I've uploaded a release for ServiceMix 4.4.0 to
https://repository.apache.org/content/repositories/orgapacheservicemix-348
An overview of issues fixed in this release can be found in JIRA at
https://issues.apache.org/jira/browse/SMX4/fixforversion/12315742
The scm tag is available on
http://svn.apache.org/repos/asf/servicemix/smx4/features/tags/features-4.4.0/
As part of this release build, we also built new releases of utils,
components, servicemix 3, nmr and archetypes.
servicemix-utils 1.5.0
* JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12316098
* Tag:
http://svn.apache.org/repos/asf/servicemix/utils/tags/servicemix-utils-1.5.0/
* Staging repo:
https://repository.apache.org/content/repositories/orgapacheservicemix-329/
components 2011.02
* JIRA:
https://issues.apache.org/jira/browse/SMXCOMP/fixforversion/12316111
* Tag:
http://svn.apache.org/repos/asf/servicemix/components/tags/components-2011.02/
* Staging repo:
https://repository.apache.org/content/repositories/orgapacheservicemix-330/
ServiceMix 3.4.0
* JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12315718
* Tag:
http://svn.apache.org/repos/asf/servicemix/smx3/tags/servicemix-3.4.0/
* Staging repo:
https://repository.apache.org/content/repositories/orgapacheservicemix-332/
NMR 1.5.0
* JIRA:
https://issues.apache.org/jira/browse/SMX4NMR/fixforversion/12316157
* Tag:
http://svn.apache.org/repos/asf/servicemix/smx4/nmr/tags/nmr-parent-1.5.0/
* Staging repo:
https://repository.apache.org/content/repositories/orgapacheservicemix-337/
Archetypes 2011.02
* JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12317842
* Tag:
https://svn.apache.org/repos/asf/servicemix/archetypes/tags/archetypes-2011.02/
* Staging repo:
https://repository.apache.org/content/repositories/orgapacheservicemix-342/
Please vote to approve these releases:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)
Given the size of this release, this vote will be open for 96 hours.
Thanks for reviewing and voting,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
I'm canceling this vote and will prepare new release builds for components,
servicemix 3 and features.
@Jean-Baptiste - thanks for volunteering to handle the bundles release in
the meanwhile!
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Fri, Dec 16, 2011 at 12:51 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Bundle release is separate from the main SMX release.
>
> I have others bundles to add, I will cut off a new SMX bundles release
> including yours.
>
> Regards
> JB
>
>
> On 12/16/2011 10:01 AM, Charles Moulliard wrote:
>
>> I have added 2 new bundles --> SMX4-1014 and SMX4-1015. Can you add it
>> for the next build please ?
>>
>>
>> On Fri, Dec 16, 2011 at 9:34 AM, Gert Vanthienen
>> <ge...@gmail.com> wrote:
>>
>>> L.S.,
>>>
>>>
>>> If we have to cut a new release for ServiceMix 4.4.0 anyway and have to
>>> restart a new vote, we might as well redo those few other bits as well -
>>> reading through the mails, it looks like there's at least one user
>>> waiting
>>> for that fix so I think we should just do the bit of extra work involved
>>> to
>>> make sure he gets his fix in ServiceMix 3.4.0.
>>>
>>> I would like to propose to take a few more hours to test the current
>>> staged
>>> release first though, just to ensure we don't have to redo these releases
>>> too often. I'll re-release the necessary bits afterwards to ensure we
>>> get
>>> a new release vote going today.
>>>
>>>
>>> Regards,
>>>
>>> Gert Vanthienen
>>> ------------------------
>>> FuseSource
>>> Web: http://fusesource.com
>>> Blog: http://gertvanthienen.**blogspot.com/<http://gertvanthienen.blogspot.com/>
>>>
>>>
>>> On Fri, Dec 16, 2011 at 7:10 AM, Freeman Fang<fr...@gmail.com>**
>>> wrote:
>>>
>>> Hi,
>>>>
>>>> This issue was resolved, tracked by SMX4-1016[1].
>>>> Seems we need cut a new release for SMX4.4.
>>>>
>>>> Also, per the discussion[2] today, I fixed the wrong embedded wss4j lib
>>>> issue in servicemix-cxf-bc-installer.****zip, to pick up it we have to
>>>> re-cut components and servicemix3.4 also.
>>>> NOTES, this issue only affect SMX3.4(it's ok when use
>>>> servicemix-cxf-bc.jar in SMX4.4 as we refer wss4j.jar from cxf
>>>> features.xml), so I'm not so sure it's a show stopper, as JBI is kind of
>>>> deprecated and
>>>> we suggest users try with SMX4.x for a long time and almost all our
>>>> endeavor focus on SMX4.x, anyway community will make this decision.
>>>>
>>>> [1]https://issues.apache.org/****jira/browse/SMX4-1016<https://issues.apache.org/**jira/browse/SMX4-1016>
>>>> <https:/**/issues.apache.org/jira/**browse/SMX4-1016<https://issues.apache.org/jira/browse/SMX4-1016>
>>>> >
>>>> [2]http://servicemix.396122.****n5.nabble.com/Re-CXF-TLS-**<http://n5.nabble.com/Re-CXF-TLS-**>
>>>> configuration-td5073601.html<h**ttp://servicemix.396122.n5.**
>>>> nabble.com/Re-CXF-TLS-**configuration-td5073601.html<http://servicemix.396122.n5.nabble.com/Re-CXF-TLS-configuration-td5073601.html>
>>>> >
>>>>
>>>> Best Regards
>>>> Freeman
>>>>
>>>>
>>>> On 2011-12-16, at 下午1:08, Johan Edstrom wrote:
>>>>
>>>> Perfect!
>>>>
>>>>>
>>>>> I think that'll take care of most issues, I tested all the cxf samples
>>>>> +
>>>>> a bunch of blueprint NS handling things.
>>>>>
>>>>> /je
>>>>>
>>>>> On Dec 15, 2011, at 10:01 PM, Freeman-2 wrote:
>>>>>
>>>>> Hi Johan,
>>>>>
>>>>>>
>>>>>> Thanks for this info, I was testing apache-servicemix-jbi-4.4.0 kit,
>>>>>> that's
>>>>>> why I can't reproduce.
>>>>>> Now I can see this problem with full distro, the problem is that the
>>>>>> war
>>>>>> feature which installed with example-cxf-* cause this problem, we can
>>>>>> add
>>>>>> war to the featuresBoot for full and the regular distro also to fix
>>>>>> it.
>>>>>>
>>>>>> Regards
>>>>>> Freeman
>>>>>>
>>>>>> --
>>>>>> View this message in context: http://servicemix.396122.n5.**
>>>>>> nabble.com/VOTE-Release-****ServiceMix-4-4-0-take-2-**<http://nabble.com/VOTE-Release-**ServiceMix-4-4-0-take-2-**>
>>>>>> tp5078716p5079320.html<http://**servicemix.396122.n5.nabble.**
>>>>>> com/VOTE-Release-ServiceMix-4-**4-0-take-2-tp5078716p5079320.**html<http://servicemix.396122.n5.nabble.com/VOTE-Release-ServiceMix-4-4-0-take-2-tp5078716p5079320.html>
>>>>>> >
>>>>>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------****---------------
>>>> Freeman Fang
>>>>
>>>> FuseSource
>>>> Email:ffang@fusesource.com
>>>> Web: fusesource.com
>>>> Twitter: freemanfang
>>>> Blog: http://freemanfang.blogspot.****com<http://freemanfang.**
>>>> blogspot.com <http://freemanfang.blogspot.com>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Bundle release is separate from the main SMX release.
I have others bundles to add, I will cut off a new SMX bundles release
including yours.
Regards
JB
On 12/16/2011 10:01 AM, Charles Moulliard wrote:
> I have added 2 new bundles --> SMX4-1014 and SMX4-1015. Can you add it
> for the next build please ?
>
>
> On Fri, Dec 16, 2011 at 9:34 AM, Gert Vanthienen
> <ge...@gmail.com> wrote:
>> L.S.,
>>
>>
>> If we have to cut a new release for ServiceMix 4.4.0 anyway and have to
>> restart a new vote, we might as well redo those few other bits as well -
>> reading through the mails, it looks like there's at least one user waiting
>> for that fix so I think we should just do the bit of extra work involved to
>> make sure he gets his fix in ServiceMix 3.4.0.
>>
>> I would like to propose to take a few more hours to test the current staged
>> release first though, just to ensure we don't have to redo these releases
>> too often. I'll re-release the necessary bits afterwards to ensure we get
>> a new release vote going today.
>>
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> FuseSource
>> Web: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>> On Fri, Dec 16, 2011 at 7:10 AM, Freeman Fang<fr...@gmail.com>wrote:
>>
>>> Hi,
>>>
>>> This issue was resolved, tracked by SMX4-1016[1].
>>> Seems we need cut a new release for SMX4.4.
>>>
>>> Also, per the discussion[2] today, I fixed the wrong embedded wss4j lib
>>> issue in servicemix-cxf-bc-installer.**zip, to pick up it we have to
>>> re-cut components and servicemix3.4 also.
>>> NOTES, this issue only affect SMX3.4(it's ok when use
>>> servicemix-cxf-bc.jar in SMX4.4 as we refer wss4j.jar from cxf
>>> features.xml), so I'm not so sure it's a show stopper, as JBI is kind of
>>> deprecated and
>>> we suggest users try with SMX4.x for a long time and almost all our
>>> endeavor focus on SMX4.x, anyway community will make this decision.
>>>
>>> [1]https://issues.apache.org/**jira/browse/SMX4-1016<https://issues.apache.org/jira/browse/SMX4-1016>
>>> [2]http://servicemix.396122.**n5.nabble.com/Re-CXF-TLS-**
>>> configuration-td5073601.html<http://servicemix.396122.n5.nabble.com/Re-CXF-TLS-configuration-td5073601.html>
>>>
>>> Best Regards
>>> Freeman
>>>
>>>
>>> On 2011-12-16, at 下午1:08, Johan Edstrom wrote:
>>>
>>> Perfect!
>>>>
>>>> I think that'll take care of most issues, I tested all the cxf samples +
>>>> a bunch of blueprint NS handling things.
>>>>
>>>> /je
>>>>
>>>> On Dec 15, 2011, at 10:01 PM, Freeman-2 wrote:
>>>>
>>>> Hi Johan,
>>>>>
>>>>> Thanks for this info, I was testing apache-servicemix-jbi-4.4.0 kit,
>>>>> that's
>>>>> why I can't reproduce.
>>>>> Now I can see this problem with full distro, the problem is that the war
>>>>> feature which installed with example-cxf-* cause this problem, we can add
>>>>> war to the featuresBoot for full and the regular distro also to fix it.
>>>>>
>>>>> Regards
>>>>> Freeman
>>>>>
>>>>> --
>>>>> View this message in context: http://servicemix.396122.n5.**
>>>>> nabble.com/VOTE-Release-**ServiceMix-4-4-0-take-2-**
>>>>> tp5078716p5079320.html<http://servicemix.396122.n5.nabble.com/VOTE-Release-ServiceMix-4-4-0-take-2-tp5078716p5079320.html>
>>>>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>>>>>
>>>>
>>>>
>>> ------------------------------**---------------
>>> Freeman Fang
>>>
>>> FuseSource
>>> Email:ffang@fusesource.com
>>> Web: fusesource.com
>>> Twitter: freemanfang
>>> Blog: http://freemanfang.blogspot.**com<http://freemanfang.blogspot.com>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Charles Moulliard <cm...@gmail.com>.
I have added 2 new bundles --> SMX4-1014 and SMX4-1015. Can you add it
for the next build please ?
On Fri, Dec 16, 2011 at 9:34 AM, Gert Vanthienen
<ge...@gmail.com> wrote:
> L.S.,
>
>
> If we have to cut a new release for ServiceMix 4.4.0 anyway and have to
> restart a new vote, we might as well redo those few other bits as well -
> reading through the mails, it looks like there's at least one user waiting
> for that fix so I think we should just do the bit of extra work involved to
> make sure he gets his fix in ServiceMix 3.4.0.
>
> I would like to propose to take a few more hours to test the current staged
> release first though, just to ensure we don't have to redo these releases
> too often. I'll re-release the necessary bits afterwards to ensure we get
> a new release vote going today.
>
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> FuseSource
> Web: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
> On Fri, Dec 16, 2011 at 7:10 AM, Freeman Fang <fr...@gmail.com>wrote:
>
>> Hi,
>>
>> This issue was resolved, tracked by SMX4-1016[1].
>> Seems we need cut a new release for SMX4.4.
>>
>> Also, per the discussion[2] today, I fixed the wrong embedded wss4j lib
>> issue in servicemix-cxf-bc-installer.**zip, to pick up it we have to
>> re-cut components and servicemix3.4 also.
>> NOTES, this issue only affect SMX3.4(it's ok when use
>> servicemix-cxf-bc.jar in SMX4.4 as we refer wss4j.jar from cxf
>> features.xml), so I'm not so sure it's a show stopper, as JBI is kind of
>> deprecated and
>> we suggest users try with SMX4.x for a long time and almost all our
>> endeavor focus on SMX4.x, anyway community will make this decision.
>>
>> [1]https://issues.apache.org/**jira/browse/SMX4-1016<https://issues.apache.org/jira/browse/SMX4-1016>
>> [2]http://servicemix.396122.**n5.nabble.com/Re-CXF-TLS-**
>> configuration-td5073601.html<http://servicemix.396122.n5.nabble.com/Re-CXF-TLS-configuration-td5073601.html>
>>
>> Best Regards
>> Freeman
>>
>>
>> On 2011-12-16, at 下午1:08, Johan Edstrom wrote:
>>
>> Perfect!
>>>
>>> I think that'll take care of most issues, I tested all the cxf samples +
>>> a bunch of blueprint NS handling things.
>>>
>>> /je
>>>
>>> On Dec 15, 2011, at 10:01 PM, Freeman-2 wrote:
>>>
>>> Hi Johan,
>>>>
>>>> Thanks for this info, I was testing apache-servicemix-jbi-4.4.0 kit,
>>>> that's
>>>> why I can't reproduce.
>>>> Now I can see this problem with full distro, the problem is that the war
>>>> feature which installed with example-cxf-* cause this problem, we can add
>>>> war to the featuresBoot for full and the regular distro also to fix it.
>>>>
>>>> Regards
>>>> Freeman
>>>>
>>>> --
>>>> View this message in context: http://servicemix.396122.n5.**
>>>> nabble.com/VOTE-Release-**ServiceMix-4-4-0-take-2-**
>>>> tp5078716p5079320.html<http://servicemix.396122.n5.nabble.com/VOTE-Release-ServiceMix-4-4-0-take-2-tp5078716p5079320.html>
>>>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>>>>
>>>
>>>
>> ------------------------------**---------------
>> Freeman Fang
>>
>> FuseSource
>> Email:ffang@fusesource.com
>> Web: fusesource.com
>> Twitter: freemanfang
>> Blog: http://freemanfang.blogspot.**com <http://freemanfang.blogspot.com>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
If we have to cut a new release for ServiceMix 4.4.0 anyway and have to
restart a new vote, we might as well redo those few other bits as well -
reading through the mails, it looks like there's at least one user waiting
for that fix so I think we should just do the bit of extra work involved to
make sure he gets his fix in ServiceMix 3.4.0.
I would like to propose to take a few more hours to test the current staged
release first though, just to ensure we don't have to redo these releases
too often. I'll re-release the necessary bits afterwards to ensure we get
a new release vote going today.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Fri, Dec 16, 2011 at 7:10 AM, Freeman Fang <fr...@gmail.com>wrote:
> Hi,
>
> This issue was resolved, tracked by SMX4-1016[1].
> Seems we need cut a new release for SMX4.4.
>
> Also, per the discussion[2] today, I fixed the wrong embedded wss4j lib
> issue in servicemix-cxf-bc-installer.**zip, to pick up it we have to
> re-cut components and servicemix3.4 also.
> NOTES, this issue only affect SMX3.4(it's ok when use
> servicemix-cxf-bc.jar in SMX4.4 as we refer wss4j.jar from cxf
> features.xml), so I'm not so sure it's a show stopper, as JBI is kind of
> deprecated and
> we suggest users try with SMX4.x for a long time and almost all our
> endeavor focus on SMX4.x, anyway community will make this decision.
>
> [1]https://issues.apache.org/**jira/browse/SMX4-1016<https://issues.apache.org/jira/browse/SMX4-1016>
> [2]http://servicemix.396122.**n5.nabble.com/Re-CXF-TLS-**
> configuration-td5073601.html<http://servicemix.396122.n5.nabble.com/Re-CXF-TLS-configuration-td5073601.html>
>
> Best Regards
> Freeman
>
>
> On 2011-12-16, at 下午1:08, Johan Edstrom wrote:
>
> Perfect!
>>
>> I think that'll take care of most issues, I tested all the cxf samples +
>> a bunch of blueprint NS handling things.
>>
>> /je
>>
>> On Dec 15, 2011, at 10:01 PM, Freeman-2 wrote:
>>
>> Hi Johan,
>>>
>>> Thanks for this info, I was testing apache-servicemix-jbi-4.4.0 kit,
>>> that's
>>> why I can't reproduce.
>>> Now I can see this problem with full distro, the problem is that the war
>>> feature which installed with example-cxf-* cause this problem, we can add
>>> war to the featuresBoot for full and the regular distro also to fix it.
>>>
>>> Regards
>>> Freeman
>>>
>>> --
>>> View this message in context: http://servicemix.396122.n5.**
>>> nabble.com/VOTE-Release-**ServiceMix-4-4-0-take-2-**
>>> tp5078716p5079320.html<http://servicemix.396122.n5.nabble.com/VOTE-Release-ServiceMix-4-4-0-take-2-tp5078716p5079320.html>
>>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>>>
>>
>>
> ------------------------------**---------------
> Freeman Fang
>
> FuseSource
> Email:ffang@fusesource.com
> Web: fusesource.com
> Twitter: freemanfang
> Blog: http://freemanfang.blogspot.**com <http://freemanfang.blogspot.com>
>
>
>
>
>
>
>
>
>
>
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
This issue was resolved, tracked by SMX4-1016[1].
Seems we need cut a new release for SMX4.4.
Also, per the discussion[2] today, I fixed the wrong embedded wss4j
lib issue in servicemix-cxf-bc-installer.zip, to pick up it we have
to re-cut components and servicemix3.4 also.
NOTES, this issue only affect SMX3.4(it's ok when use servicemix-cxf-
bc.jar in SMX4.4 as we refer wss4j.jar from cxf features.xml), so I'm
not so sure it's a show stopper, as JBI is kind of deprecated and
we suggest users try with SMX4.x for a long time and almost all our
endeavor focus on SMX4.x, anyway community will make this decision.
[1]https://issues.apache.org/jira/browse/SMX4-1016
[2]http://servicemix.396122.n5.nabble.com/Re-CXF-TLS-configuration-td5073601.html
Best Regards
Freeman
On 2011-12-16, at 下午1:08, Johan Edstrom wrote:
> Perfect!
>
> I think that'll take care of most issues, I tested all the cxf
> samples + a bunch of blueprint NS handling things.
>
> /je
>
> On Dec 15, 2011, at 10:01 PM, Freeman-2 wrote:
>
>> Hi Johan,
>>
>> Thanks for this info, I was testing apache-servicemix-jbi-4.4.0
>> kit, that's
>> why I can't reproduce.
>> Now I can see this problem with full distro, the problem is that
>> the war
>> feature which installed with example-cxf-* cause this problem, we
>> can add
>> war to the featuresBoot for full and the regular distro also to fix
>> it.
>>
>> Regards
>> Freeman
>>
>> --
>> View this message in context: http://servicemix.396122.n5.nabble.com/VOTE-Release-ServiceMix-4-4-0-take-2-tp5078716p5079320.html
>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>
---------------------------------------------
Freeman Fang
FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Johan Edstrom <se...@gmail.com>.
Perfect!
I think that'll take care of most issues, I tested all the cxf samples + a bunch of blueprint NS handling things.
/je
On Dec 15, 2011, at 10:01 PM, Freeman-2 wrote:
> Hi Johan,
>
> Thanks for this info, I was testing apache-servicemix-jbi-4.4.0 kit, that's
> why I can't reproduce.
> Now I can see this problem with full distro, the problem is that the war
> feature which installed with example-cxf-* cause this problem, we can add
> war to the featuresBoot for full and the regular distro also to fix it.
>
> Regards
> Freeman
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/VOTE-Release-ServiceMix-4-4-0-take-2-tp5078716p5079320.html
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Freeman-2 <fr...@gmail.com>.
Hi Johan,
Thanks for this info, I was testing apache-servicemix-jbi-4.4.0 kit, that's
why I can't reproduce.
Now I can see this problem with full distro, the problem is that the war
feature which installed with example-cxf-* cause this problem, we can add
war to the featuresBoot for full and the regular distro also to fix it.
Regards
Freeman
--
View this message in context: http://servicemix.396122.n5.nabble.com/VOTE-Release-ServiceMix-4-4-0-take-2-tp5078716p5079320.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Johan Edstrom <se...@gmail.com>.
These were from a clean build no modifications whatsoever actually,
tried with both the full and the regular distro.
Will try again in the AM, as well as wiping my maven repos.
/je
On Dec 15, 2011, at 7:48 PM, Freeman Fang wrote:
> Hi Johan,
>
> Good catch. My comment inline
> On 2011-12-16, at 上午6:26, Johan Edstrom wrote:
>
>> Noticed these warnings - 2011-12-15 14:59:13,085 | INFO | g.ops4j.pax.web) | JettyServerImpl | ? ? | 111 - org.ops4j.pax.web.pax-web-jetty - 1.0.7 | Pax Web available at [0.0.0.0]:[8181]
>> 2011-12-15 14:59:13,086 | WARN | g.ops4j.pax.web) | NIOSocketConnectorWrapper | ? ? | 111 - org.ops4j.pax.web.pax-web-jetty - 1.0.7 | Connection on port 8181 cannot be open. Reason: Address already in use
> We have an issue[1] to track it and explained there.
>
> [1]https://issues.apache.org/jira/browse/SMX4-1013
>>
>> And
>>
>> 2011-12-15 14:59:11,458 | WARN | rint Extender: 1 | XBeanNamespaceHandler | ? ? | 62 - org.apache.xbean.blueprint - 3.7 | Could not load class: org.apache.activemq.store.journal.JournalPersistenceAdapter due to org/apache/activeio/journal/JournalEventListener
>> 2011-12-15 14:59:11,533 | WARN | rint Extender: 1 | XBeanNamespaceHandler | ? ? | 62 - org.apache.xbean.blueprint - 3.7 | Could not load class: org.apache.activemq.store.journal.JournalPersistenceAdapterFactory due to org/apache/activeio/journal/active/JournalLockedException
>> 2011-12-15 14:59:11,590 | WARN | rint Extender: 1 | XBeanNamespaceHandler | ? ? | 62 - org.apache.xbean.blueprint - 3.7 | Could not load class: org.apache.activemq.store.PersistenceAdapterFactoryBean due to org/apache/activeio/journal/active/JournalLockedException
>>
>> Doubt neither causes any issues whatsoever…
> Just copy what Gert explained before,
> Those warnings indicate that a XBean namespace handler is unavailable,
> probably due to problems in the OSGi metadata and/or the startup order
> on the bundles that hold the namespace handlers. They're harmless
> unless you're planning on using those specific namespaces
>
> So in summary, those XBeanNamespaceHandler WARN log are harmless, but exist here for a long time, I just checked that even SMX4.3 release also has this WARN, I think we can address it after SMX4.4 release, but IMO it's not a show stopper now.
>>
>> And…
>>
>
> These two examples works for me, but given the refreshing output like(when I install those example I didn't see the refresh output)
> Refreshing bundles org.springframework.web (114), org.ops4j.pax.web.pax-web-runtime (113), org.springframework.web.servlet (115), org.ops4j.pax.web.pax-web-jetty (111), org.springframework.beans (66)
>
> I guess you modified featuresBoot of etc/org.apache.karaf.features.cfg(most likely remove some features there), so that when you install example-cxf-osgi feature, there're some
> optional packages for some bundles are available, so that can cause bundle refresh chain-action(if spring-beans get refreshed, that can cause all other bundles which import spring-beans refresh too, and so on), IIRC, there's a known issue for felix that can't handle this case very well(equinox is good in this case), I think that's why you saw those exceptions.
> But if all necessary optional packages are available at very first stage(like in featuresBoot), then you won't see this kind of issue.
>
> Best Regards
> Freeman
>
>> araf@root> features:install examples-cxf-osgi
>> Refreshing bundles org.springframework.web (114), org.ops4j.pax.web.pax-web-runtime (113), org.springframework.web.servlet (115), org.ops4j.pax.web.pax-web-jetty (111), org.springframework.beans (66)
>> ERROR: Bundle org.apache.karaf.deployer.features [39] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService)
>> java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService
>> at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:104)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
>> at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
>> at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
>> at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
>> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
>> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
>> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
>> at org.apache.felix.framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
>> at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
>> at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
>> at org.ops4j.pax.web.service.internal.Activator.createHttpServiceFactory(Activator.java:111)
>> at org.ops4j.pax.web.service.internal.Activator.access$900(Activator.java:70)
>> at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:332)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>> at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)
>> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)
>> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)
>> at org.ops4j.pax.web.service.internal.Activator.start(Activator.java:95)
>> at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
>> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1842)
>> at org.apache.felix.framework.Felix.startBundle(Felix.java:1759)
>> at org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4534)
>> at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3591)
>> at org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:363)
>> at java.lang.Thread.run(Thread.java:680)
>> ERROR: Bundle org.apache.karaf.deployer.features [39] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService)
>> java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService
>> at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:104)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
>> at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
>> at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
>> at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
>> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
>> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
>> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
>> at org.apache.felix.framework.ServiceRegistry.servicePropertiesModified(ServiceRegistry.java:480)
>> at org.apache.felix.framework.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:116)
>> at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:155)
>> at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1160)
>> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
>> at java.lang.Thread.run(Thread.java:680)
>>
>>
>> karaf@root> features:install examples-cxf-wsdl-first-osgi-package
>> Refreshing bundles org.springframework.transaction (93), org.apache.xbean.spring (79), org.apache.servicemix.bundles.jaxb-xjc (120), org.apache.servicemix.bundles.xmlbeans (140)
>> *ERROR* Configuration for org.ops4j.pax.web has already been used for service [org.osgi.service.cm.ManagedService, id=284, bundle=113] and will now also be given to [org.osgi.service.cm.ManagedService, id=372, bundle=113]
>> ERROR: Bundle org.apache.karaf.deployer.features [39] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService)
>> java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService
>> at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:104)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
>> at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
>> at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
>> at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
>> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
>> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
>> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
>> at org.apache.felix.framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
>> at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
>> at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
>> at org.ops4j.pax.web.service.internal.Activator.createHttpServiceFactory(Activator.java:111)
>> at org.ops4j.pax.web.service.internal.Activator.access$900(Activator.java:70)
>> at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:332)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
>> at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
>> at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
>> at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
>> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
>> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
>> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
>> at org.apache.felix.framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
>> at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
>> at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
>> at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:229)
>> at org.ops4j.pax.web.service.jetty.internal.Activator.start(Activator.java:46)
>> at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
>> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1842)
>> at org.apache.felix.framework.Felix.startBundle(Felix.java:1759)
>> at org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4534)
>> at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3591)
>> at org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:363)
>> at java.lang.Thread.run(Thread.java:680)
>> ERROR: Bundle org.apache.karaf.deployer.features [39] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService)
>> java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService
>> at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:104)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
>> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
>> at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
>> at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
>> at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
>> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
>> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
>> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
>> at org.apache.felix.framework.ServiceRegistry.servicePropertiesModified(ServiceRegistry.java:480)
>> at org.apache.felix.framework.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:116)
>> at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:155)
>> at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1160)
>> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
>> at java.lang.Thread.run(Thread.java:680)
>>
>> On Dec 15, 2011, at 2:21 PM, Gert Vanthienen wrote:
>>
>>> L.S.,
>>>
>>>
>>> I've uploaded a release for ServiceMix 4.4.0 to
>>> https://repository.apache.org/content/repositories/orgapacheservicemix-348
>>>
>>> An overview of issues fixed in this release can be found in JIRA at
>>> https://issues.apache.org/jira/browse/SMX4/fixforversion/12315742
>>>
>>> The scm tag is available on
>>>
>>> http://svn.apache.org/repos/asf/servicemix/smx4/features/tags/features-4.4.0/
>>>
>>>
>>> As part of this release build, we also built new releases of utils,
>>> components, servicemix 3, nmr and archetypes.
>>>
>>> servicemix-utils 1.5.0
>>> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12316098
>>> * Tag:
>>> http://svn.apache.org/repos/asf/servicemix/utils/tags/servicemix-utils-1.5.0/
>>> * Staging repo:
>>> https://repository.apache.org/content/repositories/orgapacheservicemix-329/
>>>
>>> components 2011.02
>>> * JIRA:
>>> https://issues.apache.org/jira/browse/SMXCOMP/fixforversion/12316111
>>> * Tag:
>>> http://svn.apache.org/repos/asf/servicemix/components/tags/components-2011.02/
>>> * Staging repo:
>>> https://repository.apache.org/content/repositories/orgapacheservicemix-330/
>>>
>>> ServiceMix 3.4.0
>>> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12315718
>>> * Tag:
>>> http://svn.apache.org/repos/asf/servicemix/smx3/tags/servicemix-3.4.0/
>>> * Staging repo:
>>> https://repository.apache.org/content/repositories/orgapacheservicemix-332/
>>>
>>> NMR 1.5.0
>>> * JIRA:
>>> https://issues.apache.org/jira/browse/SMX4NMR/fixforversion/12316157
>>> * Tag:
>>> http://svn.apache.org/repos/asf/servicemix/smx4/nmr/tags/nmr-parent-1.5.0/
>>> * Staging repo:
>>> https://repository.apache.org/content/repositories/orgapacheservicemix-337/
>>>
>>> Archetypes 2011.02
>>> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12317842
>>> * Tag:
>>> https://svn.apache.org/repos/asf/servicemix/archetypes/tags/archetypes-2011.02/
>>> * Staging repo:
>>> https://repository.apache.org/content/repositories/orgapacheservicemix-342/
>>>
>>>
>>>
>>> Please vote to approve these releases:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Veto the release (please provide specific comments)
>>>
>>> Given the size of this release, this vote will be open for 96 hours.
>>>
>>>
>>> Thanks for reviewing and voting,
>>>
>>> Gert Vanthienen
>>> ------------------------
>>> FuseSource
>>> Web: http://fusesource.com
>>> Blog: http://gertvanthienen.blogspot.com/
>>
>
> ---------------------------------------------
> Freeman Fang
>
> FuseSource
> Email:ffang@fusesource.com
> Web: fusesource.com
> Twitter: freemanfang
> Blog: http://freemanfang.blogspot.com
>
>
>
>
>
>
>
>
>
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Freeman Fang <fr...@gmail.com>.
Hi Johan,
Good catch. My comment inline
On 2011-12-16, at 上午6:26, Johan Edstrom wrote:
> Noticed these warnings - 2011-12-15 14:59:13,085 | INFO |
> g.ops4j.pax.web) | JettyServerImpl
> | ? ? | 111 -
> org.ops4j.pax.web.pax-web-jetty - 1.0.7 | Pax Web available at
> [0.0.0.0]:[8181]
> 2011-12-15 14:59:13,086 | WARN | g.ops4j.pax.web) |
> NIOSocketConnectorWrapper
> | ? ? | 111 -
> org.ops4j.pax.web.pax-web-jetty - 1.0.7 | Connection on port 8181
> cannot be open. Reason: Address already in use
We have an issue[1] to track it and explained there.
[1]https://issues.apache.org/jira/browse/SMX4-1013
>
> And
>
> 2011-12-15 14:59:11,458 | WARN | rint Extender: 1 |
> XBeanNamespaceHandler
> | ? ? | 62 -
> org.apache.xbean.blueprint - 3.7 | Could not load class:
> org.apache.activemq.store.journal.JournalPersistenceAdapter due to
> org/apache/activeio/journal/JournalEventListener
> 2011-12-15 14:59:11,533 | WARN | rint Extender: 1 |
> XBeanNamespaceHandler
> | ? ? | 62 -
> org.apache.xbean.blueprint - 3.7 | Could not load class:
> org.apache.activemq.store.journal.JournalPersistenceAdapterFactory
> due to org/apache/activeio/journal/active/JournalLockedException
> 2011-12-15 14:59:11,590 | WARN | rint Extender: 1 |
> XBeanNamespaceHandler
> | ? ? | 62 -
> org.apache.xbean.blueprint - 3.7 | Could not load class:
> org.apache.activemq.store.PersistenceAdapterFactoryBean due to org/
> apache/activeio/journal/active/JournalLockedException
>
> Doubt neither causes any issues whatsoever…
Just copy what Gert explained before,
Those warnings indicate that a XBean namespace handler is unavailable,
probably due to problems in the OSGi metadata and/or the startup order
on the bundles that hold the namespace handlers. They're harmless
unless you're planning on using those specific namespaces
So in summary, those XBeanNamespaceHandler WARN log are harmless, but
exist here for a long time, I just checked that even SMX4.3 release
also has this WARN, I think we can address it after SMX4.4 release,
but IMO it's not a show stopper now.
>
> And…
>
These two examples works for me, but given the refreshing output
like(when I install those example I didn't see the refresh output)
Refreshing bundles org.springframework.web (114),
org.ops4j.pax.web.pax-web-runtime (113),
org.springframework.web.servlet (115), org.ops4j.pax.web.pax-web-jetty
(111), org.springframework.beans (66)
I guess you modified featuresBoot of etc/
org.apache.karaf.features.cfg(most likely remove some features
there), so that when you install example-cxf-osgi feature, there're
some
optional packages for some bundles are available, so that can cause
bundle refresh chain-action(if spring-beans get refreshed, that can
cause all other bundles which import spring-beans refresh too, and so
on), IIRC, there's a known issue for felix that can't handle this
case very well(equinox is good in this case), I think that's why you
saw those exceptions.
But if all necessary optional packages are available at very first
stage(like in featuresBoot), then you won't see this kind of issue.
Best Regards
Freeman
> araf@root> features:install examples-cxf-osgi
> Refreshing bundles org.springframework.web (114),
> org.ops4j.pax.web.pax-web-runtime (113),
> org.springframework.web.servlet (115), org.ops4j.pax.web.pax-web-
> jetty (111), org.springframework.beans (66)
> ERROR: Bundle org.apache.karaf.deployer.features [39]
> EventDispatcher: Error during dispatch.
> (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy
> cannot be cast to org.osgi.service.http.HttpService)
> java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy
> cannot be cast to org.osgi.service.http.HttpService
> at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService
> (HttpServiceTracker.java:104)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.customizerAdding(ServiceTracker.java:896)
> at
> org
> .osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:
> 261)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:
> 233)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.serviceChanged(ServiceTracker.java:840)
> at
> org
> .apache
> .felix
> .framework
> .util
> .EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:
> 871)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
> at
> org
> .apache
> .felix
> .framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
> at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
> at
> org
> .apache
> .felix
> .framework.BundleContextImpl.registerService(BundleContextImpl.java:
> 251)
> at org.ops4j.pax.web.service.internal.Activator.createHttpServiceFactory
> (Activator.java:111)
> at org.ops4j.pax.web.service.internal.Activator.access
> $900(Activator.java:70)
> at org.ops4j.pax.web.service.internal.Activator
> $DynamicsServiceTrackerCustomizer.addingService(Activator.java:332)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.customizerAdding(ServiceTracker.java:896)
> at
> org
> .osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:
> 261)
> at
> org
> .osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:
> 184)
> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)
> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)
> at
> org.ops4j.pax.web.service.internal.Activator.start(Activator.java:95)
> at
> org
> .apache
> .felix.framework.util.SecureAction.startActivator(SecureAction.java:
> 629)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1842)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1759)
> at org.apache.felix.framework.Felix
> $RefreshHelper.restart(Felix.java:4534)
> at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3591)
> at
> org
> .apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:
> 363)
> at java.lang.Thread.run(Thread.java:680)
> ERROR: Bundle org.apache.karaf.deployer.features [39]
> EventDispatcher: Error during dispatch.
> (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy
> cannot be cast to org.osgi.service.http.HttpService)
> java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy
> cannot be cast to org.osgi.service.http.HttpService
> at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService
> (HttpServiceTracker.java:104)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.customizerAdding(ServiceTracker.java:896)
> at
> org
> .osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:
> 261)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:
> 233)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.serviceChanged(ServiceTracker.java:840)
> at
> org
> .apache
> .felix
> .framework
> .util
> .EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:
> 871)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
> at
> org
> .apache
> .felix
> .framework
> .ServiceRegistry.servicePropertiesModified(ServiceRegistry.java:480)
> at
> org
> .apache
> .felix
> .framework
> .ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:
> 116)
> at org.ops4j.pax.web.service.internal.Activator
> $2.updated(Activator.java:155)
> at org.apache.felix.cm.impl.ConfigurationManager
> $ManagedServiceUpdate.run(ConfigurationManager.java:1160)
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
> at java.lang.Thread.run(Thread.java:680)
>
>
> karaf@root> features:install examples-cxf-wsdl-first-osgi-package
> Refreshing bundles org.springframework.transaction (93),
> org.apache.xbean.spring (79), org.apache.servicemix.bundles.jaxb-xjc
> (120), org.apache.servicemix.bundles.xmlbeans (140)
> *ERROR* Configuration for org.ops4j.pax.web has already been used
> for service [org.osgi.service.cm.ManagedService, id=284, bundle=113]
> and will now also be given to [org.osgi.service.cm.ManagedService,
> id=372, bundle=113]
> ERROR: Bundle org.apache.karaf.deployer.features [39]
> EventDispatcher: Error during dispatch.
> (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy
> cannot be cast to org.osgi.service.http.HttpService)
> java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy
> cannot be cast to org.osgi.service.http.HttpService
> at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService
> (HttpServiceTracker.java:104)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.customizerAdding(ServiceTracker.java:896)
> at
> org
> .osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:
> 261)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:
> 233)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.serviceChanged(ServiceTracker.java:840)
> at
> org
> .apache
> .felix
> .framework
> .util
> .EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:
> 871)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
> at
> org
> .apache
> .felix
> .framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
> at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
> at
> org
> .apache
> .felix
> .framework.BundleContextImpl.registerService(BundleContextImpl.java:
> 251)
> at org.ops4j.pax.web.service.internal.Activator.createHttpServiceFactory
> (Activator.java:111)
> at org.ops4j.pax.web.service.internal.Activator.access
> $900(Activator.java:70)
> at org.ops4j.pax.web.service.internal.Activator
> $DynamicsServiceTrackerCustomizer.addingService(Activator.java:332)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.customizerAdding(ServiceTracker.java:896)
> at
> org
> .osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:
> 261)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:
> 233)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.serviceChanged(ServiceTracker.java:840)
> at
> org
> .apache
> .felix
> .framework
> .util
> .EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:
> 871)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
> at
> org
> .apache
> .felix
> .framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
> at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
> at
> org
> .apache
> .felix
> .framework.BundleContextImpl.registerService(BundleContextImpl.java:
> 251)
> at
> org
> .apache
> .felix
> .framework.BundleContextImpl.registerService(BundleContextImpl.java:
> 229)
> at
> org
> .ops4j.pax.web.service.jetty.internal.Activator.start(Activator.java:
> 46)
> at
> org
> .apache
> .felix.framework.util.SecureAction.startActivator(SecureAction.java:
> 629)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1842)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1759)
> at org.apache.felix.framework.Felix
> $RefreshHelper.restart(Felix.java:4534)
> at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3591)
> at
> org
> .apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:
> 363)
> at java.lang.Thread.run(Thread.java:680)
> ERROR: Bundle org.apache.karaf.deployer.features [39]
> EventDispatcher: Error during dispatch.
> (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy
> cannot be cast to org.osgi.service.http.HttpService)
> java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy
> cannot be cast to org.osgi.service.http.HttpService
> at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService
> (HttpServiceTracker.java:104)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.customizerAdding(ServiceTracker.java:896)
> at
> org
> .osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:
> 261)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:
> 233)
> at org.osgi.util.tracker.ServiceTracker
> $Tracked.serviceChanged(ServiceTracker.java:840)
> at
> org
> .apache
> .felix
> .framework
> .util
> .EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:
> 871)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
> at
> org
> .apache
> .felix
> .framework
> .util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
> at org.apache.felix.framework.Felix.access$000(Felix.java:80)
> at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
> at
> org
> .apache
> .felix
> .framework
> .ServiceRegistry.servicePropertiesModified(ServiceRegistry.java:480)
> at
> org
> .apache
> .felix
> .framework
> .ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:
> 116)
> at org.ops4j.pax.web.service.internal.Activator
> $2.updated(Activator.java:155)
> at org.apache.felix.cm.impl.ConfigurationManager
> $ManagedServiceUpdate.run(ConfigurationManager.java:1160)
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
> at java.lang.Thread.run(Thread.java:680)
>
> On Dec 15, 2011, at 2:21 PM, Gert Vanthienen wrote:
>
>> L.S.,
>>
>>
>> I've uploaded a release for ServiceMix 4.4.0 to
>> https://repository.apache.org/content/repositories/orgapacheservicemix-348
>>
>> An overview of issues fixed in this release can be found in JIRA at
>> https://issues.apache.org/jira/browse/SMX4/fixforversion/12315742
>>
>> The scm tag is available on
>>
>> http://svn.apache.org/repos/asf/servicemix/smx4/features/tags/features-4.4.0/
>>
>>
>> As part of this release build, we also built new releases of utils,
>> components, servicemix 3, nmr and archetypes.
>>
>> servicemix-utils 1.5.0
>> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12316098
>> * Tag:
>> http://svn.apache.org/repos/asf/servicemix/utils/tags/servicemix-utils-1.5.0/
>> * Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheservicemix-329/
>>
>> components 2011.02
>> * JIRA:
>> https://issues.apache.org/jira/browse/SMXCOMP/fixforversion/12316111
>> * Tag:
>> http://svn.apache.org/repos/asf/servicemix/components/tags/components-2011.02/
>> * Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheservicemix-330/
>>
>> ServiceMix 3.4.0
>> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12315718
>> * Tag:
>> http://svn.apache.org/repos/asf/servicemix/smx3/tags/
>> servicemix-3.4.0/
>> * Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheservicemix-332/
>>
>> NMR 1.5.0
>> * JIRA:
>> https://issues.apache.org/jira/browse/SMX4NMR/fixforversion/12316157
>> * Tag:
>> http://svn.apache.org/repos/asf/servicemix/smx4/nmr/tags/nmr-parent-1.5.0/
>> * Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheservicemix-337/
>>
>> Archetypes 2011.02
>> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12317842
>> * Tag:
>> https://svn.apache.org/repos/asf/servicemix/archetypes/tags/archetypes-2011.02/
>> * Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheservicemix-342/
>>
>>
>>
>> Please vote to approve these releases:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> Given the size of this release, this vote will be open for 96 hours.
>>
>>
>> Thanks for reviewing and voting,
>>
>> Gert Vanthienen
>> ------------------------
>> FuseSource
>> Web: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>
---------------------------------------------
Freeman Fang
FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Re: [VOTE] Release ServiceMix 4.4.0 (take 2)
Posted by Johan Edstrom <se...@gmail.com>.
Noticed these warnings - 2011-12-15 14:59:13,085 | INFO | g.ops4j.pax.web) | JettyServerImpl | ? ? | 111 - org.ops4j.pax.web.pax-web-jetty - 1.0.7 | Pax Web available at [0.0.0.0]:[8181]
2011-12-15 14:59:13,086 | WARN | g.ops4j.pax.web) | NIOSocketConnectorWrapper | ? ? | 111 - org.ops4j.pax.web.pax-web-jetty - 1.0.7 | Connection on port 8181 cannot be open. Reason: Address already in use
And
2011-12-15 14:59:11,458 | WARN | rint Extender: 1 | XBeanNamespaceHandler | ? ? | 62 - org.apache.xbean.blueprint - 3.7 | Could not load class: org.apache.activemq.store.journal.JournalPersistenceAdapter due to org/apache/activeio/journal/JournalEventListener
2011-12-15 14:59:11,533 | WARN | rint Extender: 1 | XBeanNamespaceHandler | ? ? | 62 - org.apache.xbean.blueprint - 3.7 | Could not load class: org.apache.activemq.store.journal.JournalPersistenceAdapterFactory due to org/apache/activeio/journal/active/JournalLockedException
2011-12-15 14:59:11,590 | WARN | rint Extender: 1 | XBeanNamespaceHandler | ? ? | 62 - org.apache.xbean.blueprint - 3.7 | Could not load class: org.apache.activemq.store.PersistenceAdapterFactoryBean due to org/apache/activeio/journal/active/JournalLockedException
Doubt neither causes any issues whatsoever…
And…
araf@root> features:install examples-cxf-osgi
Refreshing bundles org.springframework.web (114), org.ops4j.pax.web.pax-web-runtime (113), org.springframework.web.servlet (115), org.ops4j.pax.web.pax-web-jetty (111), org.springframework.beans (66)
ERROR: Bundle org.apache.karaf.deployer.features [39] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService)
java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService
at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:104)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
at org.apache.felix.framework.Felix.access$000(Felix.java:80)
at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
at org.apache.felix.framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
at org.ops4j.pax.web.service.internal.Activator.createHttpServiceFactory(Activator.java:111)
at org.ops4j.pax.web.service.internal.Activator.access$900(Activator.java:70)
at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:332)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)
at org.ops4j.pax.web.service.internal.Activator.start(Activator.java:95)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1842)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1759)
at org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4534)
at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3591)
at org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:363)
at java.lang.Thread.run(Thread.java:680)
ERROR: Bundle org.apache.karaf.deployer.features [39] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService)
java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService
at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:104)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
at org.apache.felix.framework.Felix.access$000(Felix.java:80)
at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
at org.apache.felix.framework.ServiceRegistry.servicePropertiesModified(ServiceRegistry.java:480)
at org.apache.felix.framework.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:116)
at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:155)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1160)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
at java.lang.Thread.run(Thread.java:680)
karaf@root> features:install examples-cxf-wsdl-first-osgi-package
Refreshing bundles org.springframework.transaction (93), org.apache.xbean.spring (79), org.apache.servicemix.bundles.jaxb-xjc (120), org.apache.servicemix.bundles.xmlbeans (140)
*ERROR* Configuration for org.ops4j.pax.web has already been used for service [org.osgi.service.cm.ManagedService, id=284, bundle=113] and will now also be given to [org.osgi.service.cm.ManagedService, id=372, bundle=113]
ERROR: Bundle org.apache.karaf.deployer.features [39] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService)
java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService
at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:104)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
at org.apache.felix.framework.Felix.access$000(Felix.java:80)
at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
at org.apache.felix.framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
at org.ops4j.pax.web.service.internal.Activator.createHttpServiceFactory(Activator.java:111)
at org.ops4j.pax.web.service.internal.Activator.access$900(Activator.java:70)
at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:332)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
at org.apache.felix.framework.Felix.access$000(Felix.java:80)
at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
at org.apache.felix.framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
at org.apache.felix.framework.Felix.registerService(Felix.java:2861)
at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:229)
at org.ops4j.pax.web.service.jetty.internal.Activator.start(Activator.java:46)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1842)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1759)
at org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4534)
at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3591)
at org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:363)
at java.lang.Thread.run(Thread.java:680)
ERROR: Bundle org.apache.karaf.deployer.features [39] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService)
java.lang.ClassCastException: org.ops4j.pax.web.service.internal.HttpServiceProxy cannot be cast to org.osgi.service.http.HttpService
at org.ops4j.pax.web.extender.whiteboard.internal.HttpServiceTracker.addingService(HttpServiceTracker.java:104)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840)
at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3772)
at org.apache.felix.framework.Felix.access$000(Felix.java:80)
at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:729)
at org.apache.felix.framework.ServiceRegistry.servicePropertiesModified(ServiceRegistry.java:480)
at org.apache.felix.framework.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:116)
at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:155)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1160)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
at java.lang.Thread.run(Thread.java:680)
On Dec 15, 2011, at 2:21 PM, Gert Vanthienen wrote:
> L.S.,
>
>
> I've uploaded a release for ServiceMix 4.4.0 to
> https://repository.apache.org/content/repositories/orgapacheservicemix-348
>
> An overview of issues fixed in this release can be found in JIRA at
> https://issues.apache.org/jira/browse/SMX4/fixforversion/12315742
>
> The scm tag is available on
>
> http://svn.apache.org/repos/asf/servicemix/smx4/features/tags/features-4.4.0/
>
>
> As part of this release build, we also built new releases of utils,
> components, servicemix 3, nmr and archetypes.
>
> servicemix-utils 1.5.0
> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12316098
> * Tag:
> http://svn.apache.org/repos/asf/servicemix/utils/tags/servicemix-utils-1.5.0/
> * Staging repo:
> https://repository.apache.org/content/repositories/orgapacheservicemix-329/
>
> components 2011.02
> * JIRA:
> https://issues.apache.org/jira/browse/SMXCOMP/fixforversion/12316111
> * Tag:
> http://svn.apache.org/repos/asf/servicemix/components/tags/components-2011.02/
> * Staging repo:
> https://repository.apache.org/content/repositories/orgapacheservicemix-330/
>
> ServiceMix 3.4.0
> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12315718
> * Tag:
> http://svn.apache.org/repos/asf/servicemix/smx3/tags/servicemix-3.4.0/
> * Staging repo:
> https://repository.apache.org/content/repositories/orgapacheservicemix-332/
>
> NMR 1.5.0
> * JIRA:
> https://issues.apache.org/jira/browse/SMX4NMR/fixforversion/12316157
> * Tag:
> http://svn.apache.org/repos/asf/servicemix/smx4/nmr/tags/nmr-parent-1.5.0/
> * Staging repo:
> https://repository.apache.org/content/repositories/orgapacheservicemix-337/
>
> Archetypes 2011.02
> * JIRA: https://issues.apache.org/jira/browse/SM/fixforversion/12317842
> * Tag:
> https://svn.apache.org/repos/asf/servicemix/archetypes/tags/archetypes-2011.02/
> * Staging repo:
> https://repository.apache.org/content/repositories/orgapacheservicemix-342/
>
>
>
> Please vote to approve these releases:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> Given the size of this release, this vote will be open for 96 hours.
>
>
> Thanks for reviewing and voting,
>
> Gert Vanthienen
> ------------------------
> FuseSource
> Web: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/