Skip to main content
B
bha3986515
Participant
July 11, 2025
Answered

CF 2023 Update 15 cfmail error

  • July 11, 2025
  • 2 replies
  • 2440 views

CFMail will throw error after update 15 applied. Java version: 17.0.15+9-LTS-24

 

"Error","ajp-nio-127.0.0.1-8022-exec-3","07/11/25","13:24:45","","Bad type on operand stack
Exception Details:
Location:
coldfusion/mail/mod/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/mod/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
... The specific sequence of files included or processed is:

    Correct answer BKBK

    Key message:

    Reason:
Type 'org/bouncycastle/asn1/smime/SMIMEEncryptionKeyPreferenceAttribute' (current frame, stack[1]) is not assignable to 'org/bouncycastle/asn1/ASN1Encodable'

    The message suggests that, after the installation of Update 15, ColdFusion mistakenly uses an incompatible version of the Bouncy Castle library.

     

    A solution that has often worked for such update-installation issues is to delete the Felix cache. The procedure is as follows:

    1. stop ColdFusion;
    2. open the directory \cfusion\bin\felix-cache and delete everything from it, then
    3. restart ColdFusion.

     

    2 replies

    S
    skallaje
    Inspiring
    September 22, 2025

    I encountered this cfmail related issue after the update to cf2023u15. I was very suprised when I saw the error. But, thankfully, Adobe have resolved this issue in their latest update (cf2023u16). 

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    September 23, 2025

    Actually, no, that update earlier this month addressed only a single security issue--no bug fixes. At least that's what the update technotes said.

     

    But when they had said about that mail issue that "the next" update would address it, they meant the next bugfix update. Again this one had none, as it was released urgently. That's my understanding at least.

     

    As for why you may have had no mail problem this time, there are various factors that influence experiencing it. Just chalk it up as fortunate. 🙂 

    /Charlie (troubleshooter, carehart. org)
    BKBK
    Community Expert
    BKBKCommunity ExpertCorrect answer
    Community Expert
    July 11, 2025

    Key message:

    Reason:
Type 'org/bouncycastle/asn1/smime/SMIMEEncryptionKeyPreferenceAttribute' (current frame, stack[1]) is not assignable to 'org/bouncycastle/asn1/ASN1Encodable'

    The message suggests that, after the installation of Update 15, ColdFusion mistakenly uses an incompatible version of the Bouncy Castle library.

     

    A solution that has often worked for such update-installation issues is to delete the Felix cache. The procedure is as follows:

    1. stop ColdFusion;
    2. open the directory \cfusion\bin\felix-cache and delete everything from it, then
    3. restart ColdFusion.

     

    WolfShade
    WolfShade
    Legend
    August 18, 2025

    Will Adobe ever get this fixed?  Seems like the new stock response is to stop CF, delete Felix cache, restart.

     

    WolfShade

    WolfShade
    WolfShade
    Legend
    August 27, 2025
    quote

    [snip] But, much like my request to be able to actually EDIT a Solr Collection instead of blanking all the fields when the edit button is clicked, I have a feeling that's not going to happen any time, soon.


    By @WolfShade

     

    Wolf, can you clarify what you mean there? I find that the only operations for (buttons offered to the left of) solr collections are reload, index, optimize, purge, and delete. When you refer to wanting to "edit" a collection, what page are you using---where you refer here to there being "the edit button"? And what would you mean to be editing? Sincere questions. 

     

    Or might you be referring instead to a "PDF Service"? Those DO have an "edit" button--but I find it works just fine. 


    Hi, Charlie.

     

    I haven't had access to a CFAdmin since we lost our development environment, back when we were using CF Server 11, so the button for editing a Solr collection may have been removed.  Which would not surprise me, one bit.  I do not have access to staging or production CFAdmin, which is as it should be.  I'm a developer, not an admin.

     

    Back in the days of CF11, when logging on to CFAdmin and going to Solr Collections, click a collection and there was an edit button for the collection.  I assumed that one could just click EDIT, see what is currently the value of each field, make edits and save.  But when I click the edit button, all fields were blank.. no values in any of the fields.

     

    I went to Adobe Tracker and submitted an issue.  The link is:  https://tracker.adobe.com/#/view/CF-4159661

    I believe there are comments that have been removed from that ticket.  There was at least one other person who argued with one of the Adobe developers about being lazy and not fixing what needs to be fixed.

     

    In any case, it seems that Adobe has "fixed" this issue by removing the EDIT button from Collections, instead of actually making it possible to edit a collection.  There are developers who made collections who are no longer employed, here.  It's not always obvious what a collection was consuming, so an edit feature could be a boon.

     

    WolfShade

     

     

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices