This is an app exception and surely a timing issue. Rewrite the app
synchronously it will work so i sadly think it is on your side
Le 1 nov. 2014 22:24, Radhakrishna Kalyan nrkkal...@gmail.com a écrit :
Sorry
Please find the exception at the following url
I think async usage leadd to some random execution order. Ensure it is not
random then it should work
Le 2 nov. 2014 08:38, Nrkkalyan nrkkal...@gmail.com a écrit :
Hi
Thank you. Can you please elaborate what do you mean by synchronously.
Regards
/Kalyan
0733312584
PS: I am bad at
Hi,
I am sorry, I am not clear, what do you mean by random execution order.
Our requirement is, we have 2 tasks :
*Task1:* The @Asynchronous method, BatchManager.createBatchMessage() is
triggered by a different application through a http rest request.
As I mentioned previously, the
Hi,
Anyway after a while of reading and browsing I came to the following
conclusion. I have rewritten my BatchManager class to use
@TransactionManagement(TransactionManagementType.BEAN).
@Stateless
*@TransactionManagement(TransactionManagementType.BEAN) *
public class BatchManager{
@EJB
If you forget tge rollback your tx state will be broken and you ll
potentially get more issues.
Can be linked to jms, no jms rollback? Maybe add more logs (activemq ones)
Hi,
Anyway after a while of reading and browsing I came to the following
conclusion. I have rewritten my BatchManager class
See this discussion in the mailing list of OpenJPA:
http://openjpa.208410.n2.nabble.com/OpenJPA-support-for-JPA-2-1-when-td7584157.html
It looks like the JPA provider wouldn't be ready for Tomee@JavaEE 7.0.
I guess the Hibernate LGPL will be the candidate (not bundled in the tomee
zip).
This
Hi,
I hope you are talking about the missing userTransaction.rollback(); inside
the catch(Throwable ignore) block.
The code for sending of jms message can be moved out of the try block.
Because it is ok to get any exception while sending the jms message and
still the database batchorder entity
Le 2 nov. 2014 20:23, Radhakrishna Kalyan nrkkal...@gmail.com a écrit :
Hi,
I hope you are talking about the missing userTransaction.rollback();
inside
the catch(Throwable ignore) block.
Yes mainly, just ensure the transaction is finished
The code for sending of jms message can be moved
Le 2 nov. 2014 20:16, tibor17 tibo...@lycos.com a écrit :
See this discussion in the mailing list of OpenJPA:
http://openjpa.208410.n2.nabble.com/OpenJPA-support-for-JPA-2-1-when-td7584157.html
It looks like the JPA provider wouldn't be ready for Tomee@JavaEE 7.0.
I guess the Hibernate
Hi,
We don't know if the issue was with hibernate and some kind of
configuration.
One thing I can say that I had an annotation in the BatchOrder class.
@Entity
@Cacheable
@Cache(usage = CacheConcurrencyStrategy.READ_WRITE)
@Table(name = BATCH_ORDER)
public class BatchOrder extends BaseEntity {
Hi guys,
I just subscribed to the list, so this is my first email here.
I'm currently contributing to a Java EE 7 samples project here:
https://github.com/javaee-samples/javaee7-samples, and I just added profiles to
run the samples in TomEE and TomEE Embedded. Running the samples / tests we got
Hi
While nit running the 2.0 I dont expect them to work.
Le 2 nov. 2014 21:39, Roberto Cortez radcor...@yahoo.com.invalid a
écrit :
Hi guys,
I just subscribed to the list, so this is my first email here.
I'm currently contributing to a Java EE 7 samples project here:
12 matches
Mail list logo