[Messaging, JMS & JBossMQ] - Re: HAJNDIJMSProvider mbean not installed
by shaileshhp
"shaileshhp" wrote : I am using jboss-4.0.5.GA. I have placed jboss-messaging.jar(1.3.0.GA) in server lib.
| Here are the configurations that I have done:
|
| Added tibco-bridge-service.xml to server\all\deploy-hasingleton\jms folder.
| It looks as follows:
|
|
| |
| | <server>
| | <mbean code="org.jboss.jms.server.bridge.BridgeService"
| | name="jboss.messaging:service=Bridge,name=TestBridge"
| | xmbean-dd="xmdesc/Bridge-xmbean.xml">
| | <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider</depends>
| | <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider</depends>
| | <attribute name="SourceDestinationLookup">TopicName</attribute>
| | <attribute name="TargetDestinationLookup">queue/testQueue</attribute>
| | <attribute name="SourceUsername">userName</attribute>
| | <attribute name="SourcePassword">password</attribute>
| | <attribute name="QualityOfServiceMode">2</attribute>
| | <attribute name="MaxBatchSize">5</attribute>
| | <attribute name="MaxBatchTime">-1</attribute>
| | <attribute name="SubName">Test</attribute>
| | <!--attribute name="ClientID">myClientID</attribute-->
| | <attribute name="FailureRetryInterval">5000</attribute>
| | <attribute name="MaxRetries">-1</attribute>
| | </mbean>
| | </server>
| |
| |
|
| The target queue - queue/testQueue is the one which is by default in server\all\deploy-hasingleton\jms\jbossmq-destinations-service.xml file.
|
| The server\all\deploy\jms\hajndi-jms-ds.xml contains the following:
|
|
| | <!-- Tibco JMS Provider -->
| | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider">
| | <attribute name="ProviderName">TibcoJMSProvider</attribute>
| | <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| | <attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
| | <attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
| | <attribute name="Properties">
| | java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
| | java.naming.provider.url=ldap://abc.xyz
| | </attribute>
| | </mbean>
| |
| | <!-- The JMS provider loader -->
| | <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| | name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider">
| | <attribute name="ProviderName">DefaultJMSProvider</attribute>
| | <attribute name="ProviderAdapterClass">
| | org.jboss.jms.jndi.JNDIProviderAdapter
| | </attribute>
| | <attribute name="FactoryRef">XAConnectionFactory</attribute>
| | <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| | <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| | <attribute name="Properties">
| | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| | java.naming.provider.url=localhost:1100
| | jnp.disableDiscovery=false
| | jnp.partitionName=${jboss.partition.name:DefaultPartition}
| | jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
| | jnp.discoveryPort=1102
| | jnp.discoveryTTL=16
| | jnp.discoveryTimeout=5000
| | jnp.maxRetries=1
| | </attribute>
| | </mbean>
| |
| |
|
| Please let me know where I am going wrong.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165468#4165468
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165468
17 years, 9 months
[Messaging, JMS & JBossMQ] - Re: HAJNDIJMSProvider mbean not installed
by shaileshhp
I am using jboss-4.0.5.GA. I have placed jboss-messaging.jar(1.3.0.GA) in server lib.
Here are the configurations that I have done:
Added tibco-bridge-service.xml to server\all\deploy-hasingleton\jms folder.
It looks as follows:
|
| <server>
| <mbean code="org.jboss.jms.server.bridge.BridgeService"
| name="jboss.messaging:service=Bridge,name=TestBridge"
| xmbean-dd="xmdesc/Bridge-xmbean.xml">
| <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider</depends>
| <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider</depends>
| <attribute name="SourceDestinationLookup">TopicName</attribute>
| <attribute name="TargetDestinationLookup">queue/testQueue</attribute>
| <attribute name="SourceUsername">userName</attribute>
| <attribute name="SourcePassword">password</attribute>
| <attribute name="QualityOfServiceMode">2</attribute>
| <attribute name="MaxBatchSize">5</attribute>
| <attribute name="MaxBatchTime">-1</attribute>
| <attribute name="SubName">Test</attribute>
| <!--attribute name="ClientID">myClientID</attribute-->
| <attribute name="FailureRetryInterval">5000</attribute>
| <attribute name="MaxRetries">-1</attribute>
| </mbean>
| </server>
|
|
The target queue - queue/testQueue is the one which is by default in server\all\deploy-hasingleton\jms\jbossmq-destinations-service.xml file.
The server\all\deploy\jms\hajndi-jms-ds.xml contains the following:
| <!-- Tibco JMS Provider -->
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider">
| <attribute name="ProviderName">TibcoJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
| java.naming.provider.url=ldap://abc.xyz
| </attribute>
| </mbean>
|
| <!-- The JMS provider loader -->
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider">
| <attribute name="ProviderName">DefaultJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=172.18.236.228:1100
| jnp.disableDiscovery=false
| jnp.partitionName=${jboss.partition.name:DefaultPartition}
| jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
| jnp.discoveryPort=1102
| jnp.discoveryTTL=16
| jnp.discoveryTimeout=5000
| jnp.maxRetries=1
| </attribute>
| </mbean>
|
|
Please let me know where I am going wrong.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165467#4165467
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165467
17 years, 9 months
[JBoss Messaging] - Re: question about DownCacheSize
by ataylor
anonymous wrote : so if I set DeliveryMode=Persistent, the DownCacheSize which does the batch paging is not useful any more, since it gets saved to database right away, is it correct?
Wellnot exactly, all messages will actually go in to the down cache however only non persistent messages will get paged to the database.
anonymous wrote : why is AUTO_ACKNOWLEDGE =slow ? I can't think of a reason
With AUTO_ACKNOWLEDGE the client will acknowledge every single message on receive. With DUPS_OK for instance the client is allowed to ack the message lazile making it quicker.
anonymous wrote : 2.0 is still in alpha, it looks good from the benchmark stats, when will it be released? after jboss 5.0? another 6 month?
We'll probably have a release available towards the end of the year.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165466#4165466
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165466
17 years, 9 months
[Persistence, JBoss/CMP, Hibernate, Database] - Re: MySqlDS: lost all tables (and data)!
by jaikiran
<property name="hibernate.hbm2ddl.auto" value="update"/>
When you have set this property to "update", the tables should not have been dropped. Try this, start JBoss with your application, see if the tables are created. Then stop JBoss, see if the tables are dropped. That will tell us when the drop statements are being executed.
Also, add the hibernate.show_sql property to your persistence-unit as follows:
| <properties>
| <property name="hibernate.hbm2ddl.auto" value="update"/>
| <property name="hibernate.show_sql" value="true"/>
|
| </properties>
This will print out, in server.log, the SQLs being fired. Keep an watch on the server.log file to see when the drop statements are fired.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165465#4165465
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165465
17 years, 9 months