What happened:
TcapSS7Service bean declared in standalone.xml does not get bound to the wildfly 10.1's JNDI.
As a result no SS7 resource adapters can be deployed because they look in the JNDI and find nothing.
What you expected to happen:
I expect the bean to be bound properly.
How to reproduce it (as minimally and precisely as possible):
Deploy restcomm JSS7 on wildfly 10.1 slee (built from 7.2.0-150 release).
Deploy the tcap resource adapter (from slee 7.2.0-150)
See the error message in server log saying
javax.naming.NameNotFoundException: restcomm/ss7/tcap
Anything else we need to know?:
Actually in the org.mobicents.ss7.service.SS7ExtensionService class line 1167 is commented out. And there the JNDI name gets set. After uncommenting and recompiling there is an error in server starting log saying: WFLYNAM0043: Naming context is read-only
So how can I proceed further?
Environment:
Restcomm JSS7 version (from startup logs): 8.0.112
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release): ubuntu 18.04
Kernel (e.g. uname -a): Linux gwork 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Deployment method (e.g. application server version + config + method):
/kind bug
What happened:
TcapSS7Servicebean declared instandalone.xmldoes not get bound to the wildfly 10.1's JNDI. As a result no SS7 resource adapters can be deployed because they look in the JNDI and find nothing.What you expected to happen: I expect the bean to be bound properly. How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: Actually in the
org.mobicents.ss7.service.SS7ExtensionServiceclass line 1167 is commented out. And there the JNDI name gets set. After uncommenting and recompiling there is an error in server starting log saying:WFLYNAM0043: Naming context is read-onlySo how can I proceed further?
Environment:
uname -a): Linux gwork 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux