Solved! The problematic code was instantiated several times, so at least one
jms-session per request was created. Seems this blocks the queue for a while,
because the other (old) session processes the request and puts it back (no
consumer) after a specific period.
View the original post :
I tried it again and reinstalled jboss 4.2.2.GA with messaging. After that it
look a bit different. First of all, the consumers receive the messages. But
they don't receive immediatelly, they wait up to nearly timeout seconds.
Message msg = MessageConsumer.receive(6);
Sometimes the call
Any idea, why the receive fails?
How can i find out, what goes wrong? Are there special log entries?
The ObjectMessage is stored to an oracle database, but the header fields are of
type blob, so a can't take a look into.
View the original post :
Sounds like your selector is just wrong, where are you setting
JMSType=java.lang.String?
Please post a simple java example demonstrating the problem (both sender and
receiver).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159635#4159635
Reply to the post :
mbreuer wrote : I am evaluating JBoss 4.2.2 and JBoss Messaging 1.4.0SP3.
When using MessageConsumer with a messageSelector, the communication hangs.
|
| ...
| Differences:
| Outside JBossAS the inspector indicates a SpyObjectMessage while inside the
container a JbossObjectMessage is
Thanks for the hint!
Probably the client classpath (outside) jboss contains a wrong jar, i will
check it.
What about the behavior inside the container? JBossObjectMessage seems to be
the right one. After setting JMSCorrelationID the object contains (in debugger)
the header property. Any
After installing, please run the examples as explained in the user guide.
If they don't all run successfully that means your installation was botched.
In which case you would need to re-install.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4159353#4159353
The example runs without trouble.
I used the example for my eclipse testclient. As noted, my test-client used the
the wrong classpath, i will verify this. Primary goal to get jboss messaging
running inside the container.
The message driven beans work fine. Also my jms-client works in general.
