[Installation, Configuration & DEPLOYMENT] - XAConnectionFactory Not Bounded
by neerajghiya
I am using JBoss 3.2.5. I want to change the database from hsql to MySql.For that I create mysql-ds.xml and remove hsqldb-ds.xml and also made changes in login-config.xml and other files as required.
Changes are as follows:
1.login-config.xml:add the following:
<application-policy name = "MySqlDbRealm">
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name =
"principal">the_mysql_username</module-option>
<module-option name =
"userName">the_mysql_username</module-option>
<module-option name
="password">the_mysql_pass</module-option>
<module-option name =
"managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=MySqlDS</module-option>
</login-module>
</application-policy>
2.Replace hsqldb-jdbc-state-service.xml to mysql-jdbc-state-service.xml
3.Modify the file
[jboss-location]\server\default\conf\standardjbosscmp-jdbc.xml :
<datasource-mapping>mySQL</datasource-mapping>
4.Modify the file [jboss-location]\server\default\conf\standardjaws.xml:
java:/MySqlDS
Note:In mysql-ds.xml I used: <jndi-name>DefaultDS</jndi-name>
I got the following error message on console:
2007-08-06 13:16:15,859 ERROR [DLQHandler] Initialization failed DLQHandler
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory n
ot bound
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:17
1)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBean
Support.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:
164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContaine
rInvoker.java:542)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContain
erInvoker.java:764)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:837)
Please give me the advice to remove the above error for JBoss 3.2.5 . Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071044#4071044
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071044
18Â years, 8Â months
[Installation, Configuration & DEPLOYMENT] - Classloading problem (sar within ear)
by lucdew
Hi,
i have experienced some issues with classloading in Jboss.
Actually, here's how my ear is packaged:
myapp.ear:
---->init.sar
---->mylib.jar
In my sar package, i need to load a resource which is packaged in mylib.jar
If i declare a loader repository the resource can not been seen.
I added in the init.sar 's manifest.mf file a dependency on mylib.jar by declaring
a class-path entry.
I declared the java modules in the application.xml like this:
<module>
| <java>mylib.jar</java>
| </module>
and in my jboss-app.xml:
<loader-repository>
| com.myapp:loader=testapp
| </loader-repository>
| <module>
| <service>init.sar</service>
| </module>
I even tried the different options:
<loader-repository>
| com.myapp:loader=testapp
| <loader-repository-config>
| java2ParentDelegation=false
| </loader-repository-config>
| </loader-repository>
and with java2ParentDelegation setting to true.
Even after reading the wiki and jboss documentation i am not sure to understand
which classloaders are created for my ear and the strategy they use to load
classes (parent delegation or not).
For me, by declaring a loader-repository for my ear it only isolates classes
and libraries of my ear from the other ear but the classloader is unified (flat).
Is this correct ?
How could i deal with this issue ?
Thanks in advance,
Luc
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071042#4071042
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071042
18Â years, 8Â months
[JBoss jBPM] - Re: mail node how to define actor and send email
by rossputin
hi,
whoops again, sorry, I will try with the code tag...
| <swimlane name="initiator"/>
|
| <swimlane name="line-manager">
| <assignment expression="user(user)"></assignment>
| </swimlane>
|
| <swimlane name="psm">
| <assignment expression="user(psmuser)"></assignment>
| </swimlane>
|
| <mail-node name="notify-initiator-rejected" actors="#{initiator}">
| <subject>
| line manager rejected
| </subject>
| <text>
| the line manager rejected for reason : #{reason}
| </text>
| <transition to="psr rejected"></transition>
| </mail-node>
|
| <mail-node name="notify-psm-red-light" actors="#{psm}">
| <subject>
| red light flagged building
| </subject>
| <text>
| a red light building has been found for PSR
| </text>
| <transition to="psm endorse"></transition>
| </mail-node>
So here the initiator email works fine, dispatching to whoever kicks off the process, but I am unsure how to specify other actors within the process, like the 'president' example in the docs...I have a user 'psmuser' in my JBPMTEST_ID_USER table, but no email process occurrs, I do not get an exception reported, and there is no pause in the process like when the initiator email is sent,
thanks for your help,
Ross
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071041#4071041
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071041
18Â years, 8Â months
[Messaging, JMS & JBossMQ] - JBoss MQSeries, remote connection not working....
by SriniRaghu
Hi Friends,
I am integrating JBoss with MQSeries. I have issues when I connect to MQSeries on a remote system, how ever with my local things work FINE...
I use the MDB in JBoss to listen to MQseries. below is the JBoss-service.xml for generating the sar file for JNDI lookup.
when I replace the external ip with "localhost" and then change the QM, Channel and Queue name things work fine. However with the below XML it gives me an exception
----------------------------Exception-------------
13:08:00,359 INFO [JMSContainerInvoker] Trying to reconnect to JMS provider for
MDB
13:08:20,875 ERROR [JMSContainerInvoker] Reconnect failed: JMS provider failure
detected for MDB
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '192.168.
1.91:QM_cg111'
--------------------------------------------------------
Can anyone please help me in resolving this issue. I have double checked the IP, QM, Channel, Port and Qname its all fine. I have changed the port from 1414 to 8000, and I am able to telnet to the same...
Thanks,
Srini
________________JBoss-Service.xml________________________
<server>
|
| <mbean code="jmx.service.wsmq.WSMQConnectionFactory"
| name="jmx.service.wsmq:service=WSMQXAQueueConnectionFactory">
| <attribute name="JndiName">WSMQXAQueueConnectionFactory</attribute>
| <attribute name="JMSStyle">Queue</attribute>
| <attribute name="IsXA">true</attribute>
| <attribute name="QueueManagerName">QM_cg111</attribute>
| <attribute name="HostName">192.168.1.91</attribute>
| <attribute name="Port">8000</attribute>
| <attribute name="Channel">S_cg111</attribute>
| <!-- MQJMS_TP_BINDINGS_MQ, MQJMS_TP_CLIENT_MQ_TCPIP, MQJMS_TP_DIRECT_TCPIP -->
| <attribute name="TransportType">MQJMS_TP_CLIENT_MQ_TCPIP</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
|
| <mbean code="jmx.service.wsmq.WSMQConnectionFactory"
| name="jmx.service.wsmq:service=MQQueueConnectionFactory">
| <attribute name="JndiName">WSMQQueueConnectionFactory</attribute>
| <attribute name="JMSStyle">Queue</attribute>
| <attribute name="IsXA">false</attribute>
| <attribute name="QueueManagerName">QM_cg111</attribute>
| <attribute name="HostName">192.168.1.91</attribute>
| <attribute name="Port">8000</attribute>
| <attribute name="Channel">S_cg111</attribute>
| <!-- MQJMS_TP_BINDINGS_MQ, MQJMS_TP_CLIENT_MQ_TCPIP, MQJMS_TP_DIRECT_TCPIP -->
| <attribute name="TransportType">MQJMS_TP_CLIENT_MQ_TCPIP</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
|
| <mbean code="jmx.service.wsmq.WSMQDestination"
| name="jmx.service.wsmq:service=WSMQRequestQueue">
| <attribute name="JndiName">wsmq/RequestQueue</attribute>
| <attribute name="JMSStyle">Queue</attribute>
| <attribute name="QueueManagerName">QM_cg111</attribute>
| <attribute name="DestinationName">RequestQueue</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
|
| <mbean code="jmx.service.wsmq.WSMQDestination"
| name="jmx.service.wsmq:service=WSMQResponseQueue">
| <attribute name="JndiName">wsmq/ResponseQueue</attribute>
| <attribute name="JMSStyle">Queue</attribute>
| <attribute name="QueueManagerName">QM_cg111</attribute>
| <attribute name="DestinationName">ResponseQueue</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
|
| </server>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071040#4071040
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071040
18Â years, 8Â months