SIP Presence Service migrated to JAIN SLEE 2.x

5 views
Skip to first unread message

Eduardo Martins

unread,
Dec 11, 2009, 11:32:34 AM12/11/09
to mobicent...@googlegroups.com
FYI, the 1st stage of the SIP Presence Service platform migration to Mobicents JAIN SLEE 2.x  is now complete, 2nd and final stage is about optimizing the code to take advantage of the JAIN SLEE 1.1 specs.

Some bonus features from this migration work:

* JDK 6 Support
* Configurations through unpacked XML files and JMX MBeans

In the next few days a new XCAP Client RA will be available, with core API changes for an easier work with URIs read from XML files (such as rls-services), to support interaction with multiple XCAP Servers, and on top of the new generation Apache Http Client 4.x

-- Eduardo

-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
http://emmartins.blogspot.com
http://www.redhat.com/solutions/telco

Ivelin Ivanov

unread,
Dec 11, 2009, 12:40:37 PM12/11/09
to mobicent...@googlegroups.com, mobicent...@googlegroups.com
Great. When do you expect stage 2 completion? 

Ivelin

Eduardo Martins

unread,
Dec 11, 2009, 12:59:44 PM12/11/09
to mobicent...@googlegroups.com
Due to JAIN SLEE 2.0 CR1 release this will take about 2 weeks.


-- Eduardo

-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
http://emmartins.blogspot.com
http://www.redhat.com/solutions/telco


aayush bhatnagar

unread,
Dec 11, 2009, 10:26:26 PM12/11/09
to mobicent...@googlegroups.com
need this artifact to build successfully:

org.mobicents.servers.xdm:xdms-core-configuration-meta:jar:1.0.0-SNAPSHOT

Best
Aayush

aayush bhatnagar

unread,
Dec 17, 2009, 12:56:16 AM12/17/09
to mobicent...@googlegroups.com
Some issues regarding 2.x port:

A) SBB validation error on XCAP caps app usage SBB (inherits from Abstract app usage sbb). Container thinks it has to implement these abstract methods of superclass.

DEBUG trace: 

SbbID[name=XCAPCapsAppUsageSbb,vendor=org.openxdm,version=1.0] : violates sbb constraints, it declares more abstract methods than SLEE is bound to implement.Methods directly from class: [], methods from super classes: [getAppUsageFactory[], getAUID[]]
 
B) Secondly, Aggregation proxy service cannot be recognized by the container...so it throws an exception on "activate". 

DEBUG trace:

ERROR [org.mobicents.slee.container.deployment.jboss.DeploymentManager] (Thread-1401) Failure invoking 'activate([ServiceID[name=AggregationProxyService,vendor=org.openxdm,version=1.0]]) on javax.slee.management:name=ServiceManagement
javax.management.MBeanException
at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:184)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:165)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.mobicents.slee.container.deployment.jboss.DeploymentManager.sciAction(DeploymentManager.java:351)
at org.mobicents.slee.container.deployment.jboss.DeploymentManager.installDeployableUnit(DeploymentManager.java:161)
at org.mobicents.slee.container.deployment.jboss.SLEESubDeployer.start(SLEESubDeployer.java:271)
at org.mobicents.slee.container.deployment.jboss.SLEEDeployer.callSubDeployer(SLEEDeployer.java:124)
at org.mobicents.slee.container.deployment.jboss.SLEEDeployer.sleeIsRunning(SLEEDeployer.java:130)
at org.mobicents.slee.container.deployment.jboss.SleeStateJMXMonitor.setSleeState(SleeStateJMXMonitor.java:105)
at org.mobicents.slee.container.deployment.jboss.SleeStateJMXMonitor.access$200(SleeStateJMXMonitor.java:26)
at org.mobicents.slee.container.deployment.jboss.SleeStateJMXMonitor$1.run(SleeStateJMXMonitor.java:124)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.slee.UnrecognizedServiceException: Unrecognized service ServiceID[name=AggregationProxyService,vendor=org.openxdm,version=1.0]
at org.mobicents.slee.container.management.ServiceManagement.activate(ServiceManagement.java:201)
at org.mobicents.slee.container.management.jmx.ServiceManagementMBeanImpl.activate(ServiceManagementMBeanImpl.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

C) Lastly, DataSource RA is unable to open the data source:

10:11:18,546 ERROR [JPADataSourceResourceAdaptor] Failed to open data source
javax.persistence.PersistenceException: No Persistence provider for EntityManager named mobicents-xdm-core-datasource-pu.

Is the <provider> tag needed in persistence.xml here ? 


Eduardo Martins

unread,
Dec 17, 2009, 9:31:36 AM12/17/09
to mobicent...@googlegroups.com
Are you trying it with SLEE 2.0.0.BETA2? It needs current SLEE 2.x snapshot...

Use the daily snapshots built in hudson

http://hudson.jboss.org/hudson/view/Mobicents/job/MobicentsSipPresenceRelease/


-- Eduardo

-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
http://emmartins.blogspot.com
http://www.redhat.com/solutions/telco


aayush

unread,
Dec 17, 2009, 9:41:14 AM12/17/09
to mobicents-public
yeah. I deployed in SLEE 2.0.0.BETA2. Built msps from trunk. Will try
the hudson job.

On Dec 17, 7:31 pm, Eduardo Martins <emmart...@gmail.com> wrote:
> Are you trying it with SLEE 2.0.0.BETA2? It needs current SLEE 2.x
> snapshot...
>
> Use the daily snapshots built in hudson
>

> http://hudson.jboss.org/hudson/view/Mobicents/job/MobicentsSipPresenc...
>
> -- Eduardo
>
> -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-http://emmartins.blogspot.comhttp://www.redhat.com/solutions/telco


>
> On Thu, Dec 17, 2009 at 5:56 AM, aayush bhatnagar <
>
>
>
> abhatnagar192...@gmail.com> wrote:
> > Some issues regarding 2.x port:
>
> > A) SBB validation error on XCAP caps app usage SBB (inherits from Abstract
> > app usage sbb). Container thinks it has to implement these abstract methods
> > of superclass.
>

> > *DEBUG trace: *


>
> > SbbID[name=XCAPCapsAppUsageSbb,vendor=org.openxdm,version=1.0] : violates
> > sbb constraints, it declares more abstract methods than SLEE is bound to
> > implement.Methods directly from class: [], methods from super classes:
> > [getAppUsageFactory[], getAUID[]]
>
> > B) Secondly, Aggregation proxy service cannot be recognized by the
> > container...so it throws an exception on "activate".
>

> > *DEBUG trace:*


>
> > ERROR [org.mobicents.slee.container.deployment.jboss.DeploymentManager]
> > (Thread-1401) Failure invoking

> > 'activate([ServiceID[name=AggregationProxyService,vendor=org.openxdm,versio n=1.0]])


> > on javax.slee.management:name=ServiceManagement
> > javax.management.MBeanException
> > at
> > org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(Ref lectedDispatcher.java:184)
> >  at

> > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.jav a:165)


> > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> >  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> > at
> > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:2 64)
> >  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> > at
> > org.mobicents.slee.container.deployment.jboss.DeploymentManager.sciAction(D eploymentManager.java:351)
> >  at
> > org.mobicents.slee.container.deployment.jboss.DeploymentManager.installDepl oyableUnit(DeploymentManager.java:161)
> > at
> > org.mobicents.slee.container.deployment.jboss.SLEESubDeployer.start(SLEESub Deployer.java:271)
> >  at
> > org.mobicents.slee.container.deployment.jboss.SLEEDeployer.callSubDeployer( SLEEDeployer.java:124)
> > at
> > org.mobicents.slee.container.deployment.jboss.SLEEDeployer.sleeIsRunning(SL EEDeployer.java:130)
> >  at
> > org.mobicents.slee.container.deployment.jboss.SleeStateJMXMonitor.setSleeSt ate(SleeStateJMXMonitor.java:105)
> > at
> > org.mobicents.slee.container.deployment.jboss.SleeStateJMXMonitor.access$20 0(SleeStateJMXMonitor.java:26)
> >  at

> > org.mobicents.slee.container.deployment.jboss.SleeStateJMXMonitor$1.run(Sle eStateJMXMonitor.java:124)


> > at java.lang.Thread.run(Thread.java:595)
> > Caused by: javax.slee.UnrecognizedServiceException: Unrecognized service
> > ServiceID[name=AggregationProxyService,vendor=org.openxdm,version=1.0]
> > at
> > org.mobicents.slee.container.management.ServiceManagement.activate(ServiceM anagement.java:201)
> >  at

> > org.mobicents.slee.container.management.jmx.ServiceManagementMBeanImpl.acti vate(ServiceManagementMBeanImpl.java:48)


> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >  at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9)
> > at

> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:25)
> >  at java.lang.reflect.Method.invoke(Method.java:592)
> > at
> > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.jav a:157)


>
> > C) Lastly, DataSource RA is unable to open the data source:
>
> > 10:11:18,546 ERROR [JPADataSourceResourceAdaptor] Failed to open data
> > source
> > javax.persistence.PersistenceException: No Persistence provider for
> > EntityManager named mobicents-xdm-core-datasource-pu.
>
> > Is the <provider> tag needed in persistence.xml here ?
>
> > On Sat, Dec 12, 2009 at 08:56, aayush bhatnagar <
> > abhatnagar192...@gmail.com> wrote:
>
> >> need this artifact to build successfully:
>
> >> org.mobicents.servers.xdm:xdms-core-configuration-meta:jar:1.0.0-SNAPSHOT
>
> >> Best
> >> Aayush
>

> >> On Fri, Dec 11, 2009 at 23:29, Eduardo Martins <emmart...@gmail.com>wrote:
>
> >>> Due to JAIN SLEE 2.0 CR1 release this will take about 2 weeks.
>
> >>> -- Eduardo
>
> >>> -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
> >>>http://emmartins.blogspot.com
> >>>http://www.redhat.com/solutions/telco
>
> >>> On Fri, Dec 11, 2009 at 5:40 PM, Ivelin Ivanov <
> >>> ivelin.atanasoff.iva...@gmail.com> wrote:
>
> >>>> Great. When do you expect stage 2 completion?
>
> >>>> Ivelin
>

> >>>> On Dec 11, 2009, at 10:32, Eduardo Martins <emmart...@gmail.com> wrote:
>
> >>>> FYI, the 1st stage of the SIP Presence Service platform migration to
> >>>> Mobicents JAIN SLEE 2.x  is now complete, 2nd and final stage is about
> >>>> optimizing the code to take advantage of the JAIN SLEE 1.1 specs.
>
> >>>> Some bonus features from this migration work:
>
> >>>> * JDK 6 Support
> >>>> * Configurations through unpacked XML files and JMX MBeans
>
> >>>> In the next few days a new XCAP Client RA will be available, with core
> >>>> API changes for an easier work with URIs read from XML files (such as
> >>>> rls-services), to support interaction with multiple XCAP Servers, and on top
> >>>> of the new generation Apache Http Client 4.x
>
> >>>> -- Eduardo
>
> >>>> -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-

> >>>> <http://emmartins.blogspot.com>http://emmartins.blogspot.com
> >>>>  <http://www.redhat.com/solutions/telco>

Reply all
Reply to author
Forward
0 new messages