Mobicents JAIN SLEE Server Weekly Meeting - 16 Feb 2009
Eduardo Martins
at the irc network ( irc.codehaus.org:6667 channel #mobicents). The
meeting is public and everyone is invited.
1. Participants: Alexandre, Bartosz, Eduardo, Luis, Aayush and Vicky
2. Summary:
. JAIN SLEE 1.2 Issues & Tasks:
- All related issues are closed, except documentation review,
currently in progress by Eduardo. Luis is doing a soak test with the
1.2.4.GA binary snapshot and once it's finished, and if nothing is
wrong, the released will be made.
. JAIN SLEE 2.x Issues & Tasks:
- SLEE 1.1 Management, Classlaoding and Security: components
validation is still not complete, the descriptor building is being
reworked a bit, and we already have a test framework on top of jboss
microcontainer for testing the deploybale unit building process.
. Applications (Examples/RAs)
- SLEE Basic IMS Services: a wiki page is needed for CSCF and HSS
servers, with feature list (Aayush will work on this) and roadmap,
this will be created by Eduardo. The goal for first results is a
platform that can do a call forwarding. A DNS server is still needed
and this goal was missed from last week meeting.
3. Chat log
[16 Feb 09 15:50] * martins * Agenda
[16 Feb 09 15:50] * martins * ----------
[16 Feb 09 15:50] * martins * 1. SLEE 1.2 Open Issues & Tasks
[16 Feb 09 15:50] * martins * 2. SLEE 2.0 Open Issues & Tasks
[16 Feb 09 15:50] * martins * 3. Applications
[16 Feb 09 15:50] * martins * 1. SLEE 1.2 Open issues & Tasks
[16 Feb 09 15:50] * martins * open issues:
http://code.google.com/p/mobicents/issues/list?can=1&q=component:JainSLEE-Core%20version:1.2.04
[16 Feb 09 15:51] * martins * so in 1.2 we only have an open issue for
me, to review docs, not completed yet
[16 Feb 09 15:51] * martins * but we are in progress of 1.2.4.Ga release
[16 Feb 09 15:51] * martins * barreiro asked me for the weekend to
complete tests on the snapshot
[16 Feb 09 15:52] * martins * barreiro: results? :)
[16 Feb 09 15:52] * barreiro * The functional tests all were OK.
[16 Feb 09 15:53] * barreiro * unfortunately, I had some troubles
connecting to QA lab on friday night, so I was not able to check for
performance.
[16 Feb 09 15:53] * barreiro * I'm doing that as we speak.
[16 Feb 09 15:53] ^ vicky_afk is now known as vicky
[16 Feb 09 15:54] * martins * so how much time do you need to complete those?
[16 Feb 09 15:55] * barreiro * It'a a matter of hours. If you want to
wait for a long soak test, it will take more time.
[16 Feb 09 15:56] * martins * what is the test going on and what would
be the long soak test
[16 Feb 09 15:57] * martins * almost destroyed my workplace, went back
and the chair wanted to flip, and push the table along
[16 Feb 09 15:57] * martins * ...
[16 Feb 09 15:59] * martins * barreiro?
[16 Feb 09 16:00] ! CTCP PING reply sent to martins
[16 Feb 09 16:00] * barreiro * the usual. simple call setup.
[16 Feb 09 16:00] * alexandre * martins: just because you're moving,
there's no need to destroy the old one :D
[16 Feb 09 16:02] < vicky (~vi...@59.94.189.237) has disconnected ("Leaving")
[16 Feb 09 16:02] > vicky (~vi...@59.94.189.237) has joined
[16 Feb 09 16:03] * martins * hehe
[16 Feb 09 16:03] * martins * barreiro: the usual is what, a 1 million
call with new calls per second steps?
[16 Feb 09 16:04] * barreiro * yes. I but I could test for 24h, if you wanted.
[16 Feb 09 16:05] * martins * so that would be the soak
[16 Feb 09 16:05] * martins * ?
[16 Feb 09 16:05] * barreiro * yes. I don't think we need to go that deep.
[16 Feb 09 16:06] * martins * well, since ALL 1.2 GA is out we have no hurry
[16 Feb 09 16:06] > jeand
(~jean...@dou59-2-82-244-205-122.fbx.proxad.net) has joined
[16 Feb 09 16:06] * martins * I don't think a day will make any big difference
[16 Feb 09 16:06] * martins * alexandre , baranowb_ : what do you think
[16 Feb 09 16:07] * alexandre * cool with it... friday the 13th is
gone anyway :)
[16 Feb 09 16:07] * martins * yeah, we missed that special date
[16 Feb 09 16:07] * baranowb_ * nope
[16 Feb 09 16:07] * baranowb_ * actually it was a good day :P
[16 Feb 09 16:07] * martins * if something would go wrong the date
would be the reason
[16 Feb 09 16:07] * martins * now we have no excuses
[16 Feb 09 16:08] * martins * barreiro: do the soak
[16 Feb 09 16:08] * martins * pls
[16 Feb 09 16:08] * barreiro * ok. My plan was to do it over the
weekend, but it was not possible.
[16 Feb 09 16:09] * martins * weekeand plans
[16 Feb 09 16:10] * martins * ok, any1 has something else to discuss
on the 1.2 series?
[16 Feb 09 16:10] * alexandre * done with that old stuff ;)
[16 Feb 09 16:11] * martins * allright
[16 Feb 09 16:12] * martins * 2. SLEE 2.0 Open Issues & Tasks
[16 Feb 09 16:12] * martins * this one is more a report than discussion
[16 Feb 09 16:13] * martins * since me alexandre and baranowb_ are
working together on the same issue, slee component managent of the V2
[16 Feb 09 16:14] * martins * validation is still not complete, the
descriptor building is being reworked a bit, and we already have a
test framework on top of jboss microcontainer for testing the
deploybale unit deploying process
[16 Feb 09 16:14] * baranowb_ * validation is almost done, Im fixing
junits after alex last commit
[16 Feb 09 16:15] * martins * hopefully till the ALL meeting on
wednesday we start concrete class generation
[16 Feb 09 16:15] * martins * the last feature on the new component model
[16 Feb 09 16:15] * martins * and then integrate this module on the old code
[16 Feb 09 16:16] * martins * what a task ;-)
[16 Feb 09 16:16] * martins * alexandre: have something to say to the
log watchers interested in what is the progress?
[16 Feb 09 16:17] * martins * *hi mom* ?
[16 Feb 09 16:17] * alexandre * guess that's all, we are just
integrating everything for the descriptors and tests :)
[16 Feb 09 16:17] * martins * bartosz?
[16 Feb 09 16:18] * alexandre * my mom won't read the logs :(
[16 Feb 09 16:18] * baranowb_ * hope its fast :)
[16 Feb 09 16:18] * martins * k
[16 Feb 09 16:18] * martins * #3 Applications
[16 Feb 09 16:19] * martins * welcome aayush vicky
[16 Feb 09 16:19] * vicky * hey martins
[16 Feb 09 16:19] * aayush * hello Eduardo.
[16 Feb 09 16:19] * martins * hi
[16 Feb 09 16:19] * vicky * hello aayush, I just checked the IMS
related docs and did not see any changes out there.
[16 Feb 09 16:20] * martins * I'm afraid that from me there is not
much to update on this
[16 Feb 09 16:20] * aayush * changes as in ? the new docs /
[16 Feb 09 16:20] * vicky * I did clean some code on imsoss, related
to mvn it is yet not checked in.
[16 Feb 09 16:20] * vicky * aayush, have you got a chance to update
the ims docs on mobicents project?
[16 Feb 09 16:21] * aayush * i have not circulated any doc in the past
week.I have been working on the CSCF doc...but sporadically..as i was
caught in other stuff too.
[16 Feb 09 16:21] * vicky * ok.
[16 Feb 09 16:22] * vicky * martins, I don't think we have much update
on applications ;(
[16 Feb 09 16:23] * martins * yes, unfortunately, but this is expected
[16 Feb 09 16:23] * aayush * Apart from the docs..should we also start
circulating a software architecture of the CSCF nodes parallelly?
[16 Feb 09 16:23] * vicky * aayush, yes it makes sense.
[16 Feb 09 16:23] * aayush * so as to initiate a global discussion on
the forums...and have a common understanding.
[16 Feb 09 16:23] * vicky * yes.
[16 Feb 09 16:24] * martins * good idea
[16 Feb 09 16:24] * aayush * It might instill some interest in other
members too..and they might feel like participating.
[16 Feb 09 16:24] * martins * baranowb_: can you check the CSCF stuff
on IMSOSS with Vicky
[16 Feb 09 16:25] * aayush * And we will also have greater
co-ordination apart from the weekly updates.
[16 Feb 09 16:25] * baranowb_ * y
[16 Feb 09 16:25] * martins * aayush: once we have a clear idea of
what is to implement and how
[16 Feb 09 16:25] * martins * it's just a matter of setting up tasks
[16 Feb 09 16:25] * martins * but first this kind of syncronization
work is needed
[16 Feb 09 16:26] * martins * so we don't end all doing things in very
different ways
[16 Feb 09 16:26] < jeand
(~jean...@dou59-2-82-244-205-122.fbx.proxad.net) has left (jeand)
[16 Feb 09 16:26] * martins * cscf is really the anchor on this
[16 Feb 09 16:26] * vicky * yes, the design disucssions in forums are
the way to go.
[16 Feb 09 16:26] * aayush * i meant..in the sense of identifying the
major modules and mapping them to the standard..clause by clause.
Based on that we can circulate a compliance to standards.
[16 Feb 09 16:27] * martins * yes
[16 Feb 09 16:27] * aayush * As for example, if we plan to implement
the CSCF registrar and proxy functionality in the 1st phase, what
clauses of the standards do we plan to implement ?
[16 Feb 09 16:27] * martins * agree
[16 Feb 09 16:28] * martins * ok, lets proceed on that
[16 Feb 09 16:28] * aayush * DIAMETER Cx for instance will need to
wait for later....so all procedures relating to that will need to be
marked..and we will need to see how badly it affects our core CSCF
logic.
[16 Feb 09 16:29] * martins * currently we have all subpages per interface
[16 Feb 09 16:30] * vicky * aayush, I have something in mind regarding
the DIAMETER cx. Alex can help us here, he had agreed to help me but
unfortunately I am not getting time to continue ;(
[16 Feb 09 16:30] * martins * we should have also a page per
"implemented" server
[16 Feb 09 16:30] * aayush * okies.
[16 Feb 09 16:30] * martins * and the interfaces then link there too
[16 Feb 09 16:31] * martins * is there a the IMS OSS CSCF page?
[16 Feb 09 16:31] * vicky * matins: It is not there, I have a plan to
have it there.
[16 Feb 09 16:32] * alexandre * we can have Cx.. but I wouldnt like to
put it in front of Ro/Rf interfaces, the ones we still miss in AS
[16 Feb 09 16:32] * aayush * There is one note on I-CSCF if i remember
correctly on IMS OSS.
[16 Feb 09 16:33] * baranowb_ * Ro/Rf are next, even customers ask about them
[16 Feb 09 16:33] * martins * I think it would be good to have
different iterations on what the platform can do
[16 Feb 09 16:33] * baranowb_ * but we need some time to tune diameter stack
[16 Feb 09 16:33] * vicky * aayush, there is the basic architectural
design of imsoss.
[16 Feb 09 16:33] * martins * as a start we could ame for a simple call
[16 Feb 09 16:33] * martins * served by an app
[16 Feb 09 16:34] * martins * call forwarding is a usual example
[16 Feb 09 16:34] * vicky * martins: I was thinking of starting with
simple registeration.
[16 Feb 09 16:34] * aayush * Why i was stressing on clause by clause
compliance earlier..was because the IMS standards and RFCs are
inter-related and mixed with each other. Things get confusing
sometimes :)
[16 Feb 09 16:34] * martins * we need a bit more than registration, to
include the AS
[16 Feb 09 16:35] * martins * since the big thing here is serve the UE
and also 3rd parties apps
[16 Feb 09 16:35] * vicky * martins: yes the registration and then
call forwarding, I will discuss this over the forums
[16 Feb 09 16:35] * martins * with registration unless we do an
uncommon scenario
[16 Feb 09 16:36] * martins * we won't reach the AS
[16 Feb 09 16:36] * aayush * in the 1st phase the AKAv1md5 algo will
need to be implemented locally at the CSCF ?
[16 Feb 09 16:36] * vicky * yes I think at p-cscf.
[16 Feb 09 16:37] * aayush * S-CSCF.
[16 Feb 09 16:38] > jeand
(~jean...@dou59-2-82-244-205-122.fbx.proxad.net) has joined
[16 Feb 09 16:38] * aayush * P-cscf also helps.
[16 Feb 09 16:39] * martins * seems we need a roadmap
[16 Feb 09 16:39] * vicky * surely...
[16 Feb 09 16:39] * aayush * yes.
[16 Feb 09 16:39] * aayush * i propse, we prepare a feature list
and..map it to the roadmap.
[16 Feb 09 16:39] * aayush * GRUUs for example can wait for phase 2.
[16 Feb 09 16:40] * martins * ok, aayush you seem the best person for
this feature list :)
[16 Feb 09 16:40] * vicky * martins: +1
[16 Feb 09 16:40] * aayush * yes..i had prepared one earlier..on a
very old thread
[16 Feb 09 16:40] * aayush * i had circulated some use cases on the same thread.
[16 Feb 09 16:41] * aayush * vicky must remember :) it was the very
first IMS related discussion.
[16 Feb 09 16:42] * vicky * aayush: yes, i remember there is a thread
but now associated issue.
[16 Feb 09 16:42] * vicky * ;)
[16 Feb 09 16:42] * martins * so we need a wiki page for Mobicents HSS and CSCF
[16 Feb 09 16:42] * martins * with what we need to compliant
[16 Feb 09 16:42] * aayush * yeah !
[16 Feb 09 16:42] * vicky * yes.
[16 Feb 09 16:42] * martins * a fetaure list for each
[16 Feb 09 16:42] * martins * and a roadmap individually and platform
[16 Feb 09 16:43] * martins * I can setup the initial pages
[16 Feb 09 16:43] * martins * without any pretty format
[16 Feb 09 16:44] * aayush * I will then need to work on 2 fronts-->
To explain the CSCF node in easy words for the community covering Gm
and ISC....and also to enlist the major features that we can target.
[16 Feb 09 16:44] * vicky * martins: yes it makes sense.
[16 Feb 09 16:44] * martins * ok
[16 Feb 09 16:45] * vicky * martins/aayush: I will try to get things
sorted with baranowb_ regarding the imsoss
[16 Feb 09 16:45] * martins * yes please
[16 Feb 09 16:45] * aayush * :)
[16 Feb 09 16:45] * vicky * and with alex too regarding the diameter stuff.
[16 Feb 09 16:46] * martins * I will try to setup the pages today, max tomorrow
[16 Feb 09 16:47] * vicky * martins: I think you can wrap the details
and hope we make good progress over this week .
[16 Feb 09 16:47] * martins * have a coupke ones too for presence tks
to aayush :)
[16 Feb 09 16:47] * martins * yes, we can wrap
[16 Feb 09 16:47] * aayush * :) Presence is fun
[16 Feb 09 16:47] * vicky * martins: I get lesser time as I am in jee
and jain stuff, lot of context switching for me ;)
[16 Feb 09 16:48] * martins * I believe you
[16 Feb 09 16:48] * martins * I guess you don't have kids?
[16 Feb 09 16:48] * vicky * martins: I am yet alone so can afford to
do all this ;)
[16 Feb 09 16:48] * aayush * lol
[16 Feb 09 16:49] * martins * I can imagine you calling "come here Jain"
[16 Feb 09 16:49] * vicky * lol ;)
[16 Feb 09 16:49] * martins * hehe
[16 Feb 09 16:49] * martins * k, tks all for showing up
[16 Feb 09 16:49] * martins * I will post the log in the forums
-- Eduardo
aayush bhatnagar
- CSCF basics and architectural overview (basic intro and roles of the X-CSCFs)
- Feature list for Mobicents CSCF (which will eventually map to UML use cases)
- ISC reference point: A discussion and service examples (to get an understanding of the possible procedures)
Vicky Kak
Interesting stuff, I just glanced at it ;)
-Vicky
aayush
If you can review it, and if all is well in the doc, we can then
proceed to make a wiki page for the CSCF and populate the ISC wiki
page.
aayush
On Feb 18, 8:21 pm, Vicky Kak <vicky....@gmail.com> wrote:
> Interesting stuff, I just glanced at it ;)
>
> -Vicky
> On Wed, Feb 18, 2009 at 8:31 PM, aayush bhatnagar <
>
> > Hi Eduardo,
> > Please find a document covering some of the points decided in the meeting
> > -->
>
> > X-CSCFs)
> > 2. Feature list for Mobicents CSCF (which will eventually map to UML
> > use cases)
> > 3. ISC reference point: A discussion and service examples (to get an
>
> > aayush
>
> >> [16 Feb 09 16:26] * vicky * yes, the design disucssions in forums are
> >> the way to go.
> >> [16 Feb 09 16:26] * aayush * i meant..in the sense of identifying the
> >> major modules and mapping them to the standard..clause by clause.
> >> Based on that we can circulate a compliance to standards.
> >> [16 Feb 09 16:27] * martins * yes
> >> [16 Feb 09 16:27] * aayush * As for example, if we plan to implement
> >> the CSCF registrar and proxy functionality in the 1st phase, what
> >> clauses of the standards do we plan to implement ?
> >> [16 Feb 09 16:27] * martins *
>
>
> read more »
Vicky Kak
btw, the p-cscf is not pointed in the block diagram.
-Vicky
Bartosz Baranowski
Bartosz Baranowski
JBoss R & D
==================================
Word of criticism meant to improve is always step forward.
aayush
encapsulates the X-CSCF.
@Bartosz..yes, i agree with you. Each feature will map to a bunch of
procedures in the standards. We should now prioritize these features,
to shortlist those features that are 'absolutely' necessary so that we
can call the node as a CSCF.
>
> read more »
Vicky Kak
@Vicky Um..P-CSCF is labelled inside the Mobicents CSCF box..that
encapsulates the X-CSCF.
-Vicky
aayush
the logical roles of all 3 cscf's. Thus, there will be stackless
communication between the 3 logical cscf's through local interfaces.
During the review of the last doc (where Eduardo edited my doc), the
Mw interface was decided to be NA for us..so i didnt show it here :-)
if u want, i can show it there..
>
> read more »
Bartosz Baranowski
aayush
if a property is set, the integrated CSCF is built..else a distributed
CSCF service is built (P/I/S DUs). Something similar to integrated
Presence+XDM and standalone XDM server options that is there right
now.
On Feb 19, 10:31 pm, Bartosz Baranowski <baran...@gmail.com> wrote:
> It would be great to have in mind that at some point we might use scattered
> scenario, so we should provide some layer which will allow us to switch it
> (use standard API :))
>
>
> read more »
Jean Deruelle
Eduardo Martins
component (regarding the mobicents slee related platform) is the
replacement of current SLEE SIP Services, it doesn't need to be a
super server that handles a million user network in one node. One step
at a time, otherwise we won't progress fast.
-- Eduardo
aayush
If co-located, then the SBB will implement the business logic as an
implementation of the sbb local interface methods and be part of a
larger service.
If in a distributed architecture, then the SBB can implement the logic
in the event handlers and belong to a separate service.
Both service DUs can co-exist at runtime. The decision on whether to
behave as a co-located node or a distributed CSCF can be taken on the
basis of a MBean configurable flag.
aayush
On Feb 19, 10:47 pm, Jean Deruelle <jean.derue...@gmail.com> wrote:
> Using SIP servlets to build the CSCF would be easier in this case and would
> only be a deployment issue not a compile time issue.
>
>
> read more »
Eduardo Martins
referenced sbbs in a sbb jar descriptor. I guess when you said compile
you wanted to mean "assemble".
-- Eduardo
aayush
sbb's..in order..to make different services (by manipulating the
descriptor).
On Feb 19, 11:09 pm, Eduardo Martins <emmart...@gmail.com> wrote:
> If done properly it's just a matter of changing the id of the
> referenced sbbs in a sbb jar descriptor. I guess when you said compile
> you wanted to mean "assemble".
>
> -- Eduardo
>
>
> read more »
Zdenek
I am trying to install Mocinets, using java version "1.6.0_07" and I have problems with running the run.sh script. I have tried change java version but it does not help. Does anybody have any experience with similar problem, help please. It looks the problem could be in "NetworkRegistry" but I have no idea how and where to fix it.
Thanks in advance.
Zdenek
Aplication bin # ./run.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/Mobicents/mobicents_all/jboss-4.2.3.GA
JAVA: /etc/java-config-2/current-system-vm/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
CLASSPATH: /opt/Mobicents/mobicents_all/jboss-4.2.3.GA/bin/run.jar:/etc/java-config-2/current-system-vm/lib/tools.jar
=========================================================================
00:41:55,953 INFO [Server] Starting JBoss (MX MicroKernel)...
00:41:55,954 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)
00:41:55,955 INFO [Server] Home Dir: /opt/Mobicents/mobicents_all/jboss-4.2.3.GA
00:41:55,956 INFO [Server] Home URL: file:/opt/Mobicents/mobicents_all/jboss-4.2.3.GA/
00:41:55,957 INFO [Server] Patch URL: null
00:41:55,957 INFO [Server] Server Name: default
00:41:55,957 INFO [Server] Server Home Dir: /opt/Mobicents/mobicents_all/jboss-4.2.3.GA/server/default
00:41:55,958 INFO [Server] Server Home URL: file:/opt/Mobicents/mobicents_all/jboss-4.2.3.GA/server/default/
00:41:55,974 INFO [Server] Server Log Dir: /opt/Mobicents/mobicents_all/jboss-4.2.3.GA/server/default/log
00:41:55,975 INFO [Server] Server Temp Dir: /opt/Mobicents/mobicents_all/jboss-4.2.3.GA/server/default/tmp
00:41:55,976 INFO [Server] Root Deployment Filename: jboss-service.xml
00:41:56,279 INFO [ServerInfo] Java version: 1.6.0_07,Sun Microsystems Inc.
00:41:56,279 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b23,Sun Microsystems Inc.
00:41:56,280 INFO [ServerInfo] OS-System: Linux 2.6.25-gentoo-r7,i386
00:41:56,746 INFO [Server] Core system initialized
00:41:58,851 WARN [BasicMBeanRegistry] javax.management.MBeanRegistrationException: preRegister() failed: [ObjectName='jboss.remoting:service=NetworkRegistry', Class=org.jboss.remoting.network.NetworkRegistry (org.jboss.remoting.network.NetworkRegistry@17b0998)]
00:41:58,865 ERROR [MainDeployer] Could not create deployment: file:/opt/Mobicents/mobicents_all/jboss-4.2.3.GA/server/default/conf/jboss-service.xml
org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.InvocationTargetException)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.reflect.InvocationTargetException
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1451)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1350)
at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:345)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:157)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
... 36 more
Caused by: javax.management.MBeanException
at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1422)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1417)
... 41 more
Caused by: javax.management.MBeanRegistrationException: preRegister() failed: [ObjectName='jboss.remoting:service=NetworkRegistry', Class=org.jboss.remoting.network.NetworkRegistry (org.jboss.remoting.network.NetworkRegistry@17b0998)]
at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:713)
at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:211)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
... 51 more
Caused by: java.lang.RuntimeException: Exception creating identity: Aplication: Aplication
at org.jboss.remoting.ident.Identity.get(Identity.java:211)
at org.jboss.remoting.network.NetworkRegistry.preRegister(NetworkRegistry.java:268)
at org.jboss.mx.server.AbstractMBeanInvoker.invokePreRegister(AbstractMBeanInvoker.java:966)
at org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:489)
at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654)
at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:697)
... 56 more
Failed to boot JBoss:
org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.InvocationTargetException)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.reflect.InvocationTargetException
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1451)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1350)
at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:345)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:157)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
... 36 more
Caused by: javax.management.MBeanException
at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1422)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1417)
... 41 more
Caused by: javax.management.MBeanRegistrationException: preRegister() failed: [ObjectName='jboss.remoting:service=NetworkRegistry', Class=org.jboss.remoting.network.NetworkRegistry (org.jboss.remoting.network.NetworkRegistry@17b0998)]
at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:713)
at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:211)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
... 51 more
Caused by: java.lang.RuntimeException: Exception creating identity: Aplication: Aplication
at org.jboss.remoting.ident.Identity.get(Identity.java:211)
at org.jboss.remoting.network.NetworkRegistry.preRegister(NetworkRegistry.java:268)
at org.jboss.mx.server.AbstractMBeanInvoker.invokePreRegister(AbstractMBeanInvoker.java:966)
at org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:489)
at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654)
at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:697)
... 56 more
00:41:58,911 INFO [Server] Runtime shutdown hook called, forceHalt: true
00:41:58,911 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
00:41:58,919 INFO [Server] Shutdown complete
Shutdown complete
Halting VM
Vladimir Ralev
Also, try to enable write permissions for the mobicents folder.
Vicky Kak
Yep. The red box signifies that the mobicents cscf will encapsulate
the logical roles of all 3 cscf's.
I am n
Thus, there will be stackless
communication between the 3 logical cscf's through local interfaces.
I don't think we will always land up with the scenarios where the CSCF's would be co located, we have argued about it before ;)
aayush
of an architecture we want :
1. Co-located.
2. Distributed.
3. Or both options.
Based on this basic decision, we can move forward :)
Mw interface requires the CSCFs to act as simple SIP proxy servers,so
the procedures for that are well defined. Even in a colocated
architecture, the Mw interface will exist (for inter domain session
routing).It will be masked only for intra domain session control.
aayush.
>
> read more »
Vicky Kak
Yes. So, as i had suggested that time too,we need to decide what kind
of an architecture we want :
1. Co-located.
2. Distributed.
3. Or both options.
-Vicky
Ivelin Ivanov
Ivelin
/div>
aayush
especially from the point of view of inter-op and integration testing
with the IMS nodes of other vendors.
Co-located configurations also have their pros and cons...some of them
are pretty interesting to note. I have experienced them first hand.
P/I/S co-location is a classic architecture for a small enterprise
network. (It now seems that the Mobicents CSCF will follow it for
initial development,as a consensus seems to have reached).
Many also co-locate the P and S-CSCF to improve intra-domain IMS
session throughput and keeping the border proxy separate (I-CSCF).
(However intra-domain calls in any practical deployment don't even
account for 1% of the total traffic. So i find it useless).
Some vendors co-locate the P and I-CSCF to avoid the call processing
overheads of the S-CSCF (Serving CSCF it is a potential network
bottleneck). This configuration appeals to those vendors who implement
the border gateways (I-BCF and A-BGF) as part of the I-CSCF and P-CSCF
respectively.
Co-location of the I and S-CSCF is the most beneficial of the
combinations given above. All incoming IMS sessions (terminating) as
well as originating IMS sessions and registrations benefit from it in
terms of reduced latency. However, this combination is a very 'deadly'
single point of failure. If this co-located I/S-CSCF node goes down,
all new registrations, and originating/terminating IMS sessions are
affected in the downtime.
Finally, for large geographically distributed highly available
deployments involving multiple carriers and many operating circles,
keeping the P,I and S-CSCFs separate is the most feasible choice and
the safest.
This is my thought process about co-location and distribution :)
aayush
On Feb 20, 10:30 pm, Ivelin Ivanov <ivelin.atanasoff.iva...@gmail.com>
wrote:
> possible.
>
> Ivelin
>
>
>
>
> > On Fri, Feb 20, 2009 at 8:46 AM, aayush <abhatnagar192...@gmail.com>
>
> read more »
rajat
link for it?
sincerely
Rajat T
>
> read more »
Bartosz Baranowski
We are currently creating it. So right nwo there is no link. Should popup shortly. It will be annopunced for sure so just stay on track with mc-public list or forums.
Raziya Bhayani
I had made changes to the sip-services's RegistrarSbb's code.
Thanks and regards,
Raziya
aayush
>and this goal was missed from last week meeting.
http://linux.softpedia.com/get/Internet/DNS/Dual-DHCP-DNS-Server-7767.shtml
It does not need the creation of zone files.
aayush
On Feb 21, 5:03 pm, Bartosz Baranowski <baran...@gmail.com> wrote:
> Hi Rajat
> We are currently creating it. So right nwo there is no link. Should popup
> shortly. It will be annopunced for sure so just stay on track with mc-public
> list or forums.
>
>
> read more »