I don't know why but I do know from experience that spring batch's transaction manager must be named "transactionManager" as I stated above. If you have another transaction manager defined elsewhere...
Type: Posts; User: symanco; Keyword(s):
I don't know why but I do know from experience that spring batch's transaction manager must be named "transactionManager" as I stated above. If you have another transaction manager defined elsewhere...
It probably is not a spring batch issue at all. It sounds more like you have non-deamon Threads running even after your main thread has finished executing.
Try changing the name of the bean from "jobTransactionManager" to "transactionManager"
<bean id="jobRepository"...
StaxEventItemWriter can only write to a file. However, you can easily solve your problem by taking the following steps -
First step: Use StaxEventItemWriter to write to a file.
Second step: Use...
Try using FieldSet.readString() instead of FieldSet.readDouble().
Once you have read the string, you can construct a Double by passing the string as constructor argument.
The most likely cause is that you annotated your Lot class with @XmlRootElement(name="lot") and at the same time, as I can see, your rootTagName is set to "lot".
That's why you see lot twice in the...
It sounds like you have some unwanted characters (most probably the BOM) in your xml file. To verify this, I suggest you manually create a simple XML file that resembles your actual input. Then use...
This should be pretty easy to do with JAXB marshaller. I would suggest you create a composite reader which will have a header reader (which should be read only once) and an item reader. For header...
It is very unlikely to go out of memory with StaxEventItemReader and commit-interval of just 1. I suspect the problem lies elsewhere but it's difficult to suggest anything without looking at the code...
Is the put(String, Object) method in ExecutionContext not good enough for your use case?
The only requirement to use this method is that the object must be serializable.
Thanks for your reply. That's exactly what I have done.
As you can see, the exception clearly states that the delegate writer is unable to open the file before writing in to it.
According to spring batch 2.1.8 doc, you can easily solve this problem by...
You can run spring batch without using database backed job repository. Take a look at the MapJobRepositoryFactoryBean class.
Javadoc is here...
I have an XML file which contains the following
<FragData asOfDate="01/01/2010">
<FragSet>
<FragData> <!-- This is the fragment root, I want to read -->
...
has anyone here had any luck with skip-limit on XML input or am I just asking a stupid question?
Is it possible to have skip-limit when the reader is StaxEventItemReader? I have tried this combination without any luck. Basically, as soon as the reader encounters a validation error in my XML...