[Installation, Configuration & DEPLOYMENT] - HowDoIConfigureAnMDBToTalkToARemoteQueue
by tonylmai
I am trying to port my application from JBoss 4.2.1 to 5.0.Beta1. I am running into a problem with configuration for an MDB to access a remote queue.
I had my MDB configured in JBoss 4.2.1 using the example from a great blog on JBoss' wiki HowDoIConfigureAnMDBToTalkToARemoteQueue (http://www.jboss.org/community/docs/DOC-9893)
However, this configuration seems to fail under JBoss 5.0. Can someone shed a light? I would greatly appreciate some help..
Here are the configurations:
/* 1. MDB */
| @MessageDriven(activationConfig = {
| @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic")
| , @ActivationConfigProperty(propertyName="destination", propertyValue=Configuration.BANKDESK_CHANNEL_JNDI_NAME)
| , @ActivationConfigProperty(propertyName = "providerAdapterJNDI", propertyValue="java:/IBS_JMSProvider")
| // , @ActivationConfigProperty(propertyName="DLQMaxResent", propertyValue="10")
| })
| @Name("bankTxListener") // Seam's component name
| public class BankTransactionsListener implements javax.jms.MessageListener, Serializable {
| ...
| }
|
/* 2. dest-service-ds.xml */
| <server>
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.mq:service=JMSProviderLoader,name=RemoteJMSProvider,server=SF-CORP-QA-03">
| <attribute name="ProviderName">IBS_JMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
|
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
|
| <!-- Connect to JNDI on the host "queuehost" port 1099 -->
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jnp.interfaces
| java.naming.provider.url=localhost:1099
| </attribute>
| </mbean>
| </server>
|
/* 3. jboss.xml */
| <jboss xmlns="http://www.jboss.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd"
| version="3.0">
| <invoker-proxy-bindings>
| <invoker-proxy-binding>
| <name>IBS_JMS_MDB_Invoker</name>
| <invoker-mbean>does-not-matter</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>IBS_JMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <MinimumSize>1</MinimumSize>
| <MaximumSize>15</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/DLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
| </invoker-proxy-bindings>
| </jboss>
|
Again, your help is greatly appreciated. Thanks
-tony
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220008#4220008
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220008
17 years, 1 month
[JBoss Portal] - Role Membership Cached
by analyzediz
Hi folks --
This is should be a quick one. When I create a new role membership using the MembershipModule for the current user and subsequently try to access the page/portlet in the same session, it doesn't display the resource. I essentially have to log out of the portal and then log back in to see the resource that was just assigned to the user.
The only time the assignment will work without logging out is if the view privileges assigned are view [unchecked].
So any custom role that is assigned a view privilege will not work until you re-login.
Has any one else experienced this problem? Do we have to inform our users that they need to re-login after the perform this use case?
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220006#4220006
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220006
17 years, 1 month