[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jaf-dev] MailcapCommandMap.createDataContentHandler blocking
|
Greets
We are still using javax.activation 1.1. Our server software is
frequently blocking on MailcapCommandMap.createDataContentHandler.
Would there be any performance benefit to us to upgrade to Jakarta JAF
1.2.0 vs Javax.activation 1.1? I see that your MailcapCommandMap
implementation, also synchronizes on createDataContentHandler. I guess
not, unless Jakarta Mail 16.5. MimeBodyPart.getContent calls this
function differently. Any suggestion would be appreciated. Thank you. Jamie
"filequeue-worker-704" #40881949 prio=5 os_prio=0 tid=0x00007fc4e0ba5000
nid=0x447c waiting for monitor entry [0x00007ff6561b4000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
javax.activation.MailcapCommandMap.createDataContentHandler(MailcapCommandMap.java:526)
- waiting to lock <0x00000002c3979d30> (a
javax.activation.MailcapCommandMap)
at
javax.activation.CommandMap.createDataContentHandler(CommandMap.java:221)
at
javax.activation.DataHandler.getDataContentHandler(DataHandler.java:615)
- locked <0x0000000743c5bf40> (a
javax.mail.internet.MimeBodyPart$MimePartDataHandler)
at javax.activation.DataHandler.getContent(DataHandler.java:542)
at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:683)
...
