[JBoss Messaging] - Message bridge performance in WAN
by jjacobwip
Hi,
We have an ActiveMQ queue which gets posted with 65K+ messages in an hour. These messages needs to be transfered over the WAN to a local queue created in Jboss messaging. We have created a message bridge for this where the source of the bridge is the Remote ActiveMQ queue and target is a local Jboss messaging queue.
We are seeing a very low performance here where in only 1000 messages are reaching the local queue in 1 minute. MaxBatchSize is set to 50 and MaxBatchTime is set to 1.
The question is -
1. How does MaxBatchSize work? Will the bridge pick up all 50 msgs and transfer it over WAN or will it transfer the messages one by one over the WAN and create a batch and send it to the local queue?
2. How can we get a better performance? We know that n/w speed is an important factor here and we are working on it, but just wanted to know if there is any configurations which we can tweak to get a better performance.
Env:
JBoss 5.0.1
Jboss Messaging 1.4.1 GA
Message Bridge Config:
anonymous wrote :
| <mbean code="org.jboss.jms.server.bridge.BridgeService"
| name="com.nordpool:service=Bridge,name=BridgeFromOM"
| xmbean-dd="xmdesc/Bridge-xmbean.xml">
|
| jboss.mq:service=JMSProviderLoader,name=ActiveMQJMSProvider
|
| jboss.messaging:service=JMSProviderLoader,name=JMSProvider
|
| inbound
|
| queue/LocalQueue
|
| xx
|
| xx
|
| <!--
| xx/attribute>
| xx
| -->
|
| 0
|
|
|
| 50
|
| 4000
|
|
|
|
|
| 1000
|
| 2
|
|
|
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241423#4241423
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241423
16 years, 9 months
[EJB 3.0] - java.lang.RuntimeException: java.lang.ClassCastException: $P
by ravendra.gupta
Hi all,
I am using Jboss application server 4.2.3 GA.
my problem is, when I create a stateless session bean and deploy that works fine but if I change this bean to stateful session bean by changing annotation, that give classCastException
| package com.logica.heca.lpr.ruleengine;
|
| import com.logica.heca.lpr.common.exception.FatalException;
| import com.logica.heca.lpr.common.exception.RuleParserException;
| import com.logica.heca.lpr.domain.contact.ContactVO;
| import com.logica.heca.lpr.domain.ruleengine.RuleDefinitionVO;
| import com.logica.heca.lpr.ruleengine.helper.RuleParser;
|
| import javax.ejb.EJBException;
| import javax.ejb.Stateful;
| import java.io.Serializable;
|
| /**
| * <p/>
| * Created by: kumarrg
| * Date: 17-Jun-2009
| * Time: 14:33:02
| * </br>
| * This software is a part of the LPR system, developed by Logica.
| */
| @Stateful(name = "RuleEngine")
| public class RuleEngineBean implements RuleEngineLocal, RuleEngineRemote, RuleEngine, Serializable {
|
| // private static final Logger logger= Logger.getLogger(RuleEngineBean.class);
|
| /**
| * @param contactVO to be validated against rules
| * @return ContactdVo populated with ruleId and Error Source object
| */
| public ContactVO processContact(ContactVO contactVO) {
| // try {
| // StatelessSession session = getRuleBase().newStatelessSession();
| // session.execute(contactVO);
| return contactVO;
| // } catch (Throwable ex) {
| // logger.fatal("Severe error while processing ContactVo rule", ex);
| // throw new FatalException("Fatal error while parsing rule");
| // }
| }
|
| // private RuleBase getRuleBase()throws RuleParserException {
| // // return new RuleBaseBuilder().getRuleBase();
| // return null;
| // }
|
| /**
| * parse rule as per Drools rules 4 format
| * @param ruleDefinitionVO RuleDefinitionLite
| * @return RuleDefinitionErrorVO if any error found else null
| */
| public void parseRule(RuleDefinitionVO ruleDefinitionVO) throws RuleParserException{
| try {
| new RuleParser().parseRule(ruleDefinitionVO);
| } catch (Throwable ex) {
| // logger.fatal("Severe error while parsing rule",ex);
| throw new EJBException("Fatal error while parsing rule");
| }
| }
|
| /**
| * clears Cache of RuleBase in Rule Engine
| */
| public void clearCache() {
| try {
| new RuleBaseBuilder().clearCache();
| } catch (Throwable ex) {
| // logger.fatal("Severe Error while clearing RuleBase cache", ex);
| throw new EJBException("Fatal error while clearing RuleBase cache");
| }
| }
| }
|
the exact error is
| d-25]. The thread terminates
| java.lang.ClassCastException: $Proxy61 cannot be cast to com.logica.heca.lpr.ruleengine.RuleEngineRemote
| at com.logica.heca.lpr.services.facade.RuleEngineFacade.process(RuleEngineFacade.java:31)
| at com.logica.heca.lpr.dataLoader.DataLoaderThread.run(DataLoaderThread.java:129)
| 11:51:54,243 ERROR [STDERR] Exception in thread "DataLoaderThread-25"
| 11:51:54,243 ERROR [STDERR] java.lang.RuntimeException: java.lang.ClassCastException: $Proxy61 cannot be cast to com.logica.h
| eca.lpr.ruleengine.RuleEngineRemote
| 11:51:54,243 ERROR [STDERR] at com.logica.heca.lpr.dataLoader.DataLoaderThread.run(DataLoaderThread.java:187)
|
I am running client and server code on same server
help from any one would be highly appreciable.
Thanks
-Ravi
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241421#4241421
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241421
16 years, 9 months
[JBoss Cache: Core Edition] - Re: JDBCCacheLoader with Oracle 10g problem
by mircea.markus
anonymous wrote : No, sorry, I managed to reproduce the problem with one thread on DEBUG level. Here is the log:
| Code:
|
| [2009-07-01 16:11:48,367] [Detection1] DEBUG JDBCCacheLoader - executing sql: INSERT INTO Cached_Eve
| nts (fqn, node, parent) SELECT ?, ?, ? FROM Cached_Events_D WHERE NOT EXISTS (SELECT fqn FROM Cached
| _Events WHERE fqn = ?) (/__JBossInternal__/RTDE/pattern-matching-threshold/663330655/_ID_/aaaa-uiq8a
| n-fwm4m5h3-1-fwm4m8s0-z)
|
|
|
|
| Still don't know how to fill in the question marks to run it...
yep, I've just noticed that the cache loader was modified to create a new table postfixed with "_D", so Cached_Events_D is indeed created by jbosscache. This was a changed made for following JIRA JBCACHE-1410. Guess the query (which looks a bit odd to me) doesn't work on oracle. Is this happening from the start, when you firt try to add something to the cache, or only after a while?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241417#4241417
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241417
16 years, 9 months
[Persistence, JBoss/CMP, Hibernate, Database] - JBoss 5 with Hibernate javax.naming.NameNotFoundException: h
by rhuguet
I am migrating a 4.0.2 JBOSS app which uses hibernate to JBOSS 5.0.1 GA but if i try to get a hibernate session
i keep getting the following error in JBOSS:
javax.naming.NameNotFoundException: hibernate not bound
The deployment of my UserEjb works fine (see log below) but the org.hibernate.SessionFactory of my .har in the JBoss JMX-Management Console = null.
On JBoss 4 the Application works fine.
Anyone know why this would happen? Is there some change in hibernate in JBOSS 5?
Thanks!
René
Deployment Log:
2009-07-02 10:08:59,643 DEBUG [org.jboss.deployment.OptAnnotationMetaDataDeployer] (HDScanner) Deployment is metadata-complete, skipping annotation processing, ejbJarMetaData=org.jboss.metadata.ejb.spec.EjbJar20MetaData@1f, jbossWebMetaData=null, jbossClientMetaData=null, metaDataCompleteIsDefault=false
2009-07-02 10:08:59,721 DEBUG [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (HDScanner) vfszip:/D:/Programme/jboss-5.0.1.GA/server/prodega/deploy/UserEJB.ear/ endpoint mappings:
+ ejb/UserEJB.jar#ejb/UserEjb -> ContainerDependencyMetaData(deploymentPath=UserEJB.jar,componentName=ejb/UserEjb,containerName=ejb/UserEjb,jndiNames=[ejb/UserEjb, UserEJB/ejb/UserEjb],jndiAliasDepends=[],targets=[],jndiDepends=[])
2009-07-02 10:08:59,721 DEBUG [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (HDScanner) Processing unit=UserEJB.jar, structure:
UserEJB.ear
+UserEJB.har
+UserEJB.jar
++EjbEndpoint:ejbName=ejb/UserEjb,ejbClass=com.prodega.user.ejb.UserEjb,home=com.prodega.user.interfaces.UserEjbHome,remote=com.prodega.user.interfaces.UserEjb
2009-07-02 10:08:59,721 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (HDScanner) Encountered deployment AbstractVFSDeploymentContext@13744184{vfszip:/D:/Programme/jboss-5.0.1.GA/server/prodega/deploy/UserEJB.ear/UserEJB.jar/}
2009-07-02 10:08:59,721 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (HDScanner) Encountered deployment AbstractVFSDeploymentContext@13744184{vfszip:/D:/Programme/jboss-5.0.1.GA/server/prodega/deploy/UserEJB.ear/UserEJB.jar/}
2009-07-02 10:08:59,721 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (HDScanner) Encountered deployment AbstractVFSDeploymentContext@13744184{vfszip:/D:/Programme/jboss-5.0.1.GA/server/prodega/deploy/UserEJB.ear/UserEJB.jar/}
2009-07-02 10:08:59,752 INFO [org.jboss.ejb.deployers.EjbDeployer] (HDScanner) installing bean: ejb/UserEJB.jar#ejb/UserEjb,uid20239039
2009-07-02 10:08:59,752 INFO [org.jboss.ejb.deployers.EjbDeployer] (HDScanner) with dependencies:
2009-07-02 10:08:59,752 INFO [org.jboss.ejb.deployers.EjbDeployer] (HDScanner) and supplies:
2009-07-02 10:08:59,752 INFO [org.jboss.ejb.deployers.EjbDeployer] (HDScanner) jndi:ejb/UserEjb
2009-07-02 10:08:59,752 INFO [org.jboss.ejb.deployers.EjbDeployer] (HDScanner) jndi:UserEJB/ejb/UserEjb
2009-07-02 10:08:59,955 INFO [org.jboss.ejb.EjbModule] (HDScanner) Deploying ejb/UserEjb
2009-07-02 10:09:00,033 WARN [org.jboss.ejb.EjbModule] (HDScanner) EJB configured to bypass security. Please verify if this is intended. Bean=ejb/UserEjb Deployment=vfszip:/D:/Programme/jboss-5.0.1.GA/server/prodega/deploy/UserEJB.ear/UserEJB.jar/
2009-07-02 10:09:00,330 INFO [org.jboss.proxy.ejb.ProxyFactory] (HDScanner) Bound EJB Home 'ejb/UserEjb' to jndi 'ejb/UserEjb'
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241415#4241415
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241415
16 years, 9 months