[Installation, Configuration & DEPLOYMENT] - JBoss 5.1.0: Error for ActivationSpec class com.ibm.mq.conne
by sebbay
Hello,
When deploying an application using Websphere MQ, I get the following exception:
Caused by: org.jboss.deployers.spi.DeploymentException: Error for ActivationSpec class com.ibm.mq.connector.inbound.ActivationSpecImpl as JavaBean
| at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
| at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:135)
| at org.jboss.resource.deployers.RARDeployment.createActivationSpec(RARDeployment.java:313)
| at org.jboss.resource.deployers.RARDeployment.internalInvoke(RARDeployment.java:276)
| at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:449)
| ... 137 more
| Caused by: java.beans.IntrospectionException: No property found for: acknowledgeMode on JavaBean: javax.jms.Queue:SYSTEM.DEFAULT.LOCAL.QUEUE@@localhost
| at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:354)
| at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:285)
| at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:129)
I recently get out, that WMQ Resource Adapter doesn't support the property acknowledgeMode. How can I configure JBoss 5.1.0 that this exception is not thrown?
Abridgment of the ejb-jar.xml:
<message-driven>
| <ejb-name>ServiceImpl</ejb-name>
| <ejb-class>test.ServiceImpl</ejb-class>
| <messaging-type>javax.jms.MessageListener</messaging-type>
| <transaction-type>Bean</transaction-type>
| <activation-config>
| <activation-config-property>
| <activation-config-property-name>destination</activation-config-property-name>
| <activation-config-property-value>TEST_QUEUE</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>destinationType</activation-config-property-name>
| <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
| </activation-config-property>
| <!-- activation-config-property>
| <activation-config-property-name>messagingType</activation-config-property-name>
| <activation-config-property-value>javax.jms.MessageListener</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>useJNDI</activation-config-property-name>
| <activation-config-property-value>false</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>hostName</activation-config-property-name>
| <activation-config-property-value>localhost</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>queueManager</activation-config-property-name>
| <activation-config-property-value>QM_TEST</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>port</activation-config-property-name>
| <activation-config-property-value>1414</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>transportType</activation-config-property-name>
| <activation-config-property-value>CLIENT</activation-config-property-value>
| </activation-config-property-->
| </activation-config>
| <ejb-local-ref>
| <ejb-ref-name<Service</ejb-ref-name>
| <ejb-ref-type>Session</ejb-ref-type>
| <local>test.Service</local>
| </ejb-local-ref>
| </message-driven>
Abridgment of the jboss.xml:
<?xml version="1.0" encoding="UTF-8"?>
| <jboss>
| <enterprise-beans>
| <message-driven>
| <resource-adapter-name>wmq.jmsra.rar</resource-adapter-name>
| <ejb-name>OutboundMessageListenerServiceImpl</ejb-name>
| <configuration-name>Standard Message Driven Bean</configuration-name>
| </message-driven>
| </enterprise-beans>
| </jboss>
|
Best regards,
Sebastian
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241093#4241093
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241093
15 years, 7 months
[JBoss Messaging] - Re: Embedded server - how to create JMS Topic?
by jmesnil
"Leos.Bitto" wrote : Thanks a lot for all the quick answers! Navigating me to JMSServerManagerImpl was exactly what I needed. I do not like JMSServerManagerImpl much for embedding, though, because of two reasons. First is that it somehow automagically picks the file jbm-jms.xml, which in my case belongs to a different server instance and therefore must not be used. Second is that it registers the queues and topics into JNDI (passing null as the secong argument to createTopic leads to NullPointerException) and I am trying to avoid JNDI in this case.
|
Regarding jbm-jms.xml, it will be picked up if it is in the classpath. Could you place it in a separate directory and add it to the classpath of the other server instance instead?
For JNDI, you could pass a no-op Context implementation to JMServerManager.setContext() to "disable" JNDI.
Do not hesitate to fill JIRA issues for this kind of improvements.
Thanks for the feedback,
jeff
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241087#4241087
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241087
15 years, 7 months
[JBoss Messaging] - Re: Embedded server - how to create JMS Topic?
by Leos.Bitto
Thanks a lot for all the quick answers! Navigating me to JMSServerManagerImpl was exactly what I needed. I do not like JMSServerManagerImpl much for embedding, though, because of two reasons. First is that it somehow automagically picks the file jbm-jms.xml, which in my case belongs to a different server instance and therefore must not be used. Second is that it registers the queues and topics into JNDI (passing null as the secong argument to createTopic leads to NullPointerException) and I am trying to avoid JNDI in this case. So I have just borrowed a bit of your code from JMSServerManagerImpl.java and this works fine for me:
final SimpleString t = JBossTopic.createAddressFromName(name);
server.createQueue(t, t, new SimpleString("__JBMX=-1"), true, false);
It would be nice if you could make the String "__JBMX=-1" available somewhere from your code. Maybe just change the private static final field REJECT_FILTER in JMSServerManagerImpl from private to public?
Regarding using the core API directly instead of JMS - that is a possibility, of course. However, I am trying to stick with JMS, because that makes my code compatible with many other messaging implementations, too, instead of binding it tightly to JBoss Messaging.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241082#4241082
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241082
15 years, 7 months
[JBoss Cache: Core Edition] - Re: JDBCCacheLoader with Oracle 10g problem
by niuxuetao_fiserv
Thanks Mircea,
Here is the table description:
| DESC cached_events
| Name Null Type
| ------------------------------ -------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| FQN NOT NULL VARCHAR2(255)
| NODE BLOB()
| PARENT VARCHAR2(255)
|
| 3 rows selected
|
And there is another table automatically created, called 'cached_events_d' which is not described in the jboss doc as far as I can find. And if I change the cache table's name to something else, say XXX, the automatically created table will be named as XXX_Y where Y looks a random character.
Do you know what this is for?
The description of this table is as below:
| DESC cached_events_d
| Name Null Type
| ------------------------------ -------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| I CHAR(1)
|
| 1 rows selected
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241080#4241080
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241080
15 years, 7 months