Have you tried a more recent release? (These are available in SVN but not
binary).
Or you could wait for a week or so for the next binary release.
We've fixed a lot of stuff and a lot of stuff has been fixed in remoting since
the release you're using.
View the original post :
Also make sure you use the correct version of jboss remoting on both the client
and server side as specified in the installation instructions.
Wrong remoting is the biggest cause of errors like this.
View the original post :
If you send me a link to the JIRA and mail me the test case, I'll attach it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4187105#4187105
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4187105
I would suggest reading any simple JMS tutorial.
The one at java.sun.com is quite good.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4186589#4186589
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4186589
ataylor wrote :
| anonymous wrote : - Composite destinations. See
http://activemq.apache.org/composite-destinations.html. A comma-separated list
of destination names are treated like a single destination.
|
| no we don't support this at present.
| .
Can't you get the same effect by
Those stuck messages, are messages that have been sent or consumed as part of
an XA transaction, and the server failed (crashed?) before the XA transaction
committed or rolled back.
If you're familiar with XA/JTA, you'll know they're in a prepared state (I
suggest googling on XA if you're not
There is an old JIRA for this somewhere which was fixed some time back IIRC.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4185952#4185952
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4185952
You shouldn't need to copy anything.
This error occurs because the user is attempting to start a clustered post
office in a non clustered JBoss configuration.
E.g. user is trying to start JBM clustered in the default configuration. He
should be using the all configuration.
In the all
Have you turned on message counters?
Read the manual for more info.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4185285#4185285
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4185285
szhigunov wrote : gaohoward wrote : IMO, unacknowledged messages may be
sent twice. In this case after the client reconnects, first thing it should do
is a transaction recovery.
|
| If that is correct, what would you recommend when two clients read from the
same queue? When the first
szhigunov wrote : I get the same message received twice; in both cases
transaction was committed.
|
| Here are the steps:
| 1) Remote client reads message in XA from the remote JBM queue (transaction
one).
| 2) Client dies after JBM was prepared, but before commit.
| 3) Client starts
This looks like a bug in the orderedexecutorfactory shutdown:
| public void shutdownNow()
| {
| tasks.clear();
| }
|
which is not synchronized.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4184849#4184849
Reply to the post :
What subscription id problem?
As I mentioned before, subscription name and client id are only used for
durable subscriptions, NOT non durable subscriptions.
In JMS it is impossible to create a non durable subscription with a specific
client id and name.
See the JMS spec for more details.
szhigunov wrote :
| My understanding, that if transacted session is used, JMS guarantees that
any given message delivered only once.
|
|
Not quite.
If you consume a message in a tx, *and that tx is committed* then the message
is guaranteed to never be delivered again. But in your
grafzal wrote : do I have to imlement
| manual failover with the ExceptionListener and disable supportsFailover?
yes
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182611#4182611
Reply to the post :
The java: prefix means available only in the same JVM.
See the wiki on JmsRA
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182734#4182734
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4182734
I already said in my previous post we don't support this feature.
If the user wants it they can file a feature request.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182741#4182741
Reply to the post :
Where do I start with a post like this?
JBM has been around for a few years now, and is a production quality messaging
system.
It's the default messaging provider in JBoss EAP and JBoss SOA platforms and
JBoss 5.
We're currently working on the next release JBM 2.0, which is due in Q1 2009.
Client id and subscription name are used in JMS to define *durable
subscriptions*, in JMS they have absolutely no meaning for non durable
subscriptions.
In fact, there is no way using the JMS API to create a non durable subscription
with a specific id so you couldn't be doing this on JBoss MQ
jerry.zhao wrote : jboss remoting 2.4.0 is not the correct version to use??
which version is correct version
Deep breath. Ok, I'll say it for the third time.
The installation section of the user guide explains in detail how to install
JBM into JBoss AS and which versions of remoting etc to
[EMAIL PROTECTED] wrote : anonymous wrote : it would be nice to add this as
a suggested solution to the JBMSpringJMSTemplateNotes page that warns against
using JmsTemplate with JBoss Messaging.
|
| This should be the same on any JMS provider you choose. Creating a
Session/Producer on
jmoscato wrote : From the Spring 2.5.x documentation, it appears that it
would be safe to listen for messages using a Spring message driven pojo, a
DefaultMessageListenerContainer configured with a JmsTransactionManager, and a
container managed connection factory (/JmsXA) .
|
| Is the
Like I said, remoting 2.4.0 is NOT the correct version to use.
Please read the user guide, installation section and follow it exactly. It
specifies the exact version of remoting, aop etc that must be used.
If you use any other versions then we make no guarantees that anything will or
will not
szhigunov wrote : Hi,
| I am testing JBM XA recovery. I have two JBoss servers. Server A runs a
non-clustered queue. Server B runs a JMS listener, which connects to server A
through JCA + remote JMS provider. I added the following configuration to
server B (where TM is running) to turn the
We're hoping to bring out a 1.4.1.GA release some time next week, which will
contain all the latest bug fixes and changes.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4181226#4181226
Reply to the post :
If you are using an EAP CP, then you have a support contract right?
If so, use it, and someone from support will investigate.
First you should upgrade to the latest CP though.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4180550#4180550
Reply to the post :
jerry.zhao wrote : problem: Server will running 2-3 days as well. but after
2-3 days, will have problem. consumer is not consuming, message id delivered, I
access http://localhost:8080/jmx-console, see my queue, find the allMessageSize
will increase ï¼ then delivered a message, will display
If you've already created your tables then set createTablesOnStartup to false,
since they're already there!
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.1.Beta1/html_single/index.html#conf.postoffice.attributes.createtables
That's what it's for.
GA Q1 2009
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179939#4179939
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4179939
___
jboss-user mailing list
I don't really understand what your problem is.
JBM 1.4 should support all equivalent JMX functionality to JBoss MQ. See user
guide for more info.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179940#4179940
Reply to the post :
The correct jars needed on the JBM client side classpath are detailed in the
JBM user guide.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179231#4179231
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4179231
It's in the remoting configuration. E.g. remoting-bisocket-service.xml
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4178516#4178516
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4178516
This is jboss remoting configuration, not jboss messaging configuration.
You should ask in the jboss remoting forum to get a definitive answer
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4178517#4178517
Reply to the post :
The JMS API does not support this directly without you first reading the
message body and computing the size yourself.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4178527#4178527
Reply to the post :
testrot wrote : Nobody?
| Is this an uncommon request, or did I miss something when searching for a
HA solution without without a clustered DB?
|
| Greetings,
| Martin
|
| P.S.: Even a negative response like there is not possibility and this is
not planned would be appreciated.
A
kenwdelong wrote : We have two JMS servers in a cluster. We have set up the
instances to cluster: Post Office and the Destinations have Clustered=true. We
are using JBoss Messaging 1.4.0 on JBoss AS 4.2.2.
|
| We have a queue that parses incoming (XML) messages. If the parsing breaks
If you want to make sure one service gets started before another using standard
JBoss MBean config, you just need to add a
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4178320#4178320
Reply to the post :
testrot wrote :
| Thanks for your answer. That's the information I needed.
| May I politely ask when you plan to release a production ready version of
JBM 2.0?
|
We're aiming for Q1 2009. :)
View the original post :
francesco_81 wrote : I solved my problem.
|
| i just simulated the crash of a messaging-node siple sendig the TERM
signal. If I send the KILL signal to the AS than the fault tolerance just
happen.
Yes, that's in one of the FAQs
View the original post :
tim.shaw wrote : T
| My question then becomes - How does JBM determine when the load is too
great for the initial machine?
|
Each consumer has a client side buffer of messages (see prefetchsize), when
that buffer is full the consumer is deemed busy, and won't be sent any more
messages.
Trying to be polite here. why don't you read the user guide?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4177669#4177669
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4177669
xxbrandonoxx wrote : I am trying to implement a system that will require
consistently high volume with long running and constantly connected clients.
To date I have followed the samples included with JBoss Messaging and am
creating a new connection+session+temp_response_queue on a per request
tim.shaw wrote : Is it possible, using JBM (1.4.x), to evenly distribute
message processing across the nodes of a cluster (AS 4.2.3)?
|
http://wiki.jboss.org/wiki/JBMCluster
anonymous wrote :
| If not - and my reading of the docs is that it only starts redistribution
when the original
jbossnoob wrote : If you are saying this can be done then your comments on
that Jira look contradictory since you proposed a solution then took it back.
|
| Thanks.
The FAQ is correct.
The JIRA is talking about providing singleton queue/consumer functionality
without using HA singleton
Read the FAQs!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4176314#4176314
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4176314
___
jboss-user mailing list
From the AS readme.html
JBossAS now binds its services to localhost (127.0.0.1) *by default*, instead
of binding to all available interfaces (0.0.0.0). This was primarily done for
security reasons because of concerns of users going to production without
having secured their servers properly.
If after installation, the clustered examples don't work, it's more than likely
the installation was botched.
Solution: re-install being very careful to follow all steps exactly.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4174950#4174950
Reply to the post
I don't think this is JCA, it's an ESB pooling question.
You should try posting in the ESB forum.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4174806#4174806
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4174806
francesco_81 wrote : I've the same problem but i want to use jms in clustered
environmet. May someone help me?
| Best Regards.
Read the user guide? ;)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4174807#4174807
Reply to the post :
CP stands for Cumulative patch.
We create CP releases for our paying customers (i.e. those which have bought a
support contract), and they mainly contain bug fixes.
We don't distribute binaries for these publicly, but all the source is publicly
available in
The real reason for this is probably the user has installed jboss messaging in
a non clustered app server configuration (e.g. like default), but has set
clustered=true in the config file.
If clustering is required, then jbm must be installed in a clustered app server
config where jgroups is
Please use the JCA forum for JCA questions.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4174256#4174256
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4174256
___
jboss-user
Please use the correct forums. This does not seem to be related to JBoss
Messaging.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4174257#4174257
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4174257
Please use the JBoss MQ forum for JBoss MQ issues.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4174258#4174258
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4174258
___
Please use the JCA forum for JCA issues.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4174259#4174259
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4174259
___
jboss-user mailing
There's a working EJB2 example in the distribution (see user guide).
If that doesn't work it means your installation was bodged.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4173137#4173137
Reply to the post :
I believe this was a JBR bug fixed quite some time ago
https://jira.jboss.org/jira/browse/JBREM-952.
You're using a very old version of JBM and JBR, I suggest you upgrade.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4171985#4171985
Reply to the post :
Looks like you're creating a non transacted session.
There are lots of examples around of doing this correctly. I suggest you find
one of those and copy it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4171437#4171437
Reply to the post :
ataylor wrote : There may be a way of stopping the MDB from consuming
messages i don't know, speak to the App server guys they could help you.
Alternatively you couls write you're own mbean that consumes from the queue and
stop and start the connection your self.
Or you could write a simple
Ah I just noticed you're using an interceptor, I thought you were using an EJB
which is an extremely common pattern.
The JMS JCA resource adapter requires a managed environment (read servlet or
EJB) otherwise transaction won't get enlisted automatically. But this is app
server stuff and not
perisb wrote : So your saying the enlistment of the JMS Session as an XA
resource has nothing to do with JBM (or is completely orthogonal to it)?
|
Yes, the resource enlistment is done by the JCA adapter, not JBM.
anonymous wrote :
| Just curious: the connection factory name java:/JmsXA
http://java.sun.com/j2ee/apidocs-1_5-fr/javax/resource/spi/package-summary.html
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4171510#4171510
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4171510
If you like you can add a JIRA feature request for the ability to pause resume
delivery on a queue via the management interface.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4171512#4171512
Reply to the post :
perisb wrote : If not, is there anything explicit I can do to make this
work?
If you can get a reference to the transaction, then you can always enlist the
resources yourself.
I.e. don't use JmsXA, use XAConnectionFactory, create an XAConnection, create
an XASession, and enlist the
Search for fullSize in the documentation.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4171015#4171015
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4171015
___
jboss-user
I would use a topic.
Each user can create a subscription when they join.
If you want users to see chat messages sent while they were not connected, they
can use a durable subscription.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4170913#4170913
Reply to
[EMAIL PROTECTED] wrote : I don't know your complete use case, but Temporary
Queue is better.
|
| Topic - your message would probably be sent to other internal queues that
don't need to know about your message. And besides selector has some
performance implications.
|
|
| So...
How long is a piece of string?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4170634#4170634
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4170634
___
jboss-user mailing list
Did you run the examples after installing to validate the installation?
There's a message redistribution example. If it doesn't work it means your
installation is messed up. If it does work, see how it differs from your
program to work out what is wrong.
View the original post :
The error message is pretty clear, it's saying that the object at context
foresight in your remote JNDI (I'm assuming this is Weblogic's JNDI server)
does not implement the QueueConnectionFactory interface.
View the original post :
As I said before I suspect you're starting your publisher(s) before the
subscriber has created the durable subscription, hence the first few messages
get lost since there's no durable subscription. That's to be expected.
Putting publisher and subscriber into the same file means that can't
There are two other problems with your code I can see after a quick perusal:
1) You're starting your threads but not waiting for them to complete before
exiting. You need to add calls to Thread::join() to make sure you wait until
they complete or your program will exit before they are done
2)
There's a third problem with your code:
You start the subscriber thread, then immediately start the publisher thread(s)
before waiting for the subcriber thread to finish.
This means there's a strong possibility you'll start sending messages before
the durable subscription is created, so
You already posted this here:
http://www.jboss.com/index.html?module=bbop=viewtopict=139256
The last comment on the original thread was
Please post a simple Java test that we can run that demonstrates the problem.
We're still waiting for that.
Do not repost/crosspost or I will delete your
Ok, you're almost there.
You have two programs now. You just need to combine them into a single test
that we can run to show your problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4168573#4168573
Reply to the post :
Yes, persistent is the default. But going back to my original request, please
provide a simple test program which demonstrates the problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4168592#4168592
Reply to the post :
If the problem is real, you should be able to easily provide a simple test case
to run that demonstrates it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4168594#4168594
Reply to the post :
Overlord, with respect, can you please stop the stream of consciousness posts.
If you have a problem, please do some research into it, make sure you have set
things up correctly, read all the manuals etc.
If that still doesn't work, then create a simple self contained test case that
I don't know Dan Christopherson, but the JCA people should be able to help you
out.
Also, have you looked on the wiki. IIRC there are some resources about how to
configure the JBoss JCA adaptor to talk to other messaging systems.
View the original post :
No idea, this is a JBoss Messaging forum, not a How do I use Weblogic forum -
have you asked the Weblogic guys?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4168098#4168098
Reply to the post :
zhaoxixie wrote : I wish such feature in messaging system.
|
|
We already have such feature - it is called connection.stop().
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4168096#4168096
Reply to the post :
You can use either normal or HA JNDI it's up to you.
I'd recommend a book/tutorial on JNDI.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4168100#4168100
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4168100
Or you could ask in the JCA users forum, since this seems to be a question of
how to configure the JBoss AS JMS JCA adaptor to talk to Weblogic JMS.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4168121#4168121
Reply to the post :
[EMAIL PROTECTED] wrote : Tim,
|
| The question is not a How do I use Weblogic forum - it is an
interoperability issue with JBoss.
Fine, but you are in the wrong forum. This team does not deal with
interoperability with weblogic. That's why I said try the JCA forum.
In the same way, if
dumitriu wrote : The Beta release is slated for when?
|
We're aiming for about three months time.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4167905#4167905
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4167905
Burnison-
None of the stacks you posted show any JBoss Messaging code.
All I can see is the JCA layer (that's part of JBoss AS) trying to do some
stuff with JBoss Transactions and failing.
I suggest you post in the JCA forum.
View the original post :
As previously mentioned, messages will get put back on the queue when the
client gets timed out (not when another client reconnects).
If you can produce a simple self contained test case that we can run that
demonstrates otherwise we will be happy to investigate further.
View the original post
I have to agree with Clebert.
A warm-up period is critical before taking any measurements since JIT warmup
can make a huge difference (I've noticed about a 300% performance difference).
Secondly just sending messages is not really a good measurement. One reason is
that after the call to send()
shimi wrote : and to see ActiveMQ as part as the test as well.
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/userguide-2.0.0.alpha1/html/performance.html#performance.results
What's more JBM 2.0 is even faster now then when those results were taken :)
View the
Connection.stop(). It's a standard part of JMS. See JMS spec or JMS javadoc for
more details
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4167936#4167936
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4167936
You should try asking in the MDB forum.
MDBs are a part of JBoss AS, not JBM.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4167956#4167956
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4167956
dumitriu wrote : When will high availability (broker mirroring with automatic
failover) be available in JBM 2.0?
The beta release
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4167149#4167149
Reply to the post :
Anything to do with MDBs and MDB config is not part of the JBoss Messaging
project, but is handled by the JBoss AS project.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4167152#4167152
Reply to the post :
If you have well written clients which always close their connection(s)
properly before exiting then any unacknowledged messages will be returned
immediately to the queue(s) on close of those connection(s), otherwise the
after the client exits the server will eventually time out that client and
Please post a simple Java test that we can run that demonstrates the problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4166263#4166263
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4166263
When you close the connection or session the threads should be reclaimed, so
this is only going to be a problem if you create a very large number of
sessions.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4165597#4165597
Reply to the post :
TheOverlord wrote : According to the JBoss Wiki relating to JmsTemplate, it's
safe to use JmsTemplate so long as it's used in a Jboss AS when using the
connection factory from java:/JmsXA.
|
And even then, it's only safe for sending messages, not consuming them.
View the original post :
jasonhu919 wrote :
| 3. the message dequeue is fast, but the message enqueue is really slow
compared to oracle AQ. any way, I can tune the enqueue performance?
Message consume rate is highly dependent on many factors including what
acknowledge mode you are using (e.g. AUTO_ACKNOWLEDGE
Probably you aren't creating your durable subscriber until after some of the
messages have been sent, so clearly those messages will be unavailable to
consume.
This would also explain why it only happens on the first run, since on
subsequent runs the durable subscriber already exists.
View
The reason you don't see documentation for this in the JBM documentation, is
the MDB pooling stuff is a part of JBoss App server, not JBoss messaging. It's
not part of the JBM project or code.
I believe this is documented in the app server documentation somewhere. There
are also wiki pages on
301 - 400 of 1586 matches
Mail list logo
