|
From: Blum, J. <jon...@or...> - 2016-09-16 08:00:15
|
Hello all --
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*
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*
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:
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
|