Skip to main content
J
jrathmann01
Participant
July 10, 2025
해결됨

CF2021 CFMAIL Error after update 21

  • July 10, 2025
  • 4 답변들
  • 3654 조회

Trying to wrap my head around this new error I have popping up trying to send an email. This seems to have worked through update 19. I cannot speak for Update 20 because we updated to 20 and then 21 within a few days of each other. I am running the latest approved JVM 11.0.27 from Adobe's site, on Server 2019. 

 

Below is the error I am seeing when I try to send. The page does not end up doing a redirect, but hangs after submit.  Running out of ideas for how to resolve, I have followed another Adobe post but that didn't work either so I reverted back to the old bouncy castle: Solved: CFMAIL Stopped Working After CF2018 Update 14 - Adobe Product Community - 13035484

Any suggestions would be welcome, thanks!


Jul 10, 2025 12:21:07 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [CfmServlet] in context with path [] threw exception [Servlet execution threw an exception] with root cause
java.lang.VerifyError: Bad type on operand stack
Exception Details:
Location:
coldfusion/mail/MailImpl.signMail(Ljavax/mail/internet/MimeMessage;Ljavax/mail/Session;)Ljavax/mail/internet/MimeMessage; @238: invokevirtual
Reason:
Type 'org/bouncycastle/asn1/smime/SMIMEEncryptionKeyPreferenceAttribute' (current frame, stack[1]) is not assignable to 'org/bouncycastle/asn1/ASN1Encodable'
Current Frame:
bci: @238
flags: { }
locals: { 'coldfusion/mail/MailImpl', 'javax/mail/internet/MimeMessage', 'javax/mail/Session', 'java/security/KeyStore', '[Ljava/security/cert/Certificate;', 'java/security/PrivateKey', 'org/bouncycastle/asn1/ASN1EncodableVector', 'java/security/cert/X509Certificate', 'java/lang/String', 'org/bouncycastle/asn1/cms/IssuerAndSerialNumber' }
stack: { 'org/bouncycastle/asn1/ASN1EncodableVector', 'org/bouncycastle/asn1/smime/SMIMEEncryptionKeyPreferenceAttribute' }
Bytecode:
0000000: 2ab4 0028 c600 212a b400 28b6 009e b600
0000010: 5e99 0014 bb00 e159 2ab4 0028 b700 e2b6
0000020: 00e3 9a00 0fbb 00e4 592a b400 28b7 00e5
0000030: bf2a b400 2bc7 000b 2a2a b400 2ab5 002b
0000040: 2a2a b400 282a b400 2ab7 00e6 4e2a b400
0000050: 29c6 0010 2ab4 0029 b600 9eb6 005e 9a00
0000060: 0c2a 2a2d b700 e7b5 0029 2d2a b400 29b6
0000070: 00e8 3a04 1904 c600 0919 04be 9a00 0fbb
0000080: 00e9 592a b400 29b7 00ea bf2d 2ab4 0029
0000090: 2ab4 002b b600 ebb6 00ec c000 ed3a 05a7
00000a0: 000f 3a06 bb00 ef59 1906 b700 f0bf bb00
00000b0: f159 b700 f23a 0619 0403 32c0 00de 3a07
00000c0: 1907 b600 f3b9 00f4 0100 3a08 bb00 f559
00000d0: bb00 f659 1908 b700 f719 07b6 00f8 b700
00000e0: f93a 0919 06bb 00fa 5919 09b7 00fb b600
00000f0: fc19 06bb 00fd 59b2 00fe b700 ffb6 00fc
0000100: bb01 0059 b701 013a 0a13 0102 1905 b901
0000110: 0301 00b6 0104 9900 09b2 0105 a700 0613
0000120: 0106 3a0b bb01 0759 b701 0812 b5b6 0109
0000130: bb01 0a59 1906 b701 0bb6 010c 190b 1905
0000140: 1907 b601 0d3a 0c19 0a19 0cb6 010e bb00
0000150: 1959 b700 1a3a 0d19 0d19 0403 32b9 008d
0000160: 0200 5719 0abb 010f 5919 0db7 0110 b601
0000170: 1119 0a2b b601 123a 0ebb 00bd 592c b701
0000180: 133a 0f2b b601 143a 1019 10b9 0115 0100
0000190: 9900 1519 0f19 10b9 0116 0100 c001 17b6
00001a0: 0118 a7ff e719 0f19 0eb6 0099 190f b600
00001b0: a519 0fb0 3a04 1904 bf3a 04bb 0119 5919
00001c0: 04b7 011a bf
Exception Handler Table:
bci [139, 159] => handler: 162
bci [77, 435] => handler: 436
bci [77, 435] => handler: 441
Stackmap Table:
same_frame(@37)
same_frame(@49)
same_frame(@64)
append_frame(@97,Object[#679])
same_frame(@106)
append_frame(@127,Object[#680])
same_frame(@139)
same_locals_1_stack_item_frame(@162,Object[#681])
append_frame(@174,Object[#682])
full_frame(@287,{Object[#455],Object[#603],Object[#606],Object[#679],Object[#680],Object[#682],Object[#683],Object[#652],Object[#453],Object[#684],Object[#685]},{})
same_locals_1_stack_item_frame(@290,Object[#453])
full_frame(@393,{Object[#455],Object[#603],Object[#606],Object[#679],Object[#680],Object[#682],Object[#683],Object[#652],Object[#453],Object[#684],Object[#685],Object[#453],Object[#686],Object[#608],Object[#607],Object[#603],Object[#687]},{})
same_frame(@421)
full_frame(@436,{Object[#455],Object[#603],Object[#606],Object[#679]},{Object[#632]})
same_locals_1_stack_item_frame(@441,Object[#612])

    최고의 답변: Charlie Arehart

    Yep. See the technote for the technote for update 21. There’s a new “known issue” bullet that was added today, showing that this problem is solved by stopping cf and deleting the felix-cache folder, in cfusion/bin.

     

    (Note that if you're running multiple instances, it would be [instancename]/bin.)

     

    Let us know if it works for you both. 

    4 답변

    M
    Michael Guenther
    Participant
    July 18, 2025

    Had the same issue.

    Weird things happened for me when I cleared the felix-cache.

    I restarted the service running the instance, and it just hung there until the service restart timed out.  No errors in the coldfusion-error.log, exception.log, or server.log.  About 30 or new bundle folder were created in the felix-cache. And going to the website ended up giving me a 500 error.

     

    All in all, it took four attempts to restart the service before it 'took'. About 160 new bundle folders created all told.

     

    So strange - but it works.  I'd hate to have to do this on my QA or PRD system for all the instances we have running....

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    July 12, 2025

    Thanks, folks, for the kind regards. Of course, the real thanks goes to those who first announced the resolution in comments on the Adobe forum post here about announcing the update--then to Adobe for adding the pointer in the known issue.

     

    As for what this says in the larger sense about cf and Adobe's stewardship, I'll just say it's a big ship with lots of officers and crew--and corporate bigwigs above them. They don't all know everything that's going on, let alone what each other are doing, to affect the passenger experience. It's doesn't excuse failures. I just mean there are sometimes reasons things can't change until there's full alignment of intent, purpose, action, and accountability.

     

    And I don't sense there's a true captain, instead different people with leadership roles (cruise director, executive chef, head of housekeeping, head of engineering, head of sales, etc), each responsible for their own area but none with absolute authority to command resolution of glaring issues, let alone a commitment to "go down with the ship" before all else fails.

     

    Oh well. There are other cruise lines. 🙂 Or we who choose to ride this ship seemingly must accept that it is what it is, until somehow something changes. Often things do, sometimes things don't. It's never really been clear how to truly effect significant change. It's not even about "who you know". Again, see what I said above. So I help how I can and celebrate little victories (like that technote being updated for this issue). 

    /Charlie (troubleshooter, carehart. org)
      Charlie Arehart
      Community Expert
      Charlie ArehartCommunity Expert답변
      Community Expert
      July 11, 2025

      Yep. See the technote for the technote for update 21. There’s a new “known issue” bullet that was added today, showing that this problem is solved by stopping cf and deleting the felix-cache folder, in cfusion/bin.

       

      (Note that if you're running multiple instances, it would be [instancename]/bin.)

       

      Let us know if it works for you both. 

      /Charlie (troubleshooter, carehart. org)
        T
        TuesdayM
        Participating Frequently
        July 11, 2025

        Hi Charlie - big thanks again! You are of great help! Much appreciated!
        Adobe is not delevering on its own promise: "Build robust applications with ColdFusion". The latests updates are far from robust. As big and (very) longtime CF aficionados (since Allaire) we are a tiny bit disappointed.
        But keep up the good work 🙂

          C
          chrisb84545572
          Participant
          July 11, 2025

          I'm having the same issue.  Known good code working with CF2021 Update 20 is not working with CF2021 Update 21.  If I comment out the <cfmail> block in that known good code, it works as expected.  

          I cannot find anything in coldfusion-out.log, exception.log or coldfusion-error.log related to the issue.  The app now returns an HTTP 500 error page to the browser.

          C
          chrisb84545572
          Participant
          July 11, 2025

          Forgot add I'm running OpenJDK 11.0.24

          약관 및 조건Accessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices