Ok, so what we need to do is find out what part of the complex object is
causing the problems.
Can you send me the class (you can remove any confidential/irrelevant suff) we
can investigate what is going on.
Thx
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p
Sometimes JBoss Serialization has a problem serializing complex objects.
I suspect this is what is happening in your case, especially since you are
doing stuff with readresolve.
As a workaround you can use java serialization instead. Just need to change
"serialiaztiontype" to "java" in remoting
What is the object you are trying to persist that fails?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955788#3955788
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955788
Using Tomcat but need to do more? Need to sup
Can you explain in some more detail what you're seeing?
So example code would be good.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955771#3955771
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955771
Using
Of course, if anyone is kind enough to contribute some time to do this piece of
work then that would be much appreciated :)
The piece of work would involve someone writing a set of test cases that test
JBossMessaging via the spring API, that we can include as part of our test
suite.
View the o
I would just like to make clear that we have not tested JBossMessaging with
Spring, and so we can make no guarantees on whether it will or won't work.
I.e. it's not supported.
That's not to say that it won't work, just that we don't have the resources to
invest in the work required to do the te
"mskonda" wrote : I am beginning to think that the culprit could be down to
jdbc persistence with Oracle..
Let's not jump to conclusions about what is happening here.
I'd like to see this replicated in a test case and then I will investigate.
View the original post :
http://www.jboss.com/index
Ok thx.
Someone else saw this one too. But like you it only happened rarely and they
couldn't reproduce it either.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955471#3955471
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=re
"dv_lakshmi" wrote : Well, part of the problem can be replicated even without
the spring code. i.e., the message sending problem as mentioned in the email.
Ok fine. :)
So send me a junit test case and I will be happy to look into it.
View the original post :
http://www.jboss.com/index.html?mod
Lakshmi-
The test case you send me needs to have no spring dependencies.
I.e. straight JMS code
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955461#3955461
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955461
Usin
Martin-
Please can you tell me under what circumstances this happens.
Can you please replicate in a simple case I can run so I can investigate?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955458#3955458
Reply to the post :
http://www.jboss.com/i
BTW, are you using RC3? If not, I recommend upgrading to this version.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955431#3955431
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955431
Using Tomcat but need to do mor
My guess is that you are using a transacted session and not committing, or
using client acknowledge and not explicitly acknowledging.
Although without seeing a test case I can replicate I am just guessing.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955403
You don't have to send all your code. Just replicate with a simple message
listener, this is the normal proceedure...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955215#3955215
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
Please replicate in a simple test case, and send to me and I will investigate.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955214#3955214
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955214
Using Tomcat b
When persistent messages are acked they will be removed from the
jms_message_reference table.
When all references to the message (the same message can be in many queues or
subscriptions) are acked, it will be removed from the jms_message table.
MessageCount represents the total number of messag
I have just released this and it is now available on jboss labs:
http://labs.jboss.com/portal/jbossmessaging/downloads
This fix contains several important fixes, so I highly recommend that you are
upgrade to this version if you are using an earlier version.
Release notes are available here:
ht
Don't use hypersonic, it not intended for any serious use.
This is mentioned in the getting started guide.
The reason you are running out of memory, and see little disk activity is that
hypersonic stores it's tables in memory (in the same process).
We should really prevent Jboss messaging from
Hi Clebert -
Will StringUtil work with Java serialization to?
Now, we are splitting long strings into chunks < 64K and re-assembling them on
the other side.
Would StringUtil do this more optimally?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953936#395
Please post on the JBoss MQ forum, this forum is about JBoss Messaging.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953935#3953935
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953935
Using Tomcat but need to do mo
Please post your message in the JBossMQ user's forum.
This is a JBoss Messaging forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953914#3953914
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953914
Using Tomcat b
If I remember rightly, the classloading domain needs to specified at the top
level (i.e. in jboss-app.xml) for nested deployments.
See http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953739#3
You need to specify the classloading domain in your mbean config
Also, please see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85469
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953721#3953721
Reply to the post :
http://www.jboss.com/index.html
Ok.
What we really need is for you to send us something that we can unzip and run
that reliably reproduces the problem, then we have something to go on.
Otherwise we are just guessing.
Thx.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953706#3953706
Repl
JBoss Messaging does not currently support clustering - this does not affect
any other cluster enabled components in JBoss.
Clustering will be in 1.2. We should be announcing dates for it, probably
within the next week.
View the original post :
http://www.jboss.com/index.html?module=bb&op=view
Also, can you tell me what database you are using?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953691#3953691
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953691
Using Tomcat but need to do more? Need to support w
Some more questions?
How many subscriptions do you have?
How many queues/topics?
Size of messages?
Type of message (persistent/non persistent)?
What values have you set on your queuss/topics? (please post config)
How much memory have you allocated to the VM?
How do you know there is no disk
Sounds like you're running out of memory.
Can you look in the logs for an OutOfMemoryErrory.
Also can you look at the JVM memory consumption over the 30 minutes that you
run it.
Perhaps you are sending messages faster than you can consume them?
BTW Which JVM are you using (Sun, JRockit, IBM...
There is no producer throttling at present.
However JBoss Messaging can cope with very large queues, by paging to disk. See
"Destination Paging Parameters" for more details.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953635#3953635
Reply to the post :
Sounds reasonable.
Although the type mapping step is probably not necessary.
We should probably create a wiki page on this
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953634#3953634
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=pos
This is scheduled for 1.0.2
http://jira.jboss.com/jira/browse/JBMESSAGING-381
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953633#3953633
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953633
Using Tomcat but need t
"ONIT" wrote : Tim,
|
| No change. I still get the same exception.
|
| Dennis
|
Did the security exception go away though?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953520#3953520
Reply to the post :
http://www.jboss.com/index.html?module=
Can you try adding:
| guest
|
In the config for the "other" domain, so it looks like:
|
|guest
|
|
I'm not sure if this is your main problem, but it should prevent the security
exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtop
|
| javax.jms.JMSSecurityException: User null is NOT authenticated
| at
org.jboss.jms.server.security.SecurityMetadataStore.authenticate(SecurityMetadataStore.java:181)
| at
org.jboss.jms.server.container.SecurityAspect.check(SecurityAspect.java:252)
| at
org.jboss.jms.server.contain
There's no DLQ support at present.
This is part of the same task, so will be in 1.0.2 (not too long).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953405#3953405
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953405
Delivery attempts is currently hardcoded.
Pluggable redelivery behaviour is currently scheduled for 1.0.2
http://jira.jboss.com/jira/browse/JBMESSAGING-127
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953396#3953396
Reply to the post :
http://www.jboss.co
Also, I have changed the code so that less callback servers wil be created.
This means we will be able to support more concurrent open jms connections on
the client side.
This will be available in RC3
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953194#395
Ok I have found a problem in queue redeployment which accounts for this.
The fix is fairly straightforward and will be in the next release (RC3) which
should be out early next week.
Sorry for the inconvenience.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p
In the mean-time to fix your installation you need to add the following to your
login-config.xml:
|
|
|
| guest
| messaging-users.properties
| messaging-roles.properties
|
|
|
|
Sorry about the i
The isolation is required for 4.x, since we depend on versions of JBoss AOP,
JBoss Remoting, JBoss Serialization that aren't available in 4.x
When JBoss 5 is released we will be using the same versions as in the AS so the
deployment should be much smaller and we won't have to do scoped deploymen
Are you referring to persistent or non persistent messages.
Non persistent messages don't get stored in the database.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952913#3952913
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
Ok I fixed this.
The problem here was not that the message was getting lost (it wasn't) - if you
restart the server the "lost" message re-appears. That would be spec compliant
- but annoying.
So I've changed it so that if a client dies then it's outstanding deliveries
get cancelled and redeliv
We should have another RC out early next week.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952895#3952895
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952895
Using Tomcat but need to do more? Need to support web s
Can you post your entire exception please
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952894#3952894
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952894
Using Tomcat but need to do more? Need to support web servic
"ONIT" wrote :
| This is inspite of the fact that I get a new ConnectionFactory,
InitialContext, Queue, Connection, Session, and MessageConsumer everytime the
EJB getResponse method is called.
Well you're not really getting a new Connection, Session each time.
You're using JmsXA, which is
Did you change the name of the messaging loader repository to "cris3"?
The default one is:
| jboss.messaging:loader=ScopedLoaderRepository
|
java2ParentDelegation=false
|
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952883#39528
Is this a JBoss Messaging or a JBoss MQ question?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952879#3952879
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952879
Using Tomcat but need to do more? Need to support we
Ok I have replicated this - a fix should be on it's way soon...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952719#3952719
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952719
Using Tomcat but need to do more? Need
I have replicated a similar issue where a standalone client VM does not exit.
I have traced this to a problem with JBoss Remoting. This will be fixed in the
next release.
Thx
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952703#3952703
Reply to the post :
Hi-
I was wondering if you are still seeing this problem?
We are going to cut a release fairly soon, so if there is an issue here we want
to get a fix in ASAP
Thanks for your patience.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952602#3952602
Reply to
Hi Dennis-
Can you post your code and config please?
Thx
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952587#3952587
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952587
All the advantages of Linux Managed Hosting
Just to be sure I have tried on my test setup with text messages containing xml
(jaws.dtd) and others of the same size with non XML text and send/receive times
are the same.
As I say, Jboss messaging treats the message bodies as completely opaque anyway.
View the original post :
http://www.jbo
Martin-I ran your test program with 50 messages - it took a few hours and
after my fix I didn't notice any memory leak.
This fix will be in the 1.0.1GA release which should be out fairly soon once
we've cleared up this latest few issues we are having.
View the original post :
http://www.jb
Very interesting.
The jms server or client doesn't treat xml text any differently from any other
text. In fact it doesn't even look at the messabe bodies at all, they're
ignored.
One possibility here is you have an XML firewall on your network between the
server and the client.
Some companies
Martin - I have tried out your latest test case, and I confirm that I observe a
memory leak.
After a lot of grief I have tracked it down to a race condition in message
acknowledgement that only occurs when used with EJB3.
I won't bore you with the details, but I am running your test case again
On your second point, you are correct.
The current queue browser implementation only works with in memory messages,
but this is due to be fixed in the not too distant future
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952394#3952394
Reply to the post :
h
I have just completed a test with JBoss Messaging 1.0.1.CR2 running on JBoss AS
4.0.4.GA, on an old slow intel box, connected via 100MB/s ethernet and a single
switch to my laptop.
I am sending persistent text messages with a payload of about 2K, and I'm
consuming them, both from the laptop.
I
Please post your code
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952382#3952382
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952382
___
JBoss-user mailing list
JBoss-u
You say you are sending non persistent messages, but in your code you are
sending persistent messages.
Can you explain what you are actually doing again, I am confused as to what
your use case is
Also your jms client exits without waiting to join the threads, so it will
never work.
Vi
What version of JBoss, JDK and Messaging are you running?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952363#3952363
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952363
___
No, that's not quite correct.
You are creating *two* consumers, each with the same selector expression
""target='10' OR target='20'"
For each message sent to the queue you are posting 4 messages, with target =10,
20, 30, 40
Therefore *both* of the two consumers will *each* receive the first tw
Can you send me some code to replicate this and I'll take a look...
Thx
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952348#3952348
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952348
Can try setting useBatchUpdates = false in the persistence config and try again?
It should give you a more descriptive error message.
Also, what version of JBoss AS are using, and what version of JBossMessaging
are you using?
View the original post :
http://www.jboss.com/index.html?module=bb&o
So, with the rt.gc, the system would also have run out of memory eventually,
but I guess it was slowing things down so much on my system that I didn't run
it long enough to notice
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952334#3952334
Reply to the pos
Ok, a few things to report.
The call to rt.gc() in ClientServlet really slowed things down, so I removed it.
I then noticed that memory became exhausted (500MB) in a few minutes.
I also managed to replicate this using a simple self contained jms program
(using no EJBs) which simply sends messag
I'm assuming this is using Derby?
If so, there are no guarantees Derby will work with JBoss Messaging since we
haven't put it through our testing (yet).
As I say, if you'd like to contribute your Derby config that would be cool, and
we can add a task to add Derby as supported config.
View the
Hi-
We haven't tested against Derby so it's not one of our supported databases.
However, if you have produced a persistence manager configuration for Derby
then if you would like to contribute it we can put it through the test suite.
So far we've tested against Oracle, Sybase, PostgreSQL, MSQL,
2-3 messages per sec does indeed sound very slow.
Can you try sending non persistent messages? - I want to take Oracle out of the
equation.
Also, when you say it is much faster on a "local" server, do you mean the
client is in a different VM on the same box as the server, or the same VM on
the
Ok, so this is not related to it being an XAConnection, this is because you are
using the socket transport which will attempt to start a server on the client
to receive callbacks for messages.
As I say, this is probably failing beacuse jnlp won't let you start a server
and open server sockets o
"mwelss" wrote : Tim,
|
| the memory leak becomes visible very quickly with my testcase, it will eat
1-2 MB every minute.
| BUT: I didn't try your configuration yet, I can reproduce this reliably on
jboss 4.0.4.GA-patch1 with ejb3 config and jboss-messaging 1.0.1CR2. I will try
with EJB3-
"bos" wrote : Sorry, have not been able to test without selectors yet. I'll try
out some different senarios as soon as I can, and produce some test code. But
unfortunately I won't be able to do anything before friday at the earliest.
Np, thanks for your help anyway.
View the original post :
h
Ok, I am going to run Martin's test program on a different machine and let it
run for days to see what happens.
bos - if you can reproduce your issue with a small test program that would be
great too - do you only see your problem when you use selectors?
View the original post :
http://www.jbo
Please elaborate on your comment:
| I am using XAConnectionFactory as suggested by you, but I get
MessagingJMSException
|
|
Please post your code
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952243#3952243
Reply to the post :
http://www.jboss.co
Do you need to receive messages from a jnlp client as well as post them?
anonymous wrote :
| I am using XAConnectionFactory as suggested by you, but I get
MessagingJMSException
|
Can you elaborate? Is this happening from a jnlp client, a standalone client or
something else?
View the orig
A few questions:
How fast is your network?
How large are your messages?
What kind of messages are they?
Is anyone else using the jms server?
Are they persistent messages?
If so, what database are you using?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=39
Creating connections is (relatively) a very slow process, so you should avoid
creating them every time you want to check a message (it's an anti-pattern
creating a connection every time).
Also your call to session.close() is redundant since you're calling
conn.close() which will close the sessi
However you should avoid using selectors on queues that do not match most
messages - it is an antipattern and they won't scale.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952232#3952232
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=p
Hi Martin-
Sorry for taking so long to look at this, it's been a very busy few weeks.
I have run your test you sent to me using a fresh copy of JBoss 4.0.4GA, JDK5,
and EJB3-RC8-FD.
I installed EJB3 fresh as per the EJB3 install instructions into the all
configuration of the app server, and ra
ok thx, I am going to try and replicate this.
A few more questions:
Are you using JDK1.4 or 1.5?
The Object messages are persistent, right?
What are you doing inside the MDB?
If you could provide code I could run that would be ideal.
View the original post :
http://www.jboss.com/index.html
To be clear, this is how you get and use an XAConnection:
|
| XAConnectionFactory factory =
(XAConnectionFactory)ic.lookup("MyConnectionFactory");
|
| XAConnection conn = factory.createXAConnection();
|
| XASession sess = conn.createXASession();
|
| XAResource res = sess.getX
All connection factories in JBoss Messaging are also XAConnectionFactory
instances.
I guess you are using it incorrectly - please show me your client side code.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952019#3952019
Reply to the post :
http://www.jbo
I don't know much about jnlp, but I guess it runs in a SecurityManager which
won't allow you to open sockets and listen on them for security reasons.
In order to receive messages using the default socket transport the client
needs to open server sockets so it can listen and receive messages.
On
Also see the note at the bottom of this page:
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951981#3951981
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951
The JCA aware connection factory is only valid in the same VM afaik
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951970#3951970
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951970
_
The XAConnectionFactory is the object registered in the JNDI tree at
/XAConnectionFactory, this is the one you want to use.
The WMXQueueConnectionFactory is a JCA aware connection factory - I don't know
why you are creating that.
View the original post :
http://www.jboss.com/index.html?module=
So you are saying, that you have an object in JNDI (the XAConnectionFactory),
that we have validated is there but you fail to look it up.
This sounds like an issue with the way you are using JNDI. Can you look up
other objects from the same global jndi (e.g. the testQueue)?
You should also chec
What are you looking the connection factory up as?
Have you looked at JNDI viewer to see if it is there?
http://wiki.jboss.org/wiki/Wiki.jsp?page=DisplayTheJDNITreeWithTheJMXConsole
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951929#3951929
Reply to the p
If you look in the logs it should tell you why it failed to create that table.
Most likely you do not have permission to create tables.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951823#3951823
Reply to the post :
http://www.jboss.com/index.html?module=b
Ok, I have fixed this in CVS HEAD.
We now support strings up to 4GB as bodies of TextMessages or ObjectMessages.
All other strings in messages (i.e. string properties, other string fields,
strings in map messages, stream messages or bytes messages) still have the 64K
limit.
This is because the
There was a bug in 1.0.0 related to delivery to subscriptions with selectors,
which was fixed some time ago.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=81506
I think your problem could be related.
Actually 1.0.0 is pretty old now, there have been several bug fixes since then
so b
But post your *actual* code anyway.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951655#3951655
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951655
___
JBoss-user mailin
I've just noticed you're using 1.0.0 GA, can you upgrade to the latest version?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951654#3951654
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951654
_
Please post the actual code you are running so I can replicate this.
The previous code has various errors including the initialisation of the
InitialContext, the wrong connection factory etc.
I'm not sure how I can help you unless you give me a test case I can actually
run.
Also, please tell m
How is this the same problem?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951625#3951625
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951625
___
JBoss-user mailing list
Looking at your code, there is something I do not understand.
You say that the messaging server is on one machine, and the producer, relayer
and consumer are on another machine.
However in your code, you are looking up the connection factory using
"java:/XAConnectionFactory", which is a *local*
This is a Jboss Messaging forum, not a Jboss MQ forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951620#3951620
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951620
__
I have replicated this and can confirm it is due to the 64K limit "bug" in
writeUTF (thanks Elias for the hint).
The fix is fairly straightforward and will be in the next release.
In the mean-time the workaround is not to use strings > 64K in text messages,
object messages, map messages or as s
4.0.4GA has been tested against 1.0.1CR2 from a fresh install and passes the
smoke tests fine.
I can only assume you haven't cleaned everything properly...
I spoke to Clebert (the JbossSerialization lead) and he informs me that the
error you are getting "Mismatch version of JBossSerialization s
Yes, this should be no different from configuring an MDB to talk to any foreign
jms provider.
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureAnEJB3MDBToTalkToARemoteQueue
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951511#3951511
Reply to the pos
Just to clarify:
You have 3 consumers in different VMs consuming using durable subscriptions, a
producer in another VM and a server in another VM, they are all on different
physical nodes.
You start them up and then kill one of the consumers.
You then send 10 messages.
The 2 remaining consume
1 - 100 of 222 matches
Mail list logo
