Have you considered using HornetQ - HornetQ supersedes JBoss Messaging.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4269790#4269790
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4269790
jeffleboss wrote :
| I have the same requirement.
|
| The problem is that I cannot upgrade to HornetQ, since we are using JBoss
5.1.0.
|
HornetQ works with both JBoss 4 and JBoss 5 (see quickstart guide)
View the original post :
HornetQ does support it
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4268986#4268986
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4268986
___
jboss-user mailing list
Firstly, I can't tell what messaging system you're using (could be JBoss MQ or
JBoss Messaging), but just because a message is still in a queue after TTL does
not mean TTL is not honoured.
The JMS spec just says that messages should not be delivered after TTL is
exceeded. It does not require
svn
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4268892#4268892
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4268892
___
jboss-user mailing list
jboss-user@lists.jboss.org
This depends what messaging system you are talking about.
JBoss has 3: JBoss MQ, JBoss Messaging and HornetQ.
HornetQ certainly has auto reconnect functionality
IIRC JBoss Messaging and JBoss MQ do not.
View the original post :
You didn't look very hard
All the tags are here:
http://anonsvn.jboss.org/repos/messaging/tags/
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4268902#4268902
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4268902
You're in the wrong forum.
JBoss MQ is a completely different messaging system to JBoss Messaging.
You should post in the JBoss MQ user forum instead.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4268122#4268122
Reply to the post :
If you go to the JBoss Messaging home page (go to jboss.org and follow the
links), that will explain what JBoss Messaging is.
JBoss MQ is the system that came before JBoss Messaging and is in JBoss AS 4.2.3
You'll find that JBoss Messaging, as a project is superseded by HornetQ.
So we have
Also, there's an explanation in wikipedia
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4267385#4267385
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4267385
___
jboss-user
If you're talking about HornetQ, you're in the wrong forum.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4266784#4266784
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4266784
___
You're in the wrong forum, this forum is for JBoss Messaging, not HornetQ.
Go to hornetq.org and follow the links to forums, documentation etc
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4264414#4264414
Reply to the post :
JBoss MQ forum is here.
http://www.jboss.org/index.html?module=bbop=viewforumf=48
Not sure what you mean by it's closed - can't you post messages?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4264281#4264281
Reply to the post :
asander wrote : Thank you for the link.
|
| I can post messages there but it is a subforum of closed and obviously
not in use anymore. It seems the forum is not read anymore by anyone.
That's a shame, but I don't think it will help you to post here, since no-one
here knows much about JBoss
You're asking in the wrong forum.
This forum is about JBoss Messaging, if you want to know how to configure a
different JMS provider in JBoss AS, the correct place to ask is the JCA users
forums.
Also look in the wiki
View the original post :
This forum is about JBoss Messaging. The correct place to ask questions about
other JMS providers is in the JCA user forum.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263525#4263525
Reply to the post :
If you're using a stateless session bean that means you're running on a server
so you can just use JCA pooling.
There are various wiki pages on this.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4262091#4262091
Reply to the post :
This is actually mandated by the JEE spec.
Any JMS connections you create from a SLSB must be created (and pooled) by a
JCA managed connection factory.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4262097#4262097
Reply to the post :
http://www.jboss.org/community/wiki/ShouldIcacheJMSconnectionsandJMSsessions
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4262099#4262099
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4262099
jar hell has been a known issue for a long time in JBoss Messaging.
But all new dev is on HornetQ - which doesn't have these issues.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4259583#4259583
Reply to the post :
IIRC, the user manual chapter 4 explains exactly what jars you need on the
classpath, and in what order.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4258855#4258855
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4258855
There exact jars you need on the client side is explained in detail in section
4.4 of the user manual, and yes, it does also say in a yellow note box that
they must appear in a different order:
Looks to me there is an extra . on the address:
| Caused by: java.net.UnknownHostException: 0.0.0.0..
|
Should be 0.0.0.0 not 0.0.0.0.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257577#4257577
Reply to the post :
First, I'd recommend you use beta5.
Also moving this question to the hornetq forum
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257265#4257265
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4257265
That is not correct.
It is an *anti pattern* to create a new session/consumer/producer each time you
say, send a message.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4255710#4255710
Reply to the post :
I'm going to wite a wiki page on this. This question must have come up about
10 times and I'm getting tired of answering it ;)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4255717#4255717
Reply to the post :
I've written a wiki article on this subject, on the HornetQ wiki:
http://www.jboss.org/community/wiki/ShouldIcacheJMSconnectionsandJMSsessions
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4255793#4255793
Reply to the post :
This is an exciting day for messaging at JBoss and Red Hat.
After months of preparation, the middleware messaging team are excited to
announce the birth of a new project HornetQ
What is HornetQ?
HornetQ http://hornetq.org is an open source project to build a multi-protocol,
embeddable, high
This seems to be an issue in consumer window sizing.
You can workaround it for now by setting ConsumerWindowSize on the connection
factory to a very large number (or zero).
I've opened on a JIRA on the HornetQ project http://hornetq.org
We should continue the discussion on the hornetq forum
https://jira.jboss.org/jira/browse/HORNETQ-111
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4251198#4251198
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4251198
___
jboss-user
Hello All-
With the launch of our new HornetQ http://hornetq.org project, if you've been
previously evaluating JBoss Messaging 2.0, could you please use the HornetQ
user forum http://www.jboss.org/index.html?module=bbop=viewforumf=312 for any
issue from now on.
This forum will only be used
Simon- you're absolutely right.
It's clear from looking at the code that it's highly inefficient to allocate a
large buffer when perhaps as little as one byte is read from the stream.
I have refactored the code, so this is done more sensibly!
The fix will be in the next release (on Monday)
Fixed in trunk https://jira.jboss.org/jira/browse/JBMESSAGING-1716
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4250324#4250324
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4250324
If you want messaging and a database to work as part of the same JTA
transaction in a servlet, you should use the JMS JCA adapter (java:/JmsXA) in
the same way you might do it from an EJB.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4249342#4249342
Reply
A message's timestamp is set on the *client side* before it is sent, not by the
server.
The order messages are put in a queue are the order they are received on the
server.
So, there's no guarantee that messages in a queue will be in order of timestamp.
View the original post :
clebert.suco...@jboss.com wrote :
| You could set paging-max-global-size-bytes to something very close to your
full memory. Say..if you have 1G memory. Put it 700MiB (700 * 1024 * 1024).
|
Actually, I would recommend keeping it at the default value of -1, and just
specifying paging
AIUI You shouldn't need to sign any jars since JBM should require any extra
permissions beyond those given to an applet.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4247764#4247764
Reply to the post :
clebert.suco...@jboss.com wrote : On the JMS example, the only bug I found
was the second destination didn' t enter into page mode right away. What should
be fixed. But that will mean the destination will enter into page mode right
away, so it should fail at the first time.
|
| In your
What browser are you using?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4247768#4247768
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247768
___
jboss-user mailing list
jmesnil wrote : clebert.suco...@jboss.com wrote :
| | In your case.. you have the server full. We can't route any more
messages until DestinationA had messages being consumed and Acked.
| |
|
| I'm not sure I understand it. Why would I been able to consume from
destinationA but
gaohoward wrote : Hi Tim,
|
| I'm using firefox 3.0.12.
|
|
| | You shouldn't need to sign any jars since JBM should require any extra
permissions beyond those given to an applet.
| |
|
| I don't understand it. Are you saying if i didn't sign the jars, the applet
still
gaohoward wrote :
| So if you want to access JBM from c/c++, i think you need use JNI to wrap
the JBM java client.
|
|
No, you can use any stomp client with JBM 1.x with StompConnect.
Stomp clients are available in many languages including C++
View the original post :
There is no such method Message.acknowledgeThisMethod() on the JMS API.
JMS does not support the acknowledgement of specific messages. This is not
specific to JBoss Messaging.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4247549#4247549
Reply to the post :
The JBM core api is more powerful than the JMS API in that if you call
message.acknowledge() it will acknowledge all messages up to and including that
one that have been delivered on the session.
This differs from the JMS message.acknowledge() which acknowledges *all*
messages that have been
ejb3workshop wrote :
| I haven't found this issue reported anywhere else,
|
It's in JIRA https://jira.jboss.org/jira/browse/JBMESSAGING-1682
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4247593#4247593
Reply to the post :
I'm not sure I fully understand what is going on here - if the management reply
is paged, then won't it get depaged when it is consumed?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4247422#4247422
Reply to the post :
sanches wrote : Hello all,
|
| Is it possible to receive TextMessages (with XML payload) from the client
written in c++ and using ActiveMQ?
| What URI should be given to the cpp client in such a case?
|
| Thanks.
Yes, it's possible to use activemq with c++ clients, but I don't see
clebert.suco...@jboss.com wrote : Is it possible to receive TextMessages
(with XML payload) from the client written in c++ and using ActiveMQ?
| | What URI should be given to the cpp client in such a case?
|
| Sorry... your question was a little bit obscure to me...
|
|
| I
clebert.suco...@jboss.com wrote : ... and JBossMessaging will implement AMQP,
and other clients such as C++, .NET will be able to connect to JBoss Messaging
2 using those libraries, which is a nice synergy.
Not only AMQP, JBM will be implementing REST and STOMP natively giving you a
very large
JBM 1.4 should *never* be used with an XA JDBC data source.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4247381#4247381
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247381
___
Please post on the JCA forum - this question is not about JBM
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4247382#4247382
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247382
First of all, you are using JBoss Messaging 1.x , not JBoss MQ (default JMS
provider in AS 5.0 is JBM) - I can see that in the stack trace.
| javax.jms.JMSException: There is no administratively defined topic with
name:SERVER/TOP
|
In JBM 1.x Having a forward slash in a destination name
As Clebert mentioned, MDBs are *not* part of JBoss Messaging - JBM has no
knowledge of MDBs.
MDBs exist as part of JBoss AS. MDBs provide their own pooling and buffering of
messages which is not part of JBM.
View the original post :
As I mentioned in my previous reply you need to either a) use a clustered
*temporary* queue b) use a response *topic*
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4245478#4245478
Reply to the post :
You're not specify your hostname on your acceptors, this will default to
localhost which is clearly not visible from other machines.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4245469#4245469
Reply to the post :
Also it would help a lot if you always mention what exact version you are
running.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4245470#4245470
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4245470
If you have a queue called responseQueue deployed on each of your nodes, how
can JBoss Messaging possibly know which actual version of responseQueue on what
node to send the response to? JBM is not psychic ;)
It can't, you simply haven't given it enough information.
The proper way of
There are tests in the JBM test suite which should be checking it runs ok in a
restricted security environment.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244706#4244706
Reply to the post :
It's very difficult for us to give a recommendation since we're not familiar
with your business or architecture, and there's rarely a one size fits all
solution.
But I'll try to give some pointers, if you're sending messages from web
requests into an application in the same app server instance
clebert.suco...@jboss.com wrote : anonymous wrote : You do not expect me to
look at persisted JMS messages as the system of record for my orders, do you?
|
| This all depends on your business.
|
| If the data should exist on the DB only for the life cycle of the message.
(I mean, as
The resources and tx mgr need to sync too and it doesn't solve that
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244387#4244387
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244387
The point I was trying to make is if if you are persisting the message in a
separate database for *every* message then that's likely to be the slowest link
in the chain, and the overall system will be only as fast as the slowest part.
View the original post :
Now not only are you doing that once you're doing that twice, so that will
involve 2 JTA transactions.
Each JTA transactions will involve a minimum of 3 syncs to the file system, so
that's 6 syncs +2 more for the databases = probably around 8 syncs.
So yes, it will be slow (and it's not
Why are you persisting orders in a database?
If you are using persistent messages then the JMS system can guarantee
persistence for you.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244370#4244370
Reply to the post :
clebert.suco...@jboss.com wrote : timfox wrote : Why are you persisting
orders in a database?
| |
| | If you are using persistent messages then the JMS system can guarantee
persistence for you.
|
| Usually an orders table needs to be kept for historical reasons, right?
That's
I'm slightly confused - I can't see where in your test program the Spring JMS
Template is being used...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244346#4244346
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244346
The right way depends on what you are trying to do.
From your test program I can see you are just sending messages to a queue, and
consuming them via an MDB which does nothing but log a message.
In this case you don't need transactions on your MDB, also there's no real JCA
involved here, since
clebert.suco...@jboss.com wrote : timfox wrote : If you post your example
application on a JIRA, then someone next week can have a look at it and see why
it's acting slow...
| |
|
| The test we were using to replicate the ping issue replicates this
transaction issue.
Yes I know
If you post your example application on a JIRA, then someone next week can have
a look at it and see why it's acting slow...
In the mean-time - gave you looked at the performance tuning section in the jbm
user manual?
View the original post :
In my experience most very high performance messaging installations are not
using JEE (no MDBs, JTA, JCA) - all these things have an overhead and often you
can design them out in your application.
E.g. you can often design out JTA by using duplicate detection (see user manual)
View the
nbhatia wrote : Ok I checked out your latest tweaks on the trunk, and it
seems like the problem is gone. 1 messages sent and received without any
hiccups!. That's great!
|
| As a side note, it took 12 minutes for the full round trip, which
translates to about 14 tps. Any tips on how
Nothing should be able to hold back pings since they are never written on the
same thread as other requests.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4244007#4244007
Reply to the post :
Are you sure it's really returning null?
The code from JBossSession::createTextMessage is just this:
| public TextMessage createTextMessage() throws JMSException
|{
| checkClosed();
|
| return new JBossTextMessage(session);
|}
|
So I don't see how any well
If you're servlets are running in the same AS instance as the broker and it's
JBoss AS then you can just use the JMS JCA adapter to pool connections.
If it's not JBoss then you can share a ConnectionFactory (or
ClientSessionFactory) instance between servlets - this will provide its own
pooling
Gunther-
Can you create a self contained program which replicates this issue, file a
JIRA and attach it?
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243546#4243546
Reply to the post :
nbhatia wrote :
| Thanks for the pointers. Based on your suggestions I have been able to send
and receive 1000 messages on my Windows XP box without any problems! I tried to
push this number upwards but it breaks at about 3000 messages - same
Connection failure has been detected message.
Leos.Bitto wrote :
| Cool, it is nice to see that you guys from JBoss are willing to suggest a
straight replacement of JBoss Microcontainer by Spring Framework.
Well.. we're not recommending a replacement of JBoss MC by Spring.
But we also realise that a lot of people use Spring, or A.N.
Hi Gunther-
If you run the ant install script as mentioned in the quick start guide (after
setting JBOSS_HOME) as described in
http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/quickstart-2.0.0.beta2/html/installation.html#installation.jboss
then it should create a
ataylor wrote : firstly, you shouldn't need to copy any files the install
script does this for you.
|
| also, can you use the jmx console not the admin console. have you tried
sending messages to the queue?
+1. JBM 2.0 *as yet* is not managed by the JBoss AS 5 admin console.
View the
nbhatia wrote : Andy and Tim, thanks for answering my questions. I guess I
was not very clear on the boundaries between JBM and JBoss, so your explanation
was very helpful. Since many users will use JBoss and JBM together, I suppose
including that explanation in the manual would also be very
To clarify Howard's answer:
For JBM 1.4 we try and keep releases compatible but we make no guarantees -
sometimes we have to fix bugs or other components need to fix bugs (e.g. JBoss
Remoting) which requires incompatible fixes.
For EAP CP releases, the rules are stricter and we are required to
There are other ways we could implement this, e.g. we could store a record in
the bindings journal which has the count, and checkpoint this every X records
paged and at shutdown.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242762#4242762
Reply to the post
Hi Naresh-
I don't have a Windows machine at hand (as you can imagine most of us don't use
Windows) to try and replicate your issue, but Clebert and Andy have - perhaps
they can try and replicate it.
Regarding the JCA config - there's a chapter in the user manual on how to
configure this,
Can you post your question on the JCA users forum? it's not related to JBoss
Messaging.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242790#4242790
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242790
Pinging changed between beta1/2 and beta3.
Are you sure you're not using a jar from beta1/beta2 with different jars from
beta3?
E.g. you have jars from an earlier release on the client side and different
jars on the server side. Or maybe you are using the rar from a different
release.
All
anonymous wrote :
| However I had to add the acceptors and connectors at the config.
|
The fact that Clebert had to add these acceptors and connectors in order to get
your example to work and you didn't, tells me you can't be using beta3.
Otherwise you would have had to do the same too
clebert.suco...@jboss.com wrote : Take a look at jms-ds.xml
|
|
| The JNDI is java:/XAConnectionFactory.
|
| (You need to use the local JNDI for that... just do new InitialContext().
As you may known java:/ means local VM).
|
|
| you can just do:
|
|
| InitialContext
Adrian-
Are your client threads calling send() on the same ClientProducer (core ) or
MessageProducer (JMS) instance? If you do this you would have to synchronize
access in your client application since neither JMS MessageProducers or core
ClientProducer instances are designed to be used by
AdrianWoodhead wrote : The clients are calling send() on the same
MessageProducer instance, and this isn't synchronized. This hasn't caused any
noticeable problems in the past (when the MessageProducer was using ActiveMQ)
or since we started evaluating JBM (although the loads on those 2 servers
Perhaps you also need a thread pool in your application to stop potentially
unlimited number of threads being created for your HTTP requests...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242378#4242378
Reply to the post :
Howard you should make an announcement/blog etc about this.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242169#4242169
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242169
___
The JMS spec guarantees that messages sent from a particular producer are
delivered in order to a single consumer in the absence of failures.
You don't need order grouping for that.
If you're not seeing that, please add a test case that demonstrates it and
someone will investigate it since it
Looks like a bug.
It seems that messages with an expiry set do not currently work well with
pre-ack.
Can you file a JIRA? Should be an easy fix.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242246#4242246
Reply to the post :
Andy- is this documented in the user manual? If not, we should make sure it is.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242281#4242281
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242281
Adrian-
I am trying to get my head around what you're asking here.
if you're referring to command buffering:
http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/usermanual-2.0.0.beta3/html/command-buffering.html
Then JBM will block by default on send if it hasn't
If you want a client in JBM 1.x to failover automatically from one node to
another you need to set supportsFailover to true in the descriptor where the
connection factory is deployed.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242041#4242041
Reply to the
It depends what you want to do. When you originally said failover I assume you
really meant reconnection, in which case you don't need a clustered connection
factory.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4242055#4242055
Reply to the post :
If you are sending a lot of messages in a fairly constant stream it doesn't
make a lot sense to me why you are setting maxBatchSize to a value other than
-1, since the batch will be sent anyway when maxBatchSize is reached.
Regarding the speed of bridging, this is a function of many factors
Also you have a typo here:
param key-jbm.remoting.netty.host value=server1 type=Strnig /
(Strnig)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4241573#4241573
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241573
Looks like you didn't specify host name on your acceptors. If you don't specify
it it will default to listening on localhost which won't be accessible from
another machine.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4241572#4241572
Reply to the post :
1 - 100 of 1586 matches
Mail list logo
