Exception on startup when configured to use domain security

[Patrick Nodder]

Hello,

I am using Wildfly 11 and have configured the generic JMS RA with Tibco EMS 8.3. I am using security-domain-and-application for the RA's security. The security domain is configured in the legacy security subsystem like so:

                <security-domain name="TibcoEmsRealm" cache-type="default">

                    <authentication>

                        <login-module code="ConfiguredIdentity" flag="required">

                            <module-option name="principal" value="xxxx"/>

                            <module-option name="userName" value="xxxx"/>

                            <module-option name="password" value="xxxx"/>

                        </login-module>

                    </authentication>

                </security-domain>

And the RA like so:

                <resource-adapter id="generic-jms-ra">

                    <module slot="main" id="org.jboss.genericjms"/>

                    <transaction-support>LocalTransaction</transaction-support>

                    <connection-definitions>

                        <connection-definition class-name="org.jboss.resource.adapter.jms.JmsManagedConnectionFactory" jndi-name="java:/jms/TibcoEmsLocalTxFactory" enabled="true" use-java-context="true" pool-name="GenericJmsXA" use-ccm="true">

                            <config-property name="ConnectionFactory">

                                QueueConnectionFactory

                            </config-property>

                            <config-property name="SessionDefaultType">

                                javax.jms.Queue

                            </config-property>

                            <config-property name="JndiParameters">

                                java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory;java.naming.provider.url=tcp:/xxxxx

                            </config-property>

                            <pool>

                                <min-pool-size>0</min-pool-size>

                                <max-pool-size>20</max-pool-size>

                                <prefill>false</prefill>

                                <use-strict-min>false</use-strict-min>

                                <flush-strategy>FailingConnectionOnly</flush-strategy>

                            </pool>

                            <security>

                                <security-domain-and-application>TibcoEmsRealm</security-domain-and-application>

                            </security>

                        </connection-definition>

                    </connection-definitions>

                </resource-adapter>

However, sometimes when I start Wildfly I immediately get the following error (it doesn't happen on every startup):

14:17:27,265 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": WFLYJCA0046: Failed to start RA deployment [generic-jms-ra]

at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$2.run(AbstractResourceAdapterDeploymentService.java:332)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

at org.jboss.threads.JBossThread.run(JBossThread.java:320)

Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/C:/Users/PNodder/dev/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2064)

at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$WildFlyRaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:173)

at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:116)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.IllegalStateException

at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)

at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractWildFlyRaDeployer.getSubjectFactory(AbstractResourceAdapterDeploymentService.java:635)

at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1666)

... 7 more

I'm thinking it may be related to the TibcoEmsRealm security config (the reference to getSubjectFactory()). Does anyone have any ideas how to resolve this? Is this RA security configuration correct (i.e. using a domain in the legacy security)?

Environment:

Wildfly-11.0.0.Final

Java 8

Windows 10 and linux

IntellijJ IDEA

Using the genericjms that is included in Wildfly i.e. at wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

Any help would be much appreciated.

Patrick

[Justin Bertram]

I'm not sure how much help you'll find here.  I think your questions really should be directed at the Wildfly community since they are specifically about Wildfly configuration and code. None of the code from the stack-trace is from the generic JMS JCA RA; it's all Wildfly code.  The content of the stack-trace and the fact that it's intermittent indicates to me that there might be a bug in Wildfly.  Have you tried on Wildfly 12?

[Patrick Nodder]

No I haven't tried on Wildfly 12, I have to use 11 as that's what my company has chosen. I'll post this on the Wildfly forum. It's just strange that it's an intermittent error, but as you say it could be a bug in Wildfly. Anyway, thanks for the quick response.

[Justin Bertram]

Point taken about your company choosing Wildfly 11.  However, I'd still recommend that you test using 12 for a couple of reasons:

• If it's not a problem in 12 that would likely validate your configuration and confirm it's a bug.  If it is a bug perhaps the Wildfly community could point you to the commit where it was fixed which you could backport to your own branch of 11 (since there's not likely to be any more releases for 11.x).
  
• The Wildfly community will almost certainly ask you to test on 12 since it's the latest release.