[Messaging, JMS & JBossMQ] - Re: XA trasactions over a remote MQ queue Jboss 3.2.6
by rrkraft
We're still having this issue and I'm trouble-shooting it at the JBoss server side. My configuration is as follows:
standardjboss.xml:
anonymous wrote :
| <invoker-proxy-binding>
| ATADev-mdb-invoker
| <invoker-mbean>does-not-matter</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-fac
| tory>
| <proxy-factory-config>
| ATADevJMSProvider
| StdJMSPool</ServerSessionPoolFactoryJN
| DI>
| 1
| 30000
| 15
| 1
|
| 10
|
| queue/DLQ
| 10
| 0
|
|
| </proxy-factory-config>
| </invoker-proxy-binding>
|
| <message-driven>
| <ejb-name>ejb/PRCMessageAccess</ejb-name> <destination-jndi-name>queue/PRCCustomerContactForm</destination-jndi-n
| ame>
| <invoker-bindings>
|
| <invoker-proxy-binding-name>ATADev-mdb-invoker</invoker-proxy-bin
| ding-name>
|
| </message-driven>
|
?-jms-ds.xml:
anonymous wrote :
| <connection-factories>
| <tx-connection-factory>
| <jndi-name>ATADevJmsXA</jndi-name>
| <xa-transaction/>
| <adapter-display-name>JMS Adapter</adapter-display-name>
| <config-property name="SessionDefaultType" type="java.lang.String">javax.jms
| .Queue</config-property>
| <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:
| /ATADevJMSProvider</config-property>
| <security-domain-and-application>ATADevJmsXARealm</security-domain-and-appli
| cation>
|
| </tx-connection-factory>
| </connection-factories>
|
?-ds.xml:
anonymous wrote :
|
| ATADevJMSProvider
| org.jboss.jms.jndi.JNDIProviderAdapte
| r
| <!-- The queue connection factory -->
| java:/ATADevJmsXA
| <!-- The topic factory -->
| XAConnectionFactory
| <!-- Uncomment to use HAJNDI to access JMS -->
|
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=jnp://sun9.ata.com:7045
|
|
|
login-config.xml:
anonymous wrote :
| <application-policy name = "ATADevJmsXARealm">
|
| <login-module code = "org.jboss.resource.security.ConfiguredIdentityLo
| ginModule"
| flag = "required">
| <module-option name = "principal">ppppp/module-option>
| <module-option name = "userName">uuuuu</module-option>
| <module-option name = "password">pppppp</module-option>
| <module-option name = "managedConnectionFactoryName">jboss.jca:serv
| ice=TxCM,name=ATADevJmsXA</module-option>
| </login-module>
|
| </application-policy>
|
If we use in ?-ds.xml as attribute name="QueueFactoryRef" XAConnectionFactory, we get the error, Todd mentions.
If we use there java:/XAConnectionFactory" I get the error "user uuuuu not authenticated".
I found somewhere, that I could use also a JCA connection factory (java:/ATADevJmsXA), but with this I get "Can not get a topic session from a queue connection".
I googled and searched the jboss website and cannot find any indication how this should work. I assume since I have a password protected queue, I have to use a JCA connection factory.
Very Best Regards,
Rainer
PS: Sorry for the other post. I had to learn first how to quote.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975187#3975187
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975187
17 years, 8 months
[Messaging, JMS & JBossMQ] - Re: XA trasactions over a remote MQ queue Jboss 3.2.6
by rrkraft
We're still having this issue and I'm trouble-shooting it at the JBoss server side. My configuration is as follows:
standardjboss.xml:
<invoker-proxy-binding>
ATADev-mdb-invoker
<invoker-mbean>does-not-matter</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-fac
tory>
<proxy-factory-config>
ATADevJMSProvider
StdJMSPool</ServerSessionPoolFactoryJN
DI>
1
30000
15
1
10
queue/DLQ
10
0
</proxy-factory-config>
</invoker-proxy-binding>
<message-driven>
<ejb-name>ejb/PRCMessageAccess</ejb-name> <destination-jndi-name>queue/PRCCustomerContactForm</destination-jndi-n
ame>
<invoker-bindings>
<invoker-proxy-binding-name>ATADev-mdb-invoker</invoker-proxy-bin
ding-name>
</message-driven>
?-jms-ds.xml:
<connection-factories>
<tx-connection-factory>
<jndi-name>ATADevJmsXA</jndi-name>
<xa-transaction/>
<adapter-display-name>JMS Adapter</adapter-display-name>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms
.Queue</config-property>
<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:
/ATADevJMSProvider</config-property>
<security-domain-and-application>ATADevJmsXARealm</security-domain-and-appli
cation>
</tx-connection-factory>
</connection-factories>
?-ds.xml:
ATADevJMSProvider
org.jboss.jms.jndi.JNDIProviderAdapte
r
<!-- The queue connection factory -->
java:/ATADevJmsXA
<!-- The topic factory -->
XAConnectionFactory
<!-- Uncomment to use HAJNDI to access JMS -->
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=jnp://sun9.ata.com:7045
login-config.xml:
<application-policy name = "ATADevJmsXARealm">
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLo
ginModule"
flag = "required">
<module-option name = "principal">ppppp/module-option>
<module-option name = "userName">uuuuu</module-option>
<module-option name = "password">pppppp</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:serv
ice=TxCM,name=ATADevJmsXA</module-option>
</login-module>
</application-policy>
If we use in ?-ds.xml as attribute name="QueueFactoryRef" XAConnectionFactory, we get the error, Todd mentions.
If we use there java:/XAConnectionFactory" I get the error "user uuuuu not authenticated".
I found somewhere, that I could use also a JCA connection factory (java:/ATADevJmsXA), but with this I get "Can not get a topic session from a queue connection".
I googled and searched the jboss website and cannot find any indication how this should work. I assume since I have a password protected queue, I have to use a JCA connection factory.
Very Best Regards,
Rainer
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975186#3975186
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975186
17 years, 8 months
[JBoss Portal] - Re: How to control maximized portlet layout?
by mholzner
this is described in the doc, but perhaps not easy to find ;)
You can do what you are looking for. It is controlled via the layout strategy for one, and then via the layout itself. The layout can describe individual layout JSPs (or Servlets) for each 'state'. The state is set by the layout strategy. The strategy is also the one that can move portlets into different regions depending on the state, etc. Read the layout and theme doc. It is all in there.
The default layout is using two JSPs, one for 'normal' and one for 'maximized' state. The Maximizing Strategy filters all but the portlets in the navigation and the maximized region, and temporarily moves the maximized portlet into the maximized region.
So I guess in your case you want to only change the strategy to only filter the not maximized portlets in the region that contains the maximized portlet, hece the maximized portlet gets the entire region for itself. The rest should already do what you need.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975179#3975179
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975179
17 years, 8 months