Hi,
Can anyone tell me whether this doesnt work in JBoss-3.2.3? I have been trying
to find a solution for this since a long time now.
I also, tried out by removing the creation of a transaction. Even then i got
the same exception.
Hopefully, will get a reply this time
Thank you
View the ori
Arghh! I've already shouted people for continually asking this question.
Use search.
The answer is early next month.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835840#3835840
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=r
Do you know when the next build of 3.2.4 will be? I would prefer using your build
rather than my hacked build.
Regards,
Lyndon.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835835#3835835
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=
Yes, I will add it for 3.2.4 (after some testing of my own).
Let me know how the XA tests go.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835617#3835617
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835617
--
Hi,
We are still doing testing, but initial assessment looks like your latest changes have
solved the problem.
We were able to use the ConnectionFactory to publish a text message from the WebLogic
Bridge to JBoss. The message was received by our MDB.
Your help was great. I hope that this new
I have not yet tried out your last suggestion but here is a trace after trying the
previous suggestion.
Here is a snippet from server.log with Tracing on for org.jboss.mq category.
2004-05-19 09:34:13,701 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED :
addMessage
2004-05-19 09:34:13,7
There is obviously something very peculiar about the WebLogic message
implementation.
Try it with these method implementations (which are probably more logical)
it no longer tries to set the destination on the WebLogic message then
copy it into the SpyMessage, instead it copies the WebLogic messa
BTW, I also tried using the XAConnectionFactory and while I didn't get the invalid
transaction ID, there was still some type of exception.
I am now only using the regular ConnectionFactory in my tests from my last post.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewt
As you suggested I used 3.2.4RC2 and modified the SpyMessageProducer class. The only
change was that I now had to include the class of my object message in the classpath
or else I got a class not found error in the encapsulate message method. After
including the message object class in the cla
If you can download 3.2.4RC2, that will give you a starting point.
Then modify this class to remove the wrapping mechanism when extending
external messages.
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/SpyMessageProducer.java?annotate=1.2.8.2
i.e. in the method encaps
A little more stack trace. BTW. I am also pursuing this issue from the BEA side with
BEA support.
org.jboss.mq.SpyJMSException: Cannot send a message to the JMS server; - nested
throwable: (java.lang.NullPointerException)
at org.jboss.mq.Connection.sendToServer(Connection.java:1251)
I decided to use the Connection Factory instead of the XAConnectionFactory. I now get
a little further. Instead of only seeing an exception at the client I now also see
one at the server. It is:
java.lang.NullPointerException
at
org.jboss.mq.security.ServerSecurityInterceptor.addMess
No it is in 3.2.4RC2, due out any second now.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835233#3835233
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835233
---
Is this change in JBoss 3.2.4RC1 available from sourceforge?
Thanks,
Lyndon.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835231#3835231
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835231
--
The XASession's XAResource has not been enlisted in a JTA transaction.
I recently added code for jboss-3.2.4 that allows JBossMQ's XAConnectionFactory
to be used outside a JTA transaction (it behaves the same as AUTO_ACKNOWLEDGE)
I would suggest you try it with the plain ConnectionFactory
Or fig
15 matches
Mail list logo
