`
hanfeng450
  • 浏览: 29529 次
  • 性别: Icon_minigender_1
  • 来自: 广州
社区版块
存档分类
最新评论

异常求解

阅读更多
几个系统配置的项目应用,都是使用spring集成quartz,有其中一台服务器出现下列的错误,但其他的服务器没有发现同样的异常。有没有大虾也遇到过同样的问题。

SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [com.google.common.base.internal.Finalizer] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-keep-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-max-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-pool-watch-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-keep-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-max-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-pool-watch-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-keep-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-max-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-pool-watch-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [com.google.common.base.internal.Finalizer] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-keep-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-max-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-pool-watch-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-keep-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-max-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-pool-watch-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-release-thread-helper-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-keep-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-max-alive-scheduler] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [BoneCP-pool-watch-thread] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/s] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.[align=left][/align]
分享到:
评论

相关推荐

    使用Sufer 软件求取高程异常值的方法

    ### 使用Sufer软件求取高程异常值的方法 #### 一、引言 随着全球定位系统(GPS)的广泛应用,高精度...未来,随着更多高精度地面水准测量数据的积累和技术的进步,Sufer在高程异常求解方面的应用将会更加广泛和深入。

    平坦地区GPS高程异常拟合研究.pdf

    文章列举了三种主要的高程异常求解方法:几何解析方法(数学模型法)、物理大地测量方法以及神经网络方法。其中,神经网络方法近年来受到了广泛关注,因为它能够处理复杂的非线性问题,适应性较强。 文章具体研究了...

    利用平面GPS高程拟合法求均值的讨论.pdf

    平面拟合法是常用的高程异常求解方法之一,它基于高程异常在一定区域内具有几何相关性的假设。这种方法包括三种常见形式: 1. **常数法**(零次多项式法):假设区域内所有点的高程异常相同,即所有点的高程异常...

    一种基于综合模型的GPS高程优化方法.pdf

    传统的高程异常求解方法在复杂地形下可能无法保证精度。 【加权均值法】这是一种基于周围已知点的高程异常数据,通过加权平均计算未知点高程异常的方法。加权平均考虑了各个数据点的权重,通常权重与距离的平方成...

    EGM2008模型在GPS高程转换中的适用性探讨.pdf

    【GPS水准法】GPS水准法是一种常见的高程异常求解方法,通过已知高程异常的控制点,利用模型对测区的似大地水准面进行拟合,进而计算出未知点的高程异常。这种方法的算法相对简单,但对GPS点的数量、分布均匀性和...

    Matlab在GPS高程转换中的应用.pdf

    传统的高程异常求解方法通常通过GPS水准,即选取部分GPS点与已知水准点联测,获取这些点的正常高和大地高,然后建立区域的似大地水准面模型。Matlab在此过程中发挥重要作用,可以方便地进行多项式曲面拟合,以模拟测...

    Java程序求解方程

    注意处理异常情况,如无解、多个解或数值溢出等问题。 8. **优化**:为了提高效率,可以考虑使用多线程或并行计算技术,特别是当需要求解大量方程或者高次方程时。Java的并发库提供了多种工具,如`ExecutorService`...

    实现一个求解一元二次方程的类,该类包含三个成员变量和一个求解一元二次方程解的函数,该函数需要抛出异常(1.无解的异常 2二次项系数为0的异常))

    在本题中,我们需要创建一个类,它包含三个成员变量来存储这些常数,并提供一个方法来求解方程。此外,这个方法必须能够处理两种异常情况:一是方程无解,二是二次项系数 `a` 为0。 首先,我们来创建这个类,我们...

    PNP 问题求解.doc

    PNP(Perspective-N-Point)问题是在计算机视觉和机器人定位中常见的一个问题,涉及到从多个三维点...在实际应用中,通常会结合其他策略,如RANSAC(Random Sample Consensus)来处理噪声和异常值,提高解的准确性。

    用gauss消去法求解线性方程组

    - **异常处理**:增加异常处理机制可以提高程序的健壮性和用户友好度,例如当输入不合法时给出提示。 - **优化改进**:考虑到数值稳定性,可以引入全选主元的方法进一步提高算法的准确性和效率。 综上所述,Gauss消...

    Hilbert矩阵的病态问题及线性方程数值求解.docx

    Hilbert 矩阵的病态问题及线性方程数值求解 Hilbert 矩阵是一种数学变换矩阵,正定,且高度病态,任何一个元素发生一点变动,整个矩阵的行列式的值和逆矩阵都会发生巨大变化,病态程度和阶数相关。其形式为:考虑...

    实验四 用回溯法求解跳马问题.zip

    同时,理解并合理运用C++的内存管理和异常处理机制也至关重要,以防程序在运行过程中出现意外错误。 总之,这个实验旨在让学生理解和掌握回溯法这一算法,并通过实践应用加深对C++编程的理解,尤其是在解决问题和...

    EXCEL 数据分析宏+规划求解宏

    6. **直方图**:展示数据分布,帮助识别数据的模式和异常值。 **规划求解宏** 规划求解宏是Excel的一个附加组件,用于解决线性和非线性的优化问题。它可以帮助用户找到一组变量的最佳值,以满足特定的目标函数和...

    一个带求解器的推箱子游戏

    5. **错误处理**:由于推箱子游戏中可能存在无效的操作(比如将箱子推到角落无法移动),开发者需要编写代码来处理这些异常情况,确保游戏的稳定性和可玩性。 6. **求解器优化**:为了提高求解速度,求解器可能会...

    C#实现的一元四次方程求解源代码

    在这个方法中,可以先判断系数a是否为0,若为0,则不是四次方程,需抛出异常。然后,可以设置一个迭代次数上限和精度阈值,通过迭代方法寻找方程的根。 对于迭代法,牛顿法是常用的一种,其基本思想是:在函数f(x)...

    两阶段法求解线性规划

    通过输入不同的数据集,观察程序是否能正确地输出最优解,以及是否有异常情况发生。 ### 结论 通过本次实验,不仅加深了对单纯形算法和两阶段法的理解,而且通过编程实践掌握了这两种算法的实际应用。这对于今后...

    求解一元二次方程组的c++代码

    在生产环境中,应添加错误检查和异常处理机制,以确保程序的健壮性。 总之,这段C++代码提供了一个简单的一元二次方程求解器,它使用了代入法来解方程。虽然简洁,但未涵盖所有可能的解情况,因此在实际项目中可能...

    数值分析 非线性方程求解

    2. **异常处理**:当一阶导数\( g(x_0) \)为0时,牛顿迭代法将无法继续进行,因为此时的分母为0。因此,在程序中加入了相应的判断逻辑,一旦检测到这种情况,就会提前终止迭代过程并输出提示信息。 #### 总结 通过...

Global site tag (gtag.js) - Google Analytics