I have step configured to run with SimpleAsyncTaskExecutor and for some reason if job is executed in WLS 11g running in production mode the job only utilizes two threads. If I execute it in another...
Type: Posts; User: _es; Keyword(s):
I have step configured to run with SimpleAsyncTaskExecutor and for some reason if job is executed in WLS 11g running in production mode the job only utilizes two threads. If I execute it in another...
If you have web-app inside your app, could you use it and web.xml to "publish" the persistence unit to jndi. I think with that it gets published without explicit call to any of your beans. If you...
The batch jobs are deployed as a part of ear in which there's also EJBs and Mdbs which use the same JPA-Daos as the batch jobs. The Daos inject the entitymanager with @PersistenceContext annotation....
Sorry, I wrote that in a hurry.
With JpaPagingItemReader I get this exception:
java.lang.IllegalStateException:
Exception Description: Cannot use an EntityTransaction while using JTA.
at...
I have a scenario where I need to read about 500 000 Entities from DB and create new entity for each + update couple status attributes in those 500 000 read. I need to run my batch jobs in Oracle WLS...
Oh, that delegate bean needs to implement interface in which the method is declared. My bean did not implement any interfaces and that is why it was not working. The job is no working after I created...
Hi, I have a item writer that delegates the work to another bean and it also needs some jobparameters in runtime. So because of that I tried to use late binding for the writer with scope step. The...
It seems that it is common issue with EclipseLink 1.2.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/JPASpring
Is it really so that there's no way of getting weaving work with EclipseLink...
I have currently exactly the same problem with Spring3.0.1-A and eclipselink 1.2.0. When I changed some fetchtypes from eager to lazy the problems started in JUnit tests. The same code still works...
I found out that the original problem was just because of false encoding I used in the writers. But the problem my test (in the previous post) shows up is still there.
I had scenario in which the data is read from DB then processed with ItemProcessor and wrote to xml file with StaxEventItemWriter using XStreamMarshaller (problem exists also with...
Hi, is this issue fixed also in 2.1.0 milestone releases? I am facing similar problems with 2.1.0.M4.