Problem during "ant install" - No EJB receiver available for handling

Help
2014-02-28
2014-04-06
  • Jason Separovic

    Jason Separovic - 2014-02-28

    Hi,

    I'm trying to install EJBCA 6.0.3 on JBoss AS 7.1.1. Everything works fine up to "ant install" in the process. It fails with a bunch of "No EJB receiver available for handling" errors.

    See below for trace details.

    Has anyone encountered this error, or has any ideas of how it can be fixed?

    Thanks,

    Jason

    =============================

    ejbca:install:

    ejbca:initCA:
    [echo] Initializing CA with ....
    [java] Could not run execute method for class ca
    [java] java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:ejbca, moduleName:ejbca-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@65acdea1
    [java] at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
    [java] at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
    [java] at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
    [java] at com.sun.proxy.$Proxy0.getCachedConfiguration(Unknown Source)
    [java] at org.ejbca.ui.cli.BaseCommand.parseUsernameAndPasswordFromArgs(BaseCommand.java:123)
    [java] at org.ejbca.ui.cli.ca.CaInitCommand.execute(CaInitCommand.java:131)
    [java] at org.ejbca.ui.cli.CliCommandHelper.executeCommand(CliCommandHelper.java:147)
    [java] at org.ejbca.ui.cli.CliCommandHelper.searchAndRun(CliCommandHelper.java:105)
    [java] at org.ejbca.ui.cli.EjbcaEjbCli.main(EjbcaEjbCli.java:25)
    [java] Java Result: 1

    ejbca:adminweb:
    [java] Could not run execute method for class ra
    [java] java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:ejbca, moduleName:ejbca-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@d5589d4
    [java] at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
    [java] at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
    [java] at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
    [java] at com.sun.proxy.$Proxy0.getCachedConfiguration(Unknown Source)
    [java] at org.ejbca.ui.cli.BaseCommand.parseUsernameAndPasswordFromArgs(BaseCommand.java:123)
    [java] at org.ejbca.ui.cli.ra.AddEndEntityCommand.execute(AddEndEntityCommand.java:79)
    [java] at org.ejbca.ui.cli.CliCommandHelper.executeCommand(CliCommandHelper.java:147)
    [java] at org.ejbca.ui.cli.CliCommandHelper.searchAndRun(CliCommandHelper.java:105)
    [java] at org.ejbca.ui.cli.EjbcaEjbCli.main(EjbcaEjbCli.java:25)
    [java] Java Result: 1
    [java] Could not run execute method for class ra
    [java] java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:ejbca, moduleName:ejbca-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@d5589d4
    [java] at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
    [java] at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
    [java] at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
    [java] at com.sun.proxy.$Proxy0.getCachedConfiguration(Unknown Source)
    [java] at org.ejbca.ui.cli.BaseCommand.parseUsernameAndPasswordFromArgs(BaseCommand.java:123)
    [java] at org.ejbca.ui.cli.ra.SetCleartextPasswordCommand.execute(SetCleartextPasswordCommand.java:45)
    [java] at org.ejbca.ui.cli.CliCommandHelper.executeCommand(CliCommandHelper.java:147)
    [java] at org.ejbca.ui.cli.CliCommandHelper.searchAndRun(CliCommandHelper.java:105)
    [java] at org.ejbca.ui.cli.EjbcaEjbCli.main(EjbcaEjbCli.java:25)
    [java] Java Result: 1
    [echo] batch tomcat
    [java] Could not run execute method for class null
    [java] java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:ejbca, moduleName:ejbca-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@7dad44b0
    [java] at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
    [java] at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
    [java] at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
    [java] at com.sun.proxy.$Proxy0.getCachedConfiguration(Unknown Source)
    [java] at org.ejbca.ui.cli.BaseCommand.parseUsernameAndPasswordFromArgs(BaseCommand.java:123)
    [java] at org.ejbca.ui.cli.batch.BatchMakeP12.execute(BatchMakeP12.java:91)
    [java] at org.ejbca.ui.cli.CliCommandHelper.executeCommand(CliCommandHelper.java:147)
    [java] at org.ejbca.ui.cli.CliCommandHelper.searchAndRun(CliCommandHelper.java:67)
    [java] at org.ejbca.ui.cli.EjbcaEjbCli.main(EjbcaEjbCli.java:25)
    [java] Java Result: 1
    [java] Could not run execute method for class ra
    [java] java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:ejbca, moduleName:ejbca-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@d5589d4
    [java] at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
    [java] at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
    [java] at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
    [java] at com.sun.proxy.$Proxy0.getCachedConfiguration(Unknown Source)
    [java] at org.ejbca.ui.cli.BaseCommand.parseUsernameAndPasswordFromArgs(BaseCommand.java:123)
    [java] at org.ejbca.ui.cli.ra.AddEndEntityCommand.execute(AddEndEntityCommand.java:79)
    [java] at org.ejbca.ui.cli.CliCommandHelper.executeCommand(CliCommandHelper.java:147)
    [java] at org.ejbca.ui.cli.CliCommandHelper.searchAndRun(CliCommandHelper.java:105)
    [java] at org.ejbca.ui.cli.EjbcaEjbCli.main(EjbcaEjbCli.java:25)
    [java] Java Result: 1
    [java] Could not run execute method for class ra
    [java] java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:ejbca, moduleName:ejbca-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@d5589d4
    [java] at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
    [java] at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
    [java] at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
    [java] at com.sun.proxy.$Proxy0.getCachedConfiguration(Unknown Source)
    [java] at org.ejbca.ui.cli.BaseCommand.parseUsernameAndPasswordFromArgs(BaseCommand.java:123)
    [java] at org.ejbca.ui.cli.ra.SetCleartextPasswordCommand.execute(SetCleartextPasswordCommand.java:45)
    [java] at org.ejbca.ui.cli.CliCommandHelper.executeCommand(CliCommandHelper.java:147)
    [java] at org.ejbca.ui.cli.CliCommandHelper.searchAndRun(CliCommandHelper.java:105)
    [java] at org.ejbca.ui.cli.EjbcaEjbCli.main(EjbcaEjbCli.java:25)
    [java] Java Result: 1

    ejbca:batchsuperadmin:
    [echo] batch superadmin
    [java] Could not run execute method for class null
    [java] java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:ejbca, moduleName:ejbca-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@6acbc422
    [java] at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
    [java] at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
    [java] at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
    [java] at com.sun.proxy.$Proxy0.getCachedConfiguration(Unknown Source)
    [java] at org.ejbca.ui.cli.BaseCommand.parseUsernameAndPasswordFromArgs(BaseCommand.java:123)
    [java] at org.ejbca.ui.cli.batch.BatchMakeP12.execute(BatchMakeP12.java:91)
    [java] at org.ejbca.ui.cli.CliCommandHelper.executeCommand(CliCommandHelper.java:147)
    [java] at org.ejbca.ui.cli.CliCommandHelper.searchAndRun(CliCommandHelper.java:67)
    [java] at org.ejbca.ui.cli.EjbcaEjbCli.main(EjbcaEjbCli.java:25)
    [java] Java Result: 1

    BUILD FAILED
    /opt/ejbca_ce_6_0_3/build.xml:60: The following error occurred while executing this line:
    /opt/ejbca_ce_6_0_3/build.xml:66: The following error occurred while executing this line:
    /opt/ejbca_ce_6_0_3/bin/cli.xml:96: The following error occurred while executing this line:
    /opt/ejbca_ce_6_0_3/bin/cli.xml:137: Batch generation failed!

     
  • Tomas Gustavsson

    If it says it can not find EJBCA on the server it means that you "ant deploy" did not go well. It may have returned without error on the client side, but if you check the server side there is probably some error. Perhaps you have misconfigured the database so there are no priviliges for example. This will show up in JBoss server.log (see troubleshoooting section of EJBCA docs).

    Cheers,
    Tomas


    PrimeKey Solutions offers commercial EJBCA and SignServer support subscriptions and training courses. Please see www.primekey.se or contact info@primekey.se for more information.
    http://www.primekey.se/Services/Support/
    http://www.primekey.se/Services/Training/

     
  • Jason Separovic

    Jason Separovic - 2014-03-04

    It does seem to create the schema in the db no worries. However, I am getting the following error during ant deploy:

    03-Mar-2014 17:29:35,239 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
    03-Mar-2014 17:29:35,240 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final "Steropes" started in 2329ms - Started 176 of 334 services (156 services are passive or on-demand)
    03-Mar-2014 17:29:53,428 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("composite") failed - address: ([]): java.lang.IllegalArgumentException
    at org.jboss.dmr.ModelValue.asList(ModelValue.java:128) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
    at org.jboss.dmr.ModelNode.asList(ModelNode.java:1205) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
    at org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:58) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:473) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:126) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:286) [jboss-as-protocol-7.1.2.Final.jar:7.1.2.Final]
    at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:491) [jboss-as-protocol-7.1.2.Final.jar:7.1.2.Final]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
    at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
    at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]

     
  • Tomas Gustavsson

    I have no ideas what that means. Are you sure there is no errors previous in the log? Most often the last part is not understandable, but earlier errors are.

    We will soon add a VM with EJBCA installed, to download for easy testing.

     
  • Jason Separovic

    Jason Separovic - 2014-03-04

    It was an issue with the Datasource name, I didn't look too closely at this because it was creating the tables with no issue.
    Anyway, all better and deploy/installed successfully. Thanks for your help.

     
  • uxbod

    uxbod - 2014-03-08

    Am having exactly the same problem with using MariaDB so would welcome where you changed the Datasource name please ??

     
    • Jason Separovic

      Jason Separovic - 2014-03-15

      I just applied the datasource config for Mariadb from the install guide. I had a naming difference I believe.

      One thing I have noticed is that the "ant install" will not work if you bind jboss to a specific IP address. I had to remove the "-b" from the standalone.sh command to get this to work.

       
      Last edit: Jason Separovic 2014-03-15
      • Tomas Gustavsson

        ant deploy uses the jboss-cli to configure things in JBoss. So I assume that means that jboss-cli does not wor if you bind to your specific address?

         
        • Jason Separovic

          Jason Separovic - 2014-03-16

          ant deploy works ok. It's ant install that fails. It also does not look like it's connecting to the server at all when looking at the server logs.

           
          • Tomas Gustavsson

            That means that remote ejb does not work.

             
  • ERenner

    ERenner - 2014-03-12

    we have the same problem when executing ant install i get:

    ejbca:init:
    [echo]
    [echo] ------------------- CA Properties ----------------
    [echo] ca.name : ManagementCA
    [echo] ca.dn : CN=ManagementCA,O=EJBCA Sample,C=SE
    [echo] ca.tokentype : soft
    [echo] ca.keytype : RSA
    [echo] ca.keyspec : 2048
    [echo] ca.signaturealgorithm : SHA1WithRSA
    [echo] ca.validity : 3650
    [echo] ca.policy : 2.5.29.32.0
    [echo] ca.tokenproperties :
    [echo] httpsserver.hostname : PKI
    [echo] httpsserver.dn : CN=PKI,O=EJBCA Sample,C=SE
    [echo] superadmin.cn : SuperAdmin
    [echo] superadmin.dn : CN=SuperAdmin
    [echo] superadmin.batch : true
    [echo] appserver.home : /usr/share/jbossas
    [echo]

    ejbca:install:

    ejbca:initCA:
    [echo] Initializing CA with 'ManagementCA' 'CN=ManagementCA,O=EJBCA Sample,C=SE' 'soft' <ca.tokenpassword hidden=""> '2048' 'RSA' '3650' '2.5.29.32.0' 'SHA1WithRSA' -superadmincn 'SuperAdmin'...
    [java] Could not run execute method for class ca
    [java] java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:ejbca, moduleName:ejbca-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@7c3b6645
    [java] at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:729)
    [java] at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
    [java] at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)
    [java] at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)
    [java] at com.sun.proxy.$Proxy0.getCachedConfiguration(Unknown Source)
    [java] at org.ejbca.ui.cli.BaseCommand.parseUsernameAndPasswordFromArgs(BaseCommand.java:126)
    [java] at org.ejbca.ui.cli.ca.CaInitCommand.execute(CaInitCommand.java:131)
    [java] at org.ejbca.ui.cli.CliCommandHelper.executeCommand(CliCommandHelper.java:147)
    [java] at org.ejbca.ui.cli.CliCommandHelper.searchAndRun(CliCommandHelper.java:105)
    [java] at org.ejbca.ui.cli.EjbcaEjbCli.main(EjbcaEjbCli.java:25)
    [java] Java Result: 1

    the EAP6.2 log does not show any ERROR messages, we also enabled DEBUG logging for all components without any suspicious output.

    also ant deploy verbose log does not show any errors, the ant deploy build output was executed successfully.

    the database is also accessible, at startup time of our EAP6.2 the database i checked for correct schema/table structure.

    please help.

     
  • Andreas Kuehne

    Andreas Kuehne - 2014-03-12

    Hi, we are working on puppet-ifying the ejbca setup, in other word setting up a complete ejbca VM from scratch automatically. We are currently working with the ejbca 6 / jboss 7.1.1 pair.

    We detect problems when starting 'install' directly after 'deploy'. The app server seems to need some time after 'deploy' before it's ready for the 'install'. Afaics the app server is busy with an internal restart. Calls from a subsequent 'install' fail and show strange problems later on. Even this threads 'No EJB receiver available ...' was seen ...

    Another finding: The 'install' configures SSL ports and the jboss logs show successful outcomes of this step. Surprisingly the port aren't available instantly, a restart of the server is necessary !?!

    Maybe some of the mentioned problems may be caused by by an early 'install'. Would it make sense to add a 'wait for restart' at the end of both ant tasks?

    Greetings,

    Andreas

     
  • Tomas Gustavsson

    Basically the jboss-cli is not suitable for scripting. So using that in a puppet install depending on various timeouts etc will give you a headache. I don't think we will be able to support extending current script with such timeouts. We are working on improving the overall ant scripts step by step, working around jboss-cli issues.

    In our puppet scripts we break down the installation into a more scripted installation usign a pre-configured, or sed-edited standalone.xml, so we don't have to rely on jboss-cli. It is simply not stable enough, and does not have and decent "status" commands.
    Especially if you need to support different JBoss versions, as they have new synchronous reload commands in JBoss EAP, not available in JBoss 7.1.1.

    Cheers,
    Tomas

     
  • Tomas Gustavsson

    You can of course try to add "wait for restart", but I'm not sure it will solve your second problem at least.

     
  • Frazze

    Frazze - 2014-04-05

    I seem to have the same problem as Jason had, first some Informations on my setup:

    I am running this on a KVM VM having 1 cpu and 2 cores and 4GB of RAM on Debian 7.4.

    ejbca@mail:/usr/local/jboss/standalone/log$ java -version
    java version "1.7.0_25"
    OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1~deb7u1)
    OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

    Using jboss 7.1.1.Final

    Apache Ant 1.9.3

    Ejbca 6.0.4

    mysql-connector-java-5.1.29 and the following module.xml like in the EJBCA install howto:
    "
    ejbca@mail:/usr/local/jboss/modules/com/mysql/main$ cat module.xml
    ...
    resource-root path="mysql-connector-java-5.1.29-bin.jar"/>
    ....
    "

    MySql server version: 5.5.35-0+wheezy1

    I started jboss via ./standalone.sh

    mysql driver installed in jboss via ./jboss-cli.sh
    with
    /subsystem=datasources/jdbc-driver=com.mysql.jdbc.Driver:add(driver-name=com.mysql.jdbc.Driver,driver-module-name=com.mysql,driver-xa-datasource-class-name=com.mysql.jdbc.jdbc.jdbc2.optional.MysqlXADataSource)
    :reload
    -> reported success

    ant deploy gives me "BUILD SUCCESSFULL"

    in the server.log I can find the following error:

    "19:02:55,384 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018558: Undeployed "ejbca.ear"
    19:02:58,819 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("composite") failed - address: ([]): java.lang.IllegalArgumentException
    at org.jboss.dmr.ModelValue.asList(ModelValue.java:128) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
    at org.jboss.dmr.ModelNode.asList(ModelNode.java:1205) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
    at org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:58) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
    at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:487) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
    at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
    at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]

    19:03:01,687 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011942: Stopping OSGi Framework
    "

    Then when I try "ant install" I get the following errors:

    "

    ejbca:adminweb:
    [java] Using certificate profile: SERVER, with id: 9
    [java] Could not find CA 'ejbca01' in database.
    [java] Setting clear text password for user tomcat
    [java] End entity with username 'tomcat' does not exist.
    [echo] batch tomcat
    [java] Generating keys in directory /home/ejbca/ejbca_ce_6_0_4/p12.
    [java] Unknown user, or clear text password is null: tomcat.
    [java] Could not find CA 'ejbca01' in database.
    [java] Setting clear text password for user superadmin
    [java] End entity with username 'superadmin' does not exist.

    ejbca:batchsuperadmin:
    [echo] batch superadmin
    [java] Generating keys in directory /home/ejbca/ejbca_ce_6_0_4/p12.
    [java] Unknown user, or clear text password is null: superadmin.

    BUILD FAILED
    /home/ejbca/ejbca_ce_6_0_4/build.xml:60: The following error occurred while executing this line:
    /home/ejbca/ejbca_ce_6_0_4/build.xml:66: The following error occurred while executing this line:
    /home/ejbca/ejbca_ce_6_0_4/bin/cli.xml:96: The following error occurred while executing this line:
    /home/ejbca/ejbca_ce_6_0_4/bin/cli.xml:137: Batch generation failed!

    Total time: 57 seconds
    ejbca@mail:/usr/local/ejbca$

    "

    Any help on this would be great!

    The Database tables are getting created on the MySql server, so connection seems to work.

    I don't know any further so some help I need :\

     
    Last edit: Frazze 2014-04-05
  • Tomas Gustavsson

    If you want to try out without having installation problems, you can use the pre-installed virtual machine available at ejbca.org. You can always compare your standalone.xml with the succesful one on that image.

    Cheers,
    Tomas


    PrimeKey Solutions offers commercial EJBCA and SignServer support subscriptions and training courses. Please see www.primekey.se or contact info@primekey.se for more information.
    http://www.primekey.se/Services/Support/
    http://www.primekey.se/Services/Training/

     
  • Frazze

    Frazze - 2014-04-06

    Well, yes I know, but I want to know what and how the whole system works, therefore the VM is no option.

    Thanks for the tip about the standalone.xml, I'll compare them.

    But if you look into a few recent threads here you can see that I am not the only one having exactly this same problem.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks