Forum Home


recent update -emails failing now Adrian
    recent update -emails failing now Adrian
    recent update -emails failing now Synametrics Support
        recent update -emails failing now Adrian
            recent update -emails failing now Synametrics Support
                recent update -emails failing now Adrian
                recent update -emails failing now Adrian
                    recent update -emails failing now Nicolas Blum

From: Adrian
Date: 7/16/25 11:25 AM
Topic: recent update -emails failing now
Type: General Discussions
Post a follow up

hi -after the recent update (across three servers) we are seeing no emails being sent...but the live view seems to show everything is ok. It's only just coming to light now, 6 hours on

I'm seeing this in the srvstderr log on two of the servers (not checked the other):


2025-07-16 10:35:04 Commons Daemon procrun stderr initialized
Jul 16, 2025 10:35:14 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-127.0.0.1-45555"]
Jul 16, 2025 10:35:14 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-8080"]
Jul 16, 2025 10:35:14 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["https-jsse-nio-443"]
Jul 16, 2025 10:35:15 AM org.apache.tomcat.util.net.AbstractEndpoint logCertificate
INFO: Connector [https-jsse-nio-443], TLS virtual host [_default_], certificate type [UNDEFINED] configured from keystore [C:\Xeams\config\letenc.pfx] using alias [tomcat] with trust store [null]
Jul 16, 2025 10:35:15 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Tomcat]
Jul 16, 2025 10:35:15 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet engine: [Apache Tomcat/9.0.104]
Jul 16, 2025 10:35:15 AM org.apache.catalina.webresources.DirResourceSet initInternal
WARNING: Disabled the global canonical file name cache to protect against CVE-2024-56337 when starting the WebResourceSet at [C:\Xeams\webfront\webapps\ROOT] which is part of the web application []
Jul 16, 2025 10:35:16 AM org.apache.catalina.startup.ContextConfig getDefaultWebXmlFragment
INFO: No global web.xml found
Jul 16, 2025 10:35:16 AM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Jul 16, 2025 10:35:16 AM org.apache.tomcat.util.descriptor.web.SecurityConstraint findUncoveredHttpMethods
SEVERE: For security constraints with URL pattern [/*] only the HTTP methods [DELETE OPTIONS PUT] are covered. All other methods are uncovered.
Jul 16, 2025 10:35:16 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-45555"]
Jul 16, 2025 10:35:16 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-8080"]
Jul 16, 2025 10:35:16 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["https-jsse-nio-443"]
Exception in thread "LCID_2897523" java.lang.NullPointerException
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1814)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1727)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1608)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:450)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:351)
at com.synametrics.xeams.stagingserver.l.run(SmtpStagingWorker.java:2015)
at java.lang.Thread.run(Thread.java:750)
Exception in thread "LCID_2897524" java.lang.NullPointerException
Top
From: Adrian
Date: 7/16/25 11:28 AM
Topic: recent update -emails failing now
Type: General Discussions
Post a follow up

is the same on the third server -and this is at the end of that stderror log:

Exception in thread "LCID_61309488" java.lang.NullPointerException
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1814)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1727)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1608)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:450)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:351)
at com.synametrics.xeams.stagingserver.l.run(SmtpStagingWorker.java:2015)
at java.lang.Thread.run(Thread.java:750)
Exception in thread "LCID_61309516" java.lang.NullPointerException
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1814)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1727)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1608)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:450)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:351)
at com.synametrics.xeams.stagingserver.l.run(SmtpStagingWorker.java:2015)
at java.lang.Thread.run(Thread.java:750)
Exception in thread "LCID_61309535" java.lang.NullPointerException
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1814)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1727)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1608)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:450)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:351)
at com.synametrics.xeams.stagingserver.l.run(SmtpStagingWorker.java:2015)
at java.lang.Thread.run(Thread.java:750)
Exception in thread "LCID_61309548" java.lang.NullPointerException
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1814)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1727)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1608)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:450)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:351)
at com.synametrics.xeams.stagingserver.l.run(SmtpStagingWorker.java:2015)
at java.lang.Thread.run(Thread.java:750)
Exception in thread "LCID_61309547" java.lang.NullPointerException
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1814)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1727)
at com.synametrics.xeams.util.Q.H(SmtpQueue.java:1608)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:450)
at com.synametrics.xeams.stagingserver.E.H(SmtpStagingWorker.java:351)
at com.synametrics.xeams.stagingserver.l.run(SmtpStagingWorker.java:2015)
at java.lang.Thread.run(Thread.java:750)
Top
From: Synametrics Support
Date: 7/16/25 11:30 AM
Topic: recent update -emails failing now
Type: General Discussions
Post a follow up

Please update your Xeams one more time. Go to Home > Server Options > Check for Update.

Once done, it should resolve this problem. 

 
Top
From: Adrian
Date: 7/16/25 11:34 AM
Topic: recent update -emails failing now
Type: General Discussions
Post a follow up

I got a "localhost refused to connect" image/placeholder underneath the "Download Status" message -what's happened?
Top
From: Synametrics Support
Date: 7/16/25 11:41 AM
Topic: recent update -emails failing now
Type: General Discussions
Post a follow up

Click "Home" to refresh the page. What is the build number in the upper right-hand corner? If that is 6382, the problem should be fixed. If not, try patching it manually using instructions on https://www.xeams.com/manuallypatching.htm

 
Top
From: Adrian
Date: 7/16/25 11:46 AM
Topic: recent update -emails failing now
Type: General Discussions
Post a follow up

ok thanks -two of the three servers didn't complete visually back to the home page, but one did. All three now seem to be working -the errors are no longer in the log

the version is showing as:
Xeams Admin Console - Version 9.8, build 6382

Version 9.8, build 6382

on them all
Top
From: Adrian
Date: 7/16/25 11:48 AM
Topic: recent update -emails failing now
Type: General Discussions
Post a follow up

ok thanks -two of the three servers didn't complete visually back to the home page, but one did. All three now seem to be working -the errors are no longer in the log

the version is showing as:
Xeams Admin Console - Version 9.8, build 6382

Version 9.8, build 6382

on them all
Top
From: Nicolas Blum
Date: 7/17/25 2:25 PM
Topic: recent update -emails failing now
Type: General Discussions
Post a follow up

Had the problem as well -  mind, that all mails during this endeavour are needed to be forwarded again to your mailserver, as they will not be resend at all.
Top