You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ralf Hauser (JIRA)" <ji...@apache.org> on 2018/09/12 16:07:00 UTC
[jira] [Created] (AXIS2-5933) instrument
RepositoryListener.findServicesInDirectory(File root) with Debug statements
Ralf Hauser created AXIS2-5933:
----------------------------------
Summary: instrument RepositoryListener.findServicesInDirectory(File root) with Debug statements
Key: AXIS2-5933
URL: https://issues.apache.org/jira/browse/AXIS2-5933
Project: Axis2
Issue Type: Improvement
Components: deployment
Affects Versions: 1.7.8
Environment: debian stretch
Reporter: Ralf Hauser
org.apache.axis2.deployment.RepositoryListener.findServicesInDirectory() appears to be crucial why my simple .aar in the standard services directory is not loaded
Like AXIS2-5912 it happens when migrating from v1.6.2 and results in
The service cannot be found for the endpoint reference
.
Putting
org.apache.axis2=TRACE
unfortunately only gives
(ScriptModule.java:70) - script module activated
(WarBasedAxisConfigurator.java:276) - loaded services from path: /usr/share/tomcat8/ws/WEB-INF
Therefore I suggest that
1) findServicesInDirectory counts how many times "addFileToDeploy" is called and returns this int . Then line 276 could give a hint how many services were loaded
2) in the for (File file : files) { loop
each file gets a debug trace with file.getAbsolutePath()
3) each "continue" or if-else where nothing happens gets a trace statement
4) same for "loadOtherDirectories"
5) [DeploymentEngine|eclipse-javadoc:%E2%98%82=%20/%3C%7BDeploymentEngine.java%E2%98%83DeploymentEngine]{color:#000000}.doDeploy(){color} should also get a few trace statements (e.g. wsToDeploy.size())
6) [ServiceDeployer|eclipse-javadoc:%E2%98%82=%20/%3C%7BServiceDeployer.java%E2%98%83ServiceDeployer]{color:#000000}.deploy({color}) urgently needs some trace statements
etc.
I run the service in a lab environments where the services are found, in "integration" unfortunately not
In both environments the modules load perfectly "axisConfiguration.getModules()" :
Module 0: jaxws-1.7.8
INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 1: ping-1.7.8
INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 2: metadataExchange-1.7.8
INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 3: addressing-1.7.8
INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 4: mtompolicy-1.7.8
INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 5: soapmonitor-1.7.8
INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 6: script-1.7.8
INFO [172.25.11.160-startStop-1] (AxisServletPsph.java:239) - Module 7: MyWebServiceModule
axisConfiguration.getServices() and axisConfiguration.getFaultyServices() are unfortunately empty.
It would be interesting to see the "deploymentFileDataMap" field of WarBasedAxisConfigurator
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org