[JBoss Messaging] - MySQL in Cluster question
by jbabad
Hi,
We're using JBoss 5.0.0.GA with it's JBM and want to use a MySQL cluster as the underlying DataSource.
Currently we're using MySQL 5.0.51 - so the cluster is in-memory.
What will the maximum message size that we can send. I've seen a note on the MySQL site that mentions that there's an 8K limitation on a table row in the cluster. So, question is that the JBM_MSG table stores the headers and payload as blobs and we could be sending TextMessages of 10k characters or more. Would this be a problem?
I'm a bit puzzled as I've managed to send a 10k message through the cluster - but I'm worried whether I'm missing anything.
I have had a bit of a trawl through the forums but couldn't see anything that quite fitted the bill.
As a follow-on question what would be the effect if we could upgrade either to MySQL 5.1.x or possibly to MySQL NDB Cluster 6.x?
Any help would be appreciated.
Thanks,
Joseph.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207081#4207081
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207081
17 years, 4 months
[Installation, Configuration & DEPLOYMENT] - Re: Copying large ear over network: URLDeploymentScanner rea
by PeterJ
The second URL is the best bet (doesn't reply on an administrative share and admin access to that share), and it should work. So it is debugging time. Here's what I would do:
1) Install JBoss AS locally and run twiddle from a local bin directory. This will eliminate weird issues with accessing twiddle, and the files it requires, across the network. If this works, reduce the local JBoss AS footprint to include only the necessary files to satisfy twiddle. If it does not work, go to set 2. (An alternative is to log into test-server, open a command prompt and run twiddle from there.)
2) Try the URL in jmx-console. If that works then the URL is fine and the issue is with twiddle. If it does not work, then the problem is in the MBean somewhere.
3) Then add debug code to twiddle or the mbean to figure out what is going on.
Wait a minute, another thought crossed my mind. Are you running twiddle from a remote system? If so, twiddle connects to locahost by default, which is the remote system, which is not where the app is located! Try adding "-s test-server:1099" to the command line (run "twiddle --help" for full syntax).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207079#4207079
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207079
17 years, 4 months
[JCA/JBoss] - Deployment of a RAR in an EAR with an EJB-JAR
by mcconnma
Howdy,
I have an ear deployment as such:
| META-INF/
| META-INF/MANIFEST.MF
| x.rar
| y.jar
| META-INF/application.xml
I am having a problem deploying a RAR and and EJB-JAR in an EAR deployment. From above, if I deploy the RAR and EJB-JAR seperately, no problems ... the EJB-JAR is a message endpoint for the RAR, so I know this is set up properly. The problem is when all in an EAR, I get the following error when looking at JBoss logs:
(Caused by: javax.management.InstanceNotFoundException: jboss.jca:service=RARDeployment,name='x.rar' is not registered.)
Following the stack trace, it looks like the RAR is being deployed first, then the EJB-JAR is trying to be deployed. The funny or odd thing is that after that error is shown in the logs, I get a 'start' call on my Resource Adapter in the RAR. I think I read from the JCA 1.5 spec that a RAR isn't considered 'deployed' until 'start' is successfully returned? So, my question is how do I make the EJB-JAR 'completely' dependent on the deployed RAR?
Here's my applicaiton.xml:
| <application>
| <display-name>whatever</display-name>
| <module>
| <connector>x.rar</connector>
| </module>
| <module>
| <ejb>y.jar</ejb>
| </module>
| </application>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207061#4207061
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207061
17 years, 4 months