几个系统配置的项目应用,都是使用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]
分享到:
相关推荐
实现一个求解一元二次方程的类,该类包含三个成员变量和一个求解一元二次方程解的函数,该函数需要抛出异常(1.无解的异常 2二次项系数为0的异常))
利用如下方法计算一元二次方程的根,可以设计一个图形界面输入A,B,C值,点击“求解”按钮进行计算,结果显示在一个标签中。 注意代码的异常处理。
我们考虑模型中的局部(或扰动)规范异常,这些异常将标准模型(SM)规范组的等级和手性费米子含量仅扩展了n个SM单重态。 我们给出了一个仅涉及SM费米子的ACC的额外U(1)子组的异常消除条件(ACC)的一般解决方案,...
使用广义傅里叶变换法对非线性扩散方程的解进行了数值研究。 该方程包括分形维数和幂律对径向变量和扩散函数的依赖性。 广义傅立叶变换方法是... 数值方法的优点是它提供了一种计算具有任意初始条件的异常扩散的方法。
一个异常行为投影近似基,继续进行下一个异常行为投影近似基的求解,对行为向量的异常程度进行判断。仿真结果表明, 提出方法具有较好的识别率,提高了行人异常行为检测的可行性,为后续实现道路人群拥挤行人异常...
第5章 作为问题求解技术的递归 155 5.1 定义语言 156 5.1.1 语法知识基础 156 5.1.2 两种简单的语言 158 5.2 代数表达式 160 5.2.1 代数表达式的类型 160 5.2.2 前缀表达式 162 5.2.3 后缀表达式 166 5.2.4 ...
通过对路径积分雅可比行列式的显式计算以及对Wess-Zumino一致性条件的求解,我们表明,各向异性方向上的平移对称性变得异常。 事实证明,这是增强和翻译之间的混合异常。 在时空几何学的牛顿-卡坦公式中,这种异常...
在此基础上, 实现了基于Hurst指数变化的异常检测, 有效解决了方法实现过程中FRFT最佳估计的分数阶阶数选择及Hurst参数求解的关键问题。实验表明, 基于FRFT的估计不受序列非平稳性影响, 对Hurst指数估计具有较高的...
基于高程异常拟合模型对矿区测量数据处理进行研究,分析总体最小二乘模型的几何意义,基于奇异值分解算法与拉格朗日函数算法,结合数据处理实例讨论矿区高程异常拟合。研究表明,与最小二乘算法相比,基于拉格朗日函数的...
提出一种基于抗差估计的选权迭代趋势面拟合滤波法,利用等价权将抗差估计理论与最小二乘趋势面拟合有机结合起来,以趋势面拟合系数求解模型作为判别异常值的迭代推值模型,介绍了多波束测深异常数据探测及滤波的基本...
完全协变方法描述了一般共形场理论(CFT)中四个维度中的应力-能量相关函数,作为任意弯曲... 这表明,一般弯曲空间异常有效作用所预测的特定解析结构和无质量极点实际上是任何d = 4 CFT中异常CWI精确求解的必要特征。
复杂条件下,分布式顺序统计恒虚警率(OS-CFAR)检测系统的参数选择和检测性能分析是一个典型的非线性优化问题,通常采用数值求解和计算机搜索的方法。但在复杂条件下,特别是当传感器数量较多,或采用分布式OS-CFAR...
% 函数求解开普勒方程 M = Ee*sin(E) % 输入 - 平均异常 M [rad] 、偏心率 e 和 Epsilon % 输出偏心异常 E [rad]。
针对异常入侵检测技术中传统聚类方法需要被检测类大小均衡的问题,在商空间粒度理论的基础上,论述了商空间粒度变换可以使复杂问题在不同的粒度世界求解,最终使整个问题得到简化。分析了商空间划分与聚类操作的相似...
长方形周长面积,异同比较,异常处理,模版,继承方式,分数相加减,分数除法,表面积体积
论文研究-时序约束下Guard-...如果出现异常,将问题转化为线性规划模型并进行自动求解.不但能够解决GSM业务模型的时序约束验证问题,而且能指导用户进行模型持续优化和改进.最后,通过一个企业的实例验证了其有效性.
为提高光流估计的鲁棒性,假设运动物体...通过最小二乘法求解超定的小波光流方程组以解得光 流矢量,并用中值滤波去除光流场中的异常分量 。实验表明,提出的方法在光流求解精度及算法稳定性方面优于传 统光流求解方法 。
2017年是供给侧结构性改革的深化之年,煤炭去产能任务异常艰巨。企业是过剩产能的载体,去产能之役能否取胜,关键在于企业。随着煤炭行业化解过剩产能工作的持续推进,还存在五个亟待解决的矛盾和问题,制约着煤炭企业去...
根据求解结果生成新数据集并动态测试,监测执行异常,计算代码覆盖率。经实验验证,工具能有效发现测试程序异常,并适用于大型应用软件测试,已发现Word 2003软件中存在的七个异常,代码覆盖率较传统Fuzzing测试工具...
标准模型有效理论中的重归一化组方程(RGE)通常要么通过分析求解,而忽略了规范和Yukawa耦合的比例依赖性,要么在数值上没有这种近似。 我们提出了RGE的解析解,其中考虑到由于QCD耦合αs和top-Yukawa耦合的运行而...