Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have to add a scenario replacing SecureProxy scenario for performance tests #114

Closed
Maninda opened this issue Apr 24, 2019 · 2 comments
Closed
Assignees
Labels
IceBox Older issues that are not being actively worked on but may be revisited in the future. Priority/Normal Severity/Minor Type/Bug Type/Improvement

Comments

@Maninda
Copy link
Member

Maninda commented Apr 24, 2019

microeiisfailingatsecureproxyservices.zip

Description:
SecureProxy scenario is not supported in Micro EI. A supporting secure proxy scenario has to be implemented.

Affected Product Version:
Micro EI 6.4.0

OS, DB, other environment details and versions:
Any environment

Steps to reproduce:
Try to invoke Performance Test scenario SecureProxy in repo, "performance-ei" and the following exception could be observed.

java.lang.RuntimeException: org.wso2.carbon.security.util.ServerCrypto Not Found at org.apache.ws.security.components.crypto.CryptoFactory.loadClass(CryptoFactory.java:203) at org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFactory.java:95) at org.apache.rampart.util.RampartUtil.getSignatureCrypto(RampartUtil.java:390) at org.apache.rampart.RampartEngine.process(RampartEngine.java:166) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:93) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:415) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

  1. Deploy the attached CAR file in Micro EI and start.
  2. Load the attached jmx script
  3. In the HTTP Request section, set the file path of the attached XML file as the File Path of Files Upload tab
  4. Once the request is sent above exception will happen.
  5. When the issue is fixed the below exception will come as the backend service is unavailable.

[EI-Core] WARN - ConnectCallback Connection refused or failed for : netty:8688

Related Issues:
[1] wso2/product-ei#5600

@a5anka
Copy link
Member

a5anka commented Apr 24, 2019

@Maninda Can you attach the proxy config and the related artifacts to the issue? It will help us to reproduce the issue.

@Maninda Maninda closed this as completed Apr 25, 2019
@Maninda
Copy link
Member Author

Maninda commented Apr 25, 2019

Edited the issue and attached artifacts and added the description to reproduce the exception.

@Maninda Maninda reopened this Apr 25, 2019
JanakaPushpakumara pushed a commit to JanakaPushpakumara/micro-integrator that referenced this issue Apr 22, 2021
Revert "Comment out integration module"
Tharanidk pushed a commit to Tharanidk/micro-integrator that referenced this issue Apr 20, 2023
Tharanidk pushed a commit to Tharanidk/micro-integrator that referenced this issue Apr 20, 2023
@anupama-pathirage anupama-pathirage added the IceBox Older issues that are not being actively worked on but may be revisited in the future. label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IceBox Older issues that are not being actively worked on but may be revisited in the future. Priority/Normal Severity/Minor Type/Bug Type/Improvement
Projects
None yet
Development

No branches or pull requests

4 participants