You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2009/09/01 06:56:21 UTC
[jira] Created: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
CamelNamespaceHandler is not thread safe
----------------------------------------
Key: CAMEL-1966
URL: https://issues.apache.org/activemq/browse/CAMEL-1966
Project: Apache Camel
Issue Type: Bug
Affects Versions: 2.0.0, 2.0-M3, 2.0-M2, 1.6.1, 2.0-M1, 1.6.0, 1.5.0, 1.4.0
Reporter: Willem Jiang
Assignee: Willem Jiang
Fix For: 1.6.2, 2.1.0
Here is the mail thread[1] which discusses about it.
[1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CAMEL-1966) CamelNamespaceHandler is
not thread safe
Posted by "Roman Ivanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56655#action_56655 ]
Roman Ivanov edited comment on CAMEL-1966 at 12/24/09 3:02 PM:
---------------------------------------------------------------
Hi, currently I'm upgrading to Camel version 2.1.0 from 2.0.0. And this issue reproduces again. The bundle order is explicitly defined with startup properties, though application bundles are started later then camel. We're having ServiceMix 4 with Karaf 1.0.4.
Here are logs:
<code>
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://camel.apache.org/schema/spring/camel-spring.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'camelContext'.
<code>
was (Author: roman.ivanov):
Hi, currently I' upgrading to Camel version 2.1.0 from 2.0.0. And this issue reproduces again. The bundle order is explicitly defined with startup properties, though application bundles are started later then camel. We're having ServiceMix 4 with Karaf 1.0.4.
Here are logs:
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://camel.apache.org/schema/spring/camel-spring.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'camelContext'.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CAMEL-1966) CamelNamespaceHandler is
not thread safe
Posted by "Roman Ivanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56688#action_56688 ]
Roman Ivanov edited comment on CAMEL-1966 at 12/29/09 2:37 PM:
---------------------------------------------------------------
Hi Claus, Willem
Upgrade for newer SMX version is good idea for sure, but it might be a separate issue.
Although, I tried to use camel-spring-osgi instead of 2 separate libs. It didn't made real effect.
But, I followed the idea of [this issue |http://issues.apache.org/activemq/browse/CAMEL-1730].
And made camel-spring bundle start up order earlier than camel-osgi. And it solved the issue.
was (Author: roman.ivanov):
Hi Claus, Willem
Upgrade for newer SMX version is good idea for sure, but it might be a separate issue.
Although, I tried to use camel-spring-osgi instead of 2 separate libs. I didn't made real effect.
But, I followed the idea of http://issues.apache.org/activemq/browse/CAMEL-1730.
And made camel-spring bundle start up order earlier than camel-osgi. And it solved the issue.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-1966.
---------------------------------
Resolution: Fixed
The reopened reason is not related to the JIRA.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.1.0, 1.6.2
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Roman Ivanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Ivanov reopened CAMEL-1966:
---------------------------------
Hi, currently I' upgrading to Camel version 2.1.0 from 2.0.0. And this issue reproduces again. The bundle order is explicitly defined with startup properties, though application bundles are started later then camel. We're having ServiceMix 4 with Karaf 1.0.4.
Here are logs:
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://camel.apache.org/schema/spring/camel-spring.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'camelContext'.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56670#action_56670 ]
Claus Ibsen commented on CAMEL-1966:
------------------------------------
Roman, ServiceMix is undergoing many changes recently and I guess it should be better at OSGi stuff on startup.
So what version do you exactly use for SMX and Karaf?
And if possible try with a newer version.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CAMEL-1966) CamelNamespaceHandler is
not thread safe
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56679#action_56679 ]
Willem Jiang edited comment on CAMEL-1966 at 12/29/09 3:21 AM:
---------------------------------------------------------------
Hi Roman
There are something changed in Camel 2.1.0, we merged the camel-osgi and camel-spring to avoid the some issue of
Please update the org.apache.felix.karaf.features.cfg
by replacing the camel-osgi and camel-spring with camel-spring-osgi and try again.
was (Author: njiang):
Hi Roman
There are something changed in Camel 2.1.0, we merged the camel-osgi and camel-spring to avoid the some issue of
Please update the startup properties by replacing the camel-osgi and camel-spring with camel-spring-osgi and try again.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-1966.
---------------------------------
Resolution: Fixed
trunk
http://svn.apache.org/viewvc?rev=809874&view=rev
camel 1.x
http://svn.apache.org/viewvc?rev=809931&view=rev
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CAMEL-1966) CamelNamespaceHandler is
not thread safe
Posted by "Roman Ivanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56655#action_56655 ]
Roman Ivanov edited comment on CAMEL-1966 at 12/24/09 3:07 PM:
---------------------------------------------------------------
Hi, currently I'm upgrading to Camel version 2.1.0 from 2.0.0. And this issue reproduces again. The bundle order is explicitly defined with startup properties, though application bundles are started later then camel. We're having ServiceMix 4 with Karaf 1.0.4.
Here are logs:
{code}
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://camel.apache.org/schema/spring/camel-spring.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'camelContext'.
{code}
was (Author: roman.ivanov):
Hi, currently I'm upgrading to Camel version 2.1.0 from 2.0.0. And this issue reproduces again. The bundle order is explicitly defined with startup properties, though application bundles are started later then camel. We're having ServiceMix 4 with Karaf 1.0.4.
Here are logs:
<code>
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://camel.apache.org/schema/spring/camel-spring.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'camelContext'.
<code>
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54023#action_54023 ]
Willem Jiang commented on CAMEL-1966:
-------------------------------------
Talked with Charles,
The exceptions which he said are related to the bundle loading sequences.
If his application bundle is loaded before the camel-core and camel-spring, the exceptions will be thrown.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56692#action_56692 ]
Willem Jiang commented on CAMEL-1966:
-------------------------------------
Hi Roman,
Which version of Servicemix are you using ?
There is an camel feature (which includes camel-core, camel-spring and camel-osgi) in the org.apache.felix.karaf.features.cfg, you need to replace it with camel-core and camel-spring-osgi.
Please make sure there is no camel-spring, camel-spring-osgi, camel-osgi installed at the same time.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56679#action_56679 ]
Willem Jiang commented on CAMEL-1966:
-------------------------------------
Hi Roman
There are something changed in Camel 2.1.0, we merged the camel-osgi and camel-spring to avoid the some issue of
Please update the startup properties by replacing the camel-osgi and camel-spring with camel-spring-osgi and try again.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Roman Ivanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56688#action_56688 ]
Roman Ivanov commented on CAMEL-1966:
-------------------------------------
Hi Claus, Willem
Upgrade for newer SMX version is good idea for sure, but it might be a separate issue.
Although, I tried to use camel-spring-osgi instead of 2 separate libs. I didn't made real effect.
But, I followed the idea of http://issues.apache.org/activemq/browse/CAMEL-1730.
And made camel-spring bundle start up order earlier than camel-osgi. And it solved the issue.
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1966) CamelNamespaceHandler is not thread
safe
Posted by "Charles Moulliard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54014#action_54014 ]
Charles Moulliard commented on CAMEL-1966:
------------------------------------------
Just to inform you that this error appears also when Camel 2.1-SNAPSHOT is used within Apache Karaf Felix. I have this error since around 3-4 days (when switching from Camel 2.0 to camel 2.1-SNAPSHOT. That was not the case before. I must stop/start my camel bundle to be able to work with it.
1) At the karaf launch, the following error is generated :
{code}
karaf@root:/> Exception in thread "SpringOsgiExtenderThread-8" java.lang.IllegalStateException: BeanFactory not initialized or already closed - call '
refresh' before accessing beans via the ApplicationContext
os at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:153)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.close(DependencyWaiterApplicatio
nContextExecutor.java:345)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.fail(DependencyWaiterApplication
ContextExecutor.java:401)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplica
tionContextExecutor.java:287)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicat
ionContextExecutor.java:175)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.
java:175)
at org.springframework.osgi.extender.internal.activator.ContextLoaderListener$2.run(ContextLoaderListener.java:718)
at java.lang.Thread.run(Thread.java:595)
{code}
2) My camel context is not started
3) To start it, I must stop my camel bundle. During the stop, here is the error generated :
{code}
09:46:43,499 | ERROR | Timer-3 | DelegatingTimerTask | duling.timer.DelegatingTimerTask 69 | Unexpected exception thrown from Runnable: org.springframework.osgi.extender.internal.util.concurrent.RunnableTimedExecution$MonitoredRunnable@15b4804
java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:153)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.close(DependencyWaiterApplicationContextExecutor.java:345)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.doClose(AbstractDelegatedExecutionApplicationContext.java:236)
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:794)
at org.springframework.osgi.extender.internal.activator.ContextLoaderListener$3.run(ContextLoaderListener.java:807)
at org.springframework.osgi.extender.internal.util.concurrent.RunnableTimedExecution$MonitoredRunnable.run(RunnableTimedExecution.java:60)
at org.springframework.scheduling.timer.DelegatingTimerTask.run(DelegatingTimerTask.java:66)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
I see also sometimes this warning in the log
{code}
08:59:51,718 | WARN | ExtenderThread-8 | XmlBeanDefinitionReader | k.util.xml.SimpleSaxErrorHandler 47 | Ignored XML validation warning
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://camel.apache.org/schema/spring/camel-spring.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:231)
...
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'camel:camelContext'.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:231)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:167)
{code}
> CamelNamespaceHandler is not thread safe
> ----------------------------------------
>
> Key: CAMEL-1966
> URL: https://issues.apache.org/activemq/browse/CAMEL-1966
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3, 2.0.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.1.0
>
>
> Here is the mail thread[1] which discusses about it.
> [1] http://www.nabble.com/Occasional-CamelNamespaceHandler-exception-when-running-with-Spring-DM-1.2-td25195171.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.