After installing Restcomm/jss7-8.0.112 on wildfly slee build from release 7.2.0-150 the TCAP Resource adapter fails to deploy with message:
2018-10-03 11:39:31,800 ERROR [javax.slee.RAEntityNotification[entity=TCAPRA].TCAPResourceAdaptor] (MSC service thread 1-5) Failed to activate TCAP RA : javax.naming.NameNotFoundException: restcomm/ss7/tcap -- service jboss.naming.context.java.restcomm.ss7.tcap
<------>at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
<------>at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
<------>at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
<------>at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
<------>at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
<------>at javax.naming.InitialContext.lookup(InitialContext.java:417)
<------>at javax.naming.InitialContext.lookup(InitialContext.java:417)
Seems to me that no TCAP stack is bound to JNDI may be because it is read-only. However from my application deployed as a WAR file I can bind successfully objects to JNDI.
Any suggestions?
After installing Restcomm/jss7-8.0.112 on wildfly slee build from release 7.2.0-150 the TCAP Resource adapter fails to deploy with message:
Seems to me that no TCAP stack is bound to JNDI may be because it is read-only. However from my application deployed as a WAR file I can bind successfully objects to JNDI. Any suggestions?