JIRA
  1. JIRA
  2. JRA-25836

Mails are not sent after upgrade from 4.4 to 4.4.1 on Redhat in a Virtual Machine

    Details

      Description

      After installation of version 4.4.1 (was 4.4), the notification emails rest in the mail queue and are not sent anymore. When clicking on "Flush mail queue", all mails are sent immediately without any problems. No errormessage (including OutOfMemoryException) to find in the logfiles.

        Issue Links

          Activity

          Hide
          Robert Smart [Atlassian] added a comment -

          Hi Brooke,

          This unfortunately is not the problem you were seeing. I am glad to see you could solve your problem locally. It looks to me like you were hit with a different problem to the one that customers were experiencing here.

          Cheers,

          Robert Smart.
          bugwrangler.

          Show
          Robert Smart [Atlassian] added a comment - Hi Brooke, This unfortunately is not the problem you were seeing. I am glad to see you could solve your problem locally. It looks to me like you were hit with a different problem to the one that customers were experiencing here. Cheers, Robert Smart. bugwrangler.
          Hide
          Jan Lichter added a comment -

          Hi,

          now i am confused, too. We are running Jira (4.4.1) on a Suse Enterprise Server 10, physical machine, no vm. And we have also the class loading problem:

          Exception in thread "QuartzWorker-1" java.lang.NoClassDefFoundError: com/mindprod/csv/CSVReader
          at com.javahollic.jira.emh.processor.CSVFieldProcessor.getFieldMap(CSVFieldProcessor.java:64)
          at com.javahollic.jira.emh.processor.CSVFieldProcessor.extractFieldsAndBody(CSVFieldProcessor.java:176)
          at com.javahollic.jira.emh.processor.CSVFieldProcessor.getDirectiveCount(CSVFieldProcessor.java:218)
          at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:116)
          at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:87)
          at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:186)
          at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:60)
          at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
          at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
          at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
          at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
          Caused by: java.lang.ClassNotFoundException: com.mindprod.csv.CSVReader
          at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
          at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
          ... 11 more

          though we have the latest version of the jemh-plugin (0.9.8-1)!?

          Any Idea? Original issue with logs was JSP-92922.

          Best Regards, Jan

          Show
          Jan Lichter added a comment - Hi, now i am confused, too. We are running Jira (4.4.1) on a Suse Enterprise Server 10, physical machine, no vm. And we have also the class loading problem: Exception in thread "QuartzWorker-1" java.lang.NoClassDefFoundError: com/mindprod/csv/CSVReader at com.javahollic.jira.emh.processor.CSVFieldProcessor.getFieldMap(CSVFieldProcessor.java:64) at com.javahollic.jira.emh.processor.CSVFieldProcessor.extractFieldsAndBody(CSVFieldProcessor.java:176) at com.javahollic.jira.emh.processor.CSVFieldProcessor.getDirectiveCount(CSVFieldProcessor.java:218) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:116) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:87) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:186) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:60) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47) at org.quartz.core.JobRunShell.run(JobRunShell.java:195) at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: java.lang.ClassNotFoundException: com.mindprod.csv.CSVReader at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526) ... 11 more though we have the latest version of the jemh-plugin (0.9.8-1)!? Any Idea? Original issue with logs was JSP-92922. Best Regards, Jan
          Hide
          Wojciech Seliga added a comment -

          @Jan Lichter: I think you are facing this NoClassDefFoundError issue due to JRA-25315 - that's the removal of mindprod library from JIRA installation.
          Removing this in a bugfix release was apparently not a good idea from our side - apologies.
          As a quick solution I think that taking mindprod.jar from an earlier JIRA version (up to 4.4) from <inst dir>/atlassian-jira/WEB-INF/lib and copying it to the same directory in the new installation (JIRA 4.4.1+) should most probably resolve this very problem you have.

          Cheers,
          Wojtek

          Show
          Wojciech Seliga added a comment - @Jan Lichter: I think you are facing this NoClassDefFoundError issue due to JRA-25315 - that's the removal of mindprod library from JIRA installation. Removing this in a bugfix release was apparently not a good idea from our side - apologies. As a quick solution I think that taking mindprod.jar from an earlier JIRA version (up to 4.4) from <inst dir>/atlassian-jira/WEB-INF/lib and copying it to the same directory in the new installation (JIRA 4.4.1+) should most probably resolve this very problem you have. Cheers, Wojtek
          Hide
          Brooke Hedrick added a comment -

          Jan,

          I can tell you that JEMH 0.9.8-1 definitely contains the fix for the classloading issue.

          I would NOT dig up the old class and put it in place as suggested by support, if I had your issue. This will just cause support to tell you that what you did is not supported and possible make it harder to work other support cases.

          If you open the jemh-mail-handler-0.9.8-1.jar, find the class com.javahollic.jira.emh.processor.CSVFieldProcessor and open it with something like jdgui ( Java Decompiler), you will see the following import:
          import au.com.bytecode.opencsv.CSVReader;

          Noticed it is not trying to import: com/mindprod/csv/CSVReader

          The version of JEMH just before this one, does not have the updated import.

          I suspect either you are on the previous version of the jar or maybe when you tried to fix the issue, you left the previous JEMH jar file in the classpath. Since the jars have the version number in them, it would be easy to accidently leave the old version in place when you copy the new version in.

          BTH - just an Atlassian customer!

          Show
          Brooke Hedrick added a comment - Jan, I can tell you that JEMH 0.9.8-1 definitely contains the fix for the classloading issue. I would NOT dig up the old class and put it in place as suggested by support, if I had your issue. This will just cause support to tell you that what you did is not supported and possible make it harder to work other support cases. If you open the jemh-mail-handler-0.9.8-1.jar, find the class com.javahollic.jira.emh.processor.CSVFieldProcessor and open it with something like jdgui ( Java Decompiler), you will see the following import: import au.com.bytecode.opencsv.CSVReader; Noticed it is not trying to import: com/mindprod/csv/CSVReader The version of JEMH just before this one, does not have the updated import. I suspect either you are on the previous version of the jar or maybe when you tried to fix the issue, you left the previous JEMH jar file in the classpath. Since the jars have the version number in them, it would be easy to accidently leave the old version in place when you copy the new version in. BTH - just an Atlassian customer!
          Hide
          Brooke Hedrick added a comment - - edited

          Robert,

          RE: my issue not being the one on the ticket. This is where support directed me. If I am on the wrong ticket, maybe support was wrong to send me here.

          Also, the description of this issue leaves it open to the possibility that there are multiple causes.

          I definitely was seeing: "After installation of version 4.4.1 (was 4.4), the notification emails rest in the mail queue and are not sent anymore. When clicking on "Flush mail queue", all mails are sent immediately without any problems. No errormessage (including OutOfMemoryException) to find in the logfiles."

          Show
          Brooke Hedrick added a comment - - edited Robert, RE: my issue not being the one on the ticket. This is where support directed me. If I am on the wrong ticket, maybe support was wrong to send me here. Also, the description of this issue leaves it open to the possibility that there are multiple causes. I definitely was seeing: "After installation of version 4.4.1 (was 4.4), the notification emails rest in the mail queue and are not sent anymore. When clicking on "Flush mail queue", all mails are sent immediately without any problems. No errormessage (including OutOfMemoryException) to find in the logfiles."

            People

            • Assignee:
              Unassigned
              Reporter:
              Jan Lichter
            • Votes:
              5 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: