Hibernate Exception when publishing organization

Submitted by g.lapierre on Fri, 01/22/2016 - 15:40
1
0
-1

I imported (XML) my organization and now I am trying to publish it. I get an exception during the synch:

An error occured during synchronization
org.bonitasoft.studio.actors.operation.PublishOrganizationOperation.run(PublishOrganizationOperation.java:106)
org.bonitasoft.studio.actors.ui.handler.InstallOrganizationHandler.execute(InstallOrganizationHandler.java:70)
org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
org.bonitasoft.studio.actors.ui.wizard.SynchronizeOrganizationWizard$1.run(SynchronizeOrganizationWizard.java:115)
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

I can see a org.hibernate.HibernateException: Current transaction is not in progress () in the details but the "copy" does not seem to take it?

Any clue on how to publish my organization or a way to hack around?

I am using Bonita Studio 7.1.3 Community edition.

Edit: if I reduce the number of users in the organization this works. But I wanted to match as much as possible my real environment

HibernateException
Organisation
Import Publish Organisation

Comments

Submitted by antoine.mottier on Fri, 01/22/2016 - 16:02

Hi,

Is it possible for you to share your organization XML file? That can help to reproduce the issue.

Thanks

Permalink
Submitted by g.lapierre on Fri, 01/22/2016 - 16:21

I can share it privately. Most of the data is already public but not in an XML and easy to reuse file!
(sorry I posted an answer, still new to this forum!)

Permalink
Submitted by Sean McP on Fri, 01/22/2016 - 20:06

You've custom built the XML from another source.

I've done this before and had the same error.

Make sure your XML is fully compliant with the requirements. Even Upper/Lower case can make this fail.

regards
Seán

Permalink
Submitted by g.lapierre on Mon, 01/25/2016 - 07:45

If it was a XML problem, I believe the sync process would fail even with few users.
I will try to produce an anonymised version of the XML file to share on this board

Permalink
Submitted by g.lapierre on Mon, 01/25/2016 - 09:11

Here is an anonymised version of the XML file:
https://www.dropbox.com/s/bla4m3d2d4kie6l/organisation.zip

Permalink
1 answer

Submitted by antoine.mottier on Mon, 01/25/2016 - 11:01
1
+1
-1
This one is the BEST answer!

I did some test and confirm the issue with Community edition 7.1.5.

It seems that processing the organization file take longer then the database transaction timeout. So the workaround would be to increase the transaction timeout. For Tomcat you need to edit the bitronix-config.properties file located in conf folder and add the bitronix.tm.timer.defaultTransactionTimeoutparameter (value unit is second).

Note that the feature provided in Subscription edition to synchronize organization with an LDAP server doesn't have this kind of issue as one transaction is used per user.

Comments

Submitted by g.lapierre on Mon, 01/25/2016 - 13:05

Thanks it worked.
I know there is a subscription based ldap sync but for our need we do not have the budget for it. Plus the main purpose here is to validate the Bonita Solution on simple cases. In the future we might switch to a subscription based bonita bpm solution.

Permalink
Notifications