Restcomm Diameter Mux deployment problem

[david luong]

Hi,

I'm working on setting up a working RestComm Charging Server but before I can do that, I need to to deploy the Restcomm Diameter Mux. I'm not sure what is wrong but I followed the instructions that was included in restcomm-diameter-mux-1.7.0 snapshot.

I built SAR using maven and put the SAR in the /standalone/deployments folder of my JBOSS AS and during the deployment process, I get the following errors:

17:25:47,171 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "restcomm-management.war" (runtime-name: "restcomm-management.war")
17:25:47,179 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /home/dluong/restcomm/Restcomm-JBoss-AS7-8.0.0.1114/standalone/deployments
17:25:47,179 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jolokia.war" (runtime-name: "jolokia.war")
17:25:47,180 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "restcomm-diameter-mux-sar-jboss-7-1.7.0-SNAPSHOT.sar" (runtime-name: "restcomm-diameter-mux-sar-jboss-7-1.7.0-SNAPSHOT.sar")
17:25:47,181 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "restcomm.war" (runtime-name: "restcomm.war")
17:25:47,182 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "restcomm-rvd.war" (runtime-name: "restcomm-rvd.war")
17:25:47,183 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "sip-servlets-management.war" (runtime-name: "sip-servlets-management.war")
17:25:47,184 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "olympus.war" (runtime-name: "olympus.war")
17:25:47,185 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RvdExternalServicesDemo.war" (runtime-name: "RvdExternalServicesDemo.war")
17:25:47,855 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."restcomm-diameter-mux-sar-jboss-7-1.7.0-SNAPSHOT.sar".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."restcomm-diameter-mux-sar-jboss-7-1.7.0-SNAPSHOT.sar".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "restcomm-diameter-mux-sar-jboss-7-1.7.0-SNAPSHOT.sar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_131]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_131]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018748: Error loading jboss-deployment-structure.xml from /home/dluong/restcomm/Restcomm-JBoss-AS7-8.0.0.1114/standalone/tmp/vfs/temp9cba655e0dd20f6e/restcomm-diameter-mux-sar-jboss-7-1.7.0-SNAPSHOT.sar-b7a6c4732a9f717e/contents/META-INF/jboss-deployment-structure.xml
at org.jboss.as.server.deployment.module.descriptor.DeploymentStructureDescriptorParser.parse(DeploymentStructureDescriptorParser.java:322) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.as.server.deployment.module.descriptor.DeploymentStructureDescriptorParser.parse(DeploymentStructureDescriptorParser.java:294) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.as.server.deployment.module.descriptor.DeploymentStructureDescriptorParser.deploy(DeploymentStructureDescriptorParser.java:158) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
... 5 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag().
at [row,col {unknown-source}]: [3,6]
at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:606)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:479)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:464)
at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1137)
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.nextTag(XMLExtendedStreamReaderImpl.java:152)
at org.jboss.as.server.deployment.module.descriptor.JBossDeploymentStructureParser11.readElement(JBossDeploymentStructureParser11.java:215) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.as.server.deployment.module.descriptor.JBossDeploymentStructureParser11.readElement(JBossDeploymentStructureParser11.java:68) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
at org.jboss.as.server.deployment.module.descriptor.DeploymentStructureDescriptorParser.parse(DeploymentStructureDescriptorParser.java:316) [jboss-as-server-7.2.0.Final.jar:7.2.0.Final]
... 8 more

I'm not familiar enough with this environment to understand what that means. But it seems that when the SAR is extracted, it didn't end up in tmp/vfs/temp9cba655e0dd20f6e/restcomm-diameter-mux-sar-jboss-7-1.7.0-SNAPSHOT.sar-b7a6c4732a9f717e/? I'd like some help troubleshooting this.

Regards.
David.

[david luong]

I've been able to get past the problem I mentioned earlier by moving to Restcomm JAIN SLEE 7.0.0.

Now I'm moving on to deploying the Charging Server but got the following errors:

...

15:27:07,585 WARN [org.mobicents.slee.container.deployment.jboss.DeploymentManager] (SLEE-InternalDeployer-thread-1) Unable to INSTALL diameter-restcomm-slee-ra-diameter-ro-ra-DU-7.0.11.jar right now. Waiting for dependencies to be resolved.
15:27:07,675 INFO [org.mobicents.slee.container.deployment.jboss.DeployableUnit] (SLEE-InternalDeployer-thread-1) Missing dependencies for charging-server-DU-1.0.0.3.jar:
+-- JDBCRA
+-- EventTypeID[name=javax.slee.facilities.TimerEvent,vendor=javax.slee,version=1.0]
+-- ResourceAdaptorTypeID[name=Diameter Ro,vendor=java.net,version=0.8.1]
+-- EventTypeID[name=net.java.slee.resource.diameter.ro.events.RoCreditControlRequest,vendor=java.net,version=0.8]
+-- EventTypeID[name=javax.slee.serviceactivity.ServiceStartedEvent,vendor=javax.slee,version=1.1]
+-- DiameterRo
+-- ProfileSpecificationID[name=AddressProfileSpec,vendor=javax.slee,version=1.1]
+-- EventTypeID[name=JdbcTaskExecutionThrowableEvent,vendor=org.mobicents,version=1.0]
+-- EventTypeID[name=SimpleJdbcTaskResultEvent,vendor=org.mobicents,version=1.0]
+-- ResourceAdaptorTypeID[name=JDBCResourceAdaptorType,vendor=org.mobicents,version=1.0]
+-- EventTypeID[name=javax.slee.serviceactivity.ServiceStartedEvent,vendor=javax.slee,version=1.0]
+-- HttpClientResourceAdaptor
+-- ResourceAdaptorTypeID[name=HttpClientResourceAdaptorType,vendor=org.mobicents,version=4.0]

...

15:27:12,409 WARN [org.mobicents.slee.container.deployment.jboss.SleeContainerDeployerImpl] (SLEE-InternalDeployer-thread-1) SLEE DUs not deployed, due to missing dependencies:
file:/home/dluong/restcomm/restcomm-slee-7.0.63.64-wildfly-10.1.0.Final/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempecd9e5b0bd81dc36/content-abb52babc6fe264d/content/
Missing Dependencies:
EventTypeID[name=javax.slee.facilities.TimerEvent,vendor=javax.slee,version=1.0]
EventTypeID[name=javax.slee.serviceactivity.ServiceStartedEvent,vendor=javax.slee,version=1.1]
ProfileSpecificationID[name=AddressProfileSpec,vendor=javax.slee,version=1.1]
EventTypeID[name=JdbcTaskExecutionThrowableEvent,vendor=org.mobicents,version=1.0]
EventTypeID[name=SimpleJdbcTaskResultEvent,vendor=org.mobicents,version=1.0]
ResourceAdaptorTypeID[name=JDBCResourceAdaptorType,vendor=org.mobicents,version=1.0]
EventTypeID[name=javax.slee.serviceactivity.ServiceStartedEvent,vendor=javax.slee,version=1.0]
ResourceAdaptorTypeID[name=HttpClientResourceAdaptorType,vendor=org.mobicents,version=4.0]

Any ideas how to solve this?

Regards.
David.

[Alexandre Mendonça]

Hi David,

Glad you have been able to fix the initial problem you were having. Seems you were deploying the AS7 mux on AS5. Make sure to use the correct ones.

Regarding the one you are currently facing, you seem to be missing some dependencies... you will need to deploy the Resource Adaptors for Diameter Base, Diameter Ro, HTTP Client and JDBC.. that should solve some of the dependencies, but I see others that should not be missing as they are part of the JAIN SLEE core (TimerEvent, ServiceStartedEvent and AddressProfileSpec). Please add the missing RAs and let us know if that works out.. if not, have you built or downloaded JAIN SLEE binary ?

Regards,

Alexandre Mendonça
http://ammendonca.blogspot.com/

Regards.
David.

--
You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-public+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[david luong]

Hi Alexandre,

I did resolve some of the dependency problems but still some remained.

17:29:54,189 WARN [org.mobicents.slee.container.deployment.jboss.SleeContainerDeployerImpl] (SLEE-InternalDeployer-thread-1) SLEE DUs not deployed, due to missing dependencies:
file:/home/dluong/restcomm/restcomm-slee-7.0.63.64-wildfly-10.1.0.Final/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempe8d75e9e4fbf0651/content-f7540de379ffa911/content/

Missing Dependencies:
EventTypeID[name=javax.slee.facilities.TimerEvent,vendor=javax.slee,version=1.0]
EventTypeID[name=javax.slee.serviceactivity.ServiceStartedEvent,vendor=javax.slee,version=1.1]
ProfileSpecificationID[name=AddressProfileSpec,vendor=javax.slee,version=1.1]
EventTypeID[name=JdbcTaskExecutionThrowableEvent,vendor=org.mobicents,version=1.0]
EventTypeID[name=SimpleJdbcTaskResultEvent,vendor=org.mobicents,version=1.0]
ResourceAdaptorTypeID[name=JDBCResourceAdaptorType,vendor=org.mobicents,version=1.0]
EventTypeID[name=javax.slee.serviceactivity.ServiceStartedEvent,vendor=javax.slee,version=1.0]
ResourceAdaptorTypeID[name=HttpClientResourceAdaptorType,vendor=org.mobicents,version=4.0]

As you mentioned, these should already be there in the JAIN SLEE binary. I used the release from https://github.com/RestComm/jain-slee/releases/tag/7.0.63.64

Regards,
David.

[david luong]

Hi.

I noticed that all the EventTypeID and ResourceAdaptorTypeID in the list of missing dependencies are mentioned in the Charging Server sbb-jar.xml. https://github.com/RestComm/charging-server/blob/master/sbb/src/main/resources/META-INF/sbb-jar.xml

This might be a dumb question but is this SBB compatible with or tested with JAIN SLEE 7?

Is there a way to verify whether the dependencies are present in the system? What else might be using them that I can check?

Pressing on...
David.

[Vilius Panevėžys]

On Wed, 19 Apr 2017 18:54:17 -0700 (PDT)
david luong <davidc...@gmail.com> wrote:

> Is there a way to verify whether the dependencies are present in the
> system?

There should be corresponding log entries as the components are being
deployed. Attach the complete server log from startup - it's a lot
easier to spot any possible problems seeing the complete picture.


--
Vilius Panevėžys
Elitnet

[david luong]

I'm providing the complete server log in attachment.

Regards,

David.

--
You received this message because you are subscribed to a topic in the Google Groups "mobicents-public" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mobicents-public/FguHlVrzcRw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mobicents-public+unsubscribe@googlegroups.com.

[david luong]

I'm still trying to get the Charging Server up and running. I tried deploying the following JARs one at a time to see where things are going wrong.

1. charging-server-sbb-1.0.0.3.jar (no errors)
2. charging-server-DU-1.0.0.3.jar (errors)

I did a bit more analysis of the log and noticed something I'm not sure is a problem but it seems odd to me. Please check my findings.

What I noticed was some of the missing dependencies have vendor=org.mobicents but they were installed earlier with vendor=org.restcomm ( which are highlighted in bold).

2017-04-21 11:37:38,705 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installing DeployableUnitID[url=file:/home/dluong/restcomm/restcomm-slee-7.0.63.64-wildfly-10.1.0.Final/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempbe398a3feee7b99b/content-d31f9ba97b1ee496/content/]
2017-04-21 11:37:38,729 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed LibraryID[name=jdbc-ra-library,vendor=org.restcomm.resources,version=1.0]
2017-04-21 11:37:38,729 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed EventTypeID[name=JdbcTaskExecutionThrowableEvent,vendor=org.restcomm,version=1.0]
2017-04-21 11:37:38,729 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed EventTypeID[name=SimpleJdbcTaskResultEvent,vendor=org.restcomm,version=1.0]
2017-04-21 11:37:38,732 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed ResourceAdaptorTypeID[name=JDBCResourceAdaptorType,vendor=org.restcomm,version=1.0]
2017-04-21 11:37:38,733 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed ResourceAdaptorID[name=JdbcResourceAdaptor,vendor=org.restcomm,version=1.0]
2017-04-21 11:37:38,733 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed DeployableUnitID[url=file:/home/dluong/restcomm/restcomm-slee-7.0.63.64-wildfly-10.1.0.Final/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempbe398a3feee7b99b/content-d31f9ba97b1ee496/content/]
2017-04-21 11:37:38,989 INFO  [org.mobicents.slee.container.management.ResourceManagement] (SLEE-InternalDeployer-thread-1) Created Resource Adaptor Entity JDBCRA for ResourceAdaptorID[name=JdbcResourceAdaptor,vendor=org.restcomm,version=1.0] Config Properties: [(RA_SBB_INTERFACE_CONNECTION_GETTERS_ON:java.lang.Boolean=true),(DATASOURCE_JNDI_NAME:java.lang.String=java:jboss/datasources/ExampleDS),(EXECUTOR_SERVICE_THREADS:java.lang.Integer=4)]
2017-04-21 11:37:39,239 INFO  [org.mobicents.slee.container.management.ResourceManagement] (SLEE-InternalDeployer-thread-1) Activated RA Entity JDBCRA
2017-04-21 11:37:39,489 INFO  [org.mobicents.slee.container.management.ResourceManagement] (SLEE-InternalDeployer-thread-1) Bound link between RA Entity JDBCRA and Name JDBCRA
2017-04-21 11:37:39,779 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installing DeployableUnitID[url=file:/home/dluong/restcomm/restcomm-slee-7.0.63.64-wildfly-10.1.0.Final/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempbe398a3feee7b99b/content-a6a0154497901df7/content/]
2017-04-21 11:37:39,842 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed LibraryID[name=httpcomponent-client,vendor=httpcomponent-client,version=4.0]
2017-04-21 11:37:39,842 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed EventTypeID[name=net.java.client.slee.resource.http.event.ResponseEvent,vendor=net.java.client.slee,version=4.0]
2017-04-21 11:37:39,845 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed ResourceAdaptorTypeID[name=HttpClientResourceAdaptorType,vendor=org.restcomm,version=4.0]
2017-04-21 11:37:39,845 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed ResourceAdaptorID[name=HttpClientResourceAdaptor,vendor=org.restcomm,version=4.0]
2017-04-21 11:37:39,845 INFO  [org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl] (SLEE-InternalDeployer-thread-1) Installed DeployableUnitID[url=file:/home/dluong/restcomm/restcomm-slee-7.0.63.64-wildfly-10.1.0.Final/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempbe398a3feee7b99b/content-a6a0154497901df7/content/]
2017-04-21 11:37:40,107 INFO  [org.mobicents.slee.container.management.ResourceManagement] (SLEE-InternalDeployer-thread-1) Created Resource Adaptor Entity HttpClientResourceAdaptor for ResourceAdaptorID[name=HttpClientResourceAdaptor,vendor=org.restcomm,version=4.0] Config Properties: [(MAX_CONNECTIONS_TOTAL:java.lang.Integer=1000),(HTTP_CLIENT_FACTORY:java.lang.String=),(MAX_CONNECTIONS_FOR_ROUTES:java.lang.String=http:localhost:8080:500)]
2017-04-21 11:37:40,357 INFO  [org.mobicents.slee.container.management.ResourceManagement] (SLEE-InternalDeployer-thread-1) Activated RA Entity HttpClientResourceAdaptor
2017-04-21 11:37:40,608 INFO  [org.mobicents.slee.container.management.ResourceManagement] (SLEE-InternalDeployer-thread-1) Bound link between RA Entity HttpClientResourceAdaptor and Name HttpClientResourceAdaptor
2017-04-21 11:37:40,859 WARN  [org.mobicents.slee.container.deployment.jboss.SleeContainerDeployerImpl] (SLEE-InternalDeployer-thread-1) SLEE DUs not deployed, due to missing dependencies:
file:/home/dluong/restcomm/restcomm-slee-7.0.63.64-wildfly-10.1.0.Final/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempbe398a3feee7b99b/content-72c482736938840d/content/

    Missing Dependencies:
        EventTypeID[name=javax.slee.facilities.TimerEvent,vendor=javax.slee,version=1.0]
        EventTypeID[name=javax.slee.serviceactivity.ServiceStartedEvent,vendor=javax.slee,version=1.1]
        ProfileSpecificationID[name=AddressProfileSpec,vendor=javax.slee,version=1.1]
        EventTypeID[name=JdbcTaskExecutionThrowableEvent,vendor=org.mobicents,version=1.0]
        EventTypeID[name=SimpleJdbcTaskResultEvent,vendor=org.mobicents,version=1.0]
        ResourceAdaptorTypeID[name=JDBCResourceAdaptorType,vendor=org.mobicents,version=1.0]
        EventTypeID[name=javax.slee.serviceactivity.ServiceStartedEvent,vendor=javax.slee,version=1.0]
        ResourceAdaptorTypeID[name=HttpClientResourceAdaptorType,vendor=org.mobicents,version=4.0]

[Vilius Panevėžys]

On Fri, 21 Apr 2017 11:01:03 -0500
david luong <davidc...@gmail.com> wrote:

> What I noticed was some of the missing dependencies have
> vendor=org.mobicents but they were installed earlier with
> vendor=org.restcomm ( which are highlighted in bold).

I think you've found the problem. It seems event, RA type and other
identifiers have been renamed and Charging Server has not been updated
accordingly. Try renaming the references to those components in
sbb-jar.xml.

Note that entries about missing dependencies in log are normal during
startup when the container attempts to deploy a dependent component
before it's dependencies. Failed DUs are attempted to deploy again,
after deploying other DUs and eventually everything should deploy
successfully, provided the correct dependencies are available. For
example, in the log you've provided the standard components (e.g.
TimerEvent, ServiceStartedEvent, AddressProfileSpec, etc.) get deployed
eventually, so there's no problem with those.


--
Vilius Panevėžys
Elitnet

[david luong]

Hi Vilius,

Thanks for your feedback. I made the changes as you suggested. Now the deployment proceed further but failed differently... I attached the complete log but here are the interesting parts. I'm not sure how to fix this.

2017-04-21 16:39:20,660 ERROR [org.mobicents.slee.container.deployment.jboss.DeploymentManager] (MSC service thread 1-4) Failure invoking 'InstallDeployableUnitAction[file:/home/dluong/restcomm/restcomm-slee-7.0.63.64-wildfly-10.1.0.Final/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/temp5811a6722c71c7d1/content-4586db3197c5c562/content/]: javax.slee.management.DeploymentException: Failure encountered during deploy process.
    at org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl.install(DeploymentMBeanImpl.java:340)
    at org.mobicents.slee.container.deployment.jboss.action.InstallDeployableUnitAction.invoke(InstallDeployableUnitAction.java:41)
    at org.mobicents.slee.container.deployment.jboss.DeploymentManager.sciAction(DeploymentManager.java:316)
    at org.mobicents.slee.container.deployment.jboss.DeploymentManager.installDeployableUnit(DeploymentManager.java:181)
    at org.mobicents.slee.container.deployment.jboss.SLEESubDeployer.start(SLEESubDeployer.java:278)
    at org.mobicents.slee.container.deployment.jboss.SleeContainerDeployerImpl.start(SleeContainerDeployerImpl.java:264)
    at org.restcomm.slee.container.build.as7.deployment.ExternalDeployerImpl.callSubDeployer(ExternalDeployerImpl.java:145)
    at org.restcomm.slee.container.build.as7.deployment.ExternalDeployerImpl.deploy(ExternalDeployerImpl.java:95)
    at org.restcomm.slee.container.build.as7.service.SleeContainerService.installInternalDeployments(SleeContainerService.java:395)
    at org.restcomm.slee.container.build.as7.service.SleeContainerService.start(SleeContainerService.java:349)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
    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: javax.slee.management.DeploymentException: failed to validate SbbID[name=Mobicents Charging Server Datasource SBB,vendor=org.mobicents,version=1.0]
    at org.mobicents.slee.container.component.deployment.DeployableUnitBuilderImpl.build(DeployableUnitBuilderImpl.java:265)
    at org.mobicents.slee.container.component.deployment.DeployableUnitBuilderImpl.build(DeployableUnitBuilderImpl.java:72)
    at org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl.install(DeploymentMBeanImpl.java:164)
    ... 14 more
Caused by: java.lang.NoClassDefFoundError: org/mobicents/slee/resource/jdbc/task/simple/SimpleJdbcTask
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
    at java.lang.Class.getDeclaredMethods(Class.java:1975)
    at org.mobicents.slee.container.component.validator.ClassUtils.getAbstractMethodsFromClass(ClassUtils.java:178)
    at org.mobicents.slee.container.component.validator.SbbComponentValidator.validate(SbbComponentValidator.java:139)
    at org.mobicents.slee.container.component.SbbComponentImpl.validate(SbbComponentImpl.java:309)
    at org.mobicents.slee.container.component.deployment.DeployableUnitBuilderImpl.build(DeployableUnitBuilderImpl.java:254)
    ... 16 more
Caused by: java.lang.ClassNotFoundException: org.mobicents.slee.resource.jdbc.task.simple.SimpleJdbcTask
    at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
    at org.mobicents.slee.container.component.deployment.classloading.URLClassLoaderDomainImpl.findClassLocallyLocked(URLClassLoaderDomainImpl.java:272)
    at org.mobicents.slee.container.component.deployment.classloading.URLClassLoaderDomainImpl.findClass(URLClassLoaderDomainImpl.java:241)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
    at org.mobicents.slee.container.component.deployment.classloading.URLClassLoaderDomainImpl.loadClass(URLClassLoaderDomainImpl.java:200)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    ... 23 more

2017-04-21 16:39:20,912 ERROR [org.mobicents.slee.container.deployment.jboss.SLEESubDeployer] (MSC service thread 1-4) : javax.slee.UnrecognizedServiceException: Unrecognized service ServiceID[name=Mobicents Charging Server Service,vendor=org.mobicents,version=1.0]
    at org.mobicents.slee.container.management.ServiceManagementImpl.activate(ServiceManagementImpl.java:236)
    at org.mobicents.slee.container.management.ServiceManagementImpl.activate(ServiceManagementImpl.java:217)
    at org.mobicents.slee.container.deployment.jboss.action.ActivateServiceAction.invoke(ActivateServiceAction.java:59)
    at org.mobicents.slee.container.deployment.jboss.DeploymentManager.sciAction(DeploymentManager.java:316)
    at org.mobicents.slee.container.deployment.jboss.DeploymentManager.installDeployableUnit(DeploymentManager.java:181)
    at org.mobicents.slee.container.deployment.jboss.SLEESubDeployer.start(SLEESubDeployer.java:278)
    at org.mobicents.slee.container.deployment.jboss.SleeContainerDeployerImpl.start(SleeContainerDeployerImpl.java:264)
    at org.restcomm.slee.container.build.as7.deployment.ExternalDeployerImpl.callSubDeployer(ExternalDeployerImpl.java:145)
    at org.restcomm.slee.container.build.as7.deployment.ExternalDeployerImpl.deploy(ExternalDeployerImpl.java:95)
    at org.restcomm.slee.container.build.as7.service.SleeContainerService.installInternalDeployments(SleeContainerService.java:395)
    at org.restcomm.slee.container.build.as7.service.SleeContainerService.start(SleeContainerService.java:349)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
    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)

--
Vilius Panevėžys
Elitnet

[Vilius Panevėžys]

On Fri, 21 Apr 2017 16:08:17 -0500
david luong <davidc...@gmail.com> wrote:

> Caused by: java.lang.ClassNotFoundException:
> org.mobicents.slee.resource.jdbc.task.simple.SimpleJdbcTask

Unfortunately, the renaming seems to have been thorough - not only SLEE
identifiers, but packages have also been renamed, for example, in JDBC
RA [1].

The obvious solution would be to rename the packages in Charging Server
accordingly and rebuild against the versions of components that you are
deploying. You may come across similar problems with other dependencies
of Charging Server as well.

Another alternative could be to try using older versions of Charging
Server dependencies as it obviously has not been updated to be
compatible with the latest release.

It's for you to decide which approach makes more sense in your
situation. I'll refrain from further comments on what I think about
breaking public APIs for no technical merit.


[1]
https://github.com/RestComm/jain-slee.jdbc/commit/d62c75edbfba2bed88c177cbbe8840696635ff38


--
Vilius Panevėžys
Elitnet