You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Vincent Girard-Reydet (JIRA)" <ji...@apache.org> on 2009/12/04 13:49:52 UTC
[jira] Created: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
------------------------------------------------------------------------------------
Key: SMX4-442
URL: https://issues.apache.org/activemq/browse/SMX4-442
Project: ServiceMix 4
Issue Type: Bug
Affects Versions: 4.1.0
Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
Reporter: Vincent Girard-Reydet
Fix For: 4.1.0
There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
- web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
- http (apache-felix-karaf-1.1.0-SNAPSHOT)
Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
Initially PAX-WEB 0.6.0 is installed :
[ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
[ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
[ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
[ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
[ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
[ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
[ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
[ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
...
[ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
...
[ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56273#action_56273 ]
Jean-Baptiste Onofré commented on SMX4-442:
-------------------------------------------
Definitely it makes sense. I will discuss with the team about PAX-WEB in SMX4.
> Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
> ------------------------------------------------------------------------------------
>
> Key: SMX4-442
> URL: https://issues.apache.org/activemq/browse/SMX4-442
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
> Reporter: Vincent Girard-Reydet
> Fix For: 4.1.0
>
>
> There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
> - web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
> - http (apache-felix-karaf-1.1.0-SNAPSHOT)
> Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
> Initially PAX-WEB 0.6.0 is installed :
> [ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
> [ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
> [ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
> [ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
> If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
> Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
> [ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
> [ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
> [ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
> [ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
> ...
> [ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
> ...
> [ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
> This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
> Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
> This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Posted by "Vincent Girard-Reydet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57010#action_57010 ]
Vincent Girard-Reydet commented on SMX4-442:
--------------------------------------------
Bumping issue: any news on this side ?
> Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
> ------------------------------------------------------------------------------------
>
> Key: SMX4-442
> URL: https://issues.apache.org/activemq/browse/SMX4-442
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
> Reporter: Vincent Girard-Reydet
> Fix For: 4.1.0
>
>
> There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
> - web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
> - http (apache-felix-karaf-1.1.0-SNAPSHOT)
> Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
> Initially PAX-WEB 0.6.0 is installed :
> [ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
> [ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
> [ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
> [ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
> If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
> Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
> [ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
> [ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
> [ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
> [ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
> ...
> [ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
> ...
> [ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
> This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
> Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
> This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned SMX4-442:
---------------------------------
Assignee: Freeman Fang
> Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
> ------------------------------------------------------------------------------------
>
> Key: SMX4-442
> URL: https://issues.apache.org/activemq/browse/SMX4-442
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
> Reporter: Vincent Girard-Reydet
> Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
> - web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
> - http (apache-felix-karaf-1.1.0-SNAPSHOT)
> Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
> Initially PAX-WEB 0.6.0 is installed :
> [ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
> [ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
> [ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
> [ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
> If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
> Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
> [ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
> [ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
> [ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
> [ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
> ...
> [ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
> ...
> [ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
> This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
> Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
> This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SMX4-442.
-------------------------------
Resolution: Fixed
commit fix
http://svn.apache.org/viewvc?rev=901541&view=rev
> Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
> ------------------------------------------------------------------------------------
>
> Key: SMX4-442
> URL: https://issues.apache.org/activemq/browse/SMX4-442
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
> Reporter: Vincent Girard-Reydet
> Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
> - web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
> - http (apache-felix-karaf-1.1.0-SNAPSHOT)
> Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
> Initially PAX-WEB 0.6.0 is installed :
> [ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
> [ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
> [ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
> [ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
> If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
> Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
> [ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
> [ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
> [ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
> [ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
> ...
> [ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
> ...
> [ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
> This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
> Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
> This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMX4-442 started by Freeman Fang.
> Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
> ------------------------------------------------------------------------------------
>
> Key: SMX4-442
> URL: https://issues.apache.org/activemq/browse/SMX4-442
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
> Reporter: Vincent Girard-Reydet
> Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
> - web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
> - http (apache-felix-karaf-1.1.0-SNAPSHOT)
> Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
> Initially PAX-WEB 0.6.0 is installed :
> [ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
> [ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
> [ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
> [ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
> If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
> Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
> [ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
> [ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
> [ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
> [ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
> ...
> [ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
> ...
> [ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
> This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
> Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
> This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Posted by "Vincent Girard-Reydet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57056#action_57056 ]
Vincent Girard-Reydet commented on SMX4-442:
--------------------------------------------
I have progressed on the issue. It seems that the problem comes from the servicemix-* features.
I have tried the following steps:
- remove all the servicemix-* features from the org.apache.felix.karaf.features.cfg file
- install camel, camel-cxf, cxf-osgi (works fine)
- install servicemix-bean ==> the container hangs.
No idea what makes the system hang except that I see the following appear in karaf.log (the diva.* bundles are mine and contain spring configuration files, but other bundles hang too such as org.apache.cxf.bundle)
10:27:56,875 | INFO | internal.FeaturesServiceImpl 265 | Bundles to refresh: org.apache.xbean.xbean-spring (95), org.apache.servicemix.bundles.cglib (102)
10:27:56,875 | INFO | internal.FeaturesServiceImpl 275 | Refreshing bundles: org.apache.xbean.xbean-spring (95), org.apache.servicemix.bundles.cglib (102)
10:28:06,890 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=diva.eu.diva.tis.managers.crisis, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
10:28:06,890 | INFO | support.OsgiServiceFactoryBean 373 | Unregistered service [ServiceRegistrationWrapper for org.apache.felix.framework.ServiceRegistrationImpl@19f6ce5]
10:28:16,890 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=diva.eu.diva.tis.managers.alert, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
10:28:16,906 | INFO | support.OsgiServiceFactoryBean 373 | Unregistered service [ServiceRegistrationWrapper for org.apache.felix.framework.ServiceRegistrationImpl@1a51ce0]
10:28:26,955 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=diva.eu.diva.tis.messaging, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
10:28:26,970 | INFO | activator.ContextLoaderListener 449 | Stopping [org.springframework.osgi.extender] bundle v.[1.2.0]
10:28:36,972 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=diva.eu.diva.tis.thinkingtool, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
10:28:46,975 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=diva.eu.diva.tis.managers.task, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
10:28:56,977 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=eu.diva.tis.sensors.manager.internal, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
10:29:06,979 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=org.apache.cxf.bundle, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
10:29:16,997 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=diva.eu.diva.tis.log, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
10:29:26,999 | ERROR | oncurrent.RunnableTimedExecution 109 | Closing runnable for context OsgiBundleXmlApplicationContext(bundle=eu.diva.tis.persistence, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
22 janv. 2010 10:34:16 org.apache.felix.karaf.main.SimpleFileLock lock
> Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
> ------------------------------------------------------------------------------------
>
> Key: SMX4-442
> URL: https://issues.apache.org/activemq/browse/SMX4-442
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
> Reporter: Vincent Girard-Reydet
> Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
> - web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
> - http (apache-felix-karaf-1.1.0-SNAPSHOT)
> Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
> Initially PAX-WEB 0.6.0 is installed :
> [ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
> [ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
> [ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
> [ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
> If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
> Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
> [ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
> [ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
> [ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
> [ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
> ...
> [ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
> ...
> [ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
> This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
> Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
> This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Posted by "Vincent Girard-Reydet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Girard-Reydet reopened SMX4-442:
----------------------------------------
This fix partially solves the problem. I still have to remove the woodstox bundle installed by camel-cxf in order to get it working, but then it's OK. I noted several other discrepencies :
- camel uses karaf features v1.1.0-SNAPSHOT when servicemix uses v1.2.0
- there are several libraries that are more recent in Camel than servicemix (I can provide the fix, these are minor revisions)
The major problem remaining is that the system will still hang and the console become buggy (there's a separate bug opened for this one) when the camel-cxf feature gets installed. This seems to be caused by one of the dependencies, because when I install the camel-cxf bundle alone, I do not have the problem. I cannot find where the problem does come from, but it seems that the installation of the feature causes a lot of bundles to be refreshed, and the system will hand while unloading servicemix-* bundles.
This is systematic. The manip is:
- edit the \system\org\apache\camel\karaf\features\2.1.0\features-2.1.0-features.xml file to change karaf dependency to 1.2.0 (must change the repository + the dependency to the "http" feature)
- edit the \system\org\apache\felix\karaf\apache-felix-karaf\1.2.0\apache-felix-karaf-1.2.0-features.xml to upgrade the version of jetty to v6.1.14_2 (or downgrade the required version of jetty in camel-cxf dependencies to v6.1.14_1)
- start a fresh servicemix
- install the camel-cxf feature
- look at the log and see the hang warnings
> Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
> ------------------------------------------------------------------------------------
>
> Key: SMX4-442
> URL: https://issues.apache.org/activemq/browse/SMX4-442
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
> Reporter: Vincent Girard-Reydet
> Assignee: Freeman Fang
> Fix For: 4.1.0
>
>
> There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
> - web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
> - http (apache-felix-karaf-1.1.0-SNAPSHOT)
> Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
> Initially PAX-WEB 0.6.0 is installed :
> [ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
> [ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
> [ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
> [ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
> If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
> Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
> [ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
> [ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
> [ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
> [ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
> ...
> [ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
> ...
> [ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
> This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
> Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
> This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMX4-442) Inconsisten Jetty versions between
SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SMX4-442.
-------------------------------
Resolution: Fixed
I believe the fix for SMX4-462 also fix this issue
> Inconsisten Jetty versions between SMX4.1-SNAPSHOT and Camel 2.1-SNAPSHOT breaks CXF
> ------------------------------------------------------------------------------------
>
> Key: SMX4-442
> URL: https://issues.apache.org/activemq/browse/SMX4-442
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.2.0
> Environment: Windows XP, Sun JDSK 1.6_u17, Maven 2.1.0
> Reporter: Vincent Girard-Reydet
> Assignee: Freeman Fang
> Fix For: 4.2.0
>
>
> There is an inconsistency between the declared versions of Jetty and PAX-WEB between the following features:
> - web-core and web-extender (apache-servicemix-4.1.0-SNAPSHOT)
> - http (apache-felix-karaf-1.1.0-SNAPSHOT)
> Karaf uses new PAX-WEB v0.7.1, while SMX4 uses PAX-WEB 0.6
> Initially PAX-WEB 0.6.0 is installed :
> [ 102] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.6.0)
> [ 103] [Active ] [ ] [ ] [ 60] OPS4J Pax Web - Web Container (0.6.0)
> [ 104] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - WAR (0.5.0)
> [ 105] [Active ] [ ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
> If I install the cxf, cxf-osgi and examples-cxf-osgi features, I am able to reach the sample WSDL definitions at http://localhost:8181/cxf/HelloWorld?wsdl.
> Now I install cxf-camel. First, it hangs. If I restart the server, I end up with the following bundles added but not started:
> [ 171] [Resolved ] [ ] [ ] [ 60] OPS4J Pax Web - API (0.7.1)
> [ 172] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Service SPI (0.7.1)
> [ 173] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Runtime (0.7.1)
> [ 174] [Installed ] [ ] [ ] [ 60] OPS4J Pax Web - Jetty (0.7.1)
> ...
> [ 176] [Installed ] [ ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.2)
> ...
> [ 182] [Resolved ] [ ] [ ] [ 60] Apache ServiceMix Bundles: woodstox-3.2.8 (3.2.8.1)
> This is sufficient to cause an exception when trying to access http://localhost:8181/cxf/HelloWorld?wsdl.
> Uninstalling bundles 171,172,173,174,176 and 182 + restarting is sufficient to solve the problem. This does *NOT* prevent camel-cxf from working (tested with a sample project of mine).
> This bug is surely related to SMX-426
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.