Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
21(a)technodom.kz
18 years
[EJB/JBoss] - Underlying connectivity on Remote EJB Access
by 4marcus
Hello,
I have some questions regarding technical connectivity of JBoss, which I could not resolve/find by checking the forums/documentation solely.
Accessing EJBs (SLSBs) from Remote Clients:
AFAIK, you can use RMI/IIOP to connect to the EJB Server. The actual connection handling relies on the InitialContextFactory implementation and the ORB implementation being used.
Using BEA/WLS you can also use T3 as protocol which takes over the connection handling in a performant way (multiplexing, clustercapability).
Questions regarding JBoss:
1) What are the options with JBoss towards standalone client doing remote EJB calls?
How does JBoss behave/what does JBoss use to realize the remote-EJB calls and what is configurable? I am particular interested in the lifecycle of the underlying TCP connections within failover setup (what if a connection breaks? Will it automatically be re-established/redirected)?
2) With BEA WLS you can use the T3 connection for the client also to subscripe to a Server Topic. How would this be realized with JBoss - is the TCP/IP connection built up and held open from the client to the server? Or would one use a completely different approach to realize client notification?
Reading http://wiki.jboss.org/wiki/ConfigJBossMQIL and /ConfigUIL2 contains some info. Does this mean, the client builds and maintains the connection to the server?)
Thanks
marcus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155106#4155106
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155106
18 years
[Messaging, JMS & JBossMQ] - Re: MDB does not consume messages
by jonathanztaub
"jaikiran" wrote : How about removing this message selector part and running your application again? Probably the messages sent to the queue do not match this selector and hence the MDB is not picking it up.
|
| <activation-config-property>
| | <activation-config-property-name>messageSelector</activation-config-property-name>
| | <activation-config-property-value>MessageFormat = 'Version 3.4'</activation-config-property-value>
| | </activation-config-property>
|
| P.S:While posting the logs or xml content or code, remember to wrap it in a code block using the Code button in the message editor window and please hit the Preview button to make sure your post is correctly formatted
I actually figured this out yesterday and meant to post a reply about it.
Yes, that was the gotch! I copied everything from an example and ended up matching it against various sample xml I found on the web.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155105#4155105
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155105
18 years
