Problem with starting swing-client.product / bundle org.adempiere.base_1.0.0 deadlock?

79 views
Skip to first unread message

Daniel Tamm

unread,
Apr 4, 2013, 9:10:15 AM4/4/13
to idem...@googlegroups.com
I've tried on two separate workstations to get revision 8871 to start the swing-client product but it gets me the exact same error.
When trying to launch the swing-client it takes a while (a few seconds) and then some timeout and everything ends in a long error message where the beginning goes like this:

!MESSAGE While loading class "org.compiere.model.ServerStateChangeListener", thread "Thread[Start Level Event Dispatcher,5,main]" timed out waiting (4ms) for thread "Thread[Start Level Event Dispatcher,5,main]" to finish starting bundle "org.adempiere.base_1.0.0.qualifier [22]". To avoid deadlock, thread "Thread[Start Level Event Dispatcher,5,main]" is proceeding but "org.compiere.model.ServerStateChangeListener" may not be fully initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "reference:file:/D:/dev/wkspc-notima/idempiere/org.adempiere.base/" by thread "Start Level Event Dispatcher".

I think the problem has something to do with startup-configuration of the plugins and what depends on what. It seems to be some kind of deadlock.

I'm attaching the log.

The server-product is startable but not the swing-client.

Any ideas?

Daniel Tamm

unread,
Apr 4, 2013, 9:23:42 AM4/4/13
to idem...@googlegroups.com
Revision 8797 works without above described problem.

Carlos Antonio Ruiz Gomez

unread,
Apr 4, 2013, 9:32:54 AM4/4/13
to idem...@googlegroups.com
Daniel, I don't have revision 8871 in my repository and probably my
revision 8797 is different than yours.
In mercurial we need to refer to the changeset uuid.

Can you please test the changeset af5bb320db96 that I just pushed.

Regards,

Carlos Ruiz


On 04/04/13 08:23, Daniel Tamm wrote:
> Revision 8797 works without above described problem. --

Daniel Tamm

unread,
Apr 4, 2013, 9:36:51 AM4/4/13
to idem...@googlegroups.com
The problem disappeared when I unclicked old versions org.restlet and only included the latest when choosing plugins. (2.1.2 instead of 2.0.15)

Daniel Tamm

unread,
Apr 4, 2013, 10:04:04 AM4/4/13
to idem...@googlegroups.com
It seems as if the "-Dosgi.compatibility.bootdelegation=true" causes problem as well.

I removed the bootdelegation and made sure that only org.restlet 2.1.2, org.restlet.ext.net 2.1.2 and org.restlet.ext.servlet 2.1.2 and org.restlet.ext.ssl 2.1.2 were enabled (not 2.0.x)

In the file you pushed no org.restlet were enabled and it didn't work either :-(

I have a working launch config now. Should I e-mail it?

/Daniel

Daniel Tamm

unread,
Apr 4, 2013, 2:21:44 PM4/4/13
to idem...@googlegroups.com
The last commit you did fixed the problem. Just checked out a fresh version on my home workstation and it worked right away :-) Thanks!


Den torsdagen den 4:e april 2013 kl. 15:32:54 UTC+2 skrev Carlos Antonio Ruiz Gomez:
Reply all
Reply to author
Forward
0 new messages