Long thread names make Thread Dump view hard to use

[v3rm0n]

When thread names are very long, it makes the Thread Dump view hard to use since the thread name pushes the timeline out of the screen.

It's a bit stupid, but there's a third party library that we need to use that for some reason uses very very long thread names (350 characters) which makes the view unusable for us. Unfortunately there is not a way to customize the thread naming. Maybe some wrapping could be added for long names?
If this makes sense then I could try implementing it myself.

The library in question is com.ibm.mq:com.ibm.mq.jakarta.client

and it names threads like this (redacted some identifying information) RcvThread: com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection@710892740[qmid=XXXXXXP1_2017-10-07_13.38.13,fap=15,channel=DUMMYNAME,ccsid=1111,sharecnv=10,hbint=300,peer=example.com/127.0.0.1(12345),localport=38649,ssl=TLS_RSA_WITH_AES_256_CBC_SHA256,peerDN="CN=cn name here, OU=ou here, O=org here",issuerDN="CN=isser cn here, OU=ou here, O=org here"]

[ulischulte]

Hi @v3rm0n
You are welcome to implement it like this. We look forward to your participation. If you need any help with the implementation, please feel free to contact us.

[v3rm0n]

I experimented with a view different ways how to solve this by modifying the threads__thread-name class (750px is a bit arbitrary, I just multiplied the column width of 250px with 3):

• Add max-width: 750px and text-wrap: wrap, looks ugly

• Add only max-width: 750px looks better but losing information

• Add only max-width: 750px and show full text on hover

.threads__thread-name:hover {
  height: auto;
  overflow: visible;
  white-space: normal;
}

Initially looks like the second one but if you hover over the thread name it looks like the first so you can see the thread name if needed.

• Instead of making overflow visible on hover, show the full thread name a tooltip (didn't try it out)

Are any of these solutions acceptable?

[erikpetzold]

As no one complained about this before and all these solutions won't affect existing users with shorter thread names, I would say pick the solution that fits best for you.

In general I would prefer a solution that does not lose information, so probably not option 2. As you already have a working solution for option 3, just pick this one?