So, to clarify:
If you are using straight JMS (no MDBs) and using non durable subscribers to
subscribe to the topic, then if the connection between the client and the
server is lost, any messages sent to the topic while the connection is down,
will be lost (since the subscription is non
Please state your JBM version etc
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4116791#4116791
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4116791
___
jboss-user mailing list
JA121 wrote : After I had managed to start the Message Bridge, I noticed an
interesting thing.
|
| The source queue of my bridge didn't show the amount of the sended messages.
What attribute of the source queue are you looking at? Message Count?
If so, then yes, this may well show zero,
If you want to use message counters you need to explicitly enable them.
See userguide for more details.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4116825#4116825
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4116825
assaf49 wrote : Scenario:
| A JMS Connection is used to create 10 JMS listeners on Topic MyTopic.
|
By listener I'm assuming you mean non durable subscription (?)
And I'm assuming you're not using MDBs since you haven't mentioned them.
anonymous wrote :
| Each Listener has a different
Please read the FAQ!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4116469#4116469
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4116469
___
jboss-user mailing list
The whole point of a clustered topic is that it is clustered across *all*
nodes, i.e. all consumers on *all* nodes will get the message.
If you don't want consumers on other nodes to get the message then don't user a
clustered topic!
View the original post :
You shouldn't make any assumptions about what a message id contains apart from
that it must start with 'ID:' and be unique per message. (This is what is
mandated by the JMS spec).
Making any such assumptions further than that will make your code highly
brittle and non portable.
Just because
Well, you _could_ have multiple MDBs consuming from a single live JMS server -
this is the old JBoss MQ style approach where you only have one active server
in the cluster at any one time, nothing is stopping you from doing that if you
want.
Alternatively just have MDBs always consuming from
Maybe I don't understand the question, but a topic always delivers any messages
to *all* subscribers (assuming no message selectors).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4116076#4116076
Reply to the post :
If there is only one consumer on a queue, JBM already maintains delivery order,
even after failure.
If there is more than one consumer on the queue this is not really possible.
Since order delivery order in the queue will be determined by the order the
consumers failed - i.e. non
I'm assuming you are using durable subscriptions on your topic, or they won't
survive failure anyway.
On that assumption, order after failover will be maintained.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4116086#4116086
Reply to the post :
I don't understand your use case.
If your subscriptions are non durable, then they won't survive failure,
therefore saying order is maintained is meaningless.
Maybe you need to explain your scenario in more detail...
View the original post :
The actual temporary queue _does_ get deleted on connection close, or explicit
delete.
However it seems the destination object remains in JNDI if you close the
connection without explicitly deleting the temp destination. This will give a
small resource leak (the actual destination object is
JBoss Messaging 2.0 will use MINA for its primary transport (we are already
well on the way coding this).
For JBM 1.4 you don't have much choice than use remoting.
If you post on the remoting forum, the remoting team should be able to help you
in tuning your settings.
View the original post :
Any JNDI url that begins with java: is only available in the *same virtual
machine*.
You clearly want to look up objects from JNDI from different machines, so
looking them up from your in vm context is not going going to be correct.
View the original post :
There is an example of this on the user wiki.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4115746#4115746
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4115746
___
jboss-user
If you use a connection factory with connection load balancing, this means that
subsequent connections created with that factory will be made to different
nodes in the cluster, in a round-robin fashion.
Typically with MDBs, you deploy the MDB on every node of the cluster, in a
homogenous
http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.SP3/html/configuration.html#conf.destination.queue.attributes.redeliverydelay
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4114771#4114771
Reply to the post :
The examples directory contains examples of distributed queue, topic and
failover
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4113852#4113852
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4113852
If you have a distributed queue with an MDB consuming from that queue - one on
each node, and send messages to that queue on a particular node, then the local
consumer (i.e. the local MDB) will always get the messages by preference.
This makes sense, since there's no point sending the messages
Did you run the examples after installing JBoss Messaging? (see user guide).
One of the examples tests a clustered queue. So if this works, you know that
functionality works.
Next step is to see how your code differs from the example code.
View the original post :
bodrin wrote : Thanks, Tim!
|
| The example works fine (nice ant scripts :), so I suppose the problem is in
my code and I have to investigate it ..
|
| I saw your comment at JIRA: MessagePullPolicy no longer exists
| So, message redistribution is enabled by default and there is no way
You need to look the Queue up from JNDI - please read the link to the tutorial
I posted :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4112194#4112194
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4112194
If you're in a managed environment you can use the JCA JMS resource adapter to
cache connections:
See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossJMSRA
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=491#491
Reply to the post :
Glad that works for you :)
If you want to be sure you don't receive duplicates just make sure your
consumers use a transacted session to consume - then you should get guaranteed
once and only once delivery as per spec.
Currently you're using a non transacted session so losing messages /
One observation:
You're creating a connection, session, and producer for every message that you
forward!
This will be extremely slow...
Connection and sessions are heavyweight objects that you want to create once
then re-use. Really you want to re-use the producer too.
View the original post
Ok, thx Aaron.
Please add a JIRA :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110813#4110813
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110813
___
jboss-user mailing
I didn't understand your topology.
Can you explain it again in more detail?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110947#4110947
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110947
I'm not sure I understand your topology either.
Can you explain it again, just to avoid ambiguity. Not sure what you meant by
receiving node.
Is the queue clustered? Is the MDB on each node? Are you using persistent / non
persistent messages etc?
View the original post :
chip_schoch wrote : W1 and W2 post response messages to response queue (Q2)
on L1.
|
Ok so you've posted your messages to clustered response queue Q2 on L1
anonymous wrote :
| The MessageConsumer.receive() called by the L1 service receives the
response messages it is waiting for.
|
Have a look at
org.jboss.test.messaging.jms.clustering.DistributedRequestResponseTest for an
example of how to do this.
http://anonsvn.jboss.org/repos/messaging/branches/Branch_Stable/tests/src/org/jboss/test/messaging/jms/clustering/DistributedRequestResponseTest.java
View the original post :
JMSX properties are reserved by the JMS spec.
Provider defined properties are supposed to start with JMS_vendor name, so it
seems like WSMQ is not following the spec (see JMS 1.1, 3.5.9, 3.5.10).
We could I guess add a flag to relax this checking. Please feel free to add a
feature request.
I am pleased to announce the release of JBoss Messaging 1.4.0 Service Pack 2
(SP2).
This release contains several bug fixes and several other non bug-fix tasks.
The release notes are available here
We can't really help you unless you provide us with basic information:
What exact version of JBM are you running?
What exact version of JBoss Remoting are you running?
What exact version of JBoss AS are you running?
What JDK/OS etc.
Clear instructions on how to replicate the problem.
Thanks
I'm not sure how a thread pool is going to enable you to publish messages
faster.
Can you be more specific about your perf problems? Using straight JBM you
should be able to publish many 1000s of messages / second. Of course this
depends on your messages size and whether your messages are
Did you enable message counters? :
http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.SP1/html/configuration.html#conf.serverpeer.operations.enablemessagecounters
View the original post :
Once you have obtained your connection factory, you just use the standard JMS
API to create a connection, session and producer.
This is all standard JMS stuff, I suggest a JMS tutorial to get you started.
http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/jms_tutorialTOC.html.
If you are
Does JBoss MQ block if the queue is full?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109523#4109523
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109523
___
jboss-user
Put your logging on trace, rerun it and look for errors in your logs.
For some reason it looks like failover isn't completing on node 1.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109171#4109171
Reply to the post :
ejb3workshop wrote : In Jboss MQ there was an option to configure the max
depth of a queue as well as various others, such as InMemory.
|
| http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigQueue
|
|
| Is there similar options available on JBoss Messaging and where can I find
them. I
This is http://jira.jboss.org/jira/browse/JBMESSAGING-1138
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4108820#4108820
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4108820
___
Hmm... How are you killing the node?
kill -9, CTRL-C, something else?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109054#4109054
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109054
http://jbossesb.blogspot.com/2007/11/swedish-railways-and-jbossesb.html
Swedish railways just gone live with a site using JBoss ESB, which is using JBM
as transport :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109051#4109051
Reply to the post :
seammm wrote : It might be a good opinion to provide samples for UDP to JMS,
SIP to JMS, and even for serial to JMS bridging in later releases. These would
get outside devices such as PBX switches and other hardware talking to JBoss
server. Thanks.
Yes, that's an interesting idea. I'll add a
You need jboss-aop.jar on your classpath.
See userguide for exact details of what you need on the client classpath.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109065#4109065
Reply to the post :
http://jira.jboss.org/jira/browse/JBMESSAGING-1170
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109067#4109067
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109067
___
DB2 has never been supported, it was a mistake that a configuration file for
DB2 was distributed with previous distributions.
However, it shouldn't be too hard to create a DB2 config that works. Just to
need to make sure the columns are of the correct type for DB2 and maybe make
some small
I have put in a small change to make the queue unlimited for SP2.
Not sure if we really need full configurability?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4108401#4108401
Reply to the post :
tpaterson wrote : Hi Tim,
|
| our .jnlp file specifies
|
|
| all-permissions
|
|
| which I believe allows us to do most anything..
|
| certainly our app can make socket connections to the app server (for
session bean calls - and to use JBoss MQ Queues),
|
| so I'm
It's my understanding that webstart runs in a restricted security environment.
Unfortunately JBoss remoting creates ClassLoaders - if that's prohibited by
your security policy then it's not going to work.
View the original post :
Can you post/send me your full thread dump?
Thx
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106633#4106633
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4106633
___
jboss-user
Ok sorry, you're right :)
Yeah, the unique server id issue is a known one - as you know, it's been
discussed on other threads.
If we could use a string, then it would be trivial - we could just generate a
GUID and save back into the xml like you say.
(However I don't think hashCodes are a
aslak - I think you posted on the wrong thread?
This thread is about configuring bisocket transport ports.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4105447#4105447
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4105447
Can you try with a more up to date version of JBM?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4104861#4104861
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4104861
___
Jeremy Stone wrote :
|
|CREATE_IDX_MESSAGE_REF_TX=CREATE INDEX JBM_MSG_REF_TX ON JBM_MSG_REF
(TRANSACTION_ID, STATE)
| |
|
| Not sure yet if this will have any undesired side effects or whether the
same change should be applied for other database persistence serices.
|
|
What exact version are you using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4105091#4105091
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4105091
___
jboss-user mailing list
mpr_prabhu wrote : We are using JBoss Messaging 1.4 GA
I cannot be sure it will solve your problem but I would certainly recommend
upgrading to SP1
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4105191#4105191
Reply to the post :
mclu wrote : Thx Tim!
|
| I saw the Jira entry
| http://jira.jboss.com/jira/browse/JBAS-2444
| about the ordering issu and a Link to Messaging.
|
Yes, that feature is implemented in JBM.
anonymous wrote :
| But anyway.
| Does your explanaition mean that after a NACK/Transaction
JeremyStone wrote : However the problem with this is that messages seem to
be getting acknowleged in spite of failure (setRollbackOnly called) and no
redelivery is occurring.
|
| Looking at the JBoss Messaging source, SessionAspect.handlePostDeliver()
calls
You should try out 1.4.0.SP1
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4104534#4104534
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4104534
___
jboss-user mailing list
Tracking the deadlock issue http://jira.jboss.org/jira/browse/JBMESSAGING-1152
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4104538#4104538
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4104538
kapucin wrote :
| One question on fault-tolerange to message loss. Do the messages get
replicated across the cluster (using post-office pulling or post-office
routing?), so in case a node fails, they are not lost OR are they stored in a
database until acknowledged?
|
Persistent messages
chip_schoch
I thought that clients of the clustered queue could connect to whichever node
they found first and they would get messages from any partial queue. Is this
incorrect?
[/quote wrote :
|
| This is correct, but you want to avoid unnecessary redistribution if you
can.
kapucin wrote :
| Most of the time there will be at least one consumer on each queue. So
there is no need to route/pull the messages until a consumer starts to choke or
fails completely. Of course, if my assumptions on how it works are correct.
|
That's right - JBM always tries the local
Looks like you are sending message to both of the partial queues, but both your
service instances are connected to the same node for consuming.
For this kind of topology you probably only want each consumer to consumer from
its local node? If so, then you should just use the standard connection
Thanks Jeremy for that. :)
I'll run some tests here and see if we can incorporate your fix.
BTW Regarding your usage of Spring, I don't know it applies in your case, but
have you seen
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBMSpringJMSTemplateNotes ?
View the original post :
Hello kapucin - comments inline
kapucin wrote : Hello
| Could someone, please, explain what's the advantage of using HA-singleton
vs Distributed queue (DQ)?
| Is HA-singleton simply the old way for providing the fail-over
functionality, and should not be used as DQ is better?
|
JBoss
If you use a straight JBM consumer, and only have one consumer per queue, then
order should be preserved on rollback.
However I don't think things are so simple with MDBs, since AS MDB layer
maintains a buffer of messages ready to send to MDBs.
I would need to look into this further, but maybe
Sorry my last post got a bit munged - I just re-edited it
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4104297#4104297
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4104297
___
The problem is the messages are no longer on the server side, the buffers are
on the client side.
So the server would have to query every single consumer (maybe thousands) to
find out what is in their buffers which is not really practical.
We could store a copy of them on the server side, but
Inside the app server you can use the JBoss JCA resource adapter (the thing at
/JmsXA - see the user wiki) for caching sessions.
This is useful when you're for example sending messages from an EJB.
Note that JCA JMS resource adapters do not cache JMS connections, they cache
JMS sessions.,
JBM 1.4 is not wire format compatible with earlier versions of JBM, so you
would need the same version of JBM on both the client and server side.
Once JBM gets into the EAP, we will start to provide compatibility guarantees
between successive versions.
View the original post :
Each MessageConsumer maintains its own buffer of messages (see prefetchSize in
the documentation), which are prefetched from the queue/subscription before
they are actually consumed.
IIRC the prefetch size default is 150. So, if you have a consumer open and even
if you haven't consumed any
Are you using Spring JMSTemplate currently just to send messages, or to consume
them too?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4103044#4103044
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4103044
Are you talking about usage inside the app server, or outside the app server -
e.g. in your own client programs?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4103039#4103039
Reply to the post :
You're referring to topic hierarchies which is something we're going to
implement for JBM 2 :)
http://jira.jboss.org/jira/browse/JBMESSAGING-523
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102589#4102589
Reply to the post :
Ok, thx.
I'll ask the remoting team to investigate.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102540#4102540
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4102540
___
All the timings are in JIRA :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102597#4102597
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4102597
___
jboss-user mailing list
Can you upgrade to SP1 and see if the problem still occurs.
CR1 is a candidate release and not meant for production.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102693#4102693
Reply to the post :
noxis wrote :
| BTW. As you can see in my config, I am trying to do infinite redelivery by
pointing DLQ to the same queue. Is this ok? Maybe there is a better solution?
|
You could just set maxDeliveryAttempts to a very large value.
Pointing the DLQ to the same queue would mean the
They should be the same.
-brew just means the jar is rebuilt from source in a controlled redhat build
environment - slightly worrying they are different! are you sure?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102352#4102352
Reply to the post :
I have seen something like this before when different versions of JBoss
remoting are used on the server and client side.
Can you check you have
a) Dropped remoting 2.2.2-SP1 in the server/lib directory on your as profile.
b) Make sure remoting 2.2.2-SP1 is the first entry on the client classpath
The AS JCA layer also has it's own redelivery logic (this is the one that's
controlled by DLQMaxResent) - this is so that JCA layer can be used
consistently with a range of different JMS providers who may not have their own
redelivery or DLQ functionality.
JBM also has it's own DLQ and
amalcaraz-
Could you add a JIRA report, with instructions on replication, then someone
will take a look?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101948#4101948
Reply to the post :
The installation instructions in the JBM user guide should tell you what you
need to know.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101348#4101348
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4101348
haagenhasle wrote : I
| Has anyone got this working with MySQL?
|
Of course. MySQL is the database most users use and we test heavily against it.
If you following the installation instructions from the JBM user guide, and
make sure you're using a supported DB. (see the wiki for list of
haagenhasle wrote :
| I don't really understand why you give me an attitude and tell me to RTFM,
would it hurt to help a newbie out and actually take a look at the problem I
had?
|
No one has given you attitude or told you to RTFM.
Although that might have been an appropriate response if
Hi-
Where did you get your mysql-persistence-service.xml from? Looks like you're
using an old version.
Also what version of JBM are you using?
Thx
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101428#4101428
Reply to the post :
earniedyke wrote : I downloaded jboss-messaging-1.4-0.SP1.zip an hour ago and
extracted it. I moved the DELETE_MESSAGE line up one 1 in the file to see if
the error changed. That's the only thing I have done to it.
|
|
You must be using an older version of the config. Try copying over
beve wrote : Yeah, the problem was that we had the wrong version of
mysql-persistence-service.xml but when using this version of it things worked:
|
The correct version to use for 1.4.0.SP1 is the version in the examples/config
directory of the 1.4.0.SP1 distribution.
View the original post
I don't know what version of JBM ESB is using. You better ask the ESB guys
that. :)
But the correct config to use is the one from the examples/config directory of
whatever version it is using.
I would certainly recommend using 1.4.0.SP1 over 1.4.0.GA though. Upgrading is
very simple and
1.4.0.SP1 config won't work with 1.4.0.GA and vice versa.
You need to make sure you're using the correct version.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101445#4101445
Reply to the post :
earniedyke wrote : Tim,
|
| I found 1.4.0.GA and downloaded it, copied over
mysql-persistence-service.xml and it is working now. Must be very particular
about things. Thanks for the help
|
That's great. :)
However I wouldn't recommend using 1.4.0.GA since it's been superceded by
If you give me instructions on how to replicate, I'll take a look.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100745#4100745
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100745
I am pleased to announce the release of JBoss Messaging 1.4.0 Service Pack 1
(SP1).
This release contains several bug fixes; a few relating to some failover edge
cases, an important fix in byte message handling, some sanity checking and
configuration changes in JBoss Remoting and several
Could you try with JBoss Messaging 1.4.0.SP1 (just released)?
If the problem still occurs, could you please add a JIRA task with instructions
on how to replicate, and we'll investigate?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100836#4100836
Looks like this one:
http://jira.jboss.com/jira/browse/JBMESSAGING-1079
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100445#4100445
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100445
Can you add a JIRA task for this?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4099804#4099804
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099804
___
jboss-user mailing list
Best place to start is the project page http://labs.jboss.com/jbossmessaging/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4099803#4099803
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099803
701 - 800 of 1586 matches
Mail list logo
