[jira] [Commented] (CAMEL-7431) Impossible to use an existing javax.mail.Session with DefaultJavaMailSender
[ https://issues.apache.org/jira/browse/CAMEL-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995058#comment-13995058 ] Pierre Maréchal commented on CAMEL-7431: StackTrace of the Exception : javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 0; nested exception is: java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1961) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:654) at javax.mail.Service.connect(Service.java:295) at org.apache.camel.component.mail.DefaultJavaMailSender.send(DefaultJavaMailSender.java:111) at org.apache.camel.component.mail.MailProducer.process(MailProducer.java:56) at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:143) at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:307) at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:138) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398) at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191) at org.apache.camel.processor.Pipeline.process(Pipeline.java:118) at org.apache.camel.processor.Pipeline.process(Pipeline.java:80) at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191) at org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:51) at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191) at org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:73) at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:378) at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:346) at org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:242) at org.apache.camel.impl.ProducerCache.sendExchange(ProducerCache.java:346) at org.apache.camel.impl.ProducerCache.send(ProducerCache.java:168) at org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:119) at org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:359) at lu.chd.svc.mailing.service.MailingServiceImpl.sendMail(MailingServiceImpl.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.remoting.support.RemoteInvocationTraceInterceptor.invoke(RemoteInvocationTraceInterceptor.java:78) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy56.sendMail(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.remoting.support.RemoteInvocation.invoke(RemoteInvocation.java:212) at org.springframework.remoting.support.DefaultRemoteInvocationExecutor.invoke(DefaultRemoteInvocationExecutor.java:39) at org.springframework.remoting.support.RemoteInvocationBasedExporter.invoke(RemoteInvocationBasedExporter.java:78) at org.springframework.remoting.support.RemoteInvocationBasedExporter.invokeAndCreateResult(RemoteInvocationBasedExporter.java:114) at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.handleRequest(HttpInvokerServiceExporter.java:74) at
[jira] [Commented] (CAMEL-7418) org.apache.camel.impl.JndiRegistry.findByTypeWithName
[ https://issues.apache.org/jira/browse/CAMEL-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992760#comment-13992760 ] André Ricardo da Silva Souza commented on CAMEL-7418: - ok, but at that moment we have only the class name. org.apache.camel.impl.JndiRegistry.findByTypeWithName - Key: CAMEL-7418 URL: https://issues.apache.org/jira/browse/CAMEL-7418 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.13.0 Reporter: André Ricardo da Silva Souza Priority: Minor Fix For: 2.13.2, 2.14.0 I guess this line isn't correct: if (type.isInstance(pair.getClass()) || type.getName().equals(pair.getClassName())) The variable pair.getClass() always returns javax.naming.NameClassPair or its subclasses and the method isInstance works only with Instances, but doesnt Classes. I think the correct code should be: if (type.isAssignableFrom(Class.forName(pair.getClassName( I've tried to test a transacted route, but i couldnt because the error: Failed to create route route1 at: Transacted[] in route: Route(route1)[[From[direct:start]] - [Transacted[]]] because of No bean could be found in the registry of type: PlatformTransactionManager -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-5113) Parallel and fault tolerant message processing for SQS endpoints.
[ https://issues.apache.org/jira/browse/CAMEL-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999852#comment-13999852 ] Tony Tiger commented on CAMEL-5113: --- This ticket appears to duplicate CAMEL-6286 as the changes in this patch seem to match in functionality. Parallel and fault tolerant message processing for SQS endpoints. - Key: CAMEL-5113 URL: https://issues.apache.org/jira/browse/CAMEL-5113 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Daniel Carleton I'm using Camel to implement parallel processing of jobs in an SQS queue, and ran into a few issues with the current implementation of the SQS component: # SqsConsumer uses a blocking/synchronous processor, which prevents parallel processing of multiple messages from a single endpoint. # Having a maxMessagesPerPoll other than one doesn't seem to make sense, because any messages not being actively processed should be left back in the queue for other consumers to have a chance with. # Rollback processing doesn't go back to SQS and set the visibility timeout to zero, which prevents immediate retries. I propose the following solutions to these problems: # Use an asynchronous processor in SqsConsumer by way of getAsyncProcessor(). (Messages in SQS aren't guaranteed to be FIFO anyway, so there should be no issue with order of processing.) # Replace maxMessagesPerPoll with maxInFlightMessages. Put a semaphore in SqsConsumer to control the maximum number of in flight messages, and when polling SQS always set the number of available permits as the maximum number of messages to retrieve. # In the onFailure callback for an exchange set the visibility timeout in SQS to zero via ChangeMessageVisibility. How does this sound? I'm working on a patch. This is my first work on Camel, so if you see any problems with my approach let me know! Thanks, - Dan -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7442) Upgrade Apache Jackrabbit to Version 2.8.0
[ https://issues.apache.org/jira/browse/CAMEL-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregor Zurowski updated CAMEL-7442: --- Assignee: Gregor Zurowski Upgrade Apache Jackrabbit to Version 2.8.0 -- Key: CAMEL-7442 URL: https://issues.apache.org/jira/browse/CAMEL-7442 Project: Camel Issue Type: Improvement Components: camel-jcr Reporter: Gregor Zurowski Assignee: Gregor Zurowski Priority: Minor Fix For: 2.14.0 Upgrade Apache Jackrabbit for the camel-jcr component to the recently released stable version 2.8.0 (see release notes: http://www.apache.org/dist/jackrabbit/2.8.0/RELEASE-NOTES.txt). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7424) StaxSource doesn't produce correct SAX events with default namespace
[ https://issues.apache.org/jira/browse/CAMEL-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992596#comment-13992596 ] ASF GitHub Bot commented on CAMEL-7424: --- GitHub user grgrzybek opened a pull request: https://github.com/apache/camel/pull/145 [CAMEL-7424] copy new version of StaxSource from CXF (with tests) You can merge this pull request into a Git repository by running: $ git pull https://github.com/grgrzybek/camel CAMEL-7424 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/145.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 #145 commit 7884c7ac22363cb3e0cf30230d26c37df1ae07d6 Author: Grzegorz Grzybek gr.grzy...@gmail.com Date: 2014-05-08T08:34:17Z [CAMEL-7424] copy new version of StaxSource from CXF (with tests) StaxSource doesn't produce correct SAX events with default namespace Key: CAMEL-7424 URL: https://issues.apache.org/jira/browse/CAMEL-7424 Project: Camel Issue Type: Bug Components: camel-xslt Affects Versions: 2.13.1, 3.0.0 Reporter: Grzegorz Grzybek See full description here: CXF-5733 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7442) Upgrade Apache Jackrabbit to Version 2.8.0
Gregor Zurowski created CAMEL-7442: -- Summary: Upgrade Apache Jackrabbit to Version 2.8.0 Key: CAMEL-7442 URL: https://issues.apache.org/jira/browse/CAMEL-7442 Project: Camel Issue Type: Improvement Components: camel-jcr Reporter: Gregor Zurowski Priority: Minor Fix For: 2.14.0 Upgrade Apache Jackrabbit for the camel-jcr component to the recently released stable version 2.8.0 (see release notes: http://www.apache.org/dist/jackrabbit/2.8.0/RELEASE-NOTES.txt). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7416) Improve WS-Security testing
[ https://issues.apache.org/jira/browse/CAMEL-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998811#comment-13998811 ] Colm O hEigeartaigh commented on CAMEL-7416: WSS4J is now passing with JDK 8, as are all of the WS-Security related tests in CXF. The errors in Camel only crop up when encryption is used, no idea why though. Colm. Improve WS-Security testing --- Key: CAMEL-7416 URL: https://issues.apache.org/jira/browse/CAMEL-7416 Project: Camel Issue Type: Test Components: camel-cxf Reporter: Colm O hEigeartaigh Assignee: Aki Yoshida Fix For: 2.13.2, 2.14.0 Attachments: camel-7416.patch The WS-Security testing in the camel-cxf component is a bit of a mess and only covers one use-case. Please apply the attached patch, which covers the main use-cases of Signature + Timestamp, Encryption, UsernameToken and WS-SecurityPolicy. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7443) Remote Print URI changed to UNC Name
Christian Mahnke created CAMEL-7443: --- Summary: Remote Print URI changed to UNC Name Key: CAMEL-7443 URL: https://issues.apache.org/jira/browse/CAMEL-7443 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Mac OS X with remote CUPS IPP Printer Reporter: Christian Mahnke I'm using a printing URI in the form of lpr://lh.abc.de:631/bbk-test (Hostname changed) and getting an PrintException: Reason: javax.print.PrintException: No printer found with name: \\lhgoe.gbv.de\bbk-test. Please verify that the host and printer are registered and reachable from this machine. Which is true, since Camel Printer has changed my URI to a Windows UNC (see backslashes). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7441) The Camel Bindy documentation does not provide information on the quoting property
[ https://issues.apache.org/jira/browse/CAMEL-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998726#comment-13998726 ] Jason Sherman commented on CAMEL-7441: -- Maybe something like: ||Option||Type||Default||Description|| |quoting|boolean|false|Used to specify when field is enclosed in quotes. The quote option must also be set.| The Camel Bindy documentation does not provide information on the quoting property -- Key: CAMEL-7441 URL: https://issues.apache.org/jira/browse/CAMEL-7441 Project: Camel Issue Type: Task Components: camel-bindy, documentation Reporter: Jason Sherman Priority: Minor Fix For: 2.14.0 The documentation at http://camel.apache.org/bindy.html does not provide information on the quoting property. Can the doc be updated to provide details on this option? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CAMEL-7416) Improve WS-Security testing
[ https://issues.apache.org/jira/browse/CAMEL-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998811#comment-13998811 ] Colm O hEigeartaigh edited comment on CAMEL-7416 at 5/15/14 2:52 PM: - WSS4J is now passing with JDK 8, as are all of the WS-Security related tests in CXF trunk. The errors in Camel only crop up when encryption is used, no idea why though. Colm. was (Author: coheigea): WSS4J is now passing with JDK 8, as are all of the WS-Security related tests in CXF. The errors in Camel only crop up when encryption is used, no idea why though. Colm. Improve WS-Security testing --- Key: CAMEL-7416 URL: https://issues.apache.org/jira/browse/CAMEL-7416 Project: Camel Issue Type: Test Components: camel-cxf Reporter: Colm O hEigeartaigh Assignee: Aki Yoshida Fix For: 2.13.2, 2.14.0 Attachments: camel-7416.patch The WS-Security testing in the camel-cxf component is a bit of a mess and only covers one use-case. Please apply the attached patch, which covers the main use-cases of Signature + Timestamp, Encryption, UsernameToken and WS-SecurityPolicy. -- This message was sent by Atlassian JIRA (v6.2#6252)
