【问题】INFO: TopologyManager: EndpointListener changed ...

5月份做云部署,在调试CSS系统时,出现启动系统时,卡死情况,后台日志如下:

May 03, 2016 2:34:52 AM org.apache.cxf.dosgi.topologymanager.TopologyManager$1 modifiedService

INFO: TopologyManager: EndpointListener changed ...

接下来就麻烦了, 这个系统现场可正常使用,调试用的备份系统,开发者已经找不到,只好自己查找原因

网络上的信心很少http://stackoverflow.com/ 中有人提过相同的问题,好心人回复如下:

The CXF dOSGi single bundle distribution is packaged as a jar so there must have been a problem downloading it, although from your log it does appear to be being deployed.

Try this link for cxf-dosgi-ri-singlebundle-distribution-1.2.jar

当时就有点凌乱了,回答说第三方包有问题,第三方包有问题为什么现场正常使用!

从日志上看是某个地方部署失败, 但是后台日志中没有打出相应的日志,这个郁闷!

本以为是配置某个地方配置错了,无意中在configure 文件夹中看到1462351957787.log,奇怪了这里怎么又日志

打开一看,顿时就石化了, 妹妹的!@#¥% ,异常日志瞎放啊

org.osgi.framework.BundleException: The activator com.star.css.schedule.Activator for bundle com.star.css.schedule is invalid

at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:171)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679)

at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)

at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1131)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)

at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

Caused by: java.lang.UnsupportedClassVersionError: com/star/css/schedule/WorkOrderHandle : Unsupported major.minor version 51.0

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)

at java.lang.ClassLoader.defineClass(ClassLoader.java:615)

从日志上看/WorkOrderHandle : Unsupported major.minor version 51.0 说明JDK环境不正确,更换JDK 后问题解决

整个排查过程很是坑爹

1- 该打印的日志没有打印,打印的日志几乎完全没有帮助

2-日志保存位置没有放到LOG日志文件夹反而放到了 配置文件夹

3-日志使用的LONG 没有转换成日志格式,导致不仔细看无法发现是新创建的

记录以上三点,以后不犯类似错误,让他人骂娘

时间: 2024-11-05 20:45:13

【问题】INFO: TopologyManager: EndpointListener changed ...的相关文章

tomcat 7 WARNING: A context path must either be an empty string or start with a '/' and do not end with a '/'. The path [/] does not meet these criteria and has been changed to []

tomcat 7 WARNING: A context path must either be an empty string or start with a '/' and do not end with a '/'. The path [/] does not meet these criteria and has been changed to [] 解决方法: 将server.xml中的<Context docBase="../deploy" path="/&q

详细!交叉编译时 note: the mangling of &#39;va_list&#39; has changed in GCC 4.4解决办法

为什么要在标题前面加了详细两个字,就是为了吸引看文章的你还有写文章的我这种小白,我是从坑里面爬出来了. 废话少说.... 问题就是这样子了,至于解决办法,在网上搜索了很久,大多数以一段英文作为解决办法,... I think that the warning is accurate; the mangling of va_list has indeed changed on ARM in GCC 4.4 in order to conform to the ARM ABI specificati

SSH RSA host key for has changed and you have requeste

今天在209服务器上要远程登录另外一台54的服务器,结果用ssh连接提示如下错误: [[email protected] ~]# ssh [email protected] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

It Changed Its Mind And Inte Hot As Handbag

Cover with polyethylene plastic film intended for system United States Postal Service . These plastic envelopes are resistant to puncture and tear, waterproof and available in white, which looks opaque professional and preserves the integrity of the

scp不可用:WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! After doing ssh are you seeing this error.No problem it can be solved. [email protected]:/tmp# ssh 10.10.0.16 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFI

Model backing a DB Context has changed; Consider Code First Migrations

Model增加一个字段,数据库对应的也手动添加了字段但是运行时报错 The model backing the 'TopLogDbContext' context has changed since the database was created. Consider using Code First Migrations to update the database  参考原文:Model backing a DB Context has changed; Consider Code Firs

ssh ip &quot;WARING:REMOTE HOST IDENTIFICATION HAS CHANGED!&quot;

[[email protected] network-scripts]# ssh 192.168.1.10 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOM

codeforces 782B The Meeting Place Cannot Be Changed+hdu 4355+hdu 2438 (三分)

B. The Meeting Place Cannot Be Changed The main road in Bytecity is a straight line from south to north. Conveniently, there are coordinates measured in meters from the southernmost building in north direction. At some points on the road there are n

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED

原文地址:http://linuxme.blog.51cto.com/1850814/375752 今天将阿里云服务器更换了一下系统盘,重启成功后,再次通过终端访问阿里云的公网IP报以下信息: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@