Hi
I have created a ticket to remove that plugin, we dont use it, and
dont want to maintain it
https://issues.apache.org/jira/browse/CAMEL-4065
On Mon, Jun 6, 2011 at 9:34 PM, Krsmanovic, Dragisa
wrote:
> After upgrading to Camel 2.7.2, we are seeing this error when we try to
> generate Camel
Pity about the logs, but you can log exceptions to a different
file/db/email/etc and keep it longer, or check it more frequently.
Taariq
On 07 Jun 2011, at 4:45 AM, bbuzzard wrote:
> Environment:
> ActiveMQ-5.4.2-fuse-01-00.
> jdk1.6.0_25
> Linux (Lenny)
>
> Problem:
> I have several thread
Environment:
ActiveMQ-5.4.2-fuse-01-00.
jdk1.6.0_25
Linux (Lenny)
Problem:
I have several threads pulling down files from a remote FTP server. These
threads run great for a few weeks then one of them dies. My logs rolled
over before I realized I the thread was gone so I missed the exception.
Hi,
I have a requirement to use Java DSL to dynamically try to connect to broker
and subscribe to multiple topicS. Since there are MANY brokers and topics,
I'm thinking bout using properties such as follows:
brokerUrl=url1,userId=userid1,pwd=pwd1,topicName=tname1
...
brokerUrl=url2,userId=userid2
Thanks Andreas, this fix worked for me. Appreciate the help!
Regards,
Jim
On 6/6/2011 12:12 AM, Andreas Kuhtz wrote:
Found out that you must return at least one converter to make camel happy ...
Use this updated method:
public Set> findAnnotated(Class
annotation,
After upgrading to Camel 2.7.2, we are seeing this error when we try to
generate Camel report using mvn site.
Perviously (version 2.5.0), it would just create an empty TypeConverter(s)
list. But now, it causes whole build to fail.
Is there a workaround ? Has anyone seen this before ?
[INFO] Err
Hi Claus,
that fix did the job!
Thanks, Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Build-break-in-camel-jms-tp4458546p4458957.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Okay I have commited a fix. Fell free to test it on Windows so we know it works.
On Mon, Jun 6, 2011 at 4:35 PM, bvahdat wrote:
> Hi,
>
> I've the same behaviour on Windows-OS...
>
> On Windows-OS we get:
> Failed to create Producer for endpoint:
> Endpoint[activemq://queue:foo?testConnectionOnS
Hi,
I've the same behaviour on Windows-OS...
On Windows-OS we get:
Failed to create Producer for endpoint:
Endpoint[activemq://queue:foo?testConnectionOnStartup=true]. Reason:
org.apache.camel.FailedToCreateProducerException: Failed to create Producer
for endpoint: Endpoint[activemq://queue:foo?t
Hmm
I just ran it from trunk
---
T E S T S
---
Running org.apache.camel.component.jms.JmsTestConnectionOnStartupTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.807 sec
R
Hi,
This looks like a simple change in the error message returned, but I don't know
the history to be sure:
Environment:
Apache Maven 3.0.2 (r1056850; 2011-01-09 00:58:10+)
Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_25\jre
Default locale:
The SMX components are JBI components and in SMX 4.x+ they are legacy.
See this blog about JBI being dead/legacy
http://gnodet.blogspot.com/2010/12/thoughts-about-servicemix.html
In SMX 4.x+ Camel is the preferred routing engine. So use Camel and
use SMX to host your Camel apps.
On Mon, Jun 6,
Hi Claus,
a similar question while comparing Apache Camel & Apache ServiceMix came
also into my mind many times. Somehow I've got the feeling that the wheel
has been reinvented either by ServiceMix or Camel! Just as an example what's
your opinion about the following two "wheels"?
http://servicemi
Found out that you must return at least one converter to make camel happy ...
Use this updated method:
public Set> findAnnotated(Class
annotation,
String... packageNames) {
// we must return at least 1 converter
Set> annotedCla
Try to create a small unit tests that shows the issue. Then we can use
that in the trunk source code to track down whats going on.
On Mon, Jun 6, 2011 at 11:46 AM, Xavier Coulon wrote:
> Hello,
>
> I just switch back to Camel 2.6.0 and it works fine : no inflight pending
> exchange in the file v
Hello,
I just switch back to Camel 2.6.0 and it works fine : no inflight pending
exchange in the file validation route.
BTW : the problem exists with the lastest release of Camel (2.7.2).
Any idea of what I should look at in detail in the Validation component ?
Thank you in advance
Best regards,
16 matches
Mail list logo