[jboss-user] [JBoss Messaging] - Re: MQ migration help

[tnine]

Thanks for the help again.  I've given up on the JEMS version of JBoss.  I was getting very strange serialization issues.  As soon as I installed messaging to the "all" server from the 4.2.2GA download and configured the data sources everything started working.  Note that I couldn't use the jbossall-client.jar as outlined in the doc, since it conflicted with my version of Hibernate.  Would it be possible to list each specific client jar in the doc?  I have my client working, but it was a guess and check on the jar files, and I want to be sure I have everything I need.

I'm was also having a bit of a performance issue.  When I was using MQ, I could queue up my messages very quickly.  My messages are object messages, and they're quite large, between 16k up to 40k (so far).  With JBoss MQ I could queue around 500 messages a minute with our current POJO client.  With JBoss messaging and the default queues, it takes about 10 minutes to queue 500 messages, then hangs at around 570 messages.  I though this may be due to my queue configuration and paging given the large message size.  I lowered the memory storage and paging quite a bit, which appears to have fixed my issue.  Is this a valid fix, or is there a better way to handle large messages?

Settings
Data Source: DefaultDS
Database Type: MySQL (InnoDB Tables)
Connection Info: java.naming.provider.url=jnp://localhost:1100
Connection Factory JNDI Location: ClusteredXAConnectionFactory

destinations-service.xml

  | 
  | 	<!-- Input Queue for statements -->
  | 	<mbean code="org.jboss.jms.server.destination.QueueService"
  | 		name="jboss.messaging.destination:service=Queue,name=StatementInput"
  | 		xmbean-dd="xmdesc/Queue-xmbean.xml">
  | 		<depends optional-attribute-name="ServerPeer">
  | 			jboss.messaging:service=ServerPeer
  | 		</depends>
  | 		<depends>jboss.messaging:service=PostOffice</depends>
  | 		<attribute name="DLQ">
  | 			jboss.messaging.destination:service=Queue,name=StatementDLQ
  | 		</attribute>
  | 		<attribute name="Clustered">true</attribute>
  | 		<attribute name="MaxDeliveryAttempts">2</attribute>
  | 		<attribute name="FullSize">100</attribute>
  | 		<attribute name="PageSize">50</attribute>
  | 		<attribute name="DownCacheSize">50</attribute>
  | 		
  | 	</mbean>
  | 
  | 	<mbean code="org.jboss.jms.server.destination.QueueService"
  | 		name="jboss.messaging.destination:service=Queue,name=StatementOutput"
  | 		xmbean-dd="xmdesc/Queue-xmbean.xml">
  | 		<depends optional-attribute-name="ServerPeer">
  | 			jboss.messaging:service=ServerPeer
  | 		</depends>
  | 		<depends>jboss.messaging:service=PostOffice</depends>
  | 		<attribute name="DLQ">
  | 			jboss.messaging.destination:service=Queue,name=StatementDLQ
  | 		</attribute>
  | 		<attribute name="Clustered">true</attribute>
  | 		<attribute name="FullSize">100</attribute>
  | 		<attribute name="PageSize">50</attribute>
  | 		<attribute name="DownCacheSize">50</attribute>
  | 	</mbean>
  | 
  | 
  | 	<!-- DLQ for statements -->
  | 	<mbean code="org.jboss.jms.server.destination.QueueService"
  | 		name="jboss.messaging.destination:service=Queue,name=StatementDLQ"
  | 		xmbean-dd="xmdesc/Queue-xmbean.xml">
  | 		<depends optional-attribute-name="ServerPeer">
  | 			jboss.messaging:service=ServerPeer
  | 		</depends>
  | 		<depends>jboss.messaging:service=PostOffice</depends>
  | 		<attribute name="Clustered">true</attribute>
  | 		<attribute name="FullSize">100</attribute>
  | 		<attribute name="PageSize">50</attribute>
  | 		<attribute name="DownCacheSize">50</attribute>
  | 	</mbean>
  | 


Thanks,
Todd

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144708#4144708

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144708