In sticking with the standards, I am trying to build a Model MBean which is not
based off of the proprietary JBoss XMBean implementation. Is this possible?
From what I read in the Wiki it states that in 3.2.6 only the XMBean
implementation was available Although JBoss does not use any Model
I am trying to implement a MBean which persists it's configuration to the
database rather than a xml file which a XMBean does by default. Do I need to
create my own PersistenceManager to do this or does Jboss provide any such
PersistenceManager. From what I read in the Wiki, I seems like
Not sure if JMX is the right technology to do this. I need to manage (add,
edit, delete) some records in a database table and would like to expose these
management operations via a JMX interface using an XMBean with a custom
AttributePersistenceManager. From what I can see, the default JBoss
I was reading through the JBoss AS Clustering ED 7 PDF and noticed that on page
74 or the PDF it refers to jbossha-httpsession.sar which I can't seem to find
in my jboss-4.0.2 installation. I do see a httpha-invoker.sar. Are these 2
.sars equivalent? If not how does HTTP session replication,
When a HTTP session is replicated does it get replicated to all nodes in a
cluster? If so, is there anyway to have the session replicate to some
designated nodes rather then all nodes?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3901271#3901271
Reply to
Thanks for all of the great input! I did try sending non-persistent messages
as genman suggested and it increased the number of messages sent from 60 to
about 100, but that doesn't help me any since the application requires
persistent message handling. And adrian you made a good point about
I don't think it is a bottleneck at the database. Just for testing purposes I
initialized my connection pool with 300 connections split up so that there are
3 nodes each with 100 connections. This I would imagine would be plenty of
connections. This set-up results in the 60 - 100KB
Currently, I am building a system which must have a messaging system which can
support 100 - 100KB messages/second. From what I've implemented in my
prototypes the max number of messages that I can send via clustered HA JMS is
about 60 persistent messages. In the current implementation of
Is it correct to say that a JMS Queue residing in a cluster only exists on a
single node in the cluster and fails over to another node upon failure? If
this is the case, how does loadbalancing work if only one node handles all JMS
Messages? The reason why I'm asking is because I've created a
Curious question can a queue be created and placed in branch other than queue
or in a sub branch of queue? For example if I had a destination named
TestQueue, could the queue be created under customqueue/TestQueue or
queue/jms/TestQueue?
Thanks.
View the original post :
I configured my JBoss 4.0.2 for JMS Clustering and have reliable message
delivery to topics that I've configured via durable subscription (persisting to
a mysql database), but how do I guarantee reliable message delivery for a
queue? From what I know durable subscriptions are only good for
Am I supposed to use the default java:/JMSXA connection factory or do I need to
create my own connection factory? If I should be using the java:/JMSXA
connection factory then can this connection factory be used for all JMS related
activity?
View the original post :
I am trying to determine whether or not 100 - 100KB msgs/sec is achievable or
not in JBossMQ. I've configured JBoss with the following features: mysql
persistence for JMS durable subscriptions, HA JMS, connection pool for mysql
datasource. Currently I can only the max number of messages I've
Is there any good documentation on how to configure a JDBC Connection Pool? I
read the ConfigDataSources Wiki and there isn't any explanation. I added the
following elements to my config file, but i'm not sure if I'm actually using a
connection pool now.
min-pool-size5/min-pool-size
Just curious is anyone knows the persistence logic behind HA JMS. Does JBoss:
a. upon receiving a persistent message always insert the message into the
database
b. keep a certain number of messages in memory until a threshold is reached
My best guess is that it would be doing option a because
I am trying to get durable scription working for a topic that I created so that
I can have guaranteed message delivery. The problem is that I am stuck trying
to authenticate using the mdb-user and mdb-passwd in jboss.xml. How do I
setup the users/roles? I know that I somehow need to use JAAS
I'm trying to run multiple instance of JBoss 4.0.2 on a single machine and was
reading through the Wiki pages. According to the Wiki pages, for JBoss4 it is
required to make the following changes (in the link below) to the
ServiceBindingManager.
From what I've been reading, I'm not sure if MDBs are load balanced in JBoss
4.0.2. The link below on LoadBalancedFaultTolerantMDBs, states that in
3.2.4RC2 load balancing was not available.
http://wiki.jboss.org/wiki/Wiki.jsp?page=LoadBalancedFaultTolerantMDBs
Does anyone know if I need to
18 matches
Mail list logo
