addr_out_handler.c(133) No action present. Stop processing addressing - axis2c

I'm just started to use axis2c (rev 1.5 on linux ) and I rewrite a simple service which is a copy of the add functionality of the math service.
It seems all ok but at the end of the procedure, when the service should send back the result of the sum, it report the error "No action present".
I called my service "ctictrlintf" and inside the ctictrlintf_invoke function I get that node with the 2 parameter to add.
Here the content of the node printed using axiom_node_to_string api.
<ns1:test1 xmlns:ns1="http://ws.apache.org/axis2/services/ctictrlintf">
<param1>40</param1>
<param2>8</param2>
</ns1:test1>
At the end of the function ctictrlintf_invoke is returned a nod ewith result of the addiction.
<ns1:result xmlns:ns1="http://axis2/test/namespace1">48</ns1:result>
What happened after that is reported below.
Somewhere in addr_out_handler.c the program reported the error "No action present" and abort the operation.
[debug] phase.c(210) Invoke the handler AddressingOutHandler within the phase MessageOut
[info] Starting addressing out handler
[debug] addr_out_handler.c(133) No action present. Stop processing addressing
[info] Request served in 0.012 seconds
What mean this error and what action should require the library to complete its work ?
Best reagards, Enzo
Added 18.07.2013 16:56
Inside the config file axis2.xml there is still enable the addressing module
<!-- ================================================= -->
<!-- Global Modules -->
<!-- ================================================= -->
<module ref="addressing"/>
and when the server is started the log report some note about the activation of the addressing
[debug] conf_builder.c(234) No custom dispatching order found. Continue with the default dispatching order
[debug] conf_builder.c(379) Module addressing found in axis2.xml
[debug] class_loader.c(140) /usr/local/axis2c/lib/libaxis2_http_sender.so shared lib loaded successfully
[debug] class_loader.c(140) /usr/local/axis2c/lib/libaxis2_http_receiver.so shared lib loaded successfully
[debug] dep_engine.c(1283) axis2_dep_engine_load_module_dll: DLL path is : /usr/local/axis2c/modules/addressing/libaxis2_mod_addr.so
[debug] class_loader.c(140) /usr/local/axis2c/modules/addressing/libaxis2_mod_addr.so shared lib loaded successfully
[debug] dep_engine.c(1283) axis2_dep_engine_load_module_dll: DLL path is : /usr/local/axis2c/modules/logging/libaxis2_mod_log.so
[debug] class_loader.c(140) /usr/local/axis2c/modules/logging/libaxis2_mod_log.so shared lib loaded successfully
[debug] svc_builder.c(318) DLL path is : /usr/local/axis2c/services/ctictrlintf/libctictrlintf.so
[debug] svc_builder.c(318) DLL path is : /usr/local/axis2c/services/echo/libecho.so
[debug] svc_builder.c(318) DLL path is : /usr/local/axis2c/services/math/libmath.so
[debug] phase_holder.c(139) Add handler AddressingInHandler to phase Transport
and the service code already had the following call
/* Create EPR with given address */
endpoint_ref = axis2_endpoint_ref_create(env, address);
/* Setup options */
options = axis2_options_create(env);
axis2_options_set_to(options, env, endpoint_ref);
axis2_options_set_action(options, env, "http://www.aesys.com/axis2/services/ctictrlintf/test1");
/* Set service client options */
axis2_svc_client_set_options(svc_client, env, options);
/* Engage addressing module */
axis2_svc_client_engage_module(svc_client, env, AXIS2_MODULE_ADDRESSING);

This message is produced by addressing module and this is not a error.
Your service has no addressing support and didn't send or receive any addressing-specific headers.
Information about WS-Addressing support in Axis2/C is here.

Related

How to resolve below error-ERROR: Child Process Error: Test runner sel (JUnitTester) has failed with retcode 1

When I ran the selenium script using Taurus and want to convert in JMX then got the error-
10:55:54 ERROR: Child Process Error: Test runner sel (JUnitTester) has failed with retcode 1
10:55:54 ERROR: JUnitTester STDERR:
May 02, 2022 10:55:50 AM com.blazemeter.taurus.junit.CustomRunner main
INFO: Starting: [C:\Users\sss\2022-05-02_10-55-36.435651\runner.properties]
Exception in thread "main" com.blazemeter.taurus.junit.exception.CustomRunnerException: Nothing to test
at com.blazemeter.taurus.junit.CustomRunner.main(CustomRunner.java:54)
How it resolved?
It means that Taurus JUnit Executor failed somewhere somehow, inspect logs in the Artifacts Directory and look for Java/JUnit-related errors there.
Most probably JUnit executor wasn't able to detect any test cases to run, it's impossible to tell for sure what is the root cause without seeing the full logs and your automation code.
Be aware that you can use another approach not involving Taurus, i.e.
Kick off BlazeMeter Proxy Recorder
Configure your tests to use the above recorder as the proxy
Run your tests from IDE or console
The BlazeMeter proxy recorder will capture the requests and convert them into .jmx file (you can also export it as "SmartJMX" with automatic detection and correlation of the dynamic parameters)

Cannot set configuration in Elastic Beanstalk

I have 4 Elastic Beanstalk deployments: 3 are Corretto 8 and the other one is Corretto 11.
On the Corretto 8 deployments, I can set new configuration without issue. On the Corretto 11 instance, however, any attempt to set a new configuration fails and causes a rollback.
The Corretto versions might not be the problem, but it's the only difference I can see. All 4 apps are Spring Boot apps that run as web servers (i.e embedded tomcat with exposed web ports). I am trying to set the exact same configuration name and value, and it only fails on the one instance.
The configuration I'm trying to set is pretty simple:
VALIDATE_RENEWALS = true
Even just trying to set DEBUG = true causes a failure and rollback.
I don't see a lot of information from the console about what's failing. Here is the event log:
2020-03-16 13:55:17 UTC-0600 INFO The environment was reverted to the previous configuration setting.
2020-03-16 13:54:45 UTC-0600 ERROR During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.
2020-03-16 13:54:45 UTC-0600 ERROR Failed to deploy configuration.
2020-03-16 13:54:45 UTC-0600 ERROR Unsuccessful command execution on instance id(s) 'i-00553f4ac36afd327'. Aborting the operation.
2020-03-16 13:54:45 UTC-0600 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2020-03-16 13:54:45 UTC-0600 ERROR [Instance: i-00553f4ac36afd327] Command failed on instance. An unexpected error has occurred [ErrorCode: 0000000001].
2020-03-16 13:54:20 UTC-0600 INFO Updating environment XXX's configuration settings.
2020-03-16 13:54:15 UTC-0600 INFO Environment update is starting.
I've also downloaded the full set of logs for the instance and don't see anything obvious. The app stdout doesn't have any errors or exceptions, it just starts normally and then gets terminated. None of the other log files have messages around the times above, so I'm really not sure what else I can look at.
Edit
The times don't line up but I do see this in eb-engine.log file:
2020/03/16 17:54:38.508634 [INFO] checking whether command is applicable to this instance...
2020/03/16 17:54:38.508658 [INFO] this command is applicable to the instance, thus instance should execute command
2020/03/16 17:54:38.508665 [INFO] check whether this is an enhanced env...
2020/03/16 17:54:38.508794 [INFO] Executing instruction: StageJavaApplication
2020/03/16 17:54:38.508858 [ERROR] GetArchivedFileType with file /opt/elasticbeanstalk/deployment/app_source_bundle failed with error open /opt/elasticbeanstalk/deployment/app_source_bundle: no such file or directory
2020/03/16 17:54:38.508868 [ERROR] An error occurred during execution of command [config-deploy] - [StageJavaApplication]. Stop running the command. Error: staging java app failed with error GetArchivedFileType with file /opt/elasticbeanstalk/deployment/app_source_bundle failed with error open /opt/elasticbeanstalk/deployment/app_source_bundle: no such file or directory

Failed to Resolve Target Definition on OpenShift

I'm trying to get a Tycho build to work on an OpenShift server. Locally resolving the target definition and building works fine, but when deploying I get the following error:
Unable to read repository at http://download.eclipse.org/rt/rap/2.2/content.xml. Permission denied
I'm not sure if its a problem in the Tycho configuration (but as far as I can remember, I didn't do anything outside the build reactor to make Tycho work) or the one of OpenShift. Could someone tell me what the problem is or how to narrow it down?
I tried switching from a target platform file to defining the repository in the pom.xml. Then I get a similar error message:
Failed to load p2 repository with ID 'rap' from location http://download.eclipse.org/rt/rap/2.2
I found a Linux bug that might be relevant. It doesn't help me, since I'm not even able confirm the server is a Debian. I tried to get the Jenkins to build on some other platform and tried any abbreviation or combination of "Windows" in the (seemingly undocumented) "platform" field, but neither of these values made it change the OS.
Finally got Maven to work with parameters (for how, see here). The log shows nothing out of the ordinary, as far as I can see:
[INFO] Computing target platform for MavenProject: org.acme.dummy:org.acme.dummy.feature:0.0.1-SNAPSHOT # /var/lib/openshift/537cb333e0b8cd68ad000187/app-root/runtime/repo/org.acme.dummy.feature/pom.xml
[DEBUG] Added p2 repository rap-repository (http://download.eclipse.org/rt/rap/2.2)
[DEBUG] Using default execution environment 'JavaSE-1.6'
[DEBUG] Registered artifact repository org.eclipse.tycho.repository.registry.facade.RepositoryBlackboardKey(uri=file:/resolution-context-artifacts#/var/lib/openshift/537cb333e0b8cd68ad000187/app-root/runtime/repo/org.acmr.dummy.feature)
May 21, 2014 10:15:59 AM org.apache.http.impl.client.DefaultRequestDirector tryConnect
INFO: I/O exception (java.net.BindException) caught when connecting to the target host: Permission denied
It's retrying to connect a couple of times, then there is the above exception:
!ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2014-05-21 10:16:00.073
!MESSAGE Connection to http://download.eclipse.org/rt/rap/2.2/p2.index failed on Permission denied. Retry attempt 0 started
!STACK 0
java.net.BindException: Permission denied
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
at java.net.Socket.bind(Socket.java:631)
at org.eclipse.ecf.internal.provider.filetransfer.httpclient4.ECFHttpClientProtocolSocketFactory.connectSocket(ECFHttpClientProtocolSocketFactory.java:82)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:150)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:575)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)

Error while configuring build server on windows server 2012

I'm trying to create build definitions for a project. TFS and build server machines are the same.
When I create the build definition using Default Template (Tfvc Template.12.xaml ), it gives the following error:
Exception Message: The path '$/Scrumproject/Scrumproject/Scrumproject.sln' could not be converted to a local path. Make sure this path is relative to the 'src' folder on the build machine or specify a full server path. (type ArgumentException)
Exception Stack Trace: at Microsoft.TeamFoundation.Build.Activities.Core.LocalPathProvider.GetLocalPath(String incomingPath)
at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
When I use the Upgrade template it gives the following error:
Exception Message: TF42006: The build service could not get the project file for build definition Newdefinition. Ensure the project file exists and the build service account NT AUTHORITY\NETWORK SERVICE is a member of the Build Services group for the team project. (type InvalidBuildTypeException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Can anyone help configure the build server correctly?
The first error could be due to an incorrect mapping: is $/Scrumproject/Scrumproject/ folder mapped in the build workspace?

How do I use JMockit with Gradle on the IBM J9 JVM?

I'm using Gradle (Milestone 8a) to run JUnit tests on my project with the IBM J9 JVM, which according to "Running tests with JMockit" requires that I pass the argument -javaagent:jmockit.jar to the JVM. However, JMockit isn't injecting mocked parameters which is causing my tests to fail with "Method (foo) should have no parameters)". The tests run fine in Eclipse on the HotSpot JVM.
I've extended the test task to find the JAR and add the argument to jvmArgs like this:
test {
doFirst {
// Don't do this until the task is actually being executed, because
// as soon as we call testCompile.find the configuration is resolved and
// can't be modified anymore.
jMockit = project.configurations.testCompile.find {
it.name.startsWith("jmockit-")
}
jvmArgs "-javaagent:${jMockit}"
}
}
I've also added JMockit and JUnit to the testCompile configuration, making sure that JMockit is first, and verified this by running gradle dependencies:
dependencies {
testCompile 'com.googlecode.jmockit:jmockit:0.999.13'
testCompile 'junit:junit:4.10'
}
The output of gradle check --debug confirms that the -javaagent parameter is being used:
12:44:14.788 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] creating process builder for Gradle Worker 1
12:44:14.788 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] in directory /home/bbobby/webapp
12:44:14.788 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] with argument#0 = -javaagent:/home/bbobby/.gradle/caches/artifacts-8/filestore/com.googlecode.jmockit/jmockit/0.999.13/jar/a6
ba457e09361f37e386edea176c5ce4fa9ee110/jmockit-0.999.13.jar
12:44:14.789 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] with argument#1 = -ea
12:44:14.789 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] with argument#2 = -cp
12:44:14.789 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] with argument#3 = /home/bbobby/.gradle/caches/1.0-milestone-8a/workerMain/classes
12:44:14.789 [DEBUG] [org.gradle.process.internal.ProcessBuilderFactory] with argument#4 = org.gradle.process.internal.launcher.GradleWorkerMain
12:44:14.816 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Started Gradle Worker 1.
I'm pretty sure I've done everything I'm supposed to. Why are my tests failing to run?
This is http://issues.gradle.org/browse/GRADLE-2189, which is already fixed for the upcoming 1.0-rc-1. You can try out the release candidate today.