[jira] [Created] (AXIS2-5933) instrument RepositoryListener.findServicesInDirectory(File root) with Debug statements

Discussion:

Ralf Hauser (JIRA)

2018-09-12 16:07:00 UTC

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-***@axis.apache.org
For additional commands, e-mail: java-dev-***@axis.apache.org

Ralf Hauser (JIRA)

2018-09-12 16:15:00 UTC

Permalink

[ https://issues.apache.org/jira/browse/AXIS2-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Hauser updated AXIS2-5933:
-------------------------------
Summary: instrument RepositoryListener.findServicesInDirectory(File root) etc. with Debug statements (was: instrument RepositoryListener.findServicesInDirectory(File root) with Debug statements)

instrument RepositoryListener.findServicesInDirectory(File root) etc. 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
Priority: Major
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
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-***@axis.apache.org
For additional commands, e-mail: java-dev-***@axis.apache.org

robert lazarski (JIRA)

2018-09-12 16:25:00 UTC

Permalink

[ https://issues.apache.org/jira/browse/AXIS2-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612424#comment-16612424 ]

robert lazarski commented on AXIS2-5933:
----------------------------------------

Are you running WebLogic as your application server? That was the problem in AP-5912 however the OP of that issue never followed up on the proposed solution.

Post by Ralf Hauser (JIRA)
instrument RepositoryListener.findServicesInDirectory(File root) etc. 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
Priority: Major
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
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

Ralf Hauser (JIRA)

2018-09-12 16:57:00 UTC

Permalink

[ https://issues.apache.org/jira/browse/AXIS2-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612455#comment-16612455 ]

Ralf Hauser commented on AXIS2-5933:
------------------------------------

No, plain tomcat8.5-14

Andreas Veithen (JIRA)

2018-09-14 20:46:00 UTC

Permalink

[ https://issues.apache.org/jira/browse/AXIS2-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615363#comment-16615363 ]

Andreas Veithen commented on AXIS2-5933:
----------------------------------------

Maybe you can prepare a patch?

Ralf Hauser (JIRA)

2018-09-18 05:13:00 UTC

Permalink

[ https://issues.apache.org/jira/browse/AXIS2-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618485#comment-16618485 ]

Ralf Hauser commented on AXIS2-5933:
------------------------------------

The underlying reason is found.

The axis2.xml was still from v1.62 (non backward compatible changes like "cluster" vs. "clustering"), but anyway, the log should still reveal in trace mode why in this case the services don't start