Mobicents Media Server 2.1.0.BETA3 released!

83 views
Skip to first unread message

Oleg Kulikov

unread,
Sep 2, 2011, 11:28:16 AM9/2/11
to mobicents-public
We are happy to announce the release of Mobicents Media Server (MMS) v2.1.0.BETA3

The new branch of MMS based on EDF scheduler.

The MMS 2.1.0.BETA3 ships with media control api (JSR-309)

To understand how to use Mobicents Media Server with JAIN SLEE Server look at demo for examples.

Mobicents Media Server Home Page:

MMS Guide page:

To know the details of issues fixed in this release follow

Where to download from?
-----------------------
The distribution can be found on SourceForge.net. The binary package for standalone is mms-standalone-2.1.0.BETA1.zip
Download from

Source repositories:
-------------------

SVN checkout

SVN Browsing

Looking forward to your feedback:
---------------------------------

Mobicents Media Server Team

Ivelin Ivanov

unread,
Sep 2, 2011, 11:34:51 AM9/2/11
to mobicent...@googlegroups.com
Congratulations, MMS team! 

One step closer to a production ready JSR 309 compatible release.

Ivelin

shubhanshu shukla

unread,
Sep 2, 2011, 11:35:02 AM9/2/11
to mobicent...@googlegroups.com
Hi Oleg,
Can we use this media server to play video on sipphone ?
If yes could you please share a example?

On 9/2/11, Oleg Kulikov <oleg.k...@gmail.com> wrote:
> We are happy to announce the release of *Mobicents Media Server (MMS)
> v2.1.0.BETA3*


>
> The new branch of MMS based on EDF scheduler.
>
> The MMS 2.1.0.BETA3 ships with media control api (JSR-309)
>
> To understand how to use Mobicents Media Server with JAIN SLEE Server look
> at

> demo<http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/media/examples/telephony/ivr>for
> examples.
>
> *Mobicents Media Server Home Page:*
> http://www.mobicents.org/mms/mms-main.html
>
> *MMS Guide page:*


> http://www.mobicents.org/mms/mms-docs.html
>
> To know the details of issues fixed in this release follow

> http://code.google.com/p/mobicents/issues/list?can=1&q=Component%3DMedia-Server+Release%3DType-Beta-3+Version%3D2.1.0+&cells=tiles<http://code.google.com/p/mobicents/issues/list?can=1&q=label:Component-Media-Server%20label:Version-2.1.0%20label:Release%20label:Release-Type-Beta%20status:Fixed>
>
> *Where to download from?*


> -----------------------
> The distribution can be found on SourceForge.net. The binary package for
> standalone is mms-standalone-2.1.0.BETA1.zip
> Download from

> http://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server/2.1.0.BETA3/<http://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server/2.1.0.BETA1/>
>
> *Source repositories:*
> -------------------
>
> SVN checkout
> http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/server-2.1.0.BETA3/<http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.1.0.BETA1/>
>
> SVN Browsing
> http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/server-2.1.0.BETA3<http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.1.0.BETA1>


>
> Looking forward to your feedback:
> ---------------------------------
> http://groups.google.com/group/mobicents-public
>

> *Mobicents Media Server Team*
>

--
Sent from my mobile device

shubhans...@gmail.com
Shubhanshu Shukla
9911260992

Oleg Kulikov

unread,
Sep 2, 2011, 12:23:21 PM9/2/11
to mobicent...@googlegroups.com

I want to say a BIG thanks to Laurent Schweizer and Brad Porter for their greatest testing! Thank you, guys. You made this release possible in such short time.

Oleg

On Sep 2, 2011 7:35 PM, "shubhanshu shukla" <shubhans...@gmail.com> wrote:

Hi Oleg,
Can we use this media server to play video on sipphone ?
If yes could you please share a example?


On 9/2/11, Oleg Kulikov <oleg.k...@gmail.com> wrote:

> We are happy to announce the release of ...

> demo<http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/media/examples/telephony/ivr>for

> examples.
>
> *Mobicents Media Server Home Page:*
> http://www.mobicents.org/mms/mms-main.html
>

>...

> http://code.google.com/p/mobicents/issues/list?can=1&q=Component%3DMedia-Server+Release%3DType-Beta-3+Version%3D2.1.0+&cells=tiles<http://code.google.com/p/mobicents/issues/list?can=1&q=label:Component-Media-Server%20label:Version-2.1.0%20label:Release%20label:Release-Type-Beta%20status:Fixed>
>
> *Where to download from?*

> -----------------------
> The distribution can be found on SourceForge.net. The binary package for...

> http://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server/2.1.0.BETA3/<http://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server/2.1.0.BETA1/>
>
> *Source repositories:*
> -------------------
>
> SVN checkout
> http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/server-2.1.0.BETA3/<http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.1.0.BETA1/>
>
> SVN Browsing
> http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/server-2.1.0.BETA3<http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.1.0.BETA1>

>
> Looking forward to your feedback:
> ---------------------------------

> http://groups.google.com...

Alexandre Mendonça

unread,
Sep 2, 2011, 12:28:26 PM9/2/11
to mobicent...@googlegroups.com
Thumbs up for MMS and it's community! Congrats

--
Alexandre Mendonça // JBoss R&D
http://ammendonca.blogspot.com/

Brad Porter

unread,
Sep 2, 2011, 12:34:48 PM9/2/11
to mobicent...@googlegroups.com
Congrats on the release!

And thanks, Oleg.

Thanks for being so responsive to our questions and needs!

-brad

Thomas Quintana

unread,
Sep 2, 2011, 2:00:10 PM9/2/11
to mobicent...@googlegroups.com
Congratulations!

Eduardo Martins

unread,
Sep 2, 2011, 2:04:05 PM9/2/11
to mobicent...@googlegroups.com
Congrats to all involved, surely an important step in MMS roadmap.
Happy weekend it seems :)

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

Thomas Quintana

unread,
Sep 2, 2011, 2:31:36 PM9/2/11
to mobicent...@googlegroups.com
When I change the JSR-309 implementation to Beta5 the compiler complains that org.mobicents.jsr309.mgcp.MgcpStackFactory can not be resolved.

Regards,
Thomas

Henrique Cunha

unread,
Sep 2, 2011, 2:35:10 PM9/2/11
to mobicent...@googlegroups.com, mobicents-public
That's how we evaluate a great team and a project with a bright future.

Congrats!

thomas

unread,
Sep 2, 2011, 3:36:09 PM9/2/11
to mobicents-public
FYI, I'm using the jsr-309 implementation BETA4 and I'm getting the
following exception with MMS BETA 2+:

15:29:01,459 ERROR [TransactionHandler] Could not decode message:
java.text.ParseException: unknown response code: 410
at
org.mobicents.protocols.mgcp.parser.Utils.decodeReturnCode(Utils.java:
1568)
at org.mobicents.protocols.mgcp.stack.CreateConnectionHandler
$ResponseContentHandle.header(CreateConnectionHandler.java:267)
at
org.mobicents.protocols.mgcp.parser.MgcpMessageParser.parse(MgcpMessageParser.java:
55)
at
org.mobicents.protocols.mgcp.stack.CreateConnectionHandler.decodeResponse(CreateConnectionHandler.java:
88)
at
org.mobicents.protocols.mgcp.stack.TransactionHandler.receiveResponse(TransactionHandler.java:
621)
at
org.mobicents.protocols.mgcp.stack.MessageHandler.scheduleMessages(MessageHandler.java:
223)
at
org.mobicents.protocols.mgcp.stack.JainMgcpStackImpl.run(JainMgcpStackImpl.java:
327)
15:29:01,462 ERROR [JainMgcpStackImpl] Unexpected exception occured:
java.lang.NullPointerException
at
org.mobicents.protocols.mgcp.stack.TransactionHandler.receiveResponse(TransactionHandler.java:
627)
at
org.mobicents.protocols.mgcp.stack.MessageHandler.scheduleMessages(MessageHandler.java:
223)
at
org.mobicents.protocols.mgcp.stack.JainMgcpStackImpl.run(JainMgcpStackImpl.java:
327)

Regards,
Thomas

On Sep 2, 11:28 am, Oleg Kulikov <oleg.kulik...@gmail.com> wrote:
> We are happy to announce the release of *Mobicents Media Server (MMS)
> v2.1.0.BETA3*
>
> The new branch of MMS based on EDF scheduler.
>
> The MMS 2.1.0.BETA3 ships with media control api (JSR-309)
>
> To understand how to use Mobicents Media Server with JAIN SLEE Server look
> at demo<http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/m...>for
> examples.
>
> *Mobicents Media Server Home Page:*http://www.mobicents.org/mms/mms-main.html
>
> *MMS Guide page:*http://www.mobicents.org/mms/mms-docs.html
>
> To know the details of issues fixed in this release followhttp://code.google.com/p/mobicents/issues/list?can=1&q=Component%3DMe...<http://code.google.com/p/mobicents/issues/list?can=1&q=label:Componen...>
>
> *Where to download from?*
> -----------------------
> The distribution can be found on SourceForge.net. The binary package for
> standalone is mms-standalone-2.1.0.BETA1.zip
>  Download fromhttp://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server...<http://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server...>
>
> *Source repositories:*
> -------------------
>
> SVN checkouthttp://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/server-2...<http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms...>
>
> SVN Browsinghttp://code.google.com/p/mobicents/source/browse/#svn/tags/servers/me...<http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/me...>
>
> Looking forward to your feedback:
> ---------------------------------http://groups.google.com/group/mobicents-public
>
> *Mobicents Media Server Team*

Oleg Kulikov

unread,
Sep 3, 2011, 9:15:29 AM9/3/11
to mobicent...@googlegroups.com
Thomas, you need to switch to B5 version of media control api implementation which was released with MMS 2.1.0.B3.

Oleg



2011/9/2 thomas <quintan...@gmail.com>

Oleg Kulikov

unread,
Sep 3, 2011, 9:17:23 AM9/3/11
to mobicent...@googlegroups.com
Hi Shubhanshu,

generaly yes, you can, but I did not try and have no examples yet.

Oleg

2011/9/2 shubhanshu shukla <shubhans...@gmail.com>

Amit Bhayani

unread,
Sep 3, 2011, 9:27:31 AM9/3/11
to mobicent...@googlegroups.com
Congratulations Team!

Great step ahead.

aayush

unread,
Sep 3, 2011, 9:44:27 AM9/3/11
to mobicent...@googlegroups.com

Congrats!!

dddd...@gmail.com

unread,
Sep 3, 2011, 9:54:43 AM9/3/11
to mobicent...@googlegroups.com
congrats, nice one.

Sent from my BlackBerry wireless device from MTN

From: Amit Bhayani <amit.b...@gmail.com>
Date: Sat, 3 Sep 2011 18:57:31 +0530
Subject: Re: [mobicents-public] Mobicents Media Server 2.1.0.BETA3 released!

shubhanshu shukla

unread,
Sep 3, 2011, 10:23:54 AM9/3/11
to mobicent...@googlegroups.com
Hi Oleg,
Then you can be so sure about the video since there is no example which proves that it is working.

What say?

Thanks
Shubhanshu
--
shubhans...@gmail.com
Shubhanshu Shukla
9911260992


Thomas Quintana

unread,
Sep 3, 2011, 12:57:02 PM9/3/11
to mobicent...@googlegroups.com
Hi Oleg,
I haven't had much time to play since the announcement of the release but when I tried switching to Beta 5 a couple of things happened:

- org.mobicents.jsr309.mgcp.MgcpStackFactory can not be resolved by the compiler.
So in order to continue moving forward with the test :) I went ahead and commented
out the import and relevant code (MGCP stack provider cleanup) and tried to continue.

- When I tried to deploy RestComm to the container I get the following:

12:48:11,227 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/ state=ClassLoader mode=Manual requiredState=PostClassLoader
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/
    at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
    at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
    at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
    at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:263)
    at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
    at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
    at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
    at org.jboss.remoting.Client.invoke(Client.java:1724)
    at org.jboss.remoting.Client.invoke(Client.java:629)
    at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
    at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
    at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
    at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.util.DeploymentUtils.run(DeploymentUtils.java:98)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.util.DeploymentUtils.deployArchive(DeploymentUtils.java:92)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.ApplicationServerComponent.createContentBasedResource(ApplicationServerComponent.java:370)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:224)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:616)
    at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.VerifyError: (class: org/mobicents/javax/media/mscontrol/container/ContainerImpl, method: <init> signature: (Lorg/mobicents/javax/media/mscontrol/MediaSessionImpl;Ljavax/media/mscontrol/Parameters;)V) Incompatible argument to function
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
    at java.lang.Class.getDeclaredMethods(Class.java:1808)
    at org.jboss.deployment.AnnotatedClassFilter.hasAnnotations(AnnotatedClassFilter.java:194)
    at org.jboss.deployment.AnnotatedClassFilter.accepts(AnnotatedClassFilter.java:122)
    at org.jboss.deployment.AnnotatedClassFilter.visit(AnnotatedClassFilter.java:102)
    at org.jboss.virtual.plugins.vfs.helpers.WrappingVirtualFileHandlerVisitor.visit(WrappingVirtualFileHandlerVisitor.java:62)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:361)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:306)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:306)
    at org.jboss.virtual.VFS.visit(VFS.java:421)
    at org.jboss.virtual.VirtualFile.visit(VirtualFile.java:437)
    at org.jboss.deployment.AnnotationMetaDataDeployer.getClasses(AnnotationMetaDataDeployer.java:225)
    at org.jboss.deployment.ConvergedSipAnnotationMetaDataDeployer.processSipMetaData(ConvergedSipAnnotationMetaDataDeployer.java:104)
    at org.jboss.deployment.ConvergedSipAnnotationMetaDataDeployer.deploy(ConvergedSipAnnotationMetaDataDeployer.java:91)
    at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:93)
    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
    ... 37 more
12:48:11,230 INFO  [DeployHandler] Failed to complete command: [start] for deployment: names=[vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/], copyContent=true
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/


DEPLOYMENTS IN ERROR:
  Deployment "vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/" is in error due to the following reason(s): java.lang.VerifyError: (class: org/mobicents/javax/media/mscontrol/container/ContainerImpl, method: <init> signature: (Lorg/mobicents/javax/media/mscontrol/MediaSessionImpl;Ljavax/media/mscontrol/Parameters;)V) Incompatible argument to function

    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
    at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
    at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
    at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265)
    at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
    at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
    at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
    at org.jboss.remoting.Client.invoke(Client.java:1724)
    at org.jboss.remoting.Client.invoke(Client.java:629)
    at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
    at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
    at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
    at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.util.DeploymentUtils.run(DeploymentUtils.java:98)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.util.DeploymentUtils.deployArchive(DeploymentUtils.java:92)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.ApplicationServerComponent.createContentBasedResource(ApplicationServerComponent.java:370)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:224)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:616)
    at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:679)
12:48:11,231 ERROR [ApplicationServerComponent] Error deploying application for report: CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Web Application (WAR), plugin=JBossAS5]], ResourceKey=[null]
java.lang.Exception
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.util.DeploymentUtils.run(DeploymentUtils.java:102)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.util.DeploymentUtils.deployArchive(DeploymentUtils.java:92)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.ApplicationServerComponent.createContentBasedResource(ApplicationServerComponent.java:370)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:224)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:616)
    at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/


DEPLOYMENTS IN ERROR:
  Deployment "vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/" is in error due to the following reason(s): java.lang.VerifyError: (class: org/mobicents/javax/media/mscontrol/container/ContainerImpl, method: <init> signature: (Lorg/mobicents/javax/media/mscontrol/MediaSessionImpl;Ljavax/media/mscontrol/Parameters;)V) Incompatible argument to function

    at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
    at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
    at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
    at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
    at org.rhq.plugins.mobicents.servlet.sip.jboss5.util.DeploymentUtils.run(DeploymentUtils.java:98)
    ... 13 more
Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/


DEPLOYMENTS IN ERROR:
  Deployment "vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/" is in error due to the following reason(s): java.lang.VerifyError: (class: org/mobicents/javax/media/mscontrol/container/ContainerImpl, method: <init> signature: (Lorg/mobicents/javax/media/mscontrol/MediaSessionImpl;Ljavax/media/mscontrol/Parameters;)V) Incompatible argument to function

    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
    at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
    at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
    at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265)
    at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
    at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
    at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
    at org.jboss.remoting.Client.invoke(Client.java:1724)
    at org.jboss.remoting.Client.invoke(Client.java:629)
    at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
    ... 17 more
12:48:11,239 WARN  [CreateResourceRunner] Throwable was found in creation report for request [1]: java.lang.Exception - Enable DEBUG logging to see the stack trace.
12:48:14,449 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/ state=ClassLoader mode=Manual requiredState=PostClassLoader
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/
    at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
    at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
    at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
    at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
    at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.VerifyError: (class: org/mobicents/javax/media/mscontrol/container/ContainerImpl, method: <init> signature: (Lorg/mobicents/javax/media/mscontrol/MediaSessionImpl;Ljavax/media/mscontrol/Parameters;)V) Incompatible argument to function
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
    at java.lang.Class.getDeclaredMethods(Class.java:1808)
    at org.jboss.deployment.AnnotatedClassFilter.hasAnnotations(AnnotatedClassFilter.java:194)
    at org.jboss.deployment.AnnotatedClassFilter.accepts(AnnotatedClassFilter.java:122)
    at org.jboss.deployment.AnnotatedClassFilter.visit(AnnotatedClassFilter.java:102)
    at org.jboss.virtual.plugins.vfs.helpers.WrappingVirtualFileHandlerVisitor.visit(WrappingVirtualFileHandlerVisitor.java:62)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:361)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:376)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:306)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374)
    at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:306)
    at org.jboss.virtual.VFS.visit(VFS.java:421)
    at org.jboss.virtual.VirtualFile.visit(VirtualFile.java:437)
    at org.jboss.deployment.AnnotationMetaDataDeployer.getClasses(AnnotationMetaDataDeployer.java:225)
    at org.jboss.deployment.ConvergedSipAnnotationMetaDataDeployer.processSipMetaData(ConvergedSipAnnotationMetaDataDeployer.java:104)
    at org.jboss.deployment.ConvergedSipAnnotationMetaDataDeployer.deploy(ConvergedSipAnnotationMetaDataDeployer.java:91)
    at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:93)
    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
    ... 23 more
12:48:14,452 WARN  [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/


DEPLOYMENTS IN ERROR:
  Deployment "vfsfile:/home/thomas/Applications/mss-1.6.0/server/default/deploy/restcomm-0.0.1-SNAPSHOT.war/" is in error due to the following reason(s): java.lang.VerifyError: (class: org/mobicents/javax/media/mscontrol/container/ContainerImpl, method: <init> signature: (Lorg/mobicents/javax/media/mscontrol/MediaSessionImpl;Ljavax/media/mscontrol/Parameters;)V) Incompatible argument to function

    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
    at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
    at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
    at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
    at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:679)

Best Regards,
Thomas

Oleg Kulikov

unread,
Sep 4, 2011, 11:40:51 AM9/4/11
to mobicent...@googlegroups.com
Hi Thomas, see inline

2011/9/3 Thomas Quintana <quintan...@gmail.com>

Hi Oleg,
I haven't had much time to play since the announcement of the release but when I tried switching to Beta 5 a couple of things happened:
- org.mobicents.jsr309.mgcp.MgcpStackFactory can not be resolved by the compiler.
So in order to continue moving forward with the test :) I went ahead and commented
out the import and relevant code (MGCP stack provider cleanup) and tried to continue.
 
 Make sure that you are at right revision. There is no such file in latest revision. Why your test depends from implementation instead of API only?

Thomas Quintana

unread,
Sep 4, 2011, 11:55:02 AM9/4/11
to mobicent...@googlegroups.com
Hi Oleg,
I think I have the right revision 2.0.0.BETA5. Also, I figured that depending on the implementation is a bad idea but I was following the JSR-309 example and I believe that proper clean up of resources is more important than correctness :)

Best Regards,
Thomas

Oleg Kulikov

unread,
Sep 5, 2011, 2:47:00 AM9/5/11
to mobicent...@googlegroups.com
Hi Shubhanshu, I want to say that B3 contains video channel which was tested in loopback mode, it also contains video player but I never tryied to play a video file to phone - at this stage JSR-309 certification has higher priority.

So I am saying that you can try. If something will work wrong feel free to fix the problem.

Oleg

2011/9/3 shubhanshu shukla <shubhans...@gmail.com>

Laurent Schweizer

unread,
Sep 5, 2011, 2:53:53 AM9/5/11
to mobicent...@googlegroups.com

Congratulations for this new release.

 

Laurent

 

De : Oleg Kulikov [mailto:oleg.k...@gmail.com]
Envoyé : vendredi 2 septembre 2011 18:23
À : mobicent...@googlegroups.com
Objet : [!! SPAM] Re: [mobicents-public] Mobicents Media Server 2.1.0.BETA3 released!

Jean Deruelle

unread,
Sep 5, 2011, 9:01:16 AM9/5/11
to mobicent...@googlegroups.com
Congrats ! This is great ! I'm going to bundle it in the nightly snapshots of MSS 1.7 tomorrow

Jean Deruelle

unread,
Sep 5, 2011, 9:39:57 AM9/5/11
to mobicent...@googlegroups.com
Oleg,

We used to use this piece of code when an application was undeployed or redeployed to clean the resources and connection so that the application could rebind itself on the same IP address port for the MGCP stack. How shall we proceed now on BETA 5 ?

public void contextDestroyed(ServletContextEvent event) {
//This happens automatically. No need to force it
// Iterator<Driver> drivers = DriverManager.getDrivers();
// while (drivers.hasNext()) {
// Driver driver = drivers.next();
// DriverManager.deregisterDriver(driver);
// drivers = DriverManager.getDrivers();
// }
MgcpStackFactory.getInstance().clearMgcpStackProvider(properties);

Vladimir Ralev

unread,
Sep 5, 2011, 9:58:38 AM9/5/11
to mobicent...@googlegroups.com
We should implement this in 309 impl for driver.shutdown() instead.
Unfortunately it doesn't work right now. We can make another realease
for 309 impl to cover this.

In the mean time the new way of bootstrapping 309 impl is to use
DriverManager -> Driver -> Properties -> MsFactory

Oleg Kulikov

unread,
Sep 5, 2011, 10:03:06 AM9/5/11
to mobicent...@googlegroups.com
Why not to install driver into container and application will access driver instead of registering/deristering it?

2011/9/5 Vladimir Ralev <vladimi...@gmail.com>

Vladimir Ralev

unread,
Sep 5, 2011, 10:08:45 AM9/5/11
to mobicent...@googlegroups.com
Can do, but still the 309 spec requires a working driver.shutdown()
method so we must do it anyway. This also allows things like using
multiple media servers/ failover etc.

Oleg Kulikov

unread,
Sep 5, 2011, 10:12:08 AM9/5/11
to mobicent...@googlegroups.com
Driver.shutdown() is present in our implementation but not declared by API

2011/9/5 Vladimir Ralev <vladimi...@gmail.com>

Vladimir Ralev

unread,
Sep 5, 2011, 10:15:06 AM9/5/11
to mobicent...@googlegroups.com
Yeah you are right. Still we probably need this.

Jean Deruelle

unread,
Sep 5, 2011, 12:46:04 PM9/5/11
to mobicent...@googlegroups.com
I'm lost on the code we should use to clean up the resources with B5

Vladimir Ralev

unread,
Sep 5, 2011, 1:24:30 PM9/5/11
to mobicent...@googlegroups.com
309 spec doesn't really provision clean up, so it has to be custom.

Right now this should work:


Iterator<Driver> drivers = DriverManager.getDrivers();

while (drivers.hasNext()) {
Driver driver = drivers.next();
DriverManager.deregisterDriver(driver);
DriverImpl impl = (DriverImpl) driver;
impl.shutdown();

Thomas Quintana

unread,
Sep 5, 2011, 1:27:24 PM9/5/11
to mobicent...@googlegroups.com
Sweet! Thanks guys I will try later today with RestComm and report back my finding.

Best Regards,
Thomas

Thomas Quintana

unread,
Sep 5, 2011, 10:08:55 PM9/5/11
to mobicent...@googlegroups.com
Hi Guys,
Can you please provide a code example to initialize the JSR-309 implementation using BETA5. The code I'm using for now with 2.0.0.GA is below:

@Override public final void init(final ServletConfig config) throws ServletException {
    // Initialize JSR-309 implementation.
    final String stackName = config.getInitParameter("mgcp.stack.name");
    final String stackIp = config.getInitParameter("mgcp.stack.ip");
    final int stackPort = Integer.parseInt(config.getInitParameter("mgcp.stack.port"));
    final String peerIp = config.getInitParameter("mgcp.peer.ip");
    final int peerPort = Integer.parseInt(config.getInitParameter("mgcp.peer.port"));
    configuration = new Properties();
    configuration.put("mgcp.stack.name", stackName);
    configuration.put("mgcp.stack.ip", stackIp);
    configuration.put("mgcp.stack.port", stackPort);
    configuration.put("mgcp.peer.ip", peerIp);
    configuration.put("mgcp.peer.port", peerPort);
    try {
      factory = DriverManager.getDrivers().next().getFactory(configuration);
    } catch(final MsControlException exception) {
      throw new ServletException(exception);
    }
    // Let everyone know we're ready.
    if(logger.isInfoEnabled()) {
      logger.info("The Sip Call Manager has been successfully initialized.");
    }
  }

Regards,
Thomas

Vladimir Ralev

unread,
Sep 6, 2011, 12:31:58 PM9/6/11
to mobicent...@googlegroups.com
These should work on BETA5


// Property key for the Unique MGCP stack name for this application
public static final String MGCP_STACK_NAME = "mgcp.stack.name";

// Property key for the IP address where CA MGCP Stack (SIP Servlet
// Container) is bound
public static final String MGCP_STACK_IP = "mgcp.server.address";

// Property key for the port where CA MGCP Stack is bound
public static final String MGCP_STACK_PORT = "mgcp.local.port";

// Property key for the IP address where MGW MGCP Stack (MMS) is bound
public static final String MGCP_PEER_IP = "mgcp.bind.address";

// Property key for the port where MGW MGCP Stack is bound
public static final String MGCP_PEER_PORT = "mgcp.server.port";

Properties properties = new Properties();
properties.setProperty(MGCP_STACK_NAME, "sts");
properties.setProperty(MGCP_PEER_IP, "127.0.0.1");
properties.setProperty(MGCP_PEER_PORT, "2427");

properties.setProperty(MGCP_STACK_IP, "127.0.0.1");
properties.setProperty(MGCP_STACK_PORT, "2727");


// create the Media Session Factory
final MsControlFactory msControlFactory = new
DriverImpl().getFactory(properties);

On Tue, Sep 6, 2011 at 5:08 AM, Thomas Quintana

Thomas Quintana

unread,
Sep 6, 2011, 12:59:10 PM9/6/11
to mobicent...@googlegroups.com
Vladimir,
Thank you very much.

Best Regards,
Thomas

Noodle

unread,
Oct 12, 2011, 7:16:07 PM10/12/11
to mobicents-public
How can I access MsControlFactory from
DriverManager.getFactory("drivername", properties)? what "driver name"
and "properties" needed? I don't want my code depend on mobicents
implementation.

Thanks

Noodle
> > On Mon, Sep 5, 2011 at 1:27 PM, Thomas Quintana <quintana.tho...@gmail.com>
> > wrote:
>
> >> Sweet! Thanks guys I will try later today with RestComm and report back my
> >> finding.
>
> >> Best Regards,
> >> Thomas
>
> >> On Mon, Sep 5, 2011 at 1:24 PM, Vladimir Ralev <vladimir.ra...@gmail.com>
> >> wrote:
>
> >>> 309 spec doesn't really provision clean up, so it has to be custom.
>
> >>> Right now this should work:
> >>> Iterator<Driver> drivers = DriverManager.getDrivers();
> >>>  while (drivers.hasNext()) {
> >>>  Driver driver = drivers.next();
> >>>  DriverManager.deregisterDriver(driver);
> >>>  DriverImpl impl = (DriverImpl) driver;
> >>>  impl.shutdown();
> >>>  }
>
> >>> On Mon, Sep 5, 2011 at 7:46 PM, Jean Deruelle <jean.derue...@gmail.com>
> >>> wrote:
> >>> > I'm lost on the code we should use to clean up the resources with B5
>
> >>> > On Mon, Sep 5, 2011 at 4:15 PM, Vladimir Ralev
> >>> > <vladimir.ra...@gmail.com>
> >>> > wrote:
>
> >>> >> Yeah you are right. Still we probably need this.
>
> >>> >> On Mon, Sep 5, 2011 at 5:12 PM, Oleg Kulikov <oleg.kulik...@gmail.com>
> >>> >> wrote:
> >>> >> > Driver.shutdown() is present in our implementation but not declared
> >>> >> > by
> >>> >> > API
>
> >>> >> > 2011/9/5 Vladimir Ralev <vladimir.ra...@gmail.com>
>
> >>> >> >> Can do, but still the 309 spec requires a working driver.shutdown()
> >>> >> >> method so we must do it anyway. This also allows things like using
> >>> >> >> multiple media servers/ failover etc.
>
> >>> >> >> On Mon, Sep 5, 2011 at 5:03 PM, Oleg Kulikov
> >>> >> >> <oleg.kulik...@gmail.com>
> >>> >> >> wrote:
> >>> >> >> > Why not to install driver into container and application will
> >>> >> >> > access
> >>> >> >> > driver
> >>> >> >> > instead of registering/deristering it?
>
> >>> >> >> > 2011/9/5 Vladimir Ralev <vladimir.ra...@gmail.com>
>
> >>> >> >> >> We should implement this in 309 impl for driver.shutdown()
> >>> >> >> >> instead.
> >>> >> >> >> Unfortunately it doesn't work right now. We can make another
> >>> >> >> >> realease
> >>> >> >> >> for 309 impl to cover this.
>
> >>> >> >> >> In the mean time the new way of bootstrapping 309 impl is to use
> >>> >> >> >> DriverManager -> Driver -> Properties -> MsFactory
>
> >>> >> >> >> On Mon, Sep 5, 2011 at 4:39 PM, Jean Deruelle
> >>> >> >> >> <jean.derue...@gmail.com>
> >>> >> >> >> wrote:
> >>> >> >> >> > Oleg,
> >>> >> >> >> > We used to use this piece of code when an application was
> >>> >> >> >> > undeployed
> >>> >> >> >> > or
> >>> >> >> >> > redeployed to clean the resources and connection so that the
> >>> >> >> >> > application
> >>> >> >> >> > could rebind itself on the same IP address port for the MGCP
> >>> >> >> >> > stack.
> >>> >> >> >> > How
> >>> >> >> >> > shall we proceed now on BETA 5 ?
> >>> >> >> >> > public void contextDestroyed(ServletContextEvent event) {
> >>> >> >> >> > //This happens automatically. No need to force it
> >>> >> >> >> > // Iterator<Driver> drivers = DriverManager.getDrivers();
> >>> >> >> >> > // while (drivers.hasNext()) {
> >>> >> >> >> > // Driver driver = drivers.next();
> >>> >> >> >> > // DriverManager.deregisterDriver(driver);
> >>> >> >> >> > // drivers = DriverManager.getDrivers();
> >>> >> >> >> > // }
>
> >>> >> >> >> > MgcpStackFactory.getInstance().clearMgcpStackProvider(properties);
> >>> >> >> >> > }
>
> >>> >> >> >> > On Sun, Sep 4, 2011 at 5:55 PM, Thomas Quintana
> >>> >> >> >> > <quintana.tho...@gmail.com>
> >>> >> >> >> > wrote:
>
> >>> >> >> >> >> Hi Oleg,
> >>> >> >> >> >> I think I have the right revision 2.0.0.BETA5. Also, I
> >>> >> >> >> >> figured
> >>> >> >> >> >> that
> >>> >> >> >> >> depending on the implementation is a bad idea but I was
> >>> >> >> >> >> following
> >>> >> >> >> >> the
> >>> >> >> >> >> JSR-309 example and I believe that proper clean up of
> >>> >> >> >> >> resources
> >>> >> >> >> >> is
> >>> >> >> >> >> more
> >>> >> >> >> >> important than correctness :)
>
> >>> >> >> >> >> Best Regards,
> >>> >> >> >> >> Thomas
>
> >>> >> >> >> >> On Sun, Sep 4, 2011 at 11:40 AM, Oleg Kulikov
> >>> >> >> >> >> <oleg.kulik...@gmail.com>
> >>> >> >> >> >> wrote:
>
> >>> >> >> >> >>> Hi Thomas, see inline
>
> >>> >> >> >> >>> 2011/9/3 Thomas Quintana <quintana.tho...@gmail.com>
> ...
>
> read more »
Reply all
Reply to author
Forward
0 new messages