Thanks for reply, Christian Mueller.
I am using Camel 2.8.0
Simple test with jdbcTemplate threw the same exception.
As a temporary remedy I simply have changed "createdAt" field type to
"varchar" in SQL DB. For now route works fine.
I think it proves your opinion that "SQL Server built in Ti
Thanks for advice Claus Ibsen-2.
As a temporary remedy I have changed createdAt field type to "varchar". For
now route works fine, but later I will try Camel 2.8.2 and will report with
results.
--
View this message in context:
http://camel.465427.n5.nabble.com/JDBC-exception-under-Linux-work
Thanks for reply, CLaus Ibsen-2 !
for testing reasons i have created CAMEL_MESSAGEPROCESSED manually.. i mean
via Microsoft SQL Server Management Studio, so i didn't use SQL query to
create the table yet. is this allowed?
in case of SQL Management Studio my table looks like this:
processorName
greetings !
i am kind of newbie in camel, and cant solve one problem with the EIP of
idempotent consumer. I tried to configure a simple route to filter out
duplicate messages using MessageID header. With InmemoryMessageIdRepository
it works just fine, but then i created CAMEL_MESSAGEPROCESSED tabl