服务器日志文件中包含堆栈跟踪,无法使用Camel ActiveMQ JMS停止堆栈跟踪的记录

最新推荐文章于 2022-05-21 01:46:45 发布
最新推荐文章于 2022-05-21 01:46:45 发布
阅读量340 收藏 1
点赞数 1
文章标签： 服务器日志文件中包含堆栈跟踪

我正在使用Camel 2.9.1和Spring 3.1.1.RELEASE和ActiveMQ 5.5.1 .

我有一个Swing GUI客户端，它使用Camel JMS对数据服务进行 @InOut 请求 - 回复调用，该服务在我们服务器上的Karaf / Felix OSGi容器中运行 .

在某些情况下，此服务会抛出我们希望在客户端中处理的异常 .

当抛出这些异常时，Camel将它们传递回包含在 RuntimeCamelException 中的客户端，并且一切正常 .

但现在我想要抑制Camel似乎在Exception传回客户端时自动记录的堆栈跟踪 . 这是服务器日志的一个片段：

2012-11-01 13:04:13,463 | ERROR | org.apache.camel.util.CamelLogger | Failed delivery for (MessageId: ID-pc01-48122-1351720826468-9-121549 on ExchangeId: ID-pc01-48122-1351720826468-9-121547). Exhausted after delivery attempt: 1 caught:org.apache.camel.RuntimeCamelException: our.own.SomethingException: Some explanation of exception here

org.apache.camel.RuntimeCamelException: our.own.SomethingException: Some explanation of exception here

at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1221)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanInvocation.invoke(BeanInvocation.java:87)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:128)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[120:org.apache.camel.camel-core:2.9.1]

... etc.

在日志中立即跟随：

2012-11-01 13:04:13,517 | WARN | org.apache.camel.util.CamelLogger | Execution of JMS message listener failed. Caused by: [org.apache.camel.RuntimeCamelException - our.own.SomethingException: Some explanation of exception here]

org.apache.camel.RuntimeCamelException: our.own.SomethingException: Some explanation of exception here

at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1221)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanInvocation.invoke(BeanInvocation.java:87)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:128)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:115)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:285)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:110)[120:org.apache.camel.camel-core:2.9.1]

...etc

现在 Client 的Spring文件具有以下定义：

哪个 errorHandlerLogStackTrace 属性设置为'false'，所以我'm not sure why it'仍然记录堆栈跟踪 .

我是否需要在服务器端具有类似的属性设置(因为这是包含堆栈跟踪的服务器日志)？

顺便说一句，这些东西大部分是由一位不再为我们工作的前雇员设立的 . 虽然我对正在发生的事情有相当好的理解，但对我来说，其中一些仍然是个谜 .

UPDATE: 5/11/12 - After Claus's answer

好吧，我通过Spring DSL XML文件进行了更多挖掘，发现JMS组件正在服务器上的一个名为“broker”的独立OSGi包中定义，而其他服务器包正在引用它 . 该捆绑包具有与客户端(上面)相同的'jms'bean的XML定义 .

我将'errorHandlerLogStackTrace'属性添加到此定义中，并且已设法摆脱其中一个堆栈跟踪 . 我现在得到的是带有堆栈跟踪的错误，紧接着是没有堆栈跟踪的WARN . 这是一个更完整的代码段：

2012-11-05 10:44:35,323 | ERROR | org.apache.camel.util.CamelLogger | Failed delivery for (MessageId: ID-pc01-38192-1352065125718-9-62 on ExchangeId: ID-pc01-38192-1352065125718-9-60). Exhausted after delivery attempt: 1 caught: org.apache.camel.RuntimeCamelException: our.own.SomethingException: Some explanation of exception here

org.apache.camel.RuntimeCamelException: our.own.SomethingException: Some explanation of exception here

at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1221)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanInvocation.invoke(BeanInvocation.java:87)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:128)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:115)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:285)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:110)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:333)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:223)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:304)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:71)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:86)[120:org.apache.camel.camel-core:2.9.1]

at org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:104)[147:org.apache.camel.camel-jms:2.9.1]

at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:562)[63:org.springframework.jms:3.1.1.RELEASE]

at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:500)[63:org.springframework.jms:3.1.1.RELEASE]

at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:468)[63:org.springframework.jms:3.1.1.RELEASE]

at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:326)[63:org.springframework.jms:3.1.1.RELEASE]

at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:264)[63:org.springframework.jms:3.1.1.RELEASE]

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1071)[63:org.springframework.jms:3.1.1.RELEASE]

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1063)[63:org.springframework.jms:3.1.1.RELEASE]

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:960)[63:org.springframework.jms:3.1.1.RELEASE]

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_24]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_24]

at java.lang.Thread.run(Thread.java:662)[:1.6.0_24]

Caused by: our.own.SomethingException: Some explanation of exception here

at uniworks.ServiceManagers.SuperDataManager.createInUseForEntity(SuperDataManager.java:2156)[220:uniworks-ejb:1.1.4.SNAPSHOT]

at uniworks.ServiceManagers.SuperDataManager.findForEdit(SuperDataManager.java:913)[220:uniworks-ejb:1.1.4.SNAPSHOT]

at uniworks.ServiceManagers.SuperDataManager.findForEdit(SuperDataManager.java:853)[220:uniworks-ejb:1.1.4.SNAPSHOT]

at uniworks.ServiceManagers.SuperDataManager.findForEdit(SuperDataManager.java:843)[220:uniworks-ejb:1.1.4.SNAPSHOT]

at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[:1.6.0_24]

at java.lang.reflect.Method.invoke(Method.java:597)[:1.6.0_24]

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)[65:org.springframework.transaction:3.1.1.RELEASE]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)[55:org.springframework.aop:3.1.1.RELEASE]

at $Proxy221.findForEdit(Unknown Source)

at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[:1.6.0_24]

at java.lang.reflect.Method.invoke(Method.java:597)[:1.6.0_24]

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58)

at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:56)

at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:39)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.osgi.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:59)[90:org.springframework.osgi.core:1.2.1]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)[55:org.springframework.aop:3.1.1.RELEASE]

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)[55:org.springframework.aop:3.1.1.RELEASE]

at $Proxy1044.findForEdit(Unknown Source)

at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[:1.6.0_24]

at java.lang.reflect.Method.invoke(Method.java:597)[:1.6.0_24]

at org.apache.camel.component.bean.BeanInvocation.invoke(BeanInvocation.java:83)[120:org.apache.camel.camel-core:2.9.1]

... 46 more

2012-11-05 10:44:35,335 | WARN | org.apache.camel.util.CamelLogger | Execution of JMS message listener failed. Caused by: [our.own.SomethingException: Some explanation of exception here]

现在，这里可能使这些变得复杂的是此方法调用所采用的“路径” .

客户端使用JMS Request-Reply消息使用以下路由定义来调用服务器：

该路由的服务器端在一个OSGi包中定义(让我们调用'BundleA')，如下所示：

此路由中引用的bean实际上是另一个bundle('BundleB')作为OSGi'服务' . BundleA引用了这个bean，定义如下：

interface="uniworks.ServiceManagers.a.Animal.AnimalTypeDataInterface"/>

BundleB的服务定义如下：

interface="uniworks.ServiceManagers.a.Animal.AnimalTypeDataInterface"/>

正是这个最终的服务bean抛出了异常 .

我可以在这些路由的每个服务器端(在BundleA中)放置 errorHandler ，但我希望能够在一个地方一般地执行此操作 .

我尝试在BundleA中定义一个日志记录错误处理程序(根据Camel Documentation)，如下所示：

..... [jms routes defined in here]

但这似乎没有任何区别 .

PaalMind
关注
spring-boot-camel-jms:使用 Apache Camel 和 ActiveMQ 的 Spring Boot 应用程序
05-31
2. **引入Camel和JMS依赖** - 在`pom.xml`文件中添加Apache Camel和ActiveMQ的依赖，确保项目能够使用这些组件。 3. **创建Camel路由** - 使用Java或者XML编写Camel路由，定义消息的输入、处理和输出。路由可以处理...
ApacheCamel-JMS-ActiveMQ
02-05
在"Apache Camel JMS ActiveMQ"的使用样例中，我们有两个主要的场景： 1. **从本地读取信息推送到MQ中**：这一部分涉及到了Apache Camel的数据交换模型，即从本地源（可能是文件、数据库或任何其他数据源）读取信息...
java 异常堆栈不可用_异常 Exception 异常捕获 堆栈跟踪 [MD]
weixin_35924734的博客
02-17 3441
我的GitHub我的博客我的微信我的邮箱bqt20094baiqiantao@sina.com异常捕获常用 APIsetUncaughtExceptionHandlerpublic void setUncaughtExceptionHandler(Thread.UncaughtExceptionHandler eh)设置该线程由于未捕获到异常而突然终止时调用的处理程序。通过明确设置未捕获到的异常处...
过滤日志中不相关的堆栈跟踪行
最佳 Java 编程
05-07 318
我喜欢堆栈痕迹。 不是因为我喜欢错误，而是因为发生错误的那一刻，堆栈跟踪是无价的信息源。 例如，在Web应用程序中，堆栈跟踪向您显示完整的请求处理路径，从HTTP套接字到过滤器，Servlet，控制器，服务，DAO等，直到发生错误的地方。 您可以将它们读为一本好书，其中每个事件都有因果关系。 我什至在Logback打印异常的方式上实现了一些增强功能，请参阅首先记录异常的根本原因 。 但是有...
服务器日志追踪
weixin_33905756的博客
11-11 259
http://www.2cto.com/article/201206/135026.html http://www.cnblogs.com/no7dw/p/3917108.html http://elan1986.iteye.com/blog/1580569 http://yunzhu.iteye.com/blog/1554869
【异常】553 Mail from must equal authorized user
weixin_30339969的博客
08-18 757
1 详细异常打印 2019-08-12 14:54:42,178 ERROR org.apache.camel.processor.DefaultErrorHandler: Failed delivery for exchangeId: ID-cdh4-39223-1565591676886-0-549. Exhausted after delivery attempt: 1 ca...
ActiveMQ+Camel+Spring+jms Demo（一）
06-01
项目中的“camel-example-activemq-tomcat”可能是一个包含了Tomcat服务器、Camel配置、Spring配置以及相关的Java代码的示例。Tomcat作为一个流行的Java应用服务器，将承载这个应用程序，提供运行环境。在实际操作中...
ActiveMQ+Camel+Spring+jms Demo（二）
06-01
在压缩包文件"client"中，我们可以预期找到客户端代码，这个客户端可能是一个简单的Java应用程序，它连接到ActiveMQ服务器，使用Spring的JMS模板发送消息到队列，或者从队列中消费消息。客户端代码可能包含配置文件...
8.5tomcat堆栈跟踪异常
weixin_45565294的博客
05-21 733
在写JAVAWEB项目时，运行TOMCAT后出现这个问题 ——非法访问：此Web应用程序实例已停止。无法加载[]。为了调试以及终止导致非法访问的线程，将抛出以下堆栈跟踪。 从其他地方找了很多方法，也没能解决这个问题 比如我参考的这一篇 文章 最终我把目光锁定Tomcat版本上，终于有了进展 我使用的是Tomcat8.5.50 解决方法： 修改tomcat目录下conf文件夹下的** context.xml , 注意，是 context.xml ** 最下边找到Context标签，添加一行属性为：
服务器日志文件中包含堆栈跟踪,日志框架 Logback 官方手册（第三章：Configuration）...
weixin_30467861的博客
08-10 871
以下内容翻译整理自logback官方手册，地址：logback官方手册logback 配置将日志请求插入应用程序代码需要相当多的计划和工作。观察表明，大约有4%的代码用于日志记录。因此，即使是一个中等大小的应用程序，其代码中也会包含数千条日志语句。考虑到它们的数量，我们需要工具来管理这些日志语句。可以通过编程方式配置logback，也可以使用XML或Groovy格式表示的配置脚本配置logback...
服务器日志文件中包含堆栈跟踪,报表服务器服务跟踪日志 - SQL Server Reporting Services (SSRS) | Microsoft Docs...
weixin_35752122的博客
08-10 336
报表服务器服务跟踪日志04/23/2019本文内容Reporting Services 报表服务器跟踪日志是 ASCII 文本文件，其中包含有关报表服务器服务操作的详细信息。 文件中的信息包括由报表服务器 Web 服务、Web 门户和后台处理执行的操作。 跟踪日志文件中包括其他日志文件中记录的冗余信息，还包括无法通过其他方式获得的附加信息。 如果要调试包括报表服务器的应用程序或调查已写入事件日志...
Build and deploy OSGi as Spring bundles using Felix(From IBM developerworks)
§为艺术而技术§
04-04 1483
source: http://www.ibm.com/developerworks/opensource/library/ws-osgi-spring2/index.html?ca=dgr-jw22&S_TACT=105AGX59&S_CMP=grsitejw22   developerWorks  >  SOA and Web services | Open so
在spring osgi中取得datasource时出现问题
xgbjmxn的专栏
11-02 246
在spring osgi中取得datasource时出现问题 2011-11-2 java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/osgidb at java.sql.DriverManager.getConnection(Unknown Source) at java....
ActiveMQ入门：JMS组件与消息传递模式详解
- 会话：是JMS中的核心组件，单线程，用于生产者（Producer）发送消息和消费者（Consumer）接收消息，提供事务管理，确保发送和接收操作的原子性。 - 目的地：包括队列（Queue）和主题（Topic），前者一对一通信，...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值