[jira] [Commented] (CAMEL-6707) Asynchronous Mode In camel-servlet, Servlet 3.0 AsyncContext
[ https://issues.apache.org/jira/browse/CAMEL-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920694#comment-13920694 ] David J. M. Karlsen commented on CAMEL-6707: Any update on this? We´re in the same situation and have to create our own custom servlet to accommodate async processing. Asynchronous Mode In camel-servlet, Servlet 3.0 AsyncContext Key: CAMEL-6707 URL: https://issues.apache.org/jira/browse/CAMEL-6707 Project: Camel Issue Type: Improvement Components: camel-http, camel-servlet Affects Versions: 2.13.0 Reporter: Jörg Schubert Priority: Minor My Goal is routing larger amounts of HTTP-Traffic CamelServlet is blocking the HTTP-thread while message is being processed. I'm currently preparing a patch which uses AsyncContext and starts processor in async mode. Hope that will improve throughput. The async feature is switchable by parameter. I will attach a patch as soon as it works. There is one point: To avoid conflicts geronimo-servlet_2.5_spec must be replaced by geronimo-servlet_3.0_spec in parent pom. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-6707) Asynchronous Mode In camel-servlet, Servlet 3.0 AsyncContext
[ https://issues.apache.org/jira/browse/CAMEL-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920763#comment-13920763 ] David J. M. Karlsen commented on CAMEL-6707: And here is another user with the same request: http://camel.465427.n5.nabble.com/Camel-Users-f465428i70.html Asynchronous Mode In camel-servlet, Servlet 3.0 AsyncContext Key: CAMEL-6707 URL: https://issues.apache.org/jira/browse/CAMEL-6707 Project: Camel Issue Type: Improvement Components: camel-http, camel-servlet Affects Versions: 2.13.0 Reporter: Jörg Schubert Priority: Minor My Goal is routing larger amounts of HTTP-Traffic CamelServlet is blocking the HTTP-thread while message is being processed. I'm currently preparing a patch which uses AsyncContext and starts processor in async mode. Hope that will improve throughput. The async feature is switchable by parameter. I will attach a patch as soon as it works. There is one point: To avoid conflicts geronimo-servlet_2.5_spec must be replaced by geronimo-servlet_3.0_spec in parent pom. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-6717) camel-mqtt - dead lock when processing fetching/sending messages at high frequency
[ https://issues.apache.org/jira/browse/CAMEL-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920821#comment-13920821 ] Ralf Kornberger commented on CAMEL-6717: Thanks. I think it working :-) I haven't had a deadlock so far camel-mqtt - dead lock when processing fetching/sending messages at high frequency -- Key: CAMEL-6717 URL: https://issues.apache.org/jira/browse/CAMEL-6717 Project: Camel Issue Type: Bug Components: camel-mqtt Affects Versions: 2.11.0 Environment: jdk 1.6.32 Reporter: Ralf Kornberger Assignee: Claus Ibsen Fix For: 2.12.3, 2.13.0 I'm using Apache Camel with MQTT to fetch data from a Mosquitto broker. Data are published there at high frequency ( 10s) by serveral devices. After receiving the data, I send an acknowlege message back. This is done by publishing a message to a topic for each device. I'm using the Fusesource MQTT Client (version 2.5) for this. I encountered the following problem: after some time (can be 15 minutes up to 1 day) some thing weird happens. The application stops receiving or sending any data via MQTT. Looking at it with jstack reveals the following: hawtdispatch-DEFAULT-2 daemon prio=10 tid=0x7facc1a2f000 nid=0x782d waiting on condition [0x7fac42bcf000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for 0x00078e792b88 (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:969) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1281) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:207) at org.fusesource.mqtt.client.Promise.await(Promise.java:88) at org.fusesource.mqtt.client.BlockingConnection.publish(BlockingConnection.java:73) at org.fusesource.mqtt.client.BlockingConnection.publish(BlockingConnection.java:82) at net.centersight.plugins.agent.protomqtt.comm.MQTTManager.sendACKMessage(MQTTManager.java:92) at net.centersight.plugins.agent.protomqtt.comm.MQTTCommunication.sendACKMessage(MQTTCommunication.java:116) at net.centersight.plugins.agent.protomqtt.camel.AgentMQTTbatchACKer.process(AgentMQTTbatchACKer.java:47) at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:341) at org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:238) at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:166) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:334) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220) at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90) at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73) at org.apache.camel.processor.Pipeline.process(Pipeline.java:117) at
[jira] [Commented] (CAMEL-7261) Provide camel:context-suspend and camel:context-resume commands
[ https://issues.apache.org/jira/browse/CAMEL-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920834#comment-13920834 ] ASF GitHub Bot commented on CAMEL-7261: --- GitHub user grgrzybek opened a pull request: https://github.com/apache/camel/pull/108 [CAMEL-7261] camel:context-stop. Information in command description. You can merge this pull request into a Git repository by running: $ git pull https://github.com/grgrzybek/camel CAMEL-7261-help Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/108.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #108 commit 963ac1e45f0a84d8dec3336148e21c7eb8f370a2 Author: Grzegorz Grzybek gr.grzy...@gmail.com Date: 2014-03-05T13:34:19Z [CAMEL-7261] camel:context-stop. Information in command description. Provide camel:context-suspend and camel:context-resume commands --- Key: CAMEL-7261 URL: https://issues.apache.org/jira/browse/CAMEL-7261 Project: Camel Issue Type: Improvement Components: karaf Affects Versions: 2.12.0 Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Priority: Minor Fix For: 2.12.4, 2.13.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7261) Provide camel:context-suspend and camel:context-resume commands
[
https://issues.apache.org/jira/browse/CAMEL-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved CAMEL-7261.
-
Resolution: Fixed
Updated the docs and information in {{context-stop}} command.
Provide camel:context-suspend and camel:context-resume commands
---
Key: CAMEL-7261
URL: https://issues.apache.org/jira/browse/CAMEL-7261
Project: Camel
Issue Type: Improvement
Components: karaf
Affects Versions: 2.12.0
Reporter: Grzegorz Grzybek
Assignee: Grzegorz Grzybek
Priority: Minor
Fix For: 2.12.4, 2.13.0
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7261) Provide camel:context-suspend and camel:context-resume commands
[ https://issues.apache.org/jira/browse/CAMEL-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920902#comment-13920902 ] ASF GitHub Bot commented on CAMEL-7261: --- Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/108 Provide camel:context-suspend and camel:context-resume commands --- Key: CAMEL-7261 URL: https://issues.apache.org/jira/browse/CAMEL-7261 Project: Camel Issue Type: Improvement Components: karaf Affects Versions: 2.12.0 Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Priority: Minor Fix For: 2.12.4, 2.13.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7272) Change order of releases on archives page
Sebb created CAMEL-7272: --- Summary: Change order of releases on archives page Key: CAMEL-7272 URL: https://issues.apache.org/jira/browse/CAMEL-7272 Project: Camel Issue Type: Improvement Environment: http://camel.apache.org/download-archives.html Reporter: Sebb Priority: Minor The list of releases on the download archives page seems to be sorted in alphabetic rather than numeric order. So for example we have Camel 2.1.0 Release Camel 2.10.0 Release Camel 2.10.1 Release ... Camel 2.11.0 Release ... Camel 2.12.0 Release Camel 2.12.1 Release Camel 2.12.2 Release Camel 2.12.3 Release Camel 2.2.0 Release Camel 2.3.0 Release This makes it harder to find a particular release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7273) Broken links on download pages for archived releases
Sebb created CAMEL-7273: --- Summary: Broken links on download pages for archived releases Key: CAMEL-7273 URL: https://issues.apache.org/jira/browse/CAMEL-7273 Project: Camel Issue Type: Bug Reporter: Sebb The ASF mirror systems only holds releases that are current; in the case of Camel that is currently 2.11.4 and 2.12.3. All other releases are available on the archive server. However, all of the superseded release download pages still point to the ASF mirror system. Their links are broken. For example, in the download page for 2.12.2, instead of http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.12.2/apache-camel-2.12.2.zip and http://www.apache.org/dist/camel/apache-camel/2.12.2/apache-camel-2.12.2.zip.asc the page should point to http://archive.apache.org/dist/camel/apache-camel/2.11.2/apache-camel-2.11.2.zip and http://archive.apache.org/dist/camel/apache-camel/2.12.2/apache-camel-2.12.2.zip.asc -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7274) Support roles in the camel-shiro component
Colm O hEigeartaigh created CAMEL-7274: -- Summary: Support roles in the camel-shiro component Key: CAMEL-7274 URL: https://issues.apache.org/jira/browse/CAMEL-7274 Project: Camel Issue Type: Bug Reporter: Colm O hEigeartaigh Fix For: 2.13.0 The Camel-shiro component allows the ability to perform authorization based on permissions. However, it does not allow using straight-forward roles for authorization. While using permissions is more flexible, we should also support authorization using roles. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7274) Support roles in the camel-shiro component
[ https://issues.apache.org/jira/browse/CAMEL-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7274: --- Attachment: camel-7274.patch A patch + tests for this issue. Colm. Support roles in the camel-shiro component -- Key: CAMEL-7274 URL: https://issues.apache.org/jira/browse/CAMEL-7274 Project: Camel Issue Type: Bug Reporter: Colm O hEigeartaigh Fix For: 2.13.0 Attachments: camel-7274.patch The Camel-shiro component allows the ability to perform authorization based on permissions. However, it does not allow using straight-forward roles for authorization. While using permissions is more flexible, we should also support authorization using roles. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Work started] (CAMEL-7274) Support roles in the camel-shiro component
[ https://issues.apache.org/jira/browse/CAMEL-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-7274 started by Raul Kripalani. Support roles in the camel-shiro component -- Key: CAMEL-7274 URL: https://issues.apache.org/jira/browse/CAMEL-7274 Project: Camel Issue Type: Bug Reporter: Colm O hEigeartaigh Assignee: Raul Kripalani Fix For: 2.13.0 Attachments: camel-7274.patch The Camel-shiro component allows the ability to perform authorization based on permissions. However, it does not allow using straight-forward roles for authorization. While using permissions is more flexible, we should also support authorization using roles. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7274) Support roles in the camel-shiro component
[ https://issues.apache.org/jira/browse/CAMEL-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raul Kripalani resolved CAMEL-7274. --- Resolution: Fixed Patch applied on master (2.13.x) with thanks to [~coheigea]. Support roles in the camel-shiro component -- Key: CAMEL-7274 URL: https://issues.apache.org/jira/browse/CAMEL-7274 Project: Camel Issue Type: Bug Reporter: Colm O hEigeartaigh Assignee: Raul Kripalani Fix For: 2.13.0 Attachments: camel-7274.patch The Camel-shiro component allows the ability to perform authorization based on permissions. However, it does not allow using straight-forward roles for authorization. While using permissions is more flexible, we should also support authorization using roles. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7274) Support roles in the camel-shiro component
[ https://issues.apache.org/jira/browse/CAMEL-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raul Kripalani updated CAMEL-7274: -- Component/s: camel-shiro Support roles in the camel-shiro component -- Key: CAMEL-7274 URL: https://issues.apache.org/jira/browse/CAMEL-7274 Project: Camel Issue Type: Bug Components: camel-shiro Reporter: Colm O hEigeartaigh Assignee: Raul Kripalani Fix For: 2.13.0 Attachments: camel-7274.patch The Camel-shiro component allows the ability to perform authorization based on permissions. However, it does not allow using straight-forward roles for authorization. While using permissions is more flexible, we should also support authorization using roles. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7225) should check Exchange.CHARSET_NAME header
[ https://issues.apache.org/jira/browse/CAMEL-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921390#comment-13921390 ] Christian Müller commented on CAMEL-7225: - Daniel, do you consider to provide a patch for it? should check Exchange.CHARSET_NAME header - Key: CAMEL-7225 URL: https://issues.apache.org/jira/browse/CAMEL-7225 Project: Camel Issue Type: Bug Components: camel-smpp Affects Versions: 2.12.2 Environment: any Reporter: Daniel Pocock Priority: Minor The camel-smpp component should check the Exchange.CHARSET_NAME header of each message to determine the actual encoding of byte[] messages It appears that it currently expects all byte[] messages to be encoded in the character set specified by the encoding property on the endpoint -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7224) fails to correctly send messages that require UCS-2 encoding
[ https://issues.apache.org/jira/browse/CAMEL-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921392#comment-13921392 ] Christian Müller commented on CAMEL-7224: - Daniel, do you consider to provide a patch for it? fails to correctly send messages that require UCS-2 encoding Key: CAMEL-7224 URL: https://issues.apache.org/jira/browse/CAMEL-7224 Project: Camel Issue Type: Bug Components: camel-smpp Affects Versions: 2.12.2 Environment: any Reporter: Daniel Pocock If I try to send a string without any config options or headers to indicate alphabet/data coding/encoding, it appears to be sent using an 8 bit character set even if a 16 bit UCS-2 encoding is required. If I try to set CamelSmppAlphabet=-1 (for unknown) as a header, an invalid message is sent to the SMPP peer and it is rejected with SMPP error code 0401 If I try to set alphabet=-1 in the endpoint config though and if I also set CamelSmppDataCoding=8 then it correctly sends a UCS-2 message. Looking at the code (particularly the method SmppSmCommand.determineCharset()), it seems that it can ONLY send UCS-2 if alphabet == UNKNOWN_ALPHABET. Using the value UNKNOWN_ALPHABET (-1) as a header triggers the problem with the SMPP peer so I can only set that value in the endpoint config. This determineCharset() method should also recognise alphabet == ALPHA_UCS2 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-7272) Change order of releases on archives page
[ https://issues.apache.org/jira/browse/CAMEL-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller reassigned CAMEL-7272: --- Assignee: Christian Müller Change order of releases on archives page - Key: CAMEL-7272 URL: https://issues.apache.org/jira/browse/CAMEL-7272 Project: Camel Issue Type: Improvement Environment: http://camel.apache.org/download-archives.html Reporter: Sebb Assignee: Christian Müller Priority: Minor The list of releases on the download archives page seems to be sorted in alphabetic rather than numeric order. So for example we have Camel 2.1.0 Release Camel 2.10.0 Release Camel 2.10.1 Release ... Camel 2.11.0 Release ... Camel 2.12.0 Release Camel 2.12.1 Release Camel 2.12.2 Release Camel 2.12.3 Release Camel 2.2.0 Release Camel 2.3.0 Release This makes it harder to find a particular release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7272) Change order of releases on archives page
[ https://issues.apache.org/jira/browse/CAMEL-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921555#comment-13921555 ] Christian Müller commented on CAMEL-7272: - Thanks for spotting this Sebb. It's fixed in the wiki now and should be online in a few minutes... Change order of releases on archives page - Key: CAMEL-7272 URL: https://issues.apache.org/jira/browse/CAMEL-7272 Project: Camel Issue Type: Improvement Environment: http://camel.apache.org/download-archives.html Reporter: Sebb Assignee: Christian Müller Priority: Minor The list of releases on the download archives page seems to be sorted in alphabetic rather than numeric order. So for example we have Camel 2.1.0 Release Camel 2.10.0 Release Camel 2.10.1 Release ... Camel 2.11.0 Release ... Camel 2.12.0 Release Camel 2.12.1 Release Camel 2.12.2 Release Camel 2.12.3 Release Camel 2.2.0 Release Camel 2.3.0 Release This makes it harder to find a particular release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7272) Change order of releases on archives page
[ https://issues.apache.org/jira/browse/CAMEL-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-7272. - Resolution: Fixed Change order of releases on archives page - Key: CAMEL-7272 URL: https://issues.apache.org/jira/browse/CAMEL-7272 Project: Camel Issue Type: Improvement Environment: http://camel.apache.org/download-archives.html Reporter: Sebb Assignee: Christian Müller Priority: Minor The list of releases on the download archives page seems to be sorted in alphabetic rather than numeric order. So for example we have Camel 2.1.0 Release Camel 2.10.0 Release Camel 2.10.1 Release ... Camel 2.11.0 Release ... Camel 2.12.0 Release Camel 2.12.1 Release Camel 2.12.2 Release Camel 2.12.3 Release Camel 2.2.0 Release Camel 2.3.0 Release This makes it harder to find a particular release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Work started] (CAMEL-7272) Change order of releases on archives page
[ https://issues.apache.org/jira/browse/CAMEL-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-7272 started by Christian Müller. Change order of releases on archives page - Key: CAMEL-7272 URL: https://issues.apache.org/jira/browse/CAMEL-7272 Project: Camel Issue Type: Improvement Environment: http://camel.apache.org/download-archives.html Reporter: Sebb Assignee: Christian Müller Priority: Minor The list of releases on the download archives page seems to be sorted in alphabetic rather than numeric order. So for example we have Camel 2.1.0 Release Camel 2.10.0 Release Camel 2.10.1 Release ... Camel 2.11.0 Release ... Camel 2.12.0 Release Camel 2.12.1 Release Camel 2.12.2 Release Camel 2.12.3 Release Camel 2.2.0 Release Camel 2.3.0 Release This makes it harder to find a particular release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CAMEL-7272) Change order of releases on archives page
[ https://issues.apache.org/jira/browse/CAMEL-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed CAMEL-7272. --- Thanks, than looks better Change order of releases on archives page - Key: CAMEL-7272 URL: https://issues.apache.org/jira/browse/CAMEL-7272 Project: Camel Issue Type: Improvement Environment: http://camel.apache.org/download-archives.html Reporter: Sebb Assignee: Christian Müller Priority: Minor The list of releases on the download archives page seems to be sorted in alphabetic rather than numeric order. So for example we have Camel 2.1.0 Release Camel 2.10.0 Release Camel 2.10.1 Release ... Camel 2.11.0 Release ... Camel 2.12.0 Release Camel 2.12.1 Release Camel 2.12.2 Release Camel 2.12.3 Release Camel 2.2.0 Release Camel 2.3.0 Release This makes it harder to find a particular release. -- This message was sent by Atlassian JIRA (v6.2#6252)
