Fw: locating blocked port

[debian-user@howorth.org.uk]

Haines Brown sent a reply directly to me instead of the list in
response to the post I made. I advised him to send his reply to the
list instead. He didn't, he just forwarded me another copy of his
reply. So here's his reply so anybody that's interested can read it. I
expect Haines may end up in my bitbucket soon.

Begin forwarded message:

Date: Wed, 1 Feb 2023 06:09:32 -0500
From: Haines Brown <haines@histomat.net>
To: debian-user@howorth.org.uk
Subject: Re: locating blocked port


On Tue, Jan 31, 2023 at 10:09:28PM +0000, debian-user@howorth.org.uk
wrote:
> Haines Brown wrote:  
> >   $ jabref  
...
> > 15:43:56.628 [AWT-EventQueue-0] INFO  net.sf.jabref.JabRefMain -
> > Arguments passed on to running JabRef instance. Shutting down.  
> 
> The last line there seems to imply there is already another instance
> of jabref running. Is that the case? What does
> 
> $ ps -fe | grep jabref
> 
> show, for example?  

Yes indeed. It showed two instances of jabref. I killed the processes
and now

  $ ps -fe | grep jabref
  haines    3597  3160  0 06:02 pts/1    00:00:00 grep jabref

So I should be able to start jabref:

  $ jabref
  06:04:08.576 [AWT-EventQueue-0] WARN  
    net.sf.jabref.logic.remote.server.RemoteListenerServerLifecycle - 
	  Port is blocked
  java.net.BindException: Address already in use
  ...
  06:04:08.591 [AWT-EventQueue-0] INFO  net.sf.jabref.JabRefMain - 
    Arguments passed on to running JabRef instance. Shutting down.

It seems that the jabref command i starts jabref twice. Hoewver the 
$ ps -fe command does not show them

-- 

     Haines Brown 
 /"\
 \ /  ASCII Ribbon Campaign
  X    against HTML e-mail 
 / \