Menu
▾
▴
Re: [SignServer-develop] Wildfly 10 initial setup problem
|
From: Blum, J. <jon...@or...> - 2016-09-16 12:36:26
|
Hello Markus -- thanks for your guidance here! > Just as you explore below the "No EJB recevier available for ..." > typically means that either SignServer/JBoss hasn't started up > completely or that the wrong connection configuration is used from the CLI. > What you want to look for is that you get the EVENT: SIGNSERVER_STARTUP > and not any error following it. Okay -- I can confirm that Wildlfly and SignServer are starting up successfully. From the end of server.log: 2016-09-16 01:18:48,894 INFO [org.signserver.server.log.SignServerLog4jDevice] (ServerService Thread Pool -- 67) EVENT: SIGNSERVER_STARTUP; MODULE: SERVICE; ADMINISTRATOR: StartServicesServlet.init; ISSUER: null; SERIAL_NUMBER: null; WORKER_ID: null; msg: start services startup msg; VERSION: SignServer CE 3.7.0; REPLY_TIME:1474013928894 So if the server's running, and the pages are accessible on localhost:8080, it's got to be something wrong on the client side, right? A couple of questions to help me hunt this down -- * Are there any other properties files which could affect the client EJB connections, besides conf/jboss7/jboss-ejb-client.properties? If I've mis-set something in the build process, could it be including an incorrect .properties file at build time? * Is there any way I can check specifically whether *EJB* connections are accessible over port 8080? I can confirm the JSP pages are showing properly over localhost:8080; but could the beans still be being blocked? (I did confirm that the beans are mapped to java:jboss/exported above, so they should be visible... right?) Thanks, Jon Blum On Fri, Sep 16, 2016 at 9:17 PM, Markus Kilås <ma...@pr...> wrote: > On 2016-09-16 09:42, Blum, Jon wrote: > > Hello all -- > > Hello Jon, > > > > > I'm doing an initial build and setup of SignServer from source, with the > > latest community version, as detailed on the Getting Started webpage. I > > know that this version predates Wildfly 10, but recent messages seem to > > indicate that it can at least basically function. > > > > The deployment appears to have been successful, everything is loading > > correctly in the Wildfly system log on startup and the sample JSP pages > > are displaying correctly... but the SignServer CLI at /bin/signserver > > won't run. > > > > The initial exception appears to be: > > Caused by: java.lang.IllegalStateException: EJBCLIENT000025: *No EJB > > receiver available for handling [appName:signserver, > > moduleName:SignServer-ejb, distinctName:] combination* for invocation > > context org.jboss.ejb.client.EJBClientInvocationContext@4493d195 > > > > It occurs at while getting the initial global configuration: > > at com.sun.proxy.$Proxy0.getGlobalConfiguration(Unknown Source) > > at > > org.signserver.admin.cli.defaultimpl.GetStatusCommand. > execute(GetStatusCommand.java:72) > > > > The JBoss JNDI name it's trying to retrieve is: > > *ejb:signserver/SignServer-ejb//GlobalConfigurationSessionBean > !org.signserver.ejb.interfaces.IGlobalConfigurationSession$IRemote > > * > > Just as you explore below the "No EJB recevier available for ..." > typically means that either SignServer/JBoss hasn't started up > completely or that the wrong connection configuration is used from the CLI. > > > According to the JBOSS server logfile, this bean has been successfully > > created and exported (under jboss/exported) on startup: > > > > 2016-09-15 01:07:12,446 INFO [org.jboss.as.ejb3.deployment] (MSC > > service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named > > 'GlobalConfigurationSessionBean' in deployment unit 'subdeployment > > "SignServer-ejb.jar" of deployment "signserver.ear"' are as follows: > > > > > > java:global/signserver/SignServer-ejb/GlobalConfigurationSessionBean > !org.signserver.ejb.interfaces.IGlobalConfigurationSession$ILocal > > > > java:app/SignServer-ejb/GlobalConfigurationSessionBean > !org.signserver.ejb.interfaces.IGlobalConfigurationSession$ILocal > > > > java:module/GlobalConfigurationSessionBean!org.signserver.ejb. > interfaces.IGlobalConfigurationSession$ILocal > > > > java:global/signserver/SignServer-ejb/GlobalConfigurationSessionBean > !org.signserver.ejb.interfaces.IGlobalConfigurationSession$IRemote > > > > java:app/SignServer-ejb/GlobalConfigurationSessionBean > !org.signserver.ejb.interfaces.IGlobalConfigurationSession$IRemote > > > > java:module/GlobalConfigurationSessionBean!org.signserver.ejb. > interfaces.IGlobalConfigurationSession$IRemote > > * > > java:jboss/exported/signserver/SignServer-ejb/ > GlobalConfigurationSessionBean!org.signserver.ejb.interfaces. > IGlobalConfigurationSession$IRemote > > * > > That is good but it could happen that it gets undeployed later due to > some startup failure or that JBoss gets stuck at some point due to a > configuration issue. > > What you want to look for is that you get the EVENT: SIGNSERVER_STARTUP > and not any error following it. > > > > > So it looks like a connection problem. My APPSRV_HOME is set correctly > > to /opt/wildfly. I've successfully changed the connection port to 8080, > > as mentioned in a previous email on this list; here's my > > conf/jboss7/jboss-ejb-client.properties file: > > > > remote.connectionprovider.create.options.org.xnio. > Options.SSL_ENABLED=false > > remote.connections=default > > remote.connection.default.host=localhost > > #remote.connection.default.port = 4447 > > remote.connection.default.port = 8080 > > remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_ > NOANONYMOUS=false > > > > And yes, it should be hitting that properties file -- here's the > > classpath when I try to invoke /bin/signserver: > > > > -cp*/opt/signserver/conf/jboss7*:/opt/wildfly/bin/ > client/jboss-client.jar:/opt/signserver/conf:/opt/ > signserver/lib/SignServer-AdminCLI.jar:/opt/signserver/ > res/cesecore:/opt/signserver/lib/ext/clover-dir/lib/clover.jar: > > Assuming SignServer and JBoss starts up correctly all the way then yes, > the second thing to look for is to see that correct port is used just as > you are doing. I'm not really seeing any problem here though. > > > > > > > So the question becomes... what else could I be missing? It's either a > > Wildfly configuration issue or a client-side one; where else should I > look? > > > > Cheers, > > Jon BLum > > > > Regards, > Markus Kilås > PrimeKey Solutions AB > > Save time and money with an Enterprise support subscription. Please see > www.primekey.se for more information. > https://www.primekey.se/technologies/products-overview/ > https://www.primekey.se/service-support/support/ > > |
