Page 1 of 1

Error when starting Oxygen. Cannot bind - ro.sync.ui.applica

Posted: Wed Oct 22, 2008 9:32 pm
by pstein
When I start Oxygen 9.1 by calling oxygen.bat then I got the following error
in the command prompt:

11:18:45,531 0 ERROR [ main ] ro.sync.ui.application.ApplicationLauncher - Cannot bind
11:18:53,875 8344 FATAL [ OxygenSingletonChecker-Thread ] ro.sync.ui.application.A - java.lang.NullPointerException
java.lang.NullPointerException
at ro.sync.exml.CA.?(Unknown Source)
at ro.sync.ui.application.A.run(Unknown Source)


What is the reason?

Oxygen seems to work anyway.

Peter

Re: Error when starting Oxygen. Cannot bind - ro.sync.ui.applica

Posted: Thu Oct 23, 2008 9:04 am
by sorin_ristache
Hello,

The reason is that Oxygen tries to detect another running instance of Oxygen so that a second instance is not started in parallel but this detection fails, probably because a firewall program does not allow Oxygen to bind a connection to a local port of the machine. The only possible bad consequence is that if you start a second instance of Oxygen it will fail to detect the first running instance and it will start up instead of just displaying a message about the first running instance and passing any parameters it received to that running instance.

If you really want to start a second instance of Oxygen, a third one etc. that is possible by setting the parameter -Dcom.oxygenxml.MultipleInstances=true in the startup script but by default only one instance of Oxygen is set to run on a system.


Regards,
Sorin

Re: Error when starting Oxygen. Cannot bind - ro.sync.ui.applica

Posted: Sat Oct 25, 2008 11:35 am
by pstein
Wouldn't it be better to suppress this warning message in ornder not to confuse the user wether Oxygen is working correctly or not?

Or at least to offer an option to suppress this warning?

Peter

Re: Error when starting Oxygen. Cannot bind - ro.sync.ui.applica

Posted: Mon Oct 27, 2008 5:19 pm
by sorin_ristache
Hello,

It is only a warning message and it is displayed only in the command line console that started the script. We will suppress it from the console in the next version.


Thank you for pointing it out,
Sorin