4 Replies Latest reply on Nov 8, 2016 4:39 AM by Wolfgang Mayer

    Hello all,

    Bertrand Engoulou Newbie

      i'm trying to deployed my App from Wlidfly 8.

      When i try to deploy my EAR file it's run into the below error:

       

      2016-11-02 11:15:19,912 DEBUG [org.jboss.as.config] (MSC service thread 1-5) VM Arguments: -Dprogram.name=JBossTools: WildFly  8.x -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Users/Lenovo/Workspace_Geschäfsanwendung/wildfly-8.2.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/C:/Users/Lenovo/Workspace_Geschäfsanwendung/wildfly-8.2.1.Final/standalone/configuration/logging.properties -Djboss.home.dir=C:/Users/Lenovo/Workspace_Geschäfsanwendung/wildfly-8.2.1.Final -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252

      2016-11-02 11:15:24,310 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found CustomerManagement.ear in deployment directory. To trigger deployment create a file called CustomerManagement.ear.dodeploy

      2016-11-02 11:15:24,360 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

      2016-11-02 11:15:24,396 INFO  [org.xnio] (MSC service thread 1-8) XNIO version 3.3.0.Final

      2016-11-02 11:15:24,430 INFO  [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.0.Final

      2016-11-02 11:15:24,675 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      2016-11-02 11:15:24,676 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem

      2016-11-02 11:15:24,673 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.

      2016-11-02 11:15:24,670 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem

      2016-11-02 11:15:24,710 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.

      2016-11-02 11:15:24,760 INFO  [org.jboss.as.security] (MSC service thread 1-6) JBAS013170: Current PicketBox version=4.0.21.Final

      2016-11-02 11:15:24,757 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]

      2016-11-02 11:15:24,811 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors

      2016-11-02 11:15:24,820 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.1.8.Final starting

      2016-11-02 11:15:24,826 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.8.Final starting

      2016-11-02 11:15:24,893 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)

      2016-11-02 11:15:25,138 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path C:\Users\Lenovo\Workspace_Geschäfsanwendung\wildfly-8.2.1.Final/welcome-content

      2016-11-02 11:15:25,245 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server.

      2016-11-02 11:15:25,250 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.7.Final

      2016-11-02 11:15:25,310 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      2016-11-02 11:15:25,377 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

      2016-11-02 11:15:25,400 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting

      2016-11-02 11:15:25,458 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2

      2016-11-02 11:15:25,472 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]

      2016-11-02 11:15:25,857 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017519: Undertow HTTP listener default listening on localhost/127.0.0.1:8080

      2016-11-02 11:15:25,984 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\Lenovo\Workspace_Geschäfsanwendung\wildfly-8.2.1.Final\standalone\deployments

      2016-11-02 11:15:25,989 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "CustomerManagement.ear" (runtime-name: "CustomerManagement.ear")

      2016-11-02 11:15:25,989 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "mysql-connector-java-5.1.37-bin.jar" (runtime-name: "mysql-connector-java-5.1.37-bin.jar")

      2016-11-02 11:15:26,252 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015973: Starting subdeployment (runtime-name: "CustomerManagementWeb.war")

      2016-11-02 11:15:26,253 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015973: Starting subdeployment (runtime-name: "CustomerManagementEJB.jar")

      2016-11-02 11:15:26,465 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      2016-11-02 11:15:30,742 INFO  [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for CustomerManagementEJB

      2016-11-02 11:15:34,240 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment CustomerManagement.ear

      2016-11-02 11:15:36,254 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.1.3.Final

      2016-11-02 11:15:36,285 ERROR [org.jboss.remoting.remote.connection] (XNIO-1 I/O-2) JBREM000200: Remote connection failed: java.io.IOException: Eine bestehende Verbindung wurde softwaregesteuert

      durch den Hostcomputer abgebrochen

      2016-11-02 11:15:36,285 ERROR [org.jboss.remoting.remote.connection] (XNIO-1 I/O-1) JBREM000200: Remote connection failed: java.io.IOException: Eine bestehende Verbindung wurde softwaregesteuert

      durch den Hostcomputer abgebrochen

      2016-11-02 11:15:36,439 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment CustomerManagementWeb.war

      2016-11-02 11:15:39,012 INFO  [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final

      2016-11-02 11:15:39,031 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

      2016-11-02 11:15:39,033 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)

      2016-11-02 11:15:39,047 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) JBAS010417: Started Driver service with driver-name = mysql-connector-java-5.1.37-bin.jar_com.mysql.jdbc.Driver_5_1

      2016-11-02 11:15:39,047 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = mysql-connector-java-5.1.37-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1

      2016-11-02 11:15:39,231 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "CustomerManagement.ear")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [

          "jboss.persistenceunit.\"CustomerManagement.ear/CustomerManagementEJB.jar#CustomerManagementEJB\".__FIRST_PHASE__ is missing [jboss.naming.context.java.jboss.datasources.VideoTrainingDS]",

          "jboss.deployment.unit.\"CustomerManagement.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"CustomerManagement.ear\".beanmanager]"

      ]}

      2016-11-02 11:15:39,312 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "mysql-connector-java-5.1.37-bin.jar" (runtime-name : "mysql-connector-java-5.1.37-bin.jar")

      2016-11-02 11:15:39,313 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "CustomerManagement.ear" (runtime-name : "CustomerManagement.ear")

      2016-11-02 11:15:39,315 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.deployment.unit."CustomerManagement.ear".beanmanager (missing) dependents: [service jboss.deployment.unit."CustomerManagement.ear".weld.weldClassIntrospector]

            service jboss.naming.context.java.jboss.datasources.VideoTrainingDS (missing) dependents: [service jboss.persistenceunit."CustomerManagement.ear/CustomerManagementEJB.jar#CustomerManagementEJB".__FIRST_PHASE__]

       

       

      2016-11-02 11:15:39,449 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

      2016-11-02 11:15:39,450 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

      2016-11-02 11:15:39,451 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.1.Final "Tweek" started (with errors) in 23540ms - Started 274 of 335 services (5 services failed or missing dependencies, 96 services are lazy, passive or on-demand)

      2016-11-02 11:15:39,587 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015974: Stopped subdeployment (runtime-name: CustomerManagementWeb.war) in 17ms

      2016-11-02 11:15:39,587 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015974: Stopped subdeployment (runtime-name: CustomerManagementEJB.jar) in 17ms

      2016-11-02 11:15:39,588 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment CustomerManagement.ear (runtime-name: CustomerManagement.ear) in 20ms

      2016-11-02 11:15:39,799 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "CustomerManagement.ear" (runtime-name: "CustomerManagement.ear")

      2016-11-02 11:15:39,800 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.naming.context.java.module.CustomerManagement.CustomerManagementWeb (missing) dependents: [service jboss.deployment.subunit."CustomerManagement.ear"."CustomerManagementWeb.war".INSTALL]

            service jboss.persistenceunit."CustomerManagement.ear/CustomerManagementEJB.jar#CustomerManagementEJB".__FIRST_PHASE__ (missing) dependents: [service jboss.deployment.subunit."CustomerManagement.ear"."CustomerManagementEJB.jar".POST_MODULE]

       

       

      2016-11-02 11:15:44,380 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found CustomerManagement.ear in deployment directory. To trigger deployment create a file called CustomerManagement.ear.dodeploy.

       

      Somebody can help to solution the problem. Thank of all.

      Bertrand

        • 1. Re: Hello all,
          Wolfgang Mayer Master

          Apparently WildFly (Hibernate) has problems accessing your VideoTrainingDS when processing your  persistence.xml.

          Are you able to connect the datasource via cli (like /subsystem=datasources/data-source=VideoTrainingDS:test-connection-in-pool)?

          • 2. Re: Hello all,
            Bertrand Engoulou Newbie

            Hi Wolfgang,

            this issu was solved. I have the follow problem, when i start the Junit-Client .

            java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling.

             

            This my Client

             

            try{

              //  Hashtable enthält die Einstellung für Verbindung

              final Hashtable<String, Comparable> jndiProperties =

              new Hashtable<String, Comparable>();

              // Specifische Eigenschaften

              // Create initialContext

              jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY,

              "org.jboss.naming.remote.client.InitialContextFactory");

              jndiProperties.put("jboss.naming.client.ejb.context",true); // properties wichtig für remoting

              jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");

             

              // Zugriff. http-remoting benutzt Protokol und localhost:8080 benutzt machine

              jndiProperties.put(Context.PROVIDER_URL,"http-remoting://localhost:8080");

              jndiProperties.put(Context.SECURITY_PRINCIPAL, "admin");

              jndiProperties.put(Context.SECURITY_CREDENTIALS,"sicher");

             

                 //Instanz der Context wird erzeugt

              final Context context = new InitialContext(jndiProperties);

              // Apres le deployement j'obtien ce lien ki est le nom du LookupName

              // java:global/CustomerManagement/CustomerManagementEJB/Customerbean!com.ejb.interfaces.CustomerDAO

              final String lookupName =

              "CustomerManagement/CustomerManagementEJB/Customerbean!com.ejb.interfaces.CustomerDAO";

              // Zugriff auf bean

              customerDAO = (CustomerDAO) context.lookup(lookupName);

              context.close();

             

              }

            and My Entity:

             

            @Entity

            @NamedQuery(name= Customer.QUERY_GETALL,

              query = "SELECT c FROM Customer c" ) // NamedQuery Abfrage

            public class Customer implements Serializable {

             

              /**

              *

              */

              private static final long serialVersionUID = 1L; // je genere ceci lorsk le Customer implements Serializable.

             

             

              public static final String QUERY_GETALL = "Customer.GetAll";

             

              @Id

              @GeneratedValue(strategy = GenerationType.IDENTITY) // Mit Auto wird beste Mögliche Werte genommen

              private int id;

             

              @NotNull // Darf nicht null sein

              @Size(min = 1, max=500)

              private String firstName;

              @NotNull //

              @Size(min = 1, max=200)

              private String lastName;

             

              private Gender gender;

             

              private Relationship relationship;

             

              private Date birthday;

             

              // orphanRemoval = true sagt, dass wenn Customer gelöscht wird, wird auch die Address ebenfalls gelöscht // hier wird mit hilfe von FetchType.EARGER, lazy loading dauerhaft abgeschaltet

              @OneToMany(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.EAGER)

              @JoinColumn(name="customerid")// fremdschlüssel customerid wird eingefügt in der address Table

              private List<Address> addresses = new ArrayList<Address>(); // ici est l'addresse initialisiert

             

              @OneToMany(cascade = CascadeType.ALL, orphanRemoval = true,  fetch = FetchType.EAGER)

              @JoinColumn(name="customerid")

              private List<Communication> communications = new ArrayList<Communication>(); // Communication est initialisiert ici

             

              @Version // Optimische Sperrung. Last Änderung in der DB wird gespeichert. Sicher paralelle Änderungen erkennen werden von Customer, Address und Communication

              private Timestamp lastchanged;

            • 3. Re: Hello all,
              Bertrand Engoulou Newbie

              Please help me to resolve them. Thank fo all

              • 4. Re: Hello all,
                Wolfgang Mayer Master

                Bertrand,

                 

                This is not related to your Hibernate issue. You should therefore start a new discussion for this issue.

                But when checking the org.jboss.ejb.client.Logs.java you may realize that the EJBCLIENT000025 is loggend when a 'noEJBReceiverAvailableForDeploymentDuringInvocation' ist thrown in org.jboss.ejb.client.EJBClientContext.

                In the comment for the requireEJBReceiver method you can read:

                "Get the first EJB receiver which matches the given combination of app, module and distinct name. If there's no such EJB receiver, then this method throws a {@link IllegalStateException}"

                You should therefore verify that your lookupName matches the  JNDI bindings in WildFly