simulap / simulap-plugin-sip Goto Github PK

Description

The list of SIP headers proposed by the SIP sampler GUI to help the test developers is read from a file. The file is named SipHeadersGUIDictionary.xml.
It is located under /etc/opt/OC/hpocsip/ by default and this path can be overwritten by the global property simulap.sip.dictionary.path.

If the file is not reachable, the Sampler GUI fails.

Motivation and Context

• Project context:
• SIMULAP version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

Our media calls uses STUN, ICE, and DTLS while doing media. What is the plan to add STUN, ICE, and DTLS protocol to this plugin so we succeed in the call connectivity between JMeter and the Media Server.
SIP carrying SDP info is getting signaling connectivity but our media connections are failing for lack of STUN probe support.

Motivation and Context

• JMeter version:
• Plugin version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

The following property is used as a cleanup period :
sip.cleanQueuesPeriod=5000
The default value is 5000
When this period is less than the reception timeout, reception queue is deleted , then created again by the sip node. As a consequence, there is no more any thread synchronisation on this queue object.

Motivation and Context

• Project context:
• SIMULAP version: 1.9.0
• Operating System version: Rhel6

No impact because of a work-around. Just increase sip.cleanQueuesPeriod so as to be greater than reception timeout.

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

Hello

When I first tried to load this scenario file, I had errors on "org.apache.jmeter.protocol.sip.config.SipNodeElement".
I applied hints on issue #26 (#26 (comment)) replacing all occurrences of org.apache.jmeter with com.hpe.simulap.
This solution worked for SITtest1_server.jmx : I succeded to load it in JMeter with plugin simulap.

I applied this change on SIPtest1_client as the same error was occuring.
However, the SIPtes1_client still does not load.
It generates another error "CannotResolveClassException: com.hpe.simulap.modifiers.hp.KeyConfig"

label : bug

Motivation and Context

• JMeter version: 5.5
• Plugin version: 1.10.1
• Operating System version: Windows10

Steps to reproduce the problem (if appropriate)

Resources

The complete error message displayed in the popup is:

`Problem loading XML from:'...\simulap-plugin-sip\scenario\tutorials\SIPtest1_client.jmx'.
Cause:
CannotResolveClassException: com.hpe.simulap.modifiers.hp.KeyConfig

Detail:com.thoughtworks.xstream.converters.ConversionException:
---- Debugging information ----
cause-exception : com.thoughtworks.xstream.converters.ConversionException
cause-message :
first-jmeter-class : org.apache.jmeter.save.converters.HashTreeConverter.unmarshal(HashTreeConverter.java:66)
class : org.apache.jmeter.save.ScriptWrapper
required-type : org.apache.jmeter.save.ScriptWrapper
converter-type : org.apache.jmeter.save.ScriptWrapperConverter
path : /jmeterTestPlan/hashTree/hashTree/hashTree[21]/com.hpe.simulap.modifiers.hp.KeyConfig
line number : 5300
version : 5.5

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

new parameters added to Configuring SIP nodes

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

ALM CR #37436
the SipNode is enabled with Outbound Proxy and after receiving 200 OK .
the SipNode removes the Route header from the SIP stack if SIP Node Outbound Proxy enabled and explicitly added Route header from UI is not sent.
Here problem is explicitly added Route header in SipCommandSampler for ACK not sent.

Observation : SIP plugin 1.9.0 version is working fine and SIP plugin latest version above scenario is not working.

Motivation and Context

• Project context:
• SIP plugin version: 1.9.0 vesrion and patch : simulap_dtag_1.9.0_P2
• Operating System version:
  RHEL6.X

Steps to reproduce the problem (if appropriate)

1. Enable SIP Node with Out Bound Proxy.
2. Send INVITE from the sip node and received 200 OK for the same.
3. Extract the Record-Route from 200 OK using Regular expression post Processor
4. In SipCommandSampler with ACK message and add Request Header as Route headers values from regular expression post Processor

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

sic.

Motivation and Context

• Project context:
• SIMULAP version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

I'm getting the Exception (file with stacktrace attached & excerpt posted below) when I start JMeter with the Simulap plugin as per the instructions in the Readme.

Excerpt:

2020-05-14 14:24:21,969 ERROR o.a.j.JMeter: Failure loading test file
java.lang.IllegalArgumentException: Problem loading XML from:'C:\Users\userX\Documents\Tools\simulap-plugin-sip-master\tests\SIPtestsGlobal.jmx'. 
Cause:
CannotResolveClassException: org.apache.jmeter.protocol.sip.config.SipNodeElement

 Detail:com.thoughtworks.xstream.converters.ConversionException: 
---- Debugging information ----
cause-exception     : com.thoughtworks.xstream.converters.ConversionException
cause-message       : 
first-jmeter-class  : org.apache.jmeter.save.converters.HashTreeConverter.unmarshal(HashTreeConverter.java:67)
class               : org.apache.jmeter.save.ScriptWrapper
required-type       : org.apache.jmeter.save.ScriptWrapper
converter-type      : org.apache.jmeter.save.ScriptWrapperConverter
path                : /jmeterTestPlan/hashTree/hashTree/org.apache.jmeter.protocol.sip.config.SipNodeElement
line number         : 208
version             : 5.2.1
-------------------------------
	at org.apache.jmeter.save.SaveService.readTree(SaveService.java:459) ~[ApacheJMeter_core.jar:5.2.1]
	at org.apache.jmeter.save.SaveService.loadTree(SaveService.java:432) ~[ApacheJMeter_core.jar:5.2.1]
	at org.apache.jmeter.JMeter.startGui(JMeter.java:411) [ApacheJMeter_core.jar:5.2.1]
	at org.apache.jmeter.JMeter.start(JMeter.java:545) [ApacheJMeter_core.jar:5.2.1]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_241]
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_241]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_241]
	at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_241]
	at org.apache.jmeter.NewDriver.main(NewDriver.java:253) [ApacheJMeter.jar:5.2.1]
Caused by: com.thoughtworks.xstream.converters.ConversionException: 
---- Debugging information ----
cause-exception     : com.thoughtworks.xstream.converters.ConversionException
cause-message       : 
first-jmeter-class  : org.apache.jmeter.save.converters.HashTreeConverter.unmarshal(HashTreeConverter.java:67)
class               : org.apache.jmeter.save.ScriptWrapper
required-type       : org.apache.jmeter.save.ScriptWrapper
converter-type      : org.apache.jmeter.save.ScriptWrapperConverter
path                : /jmeterTestPlan/hashTree/hashTree/org.apache.jmeter.protocol.sip.config.SipNodeElement
line number         : 208
version             : 5.2.1
-------------------------------

Can't add labels, sorry.
bug

Motivation and Context

• JMeter version: 5.2.1
• Plugin version: 19.04
• Operating System version: Windows 10 Pro

Steps to reproduce the problem (if appropriate)

Starting JMeter with the command mvn -X install -Djmeter.command=JMETER_HOME/bin/jmeter

Resources

simulapException.txt

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

Logger migration to slf4j for all simulap components : SIP

Motivation and Context

• Project context:
• SIMULAP version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

This issue follows up HGH/simulap-support#54 issue:
if debuglevel and/or stackloglevel paramters are not set into .jmx files as User Defined Variable, node instanciation fails.

Motivation and Context

• Project context:
• SIMULAP version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

When attempting to build simulap-plugin-sip, there is a build error after calling > mvn -X clean package .
The error message reads:
Failed to execute goal on project simulap-plugin-sip: Could not resolve dependencies for project com.hpe.simulap:simulap-plugin-sip:pom:1.8.0-0.0: The following artifacts could not be resolved: javax.sip:jain-sip-api:jar:1.2.0-3, javax.sip:jain-sip-ri:jar:1.2.234.2-hpe-1: Could not find artifact javax.sip:jain-sip-api:jar:1.2.0-3 in central (https://repo.maven.apache.org/maven2)

Motivation and Context

• Project context:
• SIMULAP version: 1.0
• Operating System version: Windows 10 enterprise

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 28.114 s
[INFO] Finished at: 2019-10-31T17:50:51+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on project simulap-plugin-sip: MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - error: error reading C:\Users\i2265.m2\repository\net\java\dev\jna\jna\4.1.0\jna-4.1.0.jar; invalid LOC header (bad signature)
[ERROR]
[ERROR] Command line was: "C:\Program Files\Java\jdk1.8.0_191\jre..\bin\javadoc.exe" @options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in 'C:\Users\i2265\Downloads\simulap-plugin-sip-master\target\apidocs' dir.
[ERROR]
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on project simulap-plugin-sip: MavenReportException: Error while generating Javadoc:
Exit code: 1 - error: error reading C:\Users\i2265.m2\repository\net\java\dev\jna\jna\4.1.0\jna-4.1.0.jar; invalid LOC header (bad signature)

Command line was: "C:\Program Files\Java\jdk1.8.0_191\jre..\bin\javadoc.exe" @options @packages

Refer to the generated Javadoc files in 'C:\Users\i2265\Downloads\simulap-plugin-sip-master\target\apidocs' dir.

at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

Caused by: org.apache.maven.plugin.MojoExecutionException: MavenReportException: Error while generating Javadoc:
Exit code: 1 - error: error reading C:\Users\i2265.m2\repository\net\java\dev\jna\jna\4.1.0\jna-4.1.0.jar; invalid LOC header (bad signature)

Command line was: "C:\Program Files\Java\jdk1.8.0_191\jre..\bin\javadoc.exe" @options @packages

Refer to the generated Javadoc files in 'C:\Users\i2265\Downloads\simulap-plugin-sip-master\target\apidocs' dir.

at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.failOnError (AbstractJavadocMojo.java:6202)
at org.apache.maven.plugins.javadoc.JavadocJar.doExecute (JavadocJar.java:194)
at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute (AbstractJavadocMojo.java:1912)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

Caused by: org.apache.maven.reporting.MavenReportException:
Exit code: 1 - error: error reading C:\Users\i2265.m2\repository\net\java\dev\jna\jna\4.1.0\jna-4.1.0.jar; invalid LOC header (bad signature)

Command line was: "C:\Program Files\Java\jdk1.8.0_191\jre..\bin\javadoc.exe" @options @packages

Refer to the generated Javadoc files in 'C:\Users\i2265\Downloads\simulap-plugin-sip-master\target\apidocs' dir.

at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeJavadocCommandLine (AbstractJavadocMojo.java:5298)
at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport (AbstractJavadocMojo.java:2134)
at org.apache.maven.plugins.javadoc.JavadocJar.doExecute (JavadocJar.java:190)
at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute (AbstractJavadocMojo.java:1912)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

ALM CR ID : 36896 - In dialog REFER and NOTIFY is not supported in simulap.

Description

REFER and NOTIFY messages are always sent over out Dialog.

Motivation and Context

• Project context:
• SIMULAP version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

1. execute attached jmx on simulap 1.8.0
   In dialog REFER is not supported in simulap
   200 OK of INVITE
   Response message: Success. received response : SIP/2.0 200 OK
   CSeq: 1 INVITE
   Call-ID: [email protected]
   From: sip:bill-@test-network;tag=usoi8u92eb
   To: sip:john-@test-network;tag=a5dacbd5

in the REFER message not adding the to tag
Response message: REFER sip:john-@test-network SIP/2.0
Call-ID: [email protected]
CSeq: 2 REFER
From: sip:bill-@test-network;tag=cmpg9v2e67
To: sip:john-@test-network

NOTIFY messages also not sent in dialog

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

SIP stack issue with multiple PANI headers requires to be updated

Motivation and Context

• Project context:
• SIMULAP version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

Motivation and Context

• Project context:
• SIMULAP version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.

Description

An exception is triggered because the SipNodeelement doesn't find its related resource bundle:

Localized strings not available for bean class org.apache.jmeter.protocol.sip.config.SipNodeElement java.util.MissingResourceException: Can't find bundle for base name org.apache.jmeter.protocol.sip.config.SipNodeElementResources, locale en_US

Motivation and Context

• Project context: N/A
• Plugin version: 1.8.0
• Operating System version: N/A

Steps to reproduce the problem (if appropriate)

As soon as the plugin is loaded into JMeter...

Resources (if appropriate):

Checklist:

• I have updated the documentation accordingly.
• I give my issue a label.
• I provide the required resources.

Description

I would like to use MvnDebug to debug simulap-plugin-sip while running under JMeter.

When I try to start JMeter with Simulap-plugin-sip with MvnDebug as:
mvndebug -X install -Djmeter.command=C:\Users\michael\apache-jmeter-4.0\bin\jmeter

I get:
Listening for transport dt_socket at address: 8000

But JMeter GUI does not appear.

Is there a way I can get this to work? Setting breakpoints in Eclipse would be a great help to learn how the plug-in works.

See:

• https://docs.alfresco.com/4.2/tasks/dev-extensions-maven-sdk-eclipse-remote-debugging.html
• https://dzone.com/articles/debugging-maven-build-mvndebug

Motivation and Context

• Project context:
• SIMULAP version:
• Operating System version:

Steps to reproduce the problem (if appropriate)

Resources

Checklist

• I have updated the documentation accordingly.
• I give my issue a label.
• I put my issue into Support project.
• I provide the required resources.