sean-cc / jain-slee Goto Github PK

...

Development of the new HTTP Client RA.

Issue 20 introduces stats to show the size of the SLEE Event Router working 
queues, which need to be exposed in the CLI.

TC-NOTICE occures when SCCP returns SCCP message (or it's segment) if SCCP can 
not deliver it.
Then TCAP tried to decode a message and extract transactionId to recognize 
which dialog it refers
We can get a dialog if it is a first part of SCCP segment and a Dialog has not 
been released (for example after sending TC-END a dialog is released)
Other info that TC-NOTICE carries is SCCP calling and called parties addresses 
and a cause why the message has not delivered
Even if we can not obtain a dialog SCCP addresses and cause can help us to make 
some administartive actions for example for rerouting messages
So it looks like that Dialog absence is an ordinary case in TC-NOTICE

But in TCAP RA layer we need a non-null Dailog for TCAPDialogWrapper creating 
and if dialog==null we will have an Exception here.
We need to fix somehow this.

What steps will reproduce the problem?

1. Root SBB creates a child SBB in an event handler.
2. Root SBB invokes a method exposed via child's SBB Local Object interface.
3. Child saves state in SBB Object's member variables and expects to persist 
the updates in sbbStore.

What is the expected output? What do you see instead?

After completion of the invoked child LO method and event handler of the root 
SBB (thus event routing), both root SBB and child SBB should be stored and 
passivated.

Currently, child SBB is only passivated: SBB object assigned to child SBB is 
returned to the pool without synchronizing the object's state with the child 
SBB entity's persistent state. Any updates to assigned SBB object's member 
variables that would be persisted in sbbStore will be lost.


What version of the product are you using? On what operating system?

Mobicents JAIN SLEE version 2.7.0.FINAL. OS - GNU/Linux.

Please provide any additional information below.

Attachments:
- service project to triage the issue;
- log4j config enabling relevant SBB notification sources;
- log file fragment with the issue exposed;
- log file fragment demonstrating the fix;
- patch.

Testing:
build and deploy the attached service and watch the log. To re-run the test - 
trigger redeployment:
"""
$ touch 
$JBOSS_HOME/server/default/deploy/ChildSbbPersistenceLifecycleTest-DU-1.0.jar
"""

What steps will reproduce the problem?
1. Create an EclipSLEE project.
2. Examine indentation levels of pom.xml's, SLEE descriptors, Java source files.

What is the expected output? What do you see instead?
Expected - uniform indentation (character and width).
Actual: pom.xml's use 2 spaces, SLEE descriptors use 4 spaces, Java source 
files use 1 tab.

What version of the product are you using? On what operating system?
EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6

Please provide any additional information below.
The best solution would be not only to use the same indentation style for all 
generated files but to better integrate with Eclipse by reusing the indentation 
settings defined in
Window -> Preferences -> General -> Editors -> Text Editors. Without that users 
working on projects with strict coding style policies would still be forced to 
manually fix indentation (with eclipse aids of Ctrl+Shift+F and the like, but 
it's still a pointless waste of time), which is tedious because it would have 
to be done every time a given resource is regenerated (adding a dependency to 
project regenerates pom.xml, adding an event to SBB regenerates sbb-jar.xml, 
etc.).

Due to mobicents parent defined as 2.23 previous ri version is taken and not 
the NIO.
parent should be set to 2.24 to allow work with NIO RI.

What steps will reproduce the problem?
1. Have a client send an INVITE and an Sbb responding to that, creating a 
dialog activity and attaching to it.
2. Have the client wait longer than 64*T1 before sending an ACK.
3. The ACK will be silently ignored and the dialog terminated. The Sbb is not 
aware of this situation.

What is the expected output? What do you see instead?
According RFC, a dialog timing out should prompt the sending of a BYE toward 
the client. When the dialog timeout is send as an event toward the Sbb this 
will give it the opportunity to respond to this, cleanup resources and send a 
BYE.

Please use labels and text to provide additional information.
Problem appears in 2.7.0.FINAL of sip-ra.
The JAIN-SIP stack already has provisions for this with the introduction of the 
SipListenerExt class.

See also: 
https://groups.google.com/forum/?fromgroups=#!topic/mobicents-public/glINr38U94Q

Aggregation of issues related with release of Telscale SLEE SIP 6.1.2.GA

What steps will reproduce the problem?
1. Fire a SIP INVITE to the RA.
2. Let it immediately be followed by a CANCEL (before any responses)
3. Observe the exception and stackdump.

What is the expected output? What do you see instead?
Expect the CANCEL to be fired on same activity the INVITE came in on.
I see the observed stackdump instead (see the attached server.log part)

What version of the product are you using? On what operating system?
2.7.0.FINAL on Windows.

Please provide any additional information below.

Hi,

recently we have been working on a tool that would facilitate creation of 
sbb-jar.xml descriptor basing on annotations. Generally speaking, it scans the 
source code looking for annotations, and basing on them the sbb-jar.xml file is 
created.

Main features:
 - all JSA's annotations have source code retention
 - uses Java 6 annotation processing library
 - easy to use (annotations and optionally configuration file)


In attachment there is the complete source code (with examples) and a PDF with 
documentation.


We would like to find out if other users would find it useful, so thank you for 
all your feedback.

Best regards,
Jakub Wachowski
AMG.net

TLS is not allowed in transports list
Also multiple entities are not allowed for same ip address.
Diff file is attached

There is a little mistake in event-jar.xml in CAP RA.

The correct is <event-definition> tag not <event-type-ref> tag for the new GPRS 
messages

ClientTransactionExt, ServerTransactionExt - those are needed for determining 
the physical address of remote side.

Also there are RequestEventEx and ResponseEventEx, those might make sense too.

The wrappers right now hide those and you can not cast to the extended 
interface. 

For example, instead of:

public class ServerTransactionWrapper extends TransactionWrapper implements 
ServerTransaction {

this should do it:

public class ServerTransactionWrapper extends TransactionWrapper implements 
ServerTransactionExt {


Further there is Mobicents extensitions 
http://code.google.com/p/jain-sip/source/browse/src/main/java/gov/nist/javax/sip
/stack/MobicentsSIPServerTransaction.java?repo=ext with setRetransmitTimer and 
such methods, but that would introduce more dependencies. 

Aggregation of issues related with release of Telscale SLEE Diameter 6.1.2.GA

What steps will reproduce the problem?
1. File -> Import... 
2. Select Other -> JAIN SLEE Components
3. Click Next.

What is the expected output? What do you see instead?
Expected
--------
Import wizard start.

Actual
------
"Problem Occurred" dialogue with the following details
"""
The selected wizard could not be started.
Plug-in org.mobicents.eclipslee.servicecreation was unable to load class 
org.mobicents.eclipslee.servicecreation.importing.wizard.ImportSLEEComponentsWiz
ard.
org.mobicents.eclipslee.servicecreation.importing.wizard.ImportSLEEComponentsWiz
ard
"""

What version of the product are you using? On what operating system?
EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6

Aggregation of issues related with release of Telscale SLEE SS7 6.1.2.GA

What steps will reproduce the problem?
1. Generate a high load on a diameter Ro client application in clustered 
configuration
2. Start a new Diameter Activity, send InitialRequest
3. If the load is high and the Diameter server responses fast it happens that 
on response we get:
java.lang.IllegalStateException: No activity for handle: Diameter Session 
ID[inscp-diameter;316;2038060368]
    at org.mobicents.slee.resource.diameter.ro.DiameterRoResourceAdaptor.fireEvent(DiameterRoResourceAdaptor.java:608)


Despite we used the activity for sending out request and not doing antyhing in 
meantime. It seems that under high load 
AbstractClusteredDiameterActivityManagement waits some time before putting 
activity into activities, thus if the answer comes to quick Ro RA cannot find 
activity 


What is the expected output? What do you see instead?
The requests should be sent after activity initiation is done

What version of the product are you using? On what operating system?
510a9a107f32b8b559d2ea60784a535c0ef3babd

Please provide any additional information below.
It may be somehow related with the way clustered activities are managed.

CAP RA has filter which forces RA to not fire DIALOG_TIMEOUT event if no 
services are consuming this event.

This cause Dialog to never die as in RA capDialog.keepAlive() is called.

Generated pom.xml's use deprecated properties ${pom.artifactId} and 
${pom.version}.

What steps will reproduce the problem?
1. Create a new JAIN SLEE project with all settings left to default values.
2. Run clean package goals.

What is the expected output? What do you see instead?
Expected
--------
Successful build with no warnings.

Actual
------
Build succeeds with the following warnings
"""
WARNING] Some problems were encountered while building the effective model for 
org.mobicents:TestService-sbb:jar:1.0
[WARNING] The expression ${pom.artifactId} is deprecated. Please use 
${project.artifactId} instead.
[WARNING] The expression ${pom.version} is deprecated. Please use 
${project.version} instead.
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.mobicents:TestService-DU:jar:1.0
[WARNING] The expression ${pom.artifactId} is deprecated. Please use 
${project.artifactId} instead.
[WARNING] The expression ${pom.version} is deprecated. Please use 
${project.version} instead.
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.mobicents:TestService:pom:1.0
[WARNING] The expression ${pom.artifactId} is deprecated. Please use 
${project.artifactId} instead.
[WARNING] The expression ${pom.version} is deprecated. Please use 
${project.version} instead.
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
"""

What version of the product are you using? On what operating system?
EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6

Add docs for TCAP RA

Failure is caused by a reference to
http://www.mobicents.org/slee/dtd/deploy-config_1_1.dtd
in
du/src/main/resources/META-INF/deploy-config.xml
resulting in HTTP GET to www.mobicents.org on deployment, which fails with 
confusing errors ("java.net.ConnectException: Connection refused" - quite 
strange if the RA is not supposed to connect anywhere, even more strange if the 
RA would connect to a local resource that is actually available; 
"java.util.zip.ZipException: error in opening zip file" - also confusingly 
meaningless here as the archive is intact) in case internet access is not 
available.

What steps will reproduce the problem?
1. Create a RA with all the necessary modules so that it deploys successfully 
(on a machine with internet access).
2. Deploy the RA to a machine without internet access (or make 
www.mobicents.org inaccessible using hosts file, updating kernel routing table, 
bringing down network interface, unplugging the cable, etc.)

What is the expected output? What do you see instead?
Expected successful deployment, actual - failure to deploy the RA with errors 
in the attached log excerpt.

What version of the product are you using? On what operating system?

EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6


Please provide any additional information below.

Trivial workaround - remove the DTD reference from deploy-config.xml. However, 
I think this should be considered a serious issue as the target environments of 
SLEE applications are typically isolated from the outside world, so the 
developers would be getting the unpleasant surprise of their RAs working 
everywhere except the target environment.

When viewing the TTL value for activities through web console, the value is 
always <= 0, while it should be >= 0.

(Reported in forum thread 
https://groups.google.com/d/topic/mobicents-public/N-zPPqnJk9o/discussion)

There is a little bug at addCheckImeiRequest_Huawei.
The method invoked at wrappedDialog is wrong. Should be: 
return this.wrappedDialog.addCheckImeiRequest_Huawei(imei, 
requestedEquipmentInfo, extensionContainer, imsi);

MAP RA has filter which forces RA to not fire DIALOG_TIMEOUT event if no 
services are consuming this event.

This cause Dialog to never die as in RA mapDialog.keepAlive() is called.

What steps will reproduce the problem?
1. Deploy the 2.1.0.FINAL plugin inside the plugins folder
2. Create a new JAIN SLEE project
3. Create a SBB class
4. Try to create a SLEE service associated with the SBB
5. A null pointer exception arises which bars you from creating the service 
description.

What is the expected output? What do you see instead?
The expected output is the creation of the service.xml for the service, but 
instead the NPE bars you from reaching this point in the wizard.

What version of the product are you using? On what operating system?
JAIN SLEE 2.6.0, Eclipse Indigo SR2, OpenJDK 7, Ubuntu Linux 12.04.LTS, 
EclipSLEE 2.1.0.FINAL

Please provide any additional information below.

Add docs for CAP RA

MGCP driver ( mgcp-impl ) old release did not behave well under high 
load.Responses/messages received by client where skipped and therefore requests 
where resent , which causes a lot of mess in network.

Revision 14305fc37e2c in mms 
http://code.google.com/p/mediaserver/source/detail?r=14305fc37e2cc0d7626a604c833
d19c4cda2f287

updated the mgcp driver.
So mgcp ra should work with mgcp-driver-3.0.0.FINAL

Upgrade TCAP, MAP and CAP RA to use latest API's of stack - getLocalDialogId / 
getRemoteDialogId 

What steps will reproduce the problem?
1. Trying to follow the 
https://community.jboss.org/wiki/HelloSLEEWorldServiceJAINSLEETutorial

I have encountered all the problems and got to the exception thrown when 
creating the DU service event similar to this 
http://code.google.com/p/jain-slee/issues/detail?id=5

I tried installing the latest software but eclipse says a newer version is 
already installed 
http://hudson.jboss.org/hudson/view/Mobicents/job/Mobicents-EclipSLEE/lastSucces
sfulBuild/artifact/



Eclipse version

Eclipse Java EE IDE for Web Developers.
Version: Juno Service Release 1
Build id: 20120920-0800

Slee version

mobicents-jainslee-2.7.0.FINAL-jboss-5.1.0.GA

eclipse slee plugin
org.mobicents.eclipslee.servicecreation_2.1.0.FINAL.jar

2.
3.

What is the expected output? What do you see instead?

Same error output as below




Please use labels and text to provide additional information.

Aggregation of issues wrt development of Telscale SLEE RA MAP 6.1.2.GA

What steps will reproduce the problem?
1. Create an EclipSLEE project.
2. Add an external library as dependency to a module's pom.xml
3. Add a reference to a class from the external library in a source file within 
the module.

What is the expected output? What do you see instead?
Expected - Eclipse classpath updated automatically, no errors shown.
Actual - classpath not updated, Eclipse shows an error (cannot resolve the 
class), even though maven build is successful.


What version of the product are you using? On what operating system?
EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6


Please provide any additional information below.
A workaround is to add an additional dependency using the context menu, which 
updates the .classpath to include the library that has been added by directly 
editing pom.xml. The redundant dependency can then be removed, the dependency 
that has been manually included into pom.xml remains in .classpath. This forces 
doing unnecessary manual actions and regenerates pom.xml potentially 
introducing false differences with VCS (indentation, line wrapping).

Automatic .classpath updating after editing a pom.xml works fine for standard 
maven projects (non-EclipSLEE) using the aforementioned versions of Eclipse and 
m2e.

ML thread: 
https://groups.google.com/forum/?fromgroups#!topic/mobicents-public/s315O1b2Ubg

Add stats wrt the activity queue manager and the size of the queue for each 
event router thread.

Implement TCAP RA based on jSS7 TCAP Stack

Expose SLEe Event Router stats in the web console

...

Someone changed the password, create a new account, update sbb's xml & docs

Create a REST Client enabler that uses the new HTTP Client NIO RA.

Use of mobicents-parent POM as the parent for projects created using EclipSLEE 
brings in lots of redundant configuration.

What steps will reproduce the problem?
1. Create a new project using EclipSLEE.
2. Examine effective POM
$ mvn help:effective-pom

What is the expected output? What do you see instead?
Expected: POM including only the necessary configuration for this type of 
project.

Actual: effective POM includes a lot of configuration that is only applicable 
for the projects that are part of Mobicents (developers, license, scm, 
issueManagement, URL, 272 dependencies, ...), resulting in approx. 2.5k lines 
per module for a newly created project.

What version of the product are you using? On what operating system?
EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6

In professional environments users would most probably want to define their own 
parent POM for EclipSLEE projects (e.g. with configuration specific to their 
company) extending a minimal generic parent for EclipSLEE projects (instead of 
currently used huge mobicents-parent as described in issue #35). EclipSLEE 
should allow configuring (Window -> Preferences -> Mobicents EclipSLEE) what 
parent should be used in generated projects. Possibly with a chance to change 
it in the project creation wizard but this isn't necessary as parent could be 
changed easily in a single location of the top level module's pom.xml.

groupId "org.mobicents" is only applicable to Mobicents projects. Project 
creation wizard should allow setting a groupId, allowing to configure a default 
value or remembering last used value.

What version of the product are you using? On what operating system?
EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6

Complete CAP RA for newly implemented GPRS Operations (V3)

Reported by yudhihutama, Nov 1, 2012 
(http://code.google.com/p/mobicents/issues/detail?id=3260)

What steps will reproduce the problem?
1.Create AVP 

CreditControlClientSession session = ccaProvider.createClientSession();
CreditControlAVPFactory avpFactory = session.getCCAAvpFactory(); 
ActivityContextInterface localACI = 
ccaACIF.getActivityContextInterface(session);
localACI.attach(this.getSbbContext().getSbbLocalObject());
CreditControlRequest request = session.createCreditControlRequest();
List<DiameterAvp> avps = new ArrayList<DiameterAvp>();

avps.add(avpFactory.getBaseFactory().createAvp(Avp.CC_REQUEST_TYPE, 4));
avps.add(avpFactory.getBaseFactory().createAvp(Avp.CC_REQUEST_NUMBER, 0l));
avps.add(avpFactory.getBaseFactory().createAvp(Avp.REQUESTED_ACTION,0));

2. Put AVPList in Request
request.setExtensionAvps(avps.toArray(new DiameterAvp[avps.size()]));

3. Send CCR Request
session.sendCreditControlRequest(request);

What is the expected output? What do you see instead?
20:51:38,958 INFO  [DiameterCCAResourceAdaptor] (pool-29-thread-1) Activity 
started [Diameter Session ID[127.0.0.1;314;3156828783]]
20:51:39,005 INFO  [CreditControlSessionFactory] (pool-29-thread-1) Diameter 
CCA SessionFactory :: stateChanged :: 
source[org.jdiameter.client.impl.app.cca.ClientCCASessionImpl@22e89a5a] :: 
oldState[IDLE], newState[PENDING_EVENT]
20:51:39,005 ERROR [STDERR] (pool-29-thread-1) java.io.IOException: Failed to 
send message, due to: org.jdiameter.api.InternalException: 
java.lang.ClassCastException: org.jdiameter.client.impl.parser.MessageImpl 
cannot be cast to org.jdiameter.common.impl.app.AppEventImpl
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
org.mobicents.slee.resource.diameter.cca.CreditControlClientSessionImpl.sendCred
itControlRequest(CreditControlClientSessionImpl.java:130)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
com.xl.DiameterSbb.doSendEventCCR(DiameterSbb.java:146)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
com.xl.DiameterSbb.onServiceStartedEvent(DiameterSbb.java:215)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
java.lang.reflect.Method.invoke(Method.java:597)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
org.mobicents.slee.runtime.sbbentity.SbbEntityImpl.invokeEventHandler(SbbEntityI
mpl.java:481)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
org.mobicents.slee.runtime.eventrouter.routingtask.EventRoutingTaskImpl.routeQue
uedEvent(EventRoutingTaskImpl.java:379)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
org.mobicents.slee.runtime.eventrouter.routingtask.EventRoutingTaskImpl.run(Even
tRoutingTaskImpl.java:126)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
org.mobicents.slee.runtime.eventrouter.EventRouterExecutorImpl$EventRoutingTaskS
tatsCollector.run(EventRouterExecutorImpl.java:73)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:8
85)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
20:51:39,005 ERROR [STDERR] (pool-29-thread-1)  at 
java.lang.Thread.run(Thread.java:619)


What version of the product are you using? On what operating system?
Diameter-base-2.7 Final
Diameter-CCA-2.7 Final
JANSLEE 2.7 Final
DiameterMux 1.4 Final

Aggregation of issues related with release of Telscale SLEE HTTP 6.1.2.GA

What steps will reproduce the problem?

1. Configure two RA entities with different link names (JDBC RA example):
<ra-entity
 resource-adaptor-id="ResourceAdaptorID[name=JdbcResourceAdaptor,vendor=org.mobicents,version=1.0]"
    entity-name="test_entity_1">
    <properties/>
    <ra-link name="TestRaOne" />
</ra-entity>
<ra-entity
 resource-adaptor-id="ResourceAdaptorID[name=JdbcResourceAdaptor,vendor=org.mobicents,version=1.0]"
    entity-name="test_entity_2">
    <properties/>
    <ra-link name="TestRaTwo" />
</ra-entity>

2. Create a service with two SBBs(e.g root & child) each of them respectively 
binding to a single RA entity defined in previous step.
Use identical resource-adaptor-object-name for both (e.g. 
"slee/resources/jdbc/1.0/sbbinterface").

// for SBB1
    <resource-adaptor-entity-binding>
 <resource-adaptor-object-name>slee/resources/jdbc/1.0/sbbinterface</resource-adaptor-object-name>
 <resource-adaptor-entity-link>TestRaOne</resource-adaptor-entity-link>
    </resource-adaptor-entity-binding>

// for SBB2
    <resource-adaptor-entity-binding>
 <resource-adaptor-object-name>slee/resources/jdbc/1.0/sbbinterface</resource-adaptor-object-name>
 <resource-adaptor-entity-link>TestRaTwo</resource-adaptor-entity-link>
    </resource-adaptor-entity-binding>

3. Do a context lookup for RA entity in each of the SBBs and check if the 
entity bound is the same as specified in descriptor.
(e.g. check entity name)

Context ctx = (Context) new InitialContext().lookup("java:comp/env");
ra = (JdbcResourceAdaptorSbbInterface) 
ctx.lookup("slee/resources/jdbc/1.0/sbbinterface");
// ... code to check RA entity name here ...

What is the expected output? What do you see instead?

Every SBB should receive it's own bound entity (SBB1 - "test_entity_1", SBB2 - 
"test_entity_2").
However SBB2 receives "test_entity_1" (the same entity as the first one). This 
behaviour is wrong based on
Jain SLEE 1.1 specs - section 6.13.3.1.2, page 90. Different SBB contexts 
should be isolated.
A service reproducing this issue is attached. The output produced by the 
service is:

12:15:18,260 INFO  [HDScanner] Activated 
ServiceID[name=TestService,vendor=Company,version=1.0]
12:15:19,515 INFO  [RootSbb] Root SBB active, ra entity name = test_entity_1
12:15:19,531 INFO  [ChildSbb] Child RA entity name = test_entity_1
12:15:19,531 ERROR [ChildSbb] Child RA entity expected: test_entity_2, but 
received: test_entity_1 

What version of the product are you using? On what operating system?
Linux, Windows, Mobicents 2.7.0 FINAL

(This issue is a continuation from 
http://code.google.com/p/mobicents/issues/detail?id=3038)

When trying to set (or cancel) an ActivityRemoveTimer in a clustered 
environment, an exception is thrown causing it to fail up to the application.

The cause of the exception is due to a not configured FT Timer instance. While 
this should and will be fixed, the exception should be catched and should not 
be propagated to the application.

What steps will reproduce the problem?
1. Change into Mobicents JAIN SLEE home directory (any directory other than 
<mobicents_home>/tools/twiddle would do).
2. Invoke twiddle.

What is the expected output? What do you see instead?
Expected

"""
$ tools/twiddle/twiddle.sh activity -c
2
"""

Actual

"""
$ tools/twiddle/twiddle.sh activity -c
Exception in thread "main" java.lang.NoClassDefFoundError: 
org/jboss/console/twiddle/Twiddle
Caused by: java.lang.ClassNotFoundException: org.jboss.console.twiddle.Twiddle
    at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:334)
Could not find the main class: org.jboss.console.twiddle.Twiddle. Program will 
exit.
"""

What version of the product are you using? On what operating system?
Mobicents JAIN SLEE 2.7.0.FINAL, Debian GNU/Linux.

...

Aggregation of issues related with release of Telscale SLEE Core 6.1.2.GA

A customer reported NPE occurring on a ServerTransactionWrapper#toString().

http://code.google.com/p/jain-slee/wiki/Start2SipResourceAdaptors