Opening a torrent tries to open a second instance of Vuze

[Farscape1]

If Vuze is already open and running and I try to open a new torrent instead of just adding it to the existing instance of Vuze it attempts to start up a whole new instance which fails because the first instance is already open.

Its getting dumb having to exit Vuze every single time I want to download something. Is there anything I can do to fix it?

[eroica20]

The same for me, anybody knows what to do with it? It's really annoying :/.

[pompeydigger]

Same issue here and have tried a few things to workaround it with no success.

[pompeydigger]

OK, I tried some more things and got to the bottom of it.

Port 6880 is the Vuze control port by default. I found it was still listening (using netstat) when Vuze was down. Tcpview showed that Hola is now using 6880 and that is screwing Vuze's ability to communicate internally, so it doesn't know that there is another instance running when you open a second torrent file.

Two possible fixes - remove Hola or change Vuze's control port, which is what I did. I edited 

C:\Program Files\Vuze\Azureus.exe.vmoptions

and added the line

-Dazureus.instance.port=45811

after checking that port 45811 wasn't in use.

Restarted Vuze and now it doesn't open a second copy any more. Job done.

Same issue here and have tried a few things to workaround it with no success.

 

[GaryE]

I can not fathom why that worked but I am glad you found a solution!  Also thanks for sharing the solution with all of us!

[pompeydigger]

I can not fathom why that worked but I am glad you found a solution!  Also thanks for sharing the solution with all of us!

 

My understanding is that Vuze should, by default, open the port 6880 once it is started up (for the first time) and listen on that port for incoming messages. In my case Hola starts before Vuze and grabs port 6880. When I open Vuze for the first time there is no warning that port 6880 cannot be used to start a listener (maybe there should be). It continues and displays the GUI etc. When I then open a torrent file by for instance doubleclicking on a downloaded torrent, the filetype is associated with the Vuze Launcher and a second instance of Vuze opens. The second instance sends a message out on port 6880 to see if there is already an instance running. Hola will probably squash that message and not bother replying to it. The second instance of Vuze thinks the coast is clear and continues to launch a full instance of the GUI etc. which fails a bit further down the line because of the lock file. 

By changing the default port to something unused the mechanism can work properly and in this case, the second instance of Vuze just passes the torrent info that it was opened with back to the first instance and shuts itself down seamlessly.

Hope that helps you see what is happening under the covers.

[GaryE]

That explanation actually . . . makes perfect sense.  I have no idea if that is what is really happening . . . but it does make sense.

I am just not sure if there is a lock file for ports in use.  At least I am pretty sure there is no such mechanism in Unix/Mac Os X.  As for Windows . . . no idea.  My 30 seconds of research was inconclusive!  LOL

[fiskmann]

i've tried what you guys have said. still not having any luck getting Vuze to stop trying to open a second window.

[HawkDreams]

OK, I tried some more things and got to the bottom of it.

Port 6880 is the Vuze control port by default. I found it was still listening (using netstat) when Vuze was down. Tcpview showed that Hola is now using 6880 and that is screwing Vuze's ability to communicate internally, so it doesn't know that there is another instance running when you open a second torrent file.

Two possible fixes - remove Hola or change Vuze's control port, which is what I did. I edited 

C:\Program Files\Vuze\Azureus.exe.vmoptions

and added the line

-Dazureus.instance.port=45811

after checking that port 45811 wasn't in use.

Restarted Vuze and now it doesn't open a second copy any more. Job done.

Same issue here and have tried a few things to workaround it with no success.


 

Thank you!  I tried posting my issue with the UI freezing (though still operating normally), but it disappeared after posting.  For some reason my Windows 10 took over port 6880 and it was evidently causing all kinds of issues from freezing to attempting to open a second copy of Vuze when adding a torrent through a magnet link.  I was getting the port already in use for 6880 and did not comprehend how to change the listening port from the Wiki.  Reading your post, I added the -Dazureus.instance.port=45811 line to mine, changing the port number for my PC and all my problems vanished.

Been searching for 3 weeks how to resolve this!

[bugsy2]

what will happen if you ignore this warning as the warning i get says bad things will happen?