[
https://jira.jboss.org/jira/browse/JBESB-2100?page=com.atlassian.jira.plu...
]
Joakim Sandström updated JBESB-2100:
------------------------------------
Workaround Description:
Set invm scope to NONE, since we are not using the invm feature
From programmers guide: 'The default InVM Scope for an ESB
deployment can be set in the jbossesb-properties.xml file through the
"core:jboss.esb.invm.scope.default" config property. If not defined, the default
scope is "GLOBAL".'
Workaround: [Workaround Exists]
InVM exception
--------------
Key: JBESB-2100
URL:
https://jira.jboss.org/jira/browse/JBESB-2100
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment
Affects Versions: 4.4
Reporter: Joakim Sandström
Attachments: invm.errors.txt
From my forum post:
My logs gets filled up with the following exception, any ideas what is wrong with my
configuration?
I'm using jboss-4.2.3.GA, jbossesb-4.4.GA, jboss messaging 1.4.0.SP3 and MySQL
5.0.67.
2008-10-07 05:07:20,334 DEBUG [org.jboss.internal.soa.esb.couriers.InVMCourier]
InVMCourier for EPR
'invm://6f72646572636865636b437573746f6d657246455342/false?false#10000' is not
activ
e. Cannot pickup/deliver on this courier.
java.lang.Exception
at org.jboss.internal.soa.esb.couriers.InVMCourier.isCourierActive(InVMCourier.java:281)
at org.jboss.internal.soa.esb.couriers.InVMCourier.pickup(InVMCourier.java:217)
at
org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240)
at
org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216)
at
org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
at
org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
at
org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
at java.lang.Thread.run(Thread.java:619)
JBoss esb generates about 1GB of logs each minute due to this error, about 800K of InVM
errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira