architectures

jpanico Apr 20, 2004 7:09 PM

Hello,

I'm looking for a simple JMS provider, but I have a couple of architectural restrictions.

I'm looking to use only the P2P domain.

1) I'm not allowed to deploy (or embed) any databases at all. Can JBoss use the filesystem to store P2P messages?

2) Both peers (producer and consumer) for the initial deployment will run in the same process. So I want the communications between peers to not use network based communications, but instead use a wholly intra-process communications mechanism. And the entire JMS service must run "in-process"-- there cannot be a standalone server.

Since my needs are so simple, you are probably wondering why I bother with JMS at all-- looks like running over an ant with a tank. The answer is that I want the queue based communications to use an API that would allow me to activate or swap-in fancier features in the future, such as distributed communications, persistent messages, etc.

thanks for any tips,

joe

1. Re: architectures

genman Apr 20, 2004 11:33 PM (in response to jpanico)

1) JBoss by default persists messages using a built-in database called HSQL. Adrian doesn't care for it, but it works well for me, at least for JMS. The other persistence implementations use files, but are not supported or may have bugs. Search for FilePersistenceManager and RollingLogged Persistence Manager. There are also examples in the JBoss distribution.

2) There is an in-process client/server connection factory. In your EJBs, locate javax.jms.ConnectionFactory using JNDI at java:/JmsXA. Use java:/ConnectionFactory for non-transacted use.
Actions
2. Re: architectures

adrian.brock Apr 21, 2004 8:41 AM (in response to jpanico)

There is also a NullPersistenceManager in jboss-3.2.4RC1
http://jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQNullPersistence
Actions

Go to original post