[jira] [Commented] (CAMEL-6380) Custom extensions to Camel's XML configuration
[ https://issues.apache.org/jira/browse/CAMEL-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349858#comment-14349858 ] ASF GitHub Bot commented on CAMEL-6380: --- Github user aaronjwhiteside closed the pull request at: https://github.com/apache/camel/pull/297 Custom extensions to Camel's XML configuration -- Key: CAMEL-6380 URL: https://issues.apache.org/jira/browse/CAMEL-6380 Project: Camel Issue Type: New Feature Components: camel-core Affects Versions: 2.11.0 Reporter: Aaron Whiteside Fix For: 3.0.0, Future Allow custom elements to be defined and used in Camel's XML configuration. The use case I have is that we have a fair number of Processor's that take various options and we dynamically load and unload routes from external XML files (not in any spring contexts). Currently we do this by reimplementing Camel's loadRoutesDefinition() method, and supplying additional packages when creating the JAXBContext. It would be good is there were an officially supported mechanism to do this. We place our custom *Definitions in separate namespaces. I imagine it wouldn't be too hard to add support to Camel to look for a specific META-INF/services file and add the additional packages contained within to the JAXBContext, when it is created. I guess this also means the structure of *Definition classes would need to be documented to allow others to take advantage of them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CAMEL-8335) upgrade smack version to 4.0.6
[ https://issues.apache.org/jira/browse/CAMEL-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reopened CAMEL-8335: - miss the version range upgrade in parent/pom.xml upgrade smack version to 4.0.6 -- Key: CAMEL-8335 URL: https://issues.apache.org/jira/browse/CAMEL-8335 Project: Camel Issue Type: Task Components: camel-xmpp Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8335) upgrade smack version to 4.0.6
[ https://issues.apache.org/jira/browse/CAMEL-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-8335. - Resolution: Fixed upgrade smack version to 4.0.6 -- Key: CAMEL-8335 URL: https://issues.apache.org/jira/browse/CAMEL-8335 Project: Camel Issue Type: Task Components: camel-xmpp Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8335) upgrade smack version to 4.0.6
[ https://issues.apache.org/jira/browse/CAMEL-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349878#comment-14349878 ] Freeman Fang commented on CAMEL-8335: - sorry, actually no problem here upgrade smack version to 4.0.6 -- Key: CAMEL-8335 URL: https://issues.apache.org/jira/browse/CAMEL-8335 Project: Camel Issue Type: Task Components: camel-xmpp Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8391) camel-mina / camel-mina2 - The new client mode fails test and seems to accept ghose
[ https://issues.apache.org/jira/browse/CAMEL-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349882#comment-14349882 ] Willem Jiang commented on CAMEL-8391: - Hi Claus, I managed to reproduce the error on my windows VirtualBox when the firewall is open by default. When I gave the Java right to access the network, the error went away. I guess it could relate the listener right about it. So I did some change on the mina server just listen to local loop address, it should resolve the error that you hit. Regards, Willem camel-mina / camel-mina2 - The new client mode fails test and seems to accept ghose --- Key: CAMEL-8391 URL: https://issues.apache.org/jira/browse/CAMEL-8391 Project: Camel Issue Type: Test Components: camel-mina, camel-mina2 Affects Versions: 2.15.0 Reporter: Claus Ibsen Fix For: 2.15.1 The client mode test fails sometimes, getting 2 messages. The 2nd message has empty body. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8391) camel-mina / camel-mina2 - The new client mode fails test and seems to accept ghose
[ https://issues.apache.org/jira/browse/CAMEL-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-8391: --- Assignee: Willem Jiang camel-mina / camel-mina2 - The new client mode fails test and seems to accept ghose --- Key: CAMEL-8391 URL: https://issues.apache.org/jira/browse/CAMEL-8391 Project: Camel Issue Type: Test Components: camel-mina, camel-mina2 Affects Versions: 2.15.0 Reporter: Claus Ibsen Assignee: Willem Jiang Fix For: 2.15.1 The client mode test fails sometimes, getting 2 messages. The 2nd message has empty body. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8445) camel-hdfs2 - Does not work on windows
Claus Ibsen created CAMEL-8445:
--
Summary: camel-hdfs2 - Does not work on windows
Key: CAMEL-8445
URL: https://issues.apache.org/jira/browse/CAMEL-8445
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.15.0
Environment: windows, java8
Reporter: Claus Ibsen
Fix For: 2.16.0
Seems like a bug in hadoop trying to set some permission on windows causing a
NPE in Java code
{code}
org.apache.camel.FailedToCreateProducerException: Failed to create Producer for
endpoint: Endpoint[hdfs2:E:/workspa
e/camel/components/camel-hdfs2/target/test/test-camel1?fileSystemType=LOCALfileType=SEQUENCE_FILEvalueType=TEXT].
Rea
on: java.lang.NullPointerException
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1012)
at org.apache.hadoop.util.Shell.runCommand(Shell.java:445)
at org.apache.hadoop.util.Shell.run(Shell.java:418)
at
org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:650)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:739)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:722)
at
org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:631)
at
org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:468)
at
org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:456)
at
org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:424)
at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:907)
at
org.apache.hadoop.io.SequenceFile$Writer.init(SequenceFile.java:1071)
at org.apache.hadoop.io.SequenceFile.createWriter(SequenceFile.java:270)
at
org.apache.camel.component.hdfs2.HdfsFileType$2.createOutputStream(HdfsFileType.java:212)
at
org.apache.camel.component.hdfs2.HdfsOutputStream.createOutputStream(HdfsOutputStream.java:69)
at
org.apache.camel.component.hdfs2.HdfsProducer.setupHdfs(HdfsProducer.java:143)
at
org.apache.camel.component.hdfs2.HdfsProducer.doStart(HdfsProducer.java:104)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at
org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:2869)
at
org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1097)
at
org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1058)
at
org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:405)
at
org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:123)
at
org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:219)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:74)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:59)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:103)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:89)
at
org.apache.camel.processor.RedeliveryErrorHandler.doStart(RedeliveryErrorHandler.java:1272)
at
org.apache.camel.support.ChildServiceSupport.start(ChildServiceSupport.java:44)
at
org.apache.camel.support.ChildServiceSupport.start(ChildServiceSupport.java:31)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:74)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:59)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:103)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:89)
at
org.apache.camel.processor.interceptor.DefaultChannel.doStart(DefaultChannel.java:153)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8419) Camel StreamCache does not work with CXF consumer for InOut messages
[ https://issues.apache.org/jira/browse/CAMEL-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349022#comment-14349022 ] Claus Ibsen commented on CAMEL-8419: It should be done like camel-jetty does, it lets the consumer create the uow and handle that lifecycle https://github.com/apache/camel/blob/master/components/camel-jetty-common/src/main/java/org/apache/camel/component/jetty/CamelContinuationServlet.java#L146 Then it writes the response https://github.com/apache/camel/blob/master/components/camel-jetty-common/src/main/java/org/apache/camel/component/jetty/CamelContinuationServlet.java#L198 And in the finally it done the UoW https://github.com/apache/camel/blob/master/components/camel-jetty-common/src/main/java/org/apache/camel/component/jetty/CamelContinuationServlet.java#L206 Then the stream cache which may have been offloaded to disk will only get the file deleted after the consumer has sent back the response. Camel StreamCache does not work with CXF consumer for InOut messages Key: CAMEL-8419 URL: https://issues.apache.org/jira/browse/CAMEL-8419 Project: Camel Issue Type: Bug Components: camel-cxf Affects Versions: 2.14.1 Reporter: Stephan Siano Fix For: 2.15.1, 2.16.0 Attachments: 0001-CAMEL-8419-Camel-StreamCache-does-not-work-with-CXF-.patch If a route that is started by a CXF consumer and has an InOut exchange pattern (meaning that the CXF consumer is returning a response back to the caller) contains a StreamCache as message object that is not in memory, returning the payload will fail. The reason for this is that an on-disk stream cache in Camel will be removed when the LUW ends, but CXF will return the response afterwards. See the two attached unit tests for details. I don't like the actual patch too much, as it copies on-disk camel stream caches into CXF stream caches when creating the CXF message object in camel CXF, but this is about the last step before the LUW ends (and the file gets deleted). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8440) Components with windows test failures
[ https://issues.apache.org/jira/browse/CAMEL-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8440. Resolution: Fixed Fix Version/s: (was: 2.16.0) 2.15.0 Assignee: Claus Ibsen There is a separate ticket about the univerciry Components with windows test failures - Key: CAMEL-8440 URL: https://issues.apache.org/jira/browse/CAMEL-8440 Project: Camel Issue Type: Test Components: tests Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.15.0 The following components have/may have unit test failures - jms - apns - aws - beanstalk - barcode -elasticsearch - gae - hdfs - hdfs2 - mina - mina2 - mqtt - quartz2 - restlet - univercity-parser - zookeeper -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8420) Not possible to use inner classes for Dtos in Camel Swagger
[
https://issues.apache.org/jira/browse/CAMEL-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8420:
---
Component/s: (was: camel-core)
Not possible to use inner classes for Dtos in Camel Swagger
---
Key: CAMEL-8420
URL: https://issues.apache.org/jira/browse/CAMEL-8420
Project: Camel
Issue Type: Improvement
Components: camel-swagger
Affects Versions: 2.14.1
Reporter: Espen Tjonneland
If you inline your Dto classes with your services then Camel fails to load
them (ClassNotFoundException).
Can easily be reproduced by modifying the Camel :: Example :: Serlet REST
example by moving the User class into the UserService and update the
UserRoute builder to use the moved type.
{code:title=UserService.java|borderStyle=solid}
public class UserService {
// use a tree map so they become sorted
private final MapString, org.apache.camel.example.rest.UserService.User
users = new TreeMapString, org.apache.camel.example.rest.UserService.User();
private Random ran = new Random();
public UserService() {
users.put(123, new
org.apache.camel.example.rest.UserService.User(123, John Doe));
users.put(456, new
org.apache.camel.example.rest.UserService.User(456, Donald Duck));
users.put(789, new
org.apache.camel.example.rest.UserService.User(789, Slow Turtle));
}
/**
* Gets a user by the given id
*
* @param id the id of the user
* @return the user, or ttnull/tt if no user exists
*/
public org.apache.camel.example.rest.UserService.User getUser(String id) {
}
/**
* List all users
*
* @return the list of all users
*/
public Collectionorg.apache.camel.example.rest.UserService.User
listUsers() {
}
/**
* Updates or creates the given user
*
* @param user the user
*/
public void updateUser(org.apache.camel.example.rest.UserService.User
user) {
}
public static class User {
private int id;
private String name;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8420) Not possible to use inner classes for Dtos in Camel Swagger
[
https://issues.apache.org/jira/browse/CAMEL-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349013#comment-14349013
]
Claus Ibsen commented on CAMEL-8420:
Its using swaggers approach for scanning, so not even sure if it work for them
either. But either ways it is not intended to scan inner classes.
Not possible to use inner classes for Dtos in Camel Swagger
---
Key: CAMEL-8420
URL: https://issues.apache.org/jira/browse/CAMEL-8420
Project: Camel
Issue Type: Improvement
Components: camel-swagger
Affects Versions: 2.14.1
Reporter: Espen Tjonneland
Priority: Minor
If you inline your Dto classes with your services then Camel fails to load
them (ClassNotFoundException).
Can easily be reproduced by modifying the Camel :: Example :: Serlet REST
example by moving the User class into the UserService and update the
UserRoute builder to use the moved type.
{code:title=UserService.java|borderStyle=solid}
public class UserService {
// use a tree map so they become sorted
private final MapString, org.apache.camel.example.rest.UserService.User
users = new TreeMapString, org.apache.camel.example.rest.UserService.User();
private Random ran = new Random();
public UserService() {
users.put(123, new
org.apache.camel.example.rest.UserService.User(123, John Doe));
users.put(456, new
org.apache.camel.example.rest.UserService.User(456, Donald Duck));
users.put(789, new
org.apache.camel.example.rest.UserService.User(789, Slow Turtle));
}
/**
* Gets a user by the given id
*
* @param id the id of the user
* @return the user, or ttnull/tt if no user exists
*/
public org.apache.camel.example.rest.UserService.User getUser(String id) {
}
/**
* List all users
*
* @return the list of all users
*/
public Collectionorg.apache.camel.example.rest.UserService.User
listUsers() {
}
/**
* Updates or creates the given user
*
* @param user the user
*/
public void updateUser(org.apache.camel.example.rest.UserService.User
user) {
}
public static class User {
private int id;
private String name;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8391) camel-mina / camel-mina2 - The new client mode fails test and seems to accept ghose
[ https://issues.apache.org/jira/browse/CAMEL-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349009#comment-14349009 ] Claus Ibsen commented on CAMEL-8391: I get test failures always on windows in both camel-mina and camel-mina2. But the netty components works. camel-mina / camel-mina2 - The new client mode fails test and seems to accept ghose --- Key: CAMEL-8391 URL: https://issues.apache.org/jira/browse/CAMEL-8391 Project: Camel Issue Type: Test Components: camel-mina, camel-mina2 Affects Versions: 2.15.0 Reporter: Claus Ibsen Fix For: 2.15.1 The client mode test fails sometimes, getting 2 messages. The 2nd message has empty body. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8420) Not possible to use inner classes for Dtos in Camel Swagger
[
https://issues.apache.org/jira/browse/CAMEL-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8420:
---
Priority: Minor (was: Major)
Not possible to use inner classes for Dtos in Camel Swagger
---
Key: CAMEL-8420
URL: https://issues.apache.org/jira/browse/CAMEL-8420
Project: Camel
Issue Type: Improvement
Components: camel-swagger
Affects Versions: 2.14.1
Reporter: Espen Tjonneland
Priority: Minor
If you inline your Dto classes with your services then Camel fails to load
them (ClassNotFoundException).
Can easily be reproduced by modifying the Camel :: Example :: Serlet REST
example by moving the User class into the UserService and update the
UserRoute builder to use the moved type.
{code:title=UserService.java|borderStyle=solid}
public class UserService {
// use a tree map so they become sorted
private final MapString, org.apache.camel.example.rest.UserService.User
users = new TreeMapString, org.apache.camel.example.rest.UserService.User();
private Random ran = new Random();
public UserService() {
users.put(123, new
org.apache.camel.example.rest.UserService.User(123, John Doe));
users.put(456, new
org.apache.camel.example.rest.UserService.User(456, Donald Duck));
users.put(789, new
org.apache.camel.example.rest.UserService.User(789, Slow Turtle));
}
/**
* Gets a user by the given id
*
* @param id the id of the user
* @return the user, or ttnull/tt if no user exists
*/
public org.apache.camel.example.rest.UserService.User getUser(String id) {
}
/**
* List all users
*
* @return the list of all users
*/
public Collectionorg.apache.camel.example.rest.UserService.User
listUsers() {
}
/**
* Updates or creates the given user
*
* @param user the user
*/
public void updateUser(org.apache.camel.example.rest.UserService.User
user) {
}
public static class User {
private int id;
private String name;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8420) Not possible to use inner classes for Dtos in Camel Swagger
[
https://issues.apache.org/jira/browse/CAMEL-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8420:
---
Issue Type: Improvement (was: Bug)
Not possible to use inner classes for Dtos in Camel Swagger
---
Key: CAMEL-8420
URL: https://issues.apache.org/jira/browse/CAMEL-8420
Project: Camel
Issue Type: Improvement
Components: camel-swagger
Affects Versions: 2.14.1
Reporter: Espen Tjonneland
If you inline your Dto classes with your services then Camel fails to load
them (ClassNotFoundException).
Can easily be reproduced by modifying the Camel :: Example :: Serlet REST
example by moving the User class into the UserService and update the
UserRoute builder to use the moved type.
{code:title=UserService.java|borderStyle=solid}
public class UserService {
// use a tree map so they become sorted
private final MapString, org.apache.camel.example.rest.UserService.User
users = new TreeMapString, org.apache.camel.example.rest.UserService.User();
private Random ran = new Random();
public UserService() {
users.put(123, new
org.apache.camel.example.rest.UserService.User(123, John Doe));
users.put(456, new
org.apache.camel.example.rest.UserService.User(456, Donald Duck));
users.put(789, new
org.apache.camel.example.rest.UserService.User(789, Slow Turtle));
}
/**
* Gets a user by the given id
*
* @param id the id of the user
* @return the user, or ttnull/tt if no user exists
*/
public org.apache.camel.example.rest.UserService.User getUser(String id) {
}
/**
* List all users
*
* @return the list of all users
*/
public Collectionorg.apache.camel.example.rest.UserService.User
listUsers() {
}
/**
* Updates or creates the given user
*
* @param user the user
*/
public void updateUser(org.apache.camel.example.rest.UserService.User
user) {
}
public static class User {
private int id;
private String name;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8419) Camel StreamCache does not work with CXF consumer for InOut messages
[ https://issues.apache.org/jira/browse/CAMEL-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8419: --- Fix Version/s: 2.16.0 2.15.1 Camel StreamCache does not work with CXF consumer for InOut messages Key: CAMEL-8419 URL: https://issues.apache.org/jira/browse/CAMEL-8419 Project: Camel Issue Type: Bug Components: camel-cxf Affects Versions: 2.14.1 Reporter: Stephan Siano Fix For: 2.15.1, 2.16.0 Attachments: 0001-CAMEL-8419-Camel-StreamCache-does-not-work-with-CXF-.patch If a route that is started by a CXF consumer and has an InOut exchange pattern (meaning that the CXF consumer is returning a response back to the caller) contains a StreamCache as message object that is not in memory, returning the payload will fail. The reason for this is that an on-disk stream cache in Camel will be removed when the LUW ends, but CXF will return the response afterwards. See the two attached unit tests for details. I don't like the actual patch too much, as it copies on-disk camel stream caches into CXF stream caches when creating the CXF message object in camel CXF, but this is about the last step before the LUW ends (and the file gets deleted). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8442) camel-univocity-parsers - Fails unit test on windows
[ https://issues.apache.org/jira/browse/CAMEL-8442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8442: --- Attachment: log.txt console.txt Attached console output and the test log camel-univocity-parsers - Fails unit test on windows Key: CAMEL-8442 URL: https://issues.apache.org/jira/browse/CAMEL-8442 Project: Camel Issue Type: Test Affects Versions: 2.15.0 Reporter: Claus Ibsen Fix For: 2.15.1, 2.16.0 Attachments: console.txt, log.txt Tests in error: UniVocityCsvDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityCsvDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:119 » TextParsing UniVocityFixedWidthDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityFixedWidthDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:118 » TextParsing UniVocityTsvDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityTsvDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:118 » TextParsing Tests run: 115, Failures: 0, Errors: 6, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8441) Add required 3rd party dependencies to the BOM
[
https://issues.apache.org/jira/browse/CAMEL-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348439#comment-14348439
]
ASF GitHub Bot commented on CAMEL-8441:
---
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/420
[CAMEL-8441] Add required 3rd party dependencies to the BOM
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel bom
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/420.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 #420
commit c896681e041e49303f0dcbefa1b560a5c7b9410b
Author: Thomas Diesler thomas.dies...@jboss.com
Date: 2015-03-05T09:00:56Z
[CAMEL-8441] Add required 3rd party dependencies to the BOM
Add required 3rd party dependencies to the BOM
---
Key: CAMEL-8441
URL: https://issues.apache.org/jira/browse/CAMEL-8441
Project: Camel
Issue Type: Improvement
Reporter: Thomas Diesler
Fix For: 2.15.0
For wildfly-camel we have to redefine a number of camel 3rd party
dependencies like this
{code}
!-- Camel version --
version.apache.camel2.14.1/version.apache.camel
!-- Camel 3rd party versions for artefacts that are not defined in
the BOM --
version.apache.abdera1.1.3/version.apache.abdera
version.apache.activemq5.10.0/version.apache.activemq
version.apache.cxf3.0.2/version.apache.cxf
version.apache.lucene4.6.1/version.apache.lucene
version.apache.mina2.0.7/version.apache.mina
version.beanshell2.0b5/version.beanshell
version.hapi2.2/version.hapi
{code}
These should probably come from the camel BOM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8441) Add required 3rd party dependencies to the BOM
Thomas Diesler created CAMEL-8441:
-
Summary: Add required 3rd party dependencies to the BOM
Key: CAMEL-8441
URL: https://issues.apache.org/jira/browse/CAMEL-8441
Project: Camel
Issue Type: Improvement
Reporter: Thomas Diesler
Fix For: 2.15.0
For wildfly-camel we have to redefine a number of camel 3rd party dependencies
like this
{code}
!-- Camel version --
version.apache.camel2.14.1/version.apache.camel
!-- Camel 3rd party versions for artefacts that are not defined in the
BOM --
version.apache.abdera1.1.3/version.apache.abdera
version.apache.activemq5.10.0/version.apache.activemq
version.apache.cxf3.0.2/version.apache.cxf
version.apache.lucene4.6.1/version.apache.lucene
version.apache.mina2.0.7/version.apache.mina
version.beanshell2.0b5/version.beanshell
version.hapi2.2/version.hapi
{code}
These should probably come from the camel BOM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8440) Components with windows test failures
Claus Ibsen created CAMEL-8440: -- Summary: Components with windows test failures Key: CAMEL-8440 URL: https://issues.apache.org/jira/browse/CAMEL-8440 Project: Camel Issue Type: Test Components: tests Reporter: Claus Ibsen Fix For: 2.16.0 The following components have/may have unit test failures - jms - apns - aws - beanstalk - barcode -elasticsearch - gae - hdfs - hdfs2 - mina - mina2 - mqtt - quartz2 - restlet - univercity-parser - zookeeper -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7318) Concurrency on HDFS Consumer not working efficiently
[
https://issues.apache.org/jira/browse/CAMEL-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348469#comment-14348469
]
Grzegorz Grzybek commented on CAMEL-7318:
-
Actually the file is not being read twice.
I've setup two consumers and watched the behavior under debugger.
This code you've mentioned (in
org.apache.camel.component.hdfs2.HdfsInputStream#createInputStream()):
{code:java}
info.getFileSystem().rename(new Path(ret.actualPath), new
Path(ret.suffixedPath));
{code}
doesn't return {{false}} if can't rename, it throws exception with the
following stack trace (file:// case):
{noformat}
java.io.FileNotFoundException: File
file:/data/ggrzybek/sources/github.com/grgrzybek/camel/components/camel-hdfs2/target/test/multiple-consumers/file-0194.txt
does not exist
at
org.apache.hadoop.fs.RawLocalFileSystem.deprecatedGetFileStatus(RawLocalFileSystem.java:511)
at
org.apache.hadoop.fs.RawLocalFileSystem.getFileLinkStatusInternal(RawLocalFileSystem.java:722)
at
org.apache.hadoop.fs.RawLocalFileSystem.getFileStatus(RawLocalFileSystem.java:501)
at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:337)
at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
at
org.apache.hadoop.fs.RawLocalFileSystem.rename(RawLocalFileSystem.java:334)
at
org.apache.hadoop.fs.ChecksumFileSystem.rename(ChecksumFileSystem.java:503)
at
org.apache.camel.component.hdfs2.HdfsInputStream.createInputStream(HdfsInputStream.java:49)
at
org.apache.camel.component.hdfs2.HdfsConsumer.doPoll(HdfsConsumer.java:140)
at
org.apache.camel.component.hdfs2.HdfsConsumer.poll(HdfsConsumer.java:98)
at
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
at
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
so then Camel invokes
org.apache.camel.spi.PollingConsumerPollStrategy#rollback() and simply skips
this file and move to the next one.
I'll check how it works in hdfs:// case.
Concurrency on HDFS Consumer not working efficiently
Key: CAMEL-7318
URL: https://issues.apache.org/jira/browse/CAMEL-7318
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.11.2
Reporter: Martha Obrinteschi
Assignee: Grzegorz Grzybek
Priority: Minor
Labels: concurrency, parallel
If we have two HDFS consumers the files are being processed twice (once by
each consumer, waiting one after the other) so the consumers are not working
in parallel. If we add this the consumers will work as a team and the
transfer will go faster.
This happens because there is no exception thrown (the rename method just
returns true or false and everything carries on as nothing would have
happened :).
In order to fix this we could add in the HdfsInputStream: 49
boolean tf = info.getFileSystem().rename(new Path(ret.actualPath), new
Path(ret.suffixedPath));
if (!tf) {
throw new IOException(This exception is thrown because the rename did
not succeded.);
}
And also in the HdfsConsumer: 150
try {
this.rwlock.writeLock().lock();
this.istream =
HdfsInputStream.createInputStream(fileStatuses[i].getPath().toString(),
this.config);
} catch (IOException ioe) {
log.info(ioe.getMessage()+ If the rename fails we move on to
the next file.);
continue;
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7318) Concurrency on HDFS Consumer not working efficiently
[
https://issues.apache.org/jira/browse/CAMEL-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348482#comment-14348482
]
Grzegorz Grzybek commented on CAMEL-7318:
-
You're right - for hdfs:// scheme, the rename just returns {{false}}.
Concurrency on HDFS Consumer not working efficiently
Key: CAMEL-7318
URL: https://issues.apache.org/jira/browse/CAMEL-7318
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.11.2
Reporter: Martha Obrinteschi
Assignee: Grzegorz Grzybek
Priority: Minor
Labels: concurrency, parallel
If we have two HDFS consumers the files are being processed twice (once by
each consumer, waiting one after the other) so the consumers are not working
in parallel. If we add this the consumers will work as a team and the
transfer will go faster.
This happens because there is no exception thrown (the rename method just
returns true or false and everything carries on as nothing would have
happened :).
In order to fix this we could add in the HdfsInputStream: 49
boolean tf = info.getFileSystem().rename(new Path(ret.actualPath), new
Path(ret.suffixedPath));
if (!tf) {
throw new IOException(This exception is thrown because the rename did
not succeded.);
}
And also in the HdfsConsumer: 150
try {
this.rwlock.writeLock().lock();
this.istream =
HdfsInputStream.createInputStream(fileStatuses[i].getPath().toString(),
this.config);
} catch (IOException ioe) {
log.info(ioe.getMessage()+ If the rename fails we move on to
the next file.);
continue;
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8060) Create data formats based on uniVocity parsers
[ https://issues.apache.org/jira/browse/CAMEL-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348497#comment-14348497 ] Claus Ibsen commented on CAMEL-8060: [~antoine.dessaigne] this component fails on windows testing. Do you mind taking a look and fix this? I am logging a ticket about this Create data formats based on uniVocity parsers -- Key: CAMEL-8060 URL: https://issues.apache.org/jira/browse/CAMEL-8060 Project: Camel Issue Type: New Feature Affects Versions: 2.14.0 Reporter: Antoine DESSAIGNE Assignee: Willem Jiang Labels: dataformat Fix For: 2.15.0 There's a library called [uniVocity-parsers|https://github.com/uniVocity/univocity-parsers] that provides implementations for reading and writing CSV files, fixed-width files and TSV files. It's quite fast according to [this benchmark|https://github.com/uniVocity/csv-parsers-comparison]. Obviously it may be biased since they're doing the benchmark, but they're also open enough to provide the source code of the benchmark so anyone can reproduce it. So it would be nice to have data formats that uses those parsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8434) Camel HDFS2 - Unable to consume an empty file
[ https://issues.apache.org/jira/browse/CAMEL-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348979#comment-14348979 ] Claus Ibsen commented on CAMEL-8434: I dont think this works as intended. As the consumer has no idempotency, so you would essentially end up reading the same file over and over again. Adding Thread.sleep(5000); In your empty file tests, causes java.lang.AssertionError: mock://result Received message count. Expected: 1 but was: 49931 at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1394) at org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1376) at org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:399) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:378) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:366) at org.apache.camel.component.hdfs.HdfsConsumerTest.testSimpleConsumerWithEmptyFile(HdfsConsumerTest.java:183) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) eg the file was read 49xxx times. The hdfs consumer really need a delete | idempotent option as the regular file consumer or something. Not sure what was the original thought behind the hdfs component consumer. Camel HDFS2 - Unable to consume an empty file - Key: CAMEL-8434 URL: https://issues.apache.org/jira/browse/CAMEL-8434 Project: Camel Issue Type: Bug Affects Versions: 2.14.2, 2.15.0 Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Fix For: 2.14.3, 2.15.0 It is not possible to consume an empty file with camel HDFS2 consumer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8434) Camel HDFS2 - Unable to consume an empty file
[ https://issues.apache.org/jira/browse/CAMEL-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-8434. - Resolution: Fixed Sorry for little mistake. FIxed in: * [master|https://git-wip-us.apache.org/repos/asf?p=camel.git;a=commitdiff;h=c1a74982c6e7d3ab05f40da320099a30d8f26d33] * [camel-2.14.x|https://git-wip-us.apache.org/repos/asf?p=camel.git;a=commitdiff;h=b552ceac1c3353e59b1ce261222ac6e91abddd1b] Camel HDFS2 - Unable to consume an empty file - Key: CAMEL-8434 URL: https://issues.apache.org/jira/browse/CAMEL-8434 Project: Camel Issue Type: Bug Affects Versions: 2.14.2, 2.15.0 Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Fix For: 2.14.3, 2.15.0 It is not possible to consume an empty file with camel HDFS2 consumer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8434) Camel HDFS2 - Unable to consume an empty file
[ https://issues.apache.org/jira/browse/CAMEL-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349221#comment-14349221 ] Grzegorz Grzybek commented on CAMEL-8434: - Messages read from hdfs are renamed according to readSuffix endpoint URI parameter Camel HDFS2 - Unable to consume an empty file - Key: CAMEL-8434 URL: https://issues.apache.org/jira/browse/CAMEL-8434 Project: Camel Issue Type: Bug Affects Versions: 2.14.2, 2.15.0 Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Fix For: 2.14.3, 2.15.0 It is not possible to consume an empty file with camel HDFS2 consumer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CAMEL-8434) Camel HDFS2 - Unable to consume an empty file
[ https://issues.apache.org/jira/browse/CAMEL-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reopened CAMEL-8434: - Camel HDFS2 - Unable to consume an empty file - Key: CAMEL-8434 URL: https://issues.apache.org/jira/browse/CAMEL-8434 Project: Camel Issue Type: Bug Affects Versions: 2.14.2, 2.15.0 Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Fix For: 2.14.3, 2.15.0 It is not possible to consume an empty file with camel HDFS2 consumer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8443) Add properties to route via DSL and XML, expose route properties via JMX
Jyrki Ruuskanen created CAMEL-8443: -- Summary: Add properties to route via DSL and XML, expose route properties via JMX Key: CAMEL-8443 URL: https://issues.apache.org/jira/browse/CAMEL-8443 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Jyrki Ruuskanen Priority: Minor Allow adding arbitrary String properties to a route, with .routeProperty(name, value) in Java DSL and routeProperty name=... value=.../ in XML. Expose getProperties(), getProperty(String name) and setProperty(String name, String value) for routes in JMX. Our use case: Add documentation to route in code and show it on a graph of Camel contexts, routes and endpoints in a running system. Graph is generated from JMX data. This would be nice data to show on hawtio as well. Although in this case we might want to use an explicit documentation variable rather than a reserved property name. Route has a properties map but that's used internally. These public properties would be held in a new map: publicProperties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8442) camel-univocity-parsers - Fails unit test on windows
Claus Ibsen created CAMEL-8442: -- Summary: camel-univocity-parsers - Fails unit test on windows Key: CAMEL-8442 URL: https://issues.apache.org/jira/browse/CAMEL-8442 Project: Camel Issue Type: Test Affects Versions: 2.15.0 Reporter: Claus Ibsen Fix For: 2.15.1, 2.16.0 Tests in error: UniVocityCsvDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityCsvDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:119 » TextParsing UniVocityFixedWidthDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityFixedWidthDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:118 » TextParsing UniVocityTsvDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityTsvDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:118 » TextParsing Tests run: 115, Failures: 0, Errors: 6, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7318) Concurrency on HDFS Consumer not working efficiently
[
https://issues.apache.org/jira/browse/CAMEL-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated CAMEL-7318:
Fix Version/s: 2.15.0
2.14.3
Concurrency on HDFS Consumer not working efficiently
Key: CAMEL-7318
URL: https://issues.apache.org/jira/browse/CAMEL-7318
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.11.2
Reporter: Martha Obrinteschi
Assignee: Grzegorz Grzybek
Priority: Minor
Labels: concurrency, parallel
Fix For: 2.14.3, 2.15.0
If we have two HDFS consumers the files are being processed twice (once by
each consumer, waiting one after the other) so the consumers are not working
in parallel. If we add this the consumers will work as a team and the
transfer will go faster.
This happens because there is no exception thrown (the rename method just
returns true or false and everything carries on as nothing would have
happened :).
In order to fix this we could add in the HdfsInputStream: 49
boolean tf = info.getFileSystem().rename(new Path(ret.actualPath), new
Path(ret.suffixedPath));
if (!tf) {
throw new IOException(This exception is thrown because the rename did
not succeded.);
}
And also in the HdfsConsumer: 150
try {
this.rwlock.writeLock().lock();
this.istream =
HdfsInputStream.createInputStream(fileStatuses[i].getPath().toString(),
this.config);
} catch (IOException ioe) {
log.info(ioe.getMessage()+ If the rename fails we move on to
the next file.);
continue;
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-7318) Concurrency on HDFS Consumer not working efficiently
[
https://issues.apache.org/jira/browse/CAMEL-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved CAMEL-7318.
-
Resolution: Fixed
Concurrency on HDFS Consumer not working efficiently
Key: CAMEL-7318
URL: https://issues.apache.org/jira/browse/CAMEL-7318
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.11.2
Reporter: Martha Obrinteschi
Assignee: Grzegorz Grzybek
Priority: Minor
Labels: concurrency, parallel
Fix For: 2.14.3, 2.15.0
If we have two HDFS consumers the files are being processed twice (once by
each consumer, waiting one after the other) so the consumers are not working
in parallel. If we add this the consumers will work as a team and the
transfer will go faster.
This happens because there is no exception thrown (the rename method just
returns true or false and everything carries on as nothing would have
happened :).
In order to fix this we could add in the HdfsInputStream: 49
boolean tf = info.getFileSystem().rename(new Path(ret.actualPath), new
Path(ret.suffixedPath));
if (!tf) {
throw new IOException(This exception is thrown because the rename did
not succeded.);
}
And also in the HdfsConsumer: 150
try {
this.rwlock.writeLock().lock();
this.istream =
HdfsInputStream.createInputStream(fileStatuses[i].getPath().toString(),
this.config);
} catch (IOException ioe) {
log.info(ioe.getMessage()+ If the rename fails we move on to
the next file.);
continue;
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-7318) Concurrency on HDFS Consumer not working efficiently
[
https://issues.apache.org/jira/browse/CAMEL-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348694#comment-14348694
]
Grzegorz Grzybek edited comment on CAMEL-7318 at 3/5/15 12:45 PM:
--
Thanks [~thadia] for investigating this issue. I've added [similar
check|https://github.com/apache/camel/commit/08eb8bf] to skip missing (failed
to rename) file.
was (Author: gzres):
Thanks [~thadia] for investigating this issue. I've added similar check to skip
missing (failed to rename) file.
Concurrency on HDFS Consumer not working efficiently
Key: CAMEL-7318
URL: https://issues.apache.org/jira/browse/CAMEL-7318
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.11.2
Reporter: Martha Obrinteschi
Assignee: Grzegorz Grzybek
Priority: Minor
Labels: concurrency, parallel
Fix For: 2.14.3, 2.15.0
If we have two HDFS consumers the files are being processed twice (once by
each consumer, waiting one after the other) so the consumers are not working
in parallel. If we add this the consumers will work as a team and the
transfer will go faster.
This happens because there is no exception thrown (the rename method just
returns true or false and everything carries on as nothing would have
happened :).
In order to fix this we could add in the HdfsInputStream: 49
boolean tf = info.getFileSystem().rename(new Path(ret.actualPath), new
Path(ret.suffixedPath));
if (!tf) {
throw new IOException(This exception is thrown because the rename did
not succeded.);
}
And also in the HdfsConsumer: 150
try {
this.rwlock.writeLock().lock();
this.istream =
HdfsInputStream.createInputStream(fileStatuses[i].getPath().toString(),
this.config);
} catch (IOException ioe) {
log.info(ioe.getMessage()+ If the rename fails we move on to
the next file.);
continue;
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7318) Concurrency on HDFS Consumer not working efficiently
[
https://issues.apache.org/jira/browse/CAMEL-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348694#comment-14348694
]
Grzegorz Grzybek commented on CAMEL-7318:
-
Thanks [~thadia] for investigating this issue. I've added similar check to skip
missing (failed to rename) file.
Concurrency on HDFS Consumer not working efficiently
Key: CAMEL-7318
URL: https://issues.apache.org/jira/browse/CAMEL-7318
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.11.2
Reporter: Martha Obrinteschi
Assignee: Grzegorz Grzybek
Priority: Minor
Labels: concurrency, parallel
Fix For: 2.14.3, 2.15.0
If we have two HDFS consumers the files are being processed twice (once by
each consumer, waiting one after the other) so the consumers are not working
in parallel. If we add this the consumers will work as a team and the
transfer will go faster.
This happens because there is no exception thrown (the rename method just
returns true or false and everything carries on as nothing would have
happened :).
In order to fix this we could add in the HdfsInputStream: 49
boolean tf = info.getFileSystem().rename(new Path(ret.actualPath), new
Path(ret.suffixedPath));
if (!tf) {
throw new IOException(This exception is thrown because the rename did
not succeded.);
}
And also in the HdfsConsumer: 150
try {
this.rwlock.writeLock().lock();
this.istream =
HdfsInputStream.createInputStream(fileStatuses[i].getPath().toString(),
this.config);
} catch (IOException ioe) {
log.info(ioe.getMessage()+ If the rename fails we move on to
the next file.);
continue;
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8060) Create data formats based on uniVocity parsers
[ https://issues.apache.org/jira/browse/CAMEL-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348544#comment-14348544 ] Antoine DESSAIGNE commented on CAMEL-8060: -- Sure Create data formats based on uniVocity parsers -- Key: CAMEL-8060 URL: https://issues.apache.org/jira/browse/CAMEL-8060 Project: Camel Issue Type: New Feature Affects Versions: 2.14.0 Reporter: Antoine DESSAIGNE Assignee: Willem Jiang Labels: dataformat Fix For: 2.15.0 There's a library called [uniVocity-parsers|https://github.com/uniVocity/univocity-parsers] that provides implementations for reading and writing CSV files, fixed-width files and TSV files. It's quite fast according to [this benchmark|https://github.com/uniVocity/csv-parsers-comparison]. Obviously it may be biased since they're doing the benchmark, but they're also open enough to provide the source code of the benchmark so anyone can reproduce it. So it would be nice to have data formats that uses those parsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8442) camel-univocity-parsers - Fails unit test on windows
[ https://issues.apache.org/jira/browse/CAMEL-8442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348553#comment-14348553 ] Antoine DESSAIGNE commented on CAMEL-8442: -- I'm on it ! camel-univocity-parsers - Fails unit test on windows Key: CAMEL-8442 URL: https://issues.apache.org/jira/browse/CAMEL-8442 Project: Camel Issue Type: Test Affects Versions: 2.15.0 Reporter: Claus Ibsen Fix For: 2.15.1, 2.16.0 Tests in error: UniVocityCsvDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityCsvDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:119 » TextParsing UniVocityFixedWidthDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityFixedWidthDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:118 » TextParsing UniVocityTsvDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityTsvDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:118 » TextParsing Tests run: 115, Failures: 0, Errors: 6, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8440) Components with windows test failures
[ https://issues.apache.org/jira/browse/CAMEL-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348825#comment-14348825 ] Claus Ibsen commented on CAMEL-8440: There is likely an issue in jetty with stream caching and files with windows, causing the file to not be deleted. Failed tests: HttpStreamCacheFileResponseTest.testStreamCacheToFileShouldBeDeletedInCaseOfResponse:51-Assert.assertEquals:555-Asse rt.assertEquals:118-Assert.failNotEquals:743-Assert.fail:88 There should be no files expected:0 but was:1 Tests run: 303, Failures: 1, Errors: 0, Skipped: 9 Components with windows test failures - Key: CAMEL-8440 URL: https://issues.apache.org/jira/browse/CAMEL-8440 Project: Camel Issue Type: Test Components: tests Reporter: Claus Ibsen Fix For: 2.16.0 The following components have/may have unit test failures - jms - apns - aws - beanstalk - barcode -elasticsearch - gae - hdfs - hdfs2 - mina - mina2 - mqtt - quartz2 - restlet - univercity-parser - zookeeper -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8442) camel-univocity-parsers - Fails unit test on windows
[ https://issues.apache.org/jira/browse/CAMEL-8442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348808#comment-14348808 ] Antoine DESSAIGNE commented on CAMEL-8442: -- Unfortunatly I didn't managed to reproduce this bugs. Can you attach the surefire report ? camel-univocity-parsers - Fails unit test on windows Key: CAMEL-8442 URL: https://issues.apache.org/jira/browse/CAMEL-8442 Project: Camel Issue Type: Test Affects Versions: 2.15.0 Reporter: Claus Ibsen Fix For: 2.15.1, 2.16.0 Tests in error: UniVocityCsvDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityCsvDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:119 » TextParsing UniVocityFixedWidthDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityFixedWidthDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:118 » TextParsing UniVocityTsvDataFormatUnmarshalSpringTest.shouldUnmarshalUsingIterator:117 » TextParsing UniVocityTsvDataFormatUnmarshalTest.shouldUnmarshalUsingIterator:118 » TextParsing Tests run: 115, Failures: 0, Errors: 6, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8441) Add required 3rd party dependencies to the BOM
[
https://issues.apache.org/jira/browse/CAMEL-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-8441.
-
Resolution: Fixed
Applied the patch into camel master branch and fix some build error and warning
message.
Add required 3rd party dependencies to the BOM
---
Key: CAMEL-8441
URL: https://issues.apache.org/jira/browse/CAMEL-8441
Project: Camel
Issue Type: Improvement
Reporter: Thomas Diesler
Assignee: Willem Jiang
Fix For: 2.15.0
For wildfly-camel we have to redefine a number of camel 3rd party
dependencies like this
{code}
!-- Camel version --
version.apache.camel2.14.1/version.apache.camel
!-- Camel 3rd party versions for artefacts that are not defined in
the BOM --
version.apache.abdera1.1.3/version.apache.abdera
version.apache.activemq5.10.0/version.apache.activemq
version.apache.cxf3.0.2/version.apache.cxf
version.apache.lucene4.6.1/version.apache.lucene
version.apache.mina2.0.7/version.apache.mina
version.beanshell2.0b5/version.beanshell
version.hapi2.2/version.hapi
{code}
These should probably come from the camel BOM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-8441) Add required 3rd party dependencies to the BOM
[
https://issues.apache.org/jira/browse/CAMEL-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-8441:
---
Assignee: Willem Jiang
Add required 3rd party dependencies to the BOM
---
Key: CAMEL-8441
URL: https://issues.apache.org/jira/browse/CAMEL-8441
Project: Camel
Issue Type: Improvement
Reporter: Thomas Diesler
Assignee: Willem Jiang
Fix For: 2.15.0
For wildfly-camel we have to redefine a number of camel 3rd party
dependencies like this
{code}
!-- Camel version --
version.apache.camel2.14.1/version.apache.camel
!-- Camel 3rd party versions for artefacts that are not defined in
the BOM --
version.apache.abdera1.1.3/version.apache.abdera
version.apache.activemq5.10.0/version.apache.activemq
version.apache.cxf3.0.2/version.apache.cxf
version.apache.lucene4.6.1/version.apache.lucene
version.apache.mina2.0.7/version.apache.mina
version.beanshell2.0b5/version.beanshell
version.hapi2.2/version.hapi
{code}
These should probably come from the camel BOM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8446) Camel Toolbox - Add support for @UriParam / @UriParams on component level
Claus Ibsen created CAMEL-8446: -- Summary: Camel Toolbox - Add support for @UriParam / @UriParams on component level Key: CAMEL-8446 URL: https://issues.apache.org/jira/browse/CAMEL-8446 Project: Camel Issue Type: Improvement Components: tooling Affects Versions: 2.15.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.16.0 See CAMEL-7999 and CAMEL-8444. We should allow options on component level to have same level of information as endpoints. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8443) Add properties to route via DSL and XML, expose route properties via JMX
[ https://issues.apache.org/jira/browse/CAMEL-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350051#comment-14350051 ] Claus Ibsen commented on CAMEL-8443: You can use description on a route to document it. Add properties to route via DSL and XML, expose route properties via JMX Key: CAMEL-8443 URL: https://issues.apache.org/jira/browse/CAMEL-8443 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Jyrki Ruuskanen Priority: Minor Allow adding arbitrary String properties to a route, with .routeProperty(name, value) in Java DSL and routeProperty name=... value=.../ in XML. Expose getProperties(), getProperty(String name) and setProperty(String name, String value) for routes in JMX. Our use case: Add documentation to route in code and show it on a graph of Camel contexts, routes and endpoints in a running system. Graph is generated from JMX data. This would be nice data to show on hawtio as well. Although in this case we might want to use an explicit documentation variable rather than a reserved property name. Route has a properties map but that's used internally. These public properties would be held in a new map: publicProperties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8447) Add camel-jetty module to publish the camel-jetty8 into maven repo
Willem Jiang created CAMEL-8447: --- Summary: Add camel-jetty module to publish the camel-jetty8 into maven repo Key: CAMEL-8447 URL: https://issues.apache.org/jira/browse/CAMEL-8447 Project: Camel Issue Type: Improvement Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 Here we just add the camel-jetty module which is based on the camel-jetty8 to provide the backward support, and we can switch the camel-jetty to camel-jetty9 once it is used by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8444) Camel Toolbox - Component properties to include setters
[ https://issues.apache.org/jira/browse/CAMEL-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8444. Resolution: Fixed Camel Toolbox - Component properties to include setters --- Key: CAMEL-8444 URL: https://issues.apache.org/jira/browse/CAMEL-8444 Project: Camel Issue Type: Improvement Components: tooling Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.15.0 The component options are currently discovered in apt from fields. But there is a few components that has delegate setters, such as JMS component. We can improve apt to discover those setters as well to be included. Or better to use the same set of @UriParam on component level as well so its the same all over. But that would need to migrate on all the components if going down that path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8447) Add camel-jetty module to republish the camel-jetty8 jar into maven repo
[ https://issues.apache.org/jira/browse/CAMEL-8447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8447: Description: Here we just add the camel-jetty module which is based on the camel-jetty8 to provide the pom backward support, and we can switch the camel-jetty to camel-jetty9 once it is used by default. (was: Here we just add the camel-jetty module which is based on the camel-jetty8 to provide the backward support, and we can switch the camel-jetty to camel-jetty9 once it is used by default.) Add camel-jetty module to republish the camel-jetty8 jar into maven repo Key: CAMEL-8447 URL: https://issues.apache.org/jira/browse/CAMEL-8447 Project: Camel Issue Type: Improvement Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 Here we just add the camel-jetty module which is based on the camel-jetty8 to provide the pom backward support, and we can switch the camel-jetty to camel-jetty9 once it is used by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8444) Camel Toolbox - Component properties to include setters
[ https://issues.apache.org/jira/browse/CAMEL-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350049#comment-14350049 ] Claus Ibsen commented on CAMEL-8444: Have the setters working now. We will look at supporting @UriParam / @UriParams in Camel 2.16 so its similar to as endpoints. Camel Toolbox - Component properties to include setters --- Key: CAMEL-8444 URL: https://issues.apache.org/jira/browse/CAMEL-8444 Project: Camel Issue Type: Improvement Components: tooling Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.15.0 The component options are currently discovered in apt from fields. But there is a few components that has delegate setters, such as JMS component. We can improve apt to discover those setters as well to be included. Or better to use the same set of @UriParam on component level as well so its the same all over. But that would need to migrate on all the components if going down that path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8444) Camel Toolbox - Component properties to include setters
[ https://issues.apache.org/jira/browse/CAMEL-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8444: --- Fix Version/s: (was: 2.16.0) 2.15.0 Camel Toolbox - Component properties to include setters --- Key: CAMEL-8444 URL: https://issues.apache.org/jira/browse/CAMEL-8444 Project: Camel Issue Type: Improvement Components: tooling Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.15.0 The component options are currently discovered in apt from fields. But there is a few components that has delegate setters, such as JMS component. We can improve apt to discover those setters as well to be included. Or better to use the same set of @UriParam on component level as well so its the same all over. But that would need to migrate on all the components if going down that path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8391) camel-mina / camel-mina2 - The new client mode fails test and seems to accept ghose
[ https://issues.apache.org/jira/browse/CAMEL-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-8391. - Resolution: Fixed Fix Version/s: (was: 2.15.1) 2.15.0 camel-mina / camel-mina2 - The new client mode fails test and seems to accept ghose --- Key: CAMEL-8391 URL: https://issues.apache.org/jira/browse/CAMEL-8391 Project: Camel Issue Type: Test Components: camel-mina, camel-mina2 Affects Versions: 2.15.0 Reporter: Claus Ibsen Assignee: Willem Jiang Fix For: 2.15.0 The client mode test fails sometimes, getting 2 messages. The 2nd message has empty body. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-6577) Camel Undertow Component
[ https://issues.apache.org/jira/browse/CAMEL-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned CAMEL-6577: --- Assignee: Grzegorz Grzybek Camel Undertow Component Key: CAMEL-6577 URL: https://issues.apache.org/jira/browse/CAMEL-6577 Project: Camel Issue Type: New Feature Components: extra Reporter: Aaron Walker Assignee: Grzegorz Grzybek Implement a new camel component which expose the undertow (https://github.com/undertow-io/undertow) web server as a camel component. This component will be similar to the jetty component but will probably only provide a producer endpoint. Undertow is licensed under ASL so it's compatible with camel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8447) Add camel-jetty module to republish the camel-jetty8 jar into maven repo
[ https://issues.apache.org/jira/browse/CAMEL-8447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8447: Summary: Add camel-jetty module to republish the camel-jetty8 jar into maven repo (was: Add camel-jetty module to publish the camel-jetty8 into maven repo) Add camel-jetty module to republish the camel-jetty8 jar into maven repo Key: CAMEL-8447 URL: https://issues.apache.org/jira/browse/CAMEL-8447 Project: Camel Issue Type: Improvement Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 Here we just add the camel-jetty module which is based on the camel-jetty8 to provide the backward support, and we can switch the camel-jetty to camel-jetty9 once it is used by default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-6577) Camel Undertow Component
[ https://issues.apache.org/jira/browse/CAMEL-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350084#comment-14350084 ] Willem Jiang commented on CAMEL-6577: - Hi Grzegorz, There is [a camel-undertow component|https://github.com/dsimansk/camel-undertow] that you may take a look. Regards, Willem Camel Undertow Component Key: CAMEL-6577 URL: https://issues.apache.org/jira/browse/CAMEL-6577 Project: Camel Issue Type: New Feature Components: extra Reporter: Aaron Walker Assignee: Grzegorz Grzybek Implement a new camel component which expose the undertow (https://github.com/undertow-io/undertow) web server as a camel component. This component will be similar to the jetty component but will probably only provide a producer endpoint. Undertow is licensed under ASL so it's compatible with camel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
