Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"org.apache.openjpa.persistence.TransactionRequiredException: There is no managed transaction in progress to sync this EntityManager with" - deploying in fabric #11

Open
pgfox opened this issue Aug 8, 2014 · 0 comments
Open

"org.apache.openjpa.persistence.TransactionRequiredException: There is no managed transaction in progress to sync this EntityManager with" - deploying in fabric #11

pgfox opened this issue Aug 8, 2014 · 0 comments

Comments

@pgfox
Copy link

pgfox commented Aug 8, 2014

Sometimes seeing

org.apache.openjpa.persistence.TransactionRequiredException: There is no managed transaction in progress to sync this EntityManager with.

It seems that the start order of the bundles are causing this exception. In fabric (JBoss Fuse 6.1) the only way to influence start order is to import/export OSGi services between bundles.

adding a pull request with sample update that worked around the issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pgfox