[JBoss Messaging] - Re: Destination COnfiguration issue with Jboss 5 and Messagi
by guy.finger
Hi Howard
Thanks for the reply.
I am still having the issue. I found a workaround for the same. I have configured the oracle as backend for JBoss by copying the oracle-ds.xml and oracle-persistance-service.xml files from examples folder to ${JbossRoot}/server/default/deploy and ${JbossRoot}/server/default/deploy/messaging folders respectively and modified the files to refer my local oracle db details.
But I am getting the errors during startup the server related to JBM_POSTOFFICE table creation. Table is not created which in turn not associating the destinations to ConnectionFactory.
here is the error -
09:35:29,183 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete
| deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| DEPLOYMENTS MISSING DEPENDENCIES:
| Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is mi
| ssing the following dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" is miss
| ing the following dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is missing the f
| ollowing dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=A,service=Queue" is missing the following de
| pendencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=B,service=Queue" is missing the following de
| pendencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=C,service=Queue" is missing the following de
| pendencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=D,service=Queue" is missing the following de
| pendencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the following
| dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the fo
| llowing dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=ex,service=Queue" is missing the following d
| ependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=securedTopic,service=Topic" is missing the f
| ollowing dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=serverPublishTopic,service=Topic" is missing
| the following dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=testDurableTopic,service=Topic" is missing t
| he following dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=testQueue,service=Queue" is missing the foll
| owing dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging.destination:name=testTopic,service=Topic" is missing the foll
| owing dependencies:
| Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is ac
| tually in state "Configured")
| Deployment "jboss.messaging:service=PostOffice" is missing the following dependencies:
| Dependency "jboss.jgroups:service=ChannelFactory" (should be in state "Create", but is
| actually in state "** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory' **")
|
| DEPLOYMENTS IN ERROR:
| Deployment "jboss.jgroups:service=ChannelFactory" is in error due to the following reason
| (s): ** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory' **
If I commented the following line in ${JBossRoot}/server/default/deploy/messaging/oracle-persistance-service.xml, server is coming up properly -
<depends optional-attribute-name="ChannelFactoryName">jboss.jgroups:service=ChannelFactory</depends>
Also, I have deleted the following confg file from deploy folder. This is also generating some deployment errors while starting up the server -
${JBossRoot}/server/default/deploy/ejb2-timer-service.xml
Please advise.
Thanks
Raj
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214923#4214923
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214923
17 years, 1 month
[JBoss Messaging] - Re: non-serializable XAResource error from JBoss Messaging -
by ajayazariah
configuration below:
| 1) conf/jbossjta-properties.xml :
|
|
| Node 1:
|
| <!-- (Must be unique across all Arjuna instances.) -->
| <property name="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="1"/>
|
| <!-- Configure which transactions must be recovered. Must match nodeIdentifier -->
| <property name="com.arjuna.ats.jta.xaRecoveryNode" value="1"/>
|
| <!-- configure XA recovery for JBoss Messaging -->
| <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
| value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>
|
| <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING2"
| value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/RemoteProvider2"/>
|
| <!-- specifying XA recovery for Oracle -->
| <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.Oracle"
| value="com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery;oraclejta-properties.xml"/>
|
|
| Node 2:
|
| <!-- (Must be unique across all Arjuna instances.) -->
| <property name="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="2"/>
|
| <!-- Configure which transactions must be recovered. Must match nodeIdentifier -->
| <property name="com.arjuna.ats.jta.xaRecoveryNode" value="2"/>
|
| <!-- configure XA recovery for JBoss Messaging -->
| <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
| value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>
|
| <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING2"
| value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/RemoteProvider2"/>
|
| <!-- specifying XA recovery for Oracle -->
| <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.Oracle"
| value="com.arjuna.ats.internal.jdbc.recovery.OracleXARecovery;oraclejta-properties.xml"/>
|
|
|
| 2) deploy/hajndi-jms-ds.xml
|
| Node 1:
|
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.jms:service=JMSProviderLoader,name=RemoteProvider2">
| <attribute name="ProviderName">RemoteProvider2</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <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=node_2_hostname:1099
| </attribute>
| </mbean>
|
| Node 2:
|
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.jms:service=JMSProviderLoader,name=RemoteProvider2">
| <attribute name="ProviderName">RemoteProvider2</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <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=node_1_hostname:1099
| </attribute>
| </mbean>
|
|
|
| 3) conf/oraclejta-properties.xml
|
| <transaction-service>
| <properties name="jdbc" type="system">
| <property name="DatabaseURL" value="jdbc:oracle:thin:@dbhost:25000:sid"/>
| <property name="UserName" value="jboss"/>
| <property name="Password" value="jboss"/>
| </properties>
| </transaction-service>
|
|
|
| 4) Oracle user "jboss" has been granted following permissions:
| select on DBA_PENDING_TRANSACTIONS,
| execute on SYS.DBMS_SYSTEM
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214921#4214921
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214921
17 years, 1 month
[Management, JMX/JBoss] - Does twiddle requires -b 0.0.0.0?
by alegomes
Look the facts I'm facing with JBoss 4.2.2.GA and tell me if this is the expected behaviour:
First, I started JBoss with:
| run.sh
|
and I got:
| ~/Documents/sea/edu/jboss_tuning/app/jboss-4.2.2.GA/bin$ ./twiddle.sh get jboss.system:type=ServerInfo HostAddress
| 10:54:35,761 ERROR [Twiddle] Exec failed
| org.jboss.util.NestedRuntimeException: - nested throwable: (javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.1.17; nested exception is:
| java.net.ConnectException: Connection refused])
| at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:143)
| at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:59)
| at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:149)
| at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305)
|
Then, I started JBoss with:
| run.sh -b 192.168.1.17
|
and got this time:
| ~/Documents/sea/edu/jboss_tuning/app/jboss-4.2.2.GA/bin$ ./twiddle.sh get jboss.system:type=ServerInfo HostAddress
| 11:05:41,966 ERROR [Twiddle] Exec failed
| org.jboss.util.NestedRuntimeException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]; - nested throwable: (javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]])
|
So, I tried:
run.sh -b 0.0.0.0
and, finally, there it goes:
| ~/Documents/sea/edu/jboss_tuning/app/jboss-4.2.2.GA/bin$ ./twiddle.sh get jboss.system:type=ServerInfo HostAddress
| HostAddress=192.168.1.17
|
Is that correct? Should I bind JBoss AS to every interfaces to get twiddle working?
thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214920#4214920
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214920
17 years, 1 month
[JBoss Messaging] - non-serializable XAResource error from JBoss Messaging - Clu
by ajayazariah
After killing (-9) one node, the other node picks up and processes the messages.
After that when I restart the fist node, I get the following on second pass of the recovery manager:
"[com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]
Could not find new XAResource to use for recovering non-serializable XAResource"
I have done the configuration according to http://www.jboss.org/community/docs/DOC-13171, but that does not seem to fix it.
Could someone point out the error in the configuration below:
1) conf/jbossjta-properties.xml :
Node 1:
Node 2:
2) deploy/hajndi-jms-ds.xml
Node 1:
RemoteProvider2
org.jboss.jms.jndi.JNDIProviderAdapter
<!-- The combined connection factory -->
XAConnectionFactory
<!-- The queue connection factory -->
XAConnectionFactory
<!-- The topic factory -->
XAConnectionFactory
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=node_2_hostname:1099
Node 2:
RemoteProvider2
....
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=node_1_hostname:1099
3) conf/oraclejta-properties.xml
<transaction-service>
</transaction-service>
4) Oracle user "jboss" has been granted following permissions:
select on DBA_PENDING_TRANSACTIONS,
execute on SYS.DBMS_SYSTEM
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214919#4214919
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214919
17 years, 1 month