10 Replies Latest reply on Oct 16, 2013 6:00 PM by Sheeraz Junejo

    EAR on jBoss EAP 6.1.Final not able to find res-ref

    Sheeraz Junejo Newbie

      I am trying to port my application to jBoss EAP6.1.Final and while deploying my ear with currently only one EJB 2.1 module is activated I am getting following errors;

      20:34:42,120 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.naming.context.java.jboss.resources.eis.myConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.tocfee. message-ejb.MessageMDB.env.eis.myConnectionFactory] service jboss.naming.context.java.jboss.resources.jms.jmsConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.tocfee. message-ejb.MessageMDB.env.jms.jmsConnectionFactory] service jboss.naming.context.java.jboss.resources.queue.responseQueue (missing) dependents: [service jboss.naming.context.java.comp.tocfee.message-ejb.MessageMDB.env.queue.responseQueue] 

      While I have following in my jboss.xml;

      <resource-ref> <res-ref-name>jms/jmsConnectionFactory</res-ref-name> <jndi-name>java:/ConnectionFactory</jndi-name> </resource-ref> <resource-ref> <res-ref-name>queue/responseQueue</res-ref-name> <jndi-name>java:/queue/responseQueue</jndi-name> </resource-ref> <resource-ref> <res-ref-name>eis/myConnectionFactory</res-ref-name> <jndi-name>java:jboss/jca/myConnectionFactory</jndi-name> </resource-ref> 

      I have verified the JNDI name in JNDI tree and they are exactly the same. I am not sure what am I missing. I have looked at quite a few topic on the same discussion including jboss 7 docs but still no use.

      P.S. I know this has been discusses 100 of time but I can not help it as its not working for me.

      Thanks

       

      Message was edited by: Sheeraz Junejo. Deployment Descriptor and Log files attached

        • 1. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
          Wolf-Dieter Fink Master

          Could you post the deployment descriptor and the server.log file?

          Other option is to raise a support ticket if you have an active subscription and not a 0$ developer subscription.

           

          Tip: you need to edit the post to attach files.

          • 2. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
            Sheeraz Junejo Newbie

            Thanks for the response. Files attached.

             

            Any idea whats wrong?

            • 4. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
              Sheeraz Junejo Newbie

              Thanks Jaikiran for the pointer now I am able to deploy my MDB successfully but still I am unable to consume messages from jms queue. I can see the messages are residing in the queue but my MDB is unable to consume them. New jobnss-ejb3.xml do not accept the 'destination-jndi-name' and throws an exception, so I added in my ejb-jar.xml under <activation-config> tag.

               

              Updated deployment descriptors are as follows;

               

              ejb-jar.xml

               

              <?xml version="1.0" encoding="UTF-8"?>

              <ejb-jar id="EJBJar_OfsMessageMDB" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">

                  <display-name>OFSMessage</display-name>

                  <enterprise-beans>

                      <message-driven id="MessageDriven_OfsMessageMDB">

                          <display-name>OFSMessage Bean</display-name>

                          <ejb-name>OFSMessageMDB</ejb-name>

                          <ejb-class>com.temenos.tocf.ofsmessage.mdb.OFSMessageMDB</ejb-class>

                          <messaging-type>javax.jms.MessageListener</messaging-type>

                          <transaction-type>Bean</transaction-type>

                <message-destination-type>javax.jms.Queue</message-destination-type>

                         <activation-config>

                              <activation-config-property>

                                  <activation-config-property-name>acknowledgeMode</activation-config-property-name>

                                  <activation-config-property-value>Auto-acknowledge</activation-config-property-value>

                              </activation-config-property>

                <activation-config-property>

                                  <activation-config-property-name>destination</activation-config-property-name>

                                  <activation-config-property-value>java:/queue/t24OFSQueue</activation-config-property-value>

                               </activation-config-property>

                          </activation-config>

                          <resource-ref id="ResourceRef_jmsQueueConnectionFactory">

                <description>T24 Queue Connection Factory</description>

                              <res-ref-name>jms/jmsConnectionFactory</res-ref-name>

                              <res-type>javax.jms.QueueConnectionFactory</res-type>

                              <res-auth>Container</res-auth>

                          </resource-ref>

                          <resource-ref id="ResourceRef_t24ConnectionFactory">

                              <description>T24 JCA Connection Factory</description>

                              <res-ref-name>eis/t24ConnectionFactory</res-ref-name>

                              <res-type>com.temenos.tocf.t24ra.T24ConnectionFactory</res-type>

                              <res-auth>Container</res-auth>

                          </resource-ref>

                          <resource-ref id="ResourceRef_t24OFSReplyQueue">

                              <description>OFS reply queue</description>

                              <res-ref-name>queue/t24OFSReplyQueue</res-ref-name>

                              <res-type>javax.jms.Queue</res-type>

                              <res-auth>Container</res-auth>

                          </resource-ref>

                      </message-driven>

                  </enterprise-beans>

              </ejb-jar>

               

              jboss-ejb3.xml

               

              <?xml version="1.0"?> 

                 <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"

                                xmlns="http://java.sun.com/xml/ns/javaee"

                                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                                xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd

                                   http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"

                                version="3.1"

                                impl-version="2.0">

                  <enterprise-beans>

                      <session>

                          <ejb-name>OFSMessageMDB</ejb-name>

                <session-type>Stateless</session-type>

                <resource-ref>

                              <res-ref-name>jms/jmsConnectionFactory</res-ref-name>

                              <jndi-name>java:/ConnectionFactory</jndi-name>

                          </resource-ref>

                          <resource-ref>

                              <res-ref-name>queue/t24OFSReplyQueue</res-ref-name>

                              <jndi-name>java:/queue/t24OFSReplyQueue</jndi-name>

                          </resource-ref>

                          <resource-ref>

                              <res-ref-name>eis/t24ConnectionFactory</res-ref-name>

                              <jndi-name>java:/jca/t24ConnectionFactory</jndi-name>

                          </resource-ref>

                      </session>

                  </enterprise-beans>

              </jboss:ejb-jar>

              • 5. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
                jaikiran pai Master

                When you deploy the queue (or start the server) what JNDI name does it print? Also, are you sure you are starting the standalone-full.xml configuration:

                 

                ./standalone.sh -c standalone-full.xml

                • 6. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
                  Sheeraz Junejo Newbie

                  Yes I am starting with full profile. See below as full log;

                   

                  13:04:38,049 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1

                  13:04:38,258 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1

                  13:04:38,312 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting

                  13:04:38,319 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties:

                    awt.toolkit = sun.awt.windows.WToolkit

                    file.encoding = Cp1252

                    file.encoding.pkg = sun.io

                    file.separator = \

                    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

                    java.awt.printerjob = sun.awt.windows.WPrinterJob

                    java.class.path = D:\jBoss\jboss-eap-6.1\jboss-modules.jar

                    java.class.version = 51.0

                    java.endorsed.dirs = D:\Java\jdk1.7.0\jre\lib\endorsed

                    java.ext.dirs = D:\Java\jdk1.7.0\jre\lib\ext;C:\windows\Sun\Java\lib\ext

                    java.home = D:\Java\jdk1.7.0\jre

                    java.io.tmpdir = C:\Users\sjunejo\AppData\Local\Temp\

                    java.library.path = D:\Java\jdk1.7.0\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64;C:\windows\Microsoft.NET\Framework64\v4.0.30319;C:\windows\Microsoft.NET\Framework64\v3.5;C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Team Tools\Performance Tools;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools\x64;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\x64;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;D:\Java\jdk1.7.0\bin;C:\Program Files\Perforce;C:\Program Files\TortoiseGit\bin;.

                    java.net.preferIPv4Stack = true

                    java.runtime.name = Java(TM) SE Runtime Environment

                    java.runtime.version = 1.7.0-b147

                    java.specification.name = Java Platform API Specification

                    java.specification.vendor = Oracle Corporation

                    java.specification.version = 1.7

                    java.util.logging.manager = org.jboss.logmanager.LogManager

                    java.vendor = Oracle Corporation

                    java.vendor.url = http://java.oracle.com/

                    java.vendor.url.bug = http://bugreport.sun.com/bugreport/

                    java.version = 1.7.0

                    java.vm.info = mixed mode

                    java.vm.name = Java HotSpot(TM) 64-Bit Server VM

                    java.vm.specification.name = Java Virtual Machine Specification

                    java.vm.specification.vendor = Oracle Corporation

                    java.vm.specification.version = 1.7

                    java.vm.vendor = Oracle Corporation

                    java.vm.version = 21.0-b17

                    javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder

                    javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory

                    javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory

                    javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory

                    javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory

                    javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory

                    javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory

                    javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory

                    javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory

                    javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory

                    jboss.home.dir = D:\jBoss\jboss-eap-6.1

                    jboss.host.name = lfzc2zn1

                    jboss.modules.dir = D:\jBoss\jboss-eap-6.1\modules

                    jboss.modules.system.pkgs = org.jboss.byteman

                    jboss.node.name = lfzc2zn1

                    jboss.qualified.host.name = lfzc2zn1

                    jboss.server.base.dir = D:\jBoss\jboss-eap-6.1\standalone

                    jboss.server.config.dir = D:\jBoss\jboss-eap-6.1\standalone\configuration

                    jboss.server.data.dir = D:\jBoss\jboss-eap-6.1\standalone\data

                    jboss.server.deploy.dir = D:\jBoss\jboss-eap-6.1\standalone\data\content

                    jboss.server.log.dir = D:\jBoss\jboss-eap-6.1\standalone\log

                    jboss.server.name = lfzc2zn1

                    jboss.server.persist.config = true

                    jboss.server.temp.dir = D:\jBoss\jboss-eap-6.1\standalone\tmp

                    line.separator =

                   

                   

                    logging.configuration = file:D:\jBoss\jboss-eap-6.1\standalone/configuration/logging.properties

                    module.path = D:\jBoss\jboss-eap-6.1\modules

                    org.jboss.boot.log.file = D:\jBoss\jboss-eap-6.1\standalone\log\server.log

                    org.jboss.resolver.warning = true

                    org.xml.sax.driver = __redirected.__XMLReaderFactory

                    os.arch = amd64

                    os.name = Windows 7

                    os.version = 6.1

                    path.separator = ;

                    program.name = standalone.bat

                    sun.arch.data.model = 64

                    sun.boot.class.path = D:\Java\jdk1.7.0\jre\lib\resources.jar;D:\Java\jdk1.7.0\jre\lib\rt.jar;D:\Java\jdk1.7.0\jre\lib\sunrsasign.jar;D:\Java\jdk1.7.0\jre\lib\jsse.jar;D:\Java\jdk1.7.0\jre\lib\jce.jar;D:\Java\jdk1.7.0\jre\lib\charsets.jar;D:\Java\jdk1.7.0\jre\classes

                    sun.boot.library.path = D:\Java\jdk1.7.0\jre\bin

                    sun.cpu.endian = little

                    sun.cpu.isalist = amd64

                    sun.desktop = windows

                    sun.io.unicode.encoding = UnicodeLittle

                    sun.java.command = D:\jBoss\jboss-eap-6.1\jboss-modules.jar -mp D:\jBoss\jboss-eap-6.1\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=D:\jBoss\jboss-eap-6.1 -c standalone-full.xml

                    sun.java.launcher = SUN_STANDARD

                    sun.jnu.encoding = Cp1252

                    sun.management.compiler = HotSpot 64-Bit Tiered Compilers

                    sun.os.patch.level = Service Pack 1

                    user.country = US

                    user.country.format = GB

                    user.dir = D:\jBoss\jboss-eap-6.1\bin

                    user.home = C:\Users\sjunejo

                    user.language = en

                    user.name = sjunejo

                    user.script =

                    user.timezone = Europe/London

                    user.variant =

                  13:04:38,321 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -XX:+TieredCompilation -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms1303M -Xmx1303M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -Dorg.jboss.boot.log.file=D:\jBoss\jboss-eap-6.1\standalone\log\server.log -Dlogging.configuration=file:D:\jBoss\jboss-eap-6.1\standalone/configuration/logging.properties

                  13:04:39,809 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

                  13:04:39,814 INFO  [org.xnio] (MSC service thread 1-7) XNIO Version 3.0.7.GA-redhat-1

                  13:04:39,829 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.0.7.GA-redhat-1

                  13:04:39,840 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 3.2.16.GA-redhat-1

                  13:04:39,966 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012605: Activated the following JSF Implementations: [main, 1.2]

                  13:04:39,967 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

                  13:04:39,984 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.

                  13:04:39,991 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)

                  13:04:40,006 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem

                  13:04:40,054 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension

                  13:04:40,082 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem

                  13:04:40,194 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem

                  13:04:40,198 INFO  [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service

                  13:04:40,219 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]

                  13:04:40,447 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.17.Final-redhat-1

                  13:04:40,474 INFO  [org.jboss.jaxr] (MSC service thread 1-6) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory

                  13:04:40,860 INFO  [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3

                  13:04:41,072 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "tocfee.ear" (runtime-name: "tocfee.ear")

                  13:04:41,082 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory D:\jBoss\jboss-eap-6.1\standalone\deployments

                  13:04:41,084 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "T24Utility.war" (runtime-name: "T24Utility.war")

                  13:04:41,142 INFO  [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-127.0.0.1/127.0.0.1:8080

                  13:04:41,149 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999

                  13:04:41,150 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447

                  13:04:41,162 INFO  [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-127.0.0.1/127.0.0.1:8080

                  13:04:41,200 WARN  [org.jboss.metadata.parser.jboss.JBossAppMetaDataParser] (MSC service thread 1-3) loader-repository element in jboss-app.xml is deprecated and has been ignored

                  13:04:41,401 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=D:\jBoss\jboss-eap-6.1\standalone\data\messagingjournal,bindingsDirectory=D:\jBoss\jboss-eap-6.1\standalone\data\messagingbindings,largeMessagesDirectory=D:\jBoss\jboss-eap-6.1\standalone\data\messaginglargemessages,pagingDirectory=D:\jBoss\jboss-eap-6.1\standalone\data\messagingpaging)

                  13:04:41,453 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221006: Waiting to obtain live lock

                  13:04:41,639 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xercesImpl.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/propertybag.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,659 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry commons-digester.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,676 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry commons-logging.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,681 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry commons-logging-api.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,686 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry log4j-1.2.13.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,710 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry mx4j.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,726 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry mx4j-impl.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,737 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry mx4j-jmx.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,676 WARN  [jacorb.codeset] (MSC service thread 1-5) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

                  13:04:41,759 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry mx4j-tools.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,793 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry mx4j-remote.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,807 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry tocfcommon.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/tocflistener-ejb.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,822 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jremote.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/delivery-ejb.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,756 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-2) IJ020001: Required license terms for file:/D:/jBoss/jboss-eap-6.1/modules/system/layers/base/com/temenos/tocf/t24ra/main/./

                  13:04:41,702 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221013: Using NIO Journal

                  13:04:41,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry tocfcommon.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/delivery-ejb.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,818 INFO  [org.jboss.as.jacorb] (MSC service thread 1-5) JBAS016330: CORBA ORB Service started

                  13:04:41,809 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

                  13:04:41,881 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry xercesImpl.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/propertybag.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,882 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "tocfOFSmessage-ejb.jar")

                  13:04:41,898 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry commons-digester.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,911 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry commons-logging.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,918 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry commons-logging-api.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,924 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry log4j-1.2.13.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,927 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry mx4j.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,931 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry mx4j-impl.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,932 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry mx4j-jmx.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,895 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-2) IJ020001: Required license terms for file:/D:/jBoss/jboss-eap-6.1/modules/system/layers/base/com/temenos/tocf/t24ra/main/./

                  13:04:41,942 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry mx4j-tools.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,950 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry mx4j-remote.jar in /D:/jBoss/jboss-eap-6.1/bin/content/T24Utility.war/WEB-INF/lib/tcommon.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:41,960 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry tocfcommon.jar in /D:/jBoss/jboss-eap-6.1/bin/content/tocfee.ear/tocfOFSmessage-ejb.jar  does not point to a valid jar for a Class-Path reference.

                  13:04:42,034 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/jca/t24ConnectionFactory

                  13:04:42,047 WARN  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-2) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/jca/t24ConnectionFactory

                  13:04:42,060 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-2) IJ020002: Deployed: file:/D:/jBoss/jboss-eap-6.1/modules/system/layers/base/com/temenos/tocf/t24ra/main/./

                  13:04:42,071 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/jca/t24ConnectionFactory]

                  13:04:42,097 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221034: Waiting to obtain live lock

                  13:04:42,099 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221035: Live Server Obtained live lock

                  13:04:42,146 INFO  [org.jboss.as.jacorb] (MSC service thread 1-3) JBAS016328: CORBA Naming Service started

                  13:04:42,419 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named OFSMessageMDB in deployment unit subdeployment "tocfOFSmessage-ejb.jar" of deployment "tocfee.ear" are as follows:

                   

                   

                    java:global/tocfee/tocfOFSmessage-ejb/OFSMessageMDB!javax.jms.MessageListener

                    java:app/tocfOFSmessage-ejb/OFSMessageMDB!javax.jms.MessageListener

                    java:module/OFSMessageMDB!javax.jms.MessageListener

                    java:global/tocfee/tocfOFSmessage-ejb/OFSMessageMDB

                    java:app/tocfOFSmessage-ejb/OFSMessageMDB

                    java:module/OFSMessageMDB

                   

                   

                  13:04:42,970 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 127.0.0.1:5445 for CORE protocol

                  13:04:42,974 INFO  [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 60) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.6.Final

                  13:04:42,982 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 127.0.0.1:5455 for CORE protocol

                  13:04:42,996 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221007: Server is now live

                  13:04:42,997 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221001: HornetQ Server version 2.3.1.Final (Wild Hornet, 123) [84ea8751-31b9-11e3-8bd3-7758138b7e0c]

                  13:04:43,049 INFO  [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 64) ISPN000161: Using a batchMode transaction manager

                  13:04:43,070 INFO  [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 60) ISPN000161: Using a batchMode transaction manager

                  13:04:43,091 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-8) JBAS010406: Registered connection factory java:/JmsXA

                  13:04:43,096 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

                  13:04:43,110 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.requestQueue

                  13:04:43,136 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:/queue/requestQueue

                  13:04:43,142 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.queue.responseQueue

                  13:04:43,145 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/queue/responseQueue

                  13:04:43,151 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queue.t24OFSReplyQueue

                  13:04:43,163 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/queue/t24OFSReplyQueue

                  13:04:43,168 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

                  13:04:43,170 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 63) HQ221003: trying to deploy queue jms.queue.t24OFSQueue

                  13:04:43,172 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:/queue/t24OFSQueue

                  13:04:43,200 INFO  [org.hornetq.ra] (MSC service thread 1-8) HornetQ resource adaptor started

                  13:04:43,201 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file://RaActivatorhornetq-ra

                  13:04:43,214 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

                  13:04:43,407 INFO  [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 64) ISPN000031: MBeans were successfully registered to the platform MBean server.

                  13:04:43,411 INFO  [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 60) ISPN000031: MBeans were successfully registered to the platform MBean server.

                  13:04:43,414 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64) JBAS010281: Started local-web cache from web container

                  13:04:43,414 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 60) JBAS010281: Started default-host/T24Utility cache from web container

                  13:04:43,449 INFO  [org.jboss.web] (ServerService Thread Pool -- 60) JBAS018210: Register web context: /T24Utility

                  13:04:43,719 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "tocfee.ear" (runtime-name : "tocfee.ear")

                  13:04:43,721 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "T24Utility.war" (runtime-name : "T24Utility.war")

                  13:04:43,750 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

                  13:04:43,752 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

                  13:04:43,753 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 6075ms - Started 287 of 363 services (75 services are passive or on-demand)

                  • 7. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
                    jaikiran pai Master

                    It doesn't look like your MDB is being deployed. What does your deployment packaging look like?

                     

                    jar -tf tocfOFSmessage-ejb.jar

                    • 8. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
                      Wolf-Dieter Fink Master

                      You should see a message like this

                      Started message driven bean 'Your MDB Bean' with 'hornetq-ra' resource adapter

                      • 9. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
                        Sheeraz Junejo Newbie

                        OK I haven't got this message in my logs but  can see following in the log;

                         

                        13:04:42,419 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named OFSMessageMDB in deployment unit subdeployment "tocfOFSmessage-ejb.jar" of deployment "tocfee.ear" are as follows:

                         

                         

                          java:global/tocfee/tocfOFSmessage-ejb/OFSMessageMDB!javax.jms.MessageListener

                          java:app/tocfOFSmessage-ejb/OFSMessageMDB!javax.jms.MessageListener

                          java:module/OFSMessageMDB!javax.jms.MessageListener

                          java:global/tocfee/tocfOFSmessage-ejb/OFSMessageMDB

                          java:app/tocfOFSmessage-ejb/OFSMessageMDB

                          java:module/OFSMessageMDB

                         

                         

                        13:04:42,970 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 127.0.0.1:5445 for CORE protocol

                         

                        My MDB is packaged as tocfee.ear/tocfOFSmessage-ejb.jar and I can see in logs about the queues definition as follows;

                        ....

                        13:04:43,110 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.requestQueue

                        13:04:43,136 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:/queue/requestQueue

                        13:04:43,142 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.queue.responseQueue

                        13:04:43,145 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/queue/responseQueue

                        13:04:43,151 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queue.t24OFSReplyQueue

                        13:04:43,163 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/queue/t24OFSReplyQueue

                        13:04:43,168 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

                        13:04:43,170 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 63) HQ221003: trying to deploy queue jms.queue.t24OFSQueue

                        13:04:43,172 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:/queue/t24OFSQueue

                        13:04:43,200 INFO  [org.hornetq.ra] (MSC service thread 1-8) HornetQ resource adaptor started

                        ....

                         

                        I am not sure now what is the problem as there is not a single Exception in the entire startup log. Also if its not deployed then why it is showing the JNDI bindings of my MDB as shown above?

                         

                        Also is there any example of deploying this kind of basic setup like deploying EJB2.1 onto jBoss with simple JMS?

                        • 10. Re: EAR on jBoss EAP 6.1.Final not able to find res-ref
                          Sheeraz Junejo Newbie

                          Just to update you that I landed on this page jboss-ejb3.xml Reference - JBoss AS 7.1 - Project Documentation Editor and it works now when moving the Activation Config Properties are moved to jboss-ejb3.xml. My final ejb-jar.xml, jboss-ejb3.xml looks like as follows (might be useful for someone)

                           

                          ejb-jar.xml [Working Version]

                          <enterprise-beans>

                                  <message-driven id="MessageDriven_OfsMessageMDB">

                                      <display-name>OFSMessage Bean</display-name>

                                      <ejb-name>OFSMessageMDB</ejb-name>

                                      <ejb-class>com.temenos.tocf.ofsmessage.mdb.OFSMessageMDB</ejb-class>

                                      <messaging-type>javax.jms.MessageListener</messaging-type>

                                      <transaction-type>Bean</transaction-type>

                            <message-destination-type>javax.jms.Queue</message-destination-type>

                                      <resource-ref id="ResourceRef_jmsQueueConnectionFactory">

                            <description>T24 Queue Connection Factory</description>

                                          <res-ref-name>jms/jmsConnectionFactory</res-ref-name>

                                          <res-type>javax.jms.QueueConnectionFactory</res-type>

                                          <res-auth>Container</res-auth>

                                      </resource-ref>

                                      <resource-ref id="ResourceRef_t24ConnectionFactory">

                                          <description>T24 JCA Connection Factory</description>

                                          <res-ref-name>eis/t24ConnectionFactory</res-ref-name>

                                          <res-type>com.temenos.tocf.t24ra.T24ConnectionFactory</res-type>

                                          <res-auth>Container</res-auth>

                                      </resource-ref>

                                      <resource-ref id="ResourceRef_t24OFSReplyQueue">

                                          <description>OFS reply queue</description>

                                          <res-ref-name>queue/t24OFSReplyQueue</res-ref-name>

                                          <res-type>javax.jms.Queue</res-type>

                                          <res-auth>Container</res-auth>

                                      </resource-ref>

                                  </message-driven>

                              </enterprise-beans>

                           

                          jboss-ejb3.xml

                           

                          <?xml version="1.0"?> 

                          <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"

                                            xmlns="http://java.sun.com/xml/ns/javaee"

                                            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                                            xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd

                                               http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"

                                            version="3.1"

                                            impl-version="2.0">

                              <enterprise-beans>

                            <message-driven>

                                      <ejb-name>OFSMessageMDB</ejb-name>

                                      <activation-config>

                            <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>destination</activation-config-property-name>

                                              <activation-config-property-value>java:/queue/t24OFSQueue</activation-config-property-value>

                                          </activation-config-property>

                            <activation-config-property>

                                              <activation-config-property-name>acknowledgeMode</activation-config-property-name>

                                              <activation-config-property-value>Auto-acknowledge</activation-config-property-value>

                                          </activation-config-property>

                            </activation-config>

                            <resource-ref>

                                          <res-ref-name>jms/jmsConnectionFactory</res-ref-name>

                                          <jndi-name>java:/ConnectionFactory</jndi-name>

                                      </resource-ref>

                                      <resource-ref>

                                          <res-ref-name>queue/t24OFSReplyQueue</res-ref-name>

                                          <jndi-name>java:/queue/t24OFSReplyQueue</jndi-name>

                                      </resource-ref>

                                      <resource-ref>

                                          <res-ref-name>eis/t24ConnectionFactory</res-ref-name>

                                          <jndi-name>java:/jca/t24ConnectionFactory</jndi-name>

                                      </resource-ref>

                                  </message-driven>

                              </enterprise-beans>

                          </jboss:ejb-jar>