ReportPortal plugin cannot be initialized. 'org.apache.log4j.spi.LoggerRepository org.apache.log4j.Logger.getLoggerRepository()'

[mdfarhanin]

Seems like readyapi-3.10.0 pro has logger issues with reportportal

Followed steps to add the jar and listener to respective folders - Here are the details

Added Project Custom Properties - I am able to see that reportportal throws error if rp.api.key if not mentioned - This proves that reportportal is able to read the properties

But after providing proper properties - for some reason log4j has some issues

Definitely need some guidance here - ALso note: soapui lib folder already has log4j 2.11

Please assist in integration - Thanks.

[f4br3]

@mdfarhanin How do you launch test case/cases when you get this error? Is it a separate test case, a separate suite, or the whole project at once?

[mdfarhanin]

@f4br3 - Whole Project (Run on Functional Tests)

[f4br3]

@mdfarhanin Try to run it as separate suite and check if there are any results on the report portal.

[mdfarhanin]

@f4br3 - I dont see reportportal being triggered when running on test suite level - Are you available for a quick call on zoom at CST hours" - Just let me know when - I can send an invite to your email - I would like to integrate this for our project

Note: I have upgraded to ReadyAPI 3.10.1 - Seeing the same issue when running project level

[f4br3]

@mdfarhanin If you are still facing problems with the agent, email me.

[orcunbalcilar]

We are facing the same issue. Could you examine it again please?

[isolodkyi-clgx]

I am having the same issue after migration from ReadyAPI 2.x.x to 3.x.x. And it happens when running the whole project (separate test suites works fine).

[orcunbalcilar]

Hi @isolodkyi,
As I understand, report portal does not support readyapi (soapui pro) officially. They will maybe answer better. But as a solution to this issue, I have created a pull request (fork). Rp team has not yet reviewed it. But that solves this problem. The problem is actually due to migration from log4j 1 to log4j2 by updating readyapi version. Even if it is not an official solution, you can use my fork (log4j2 integration). The last commit was about supporting running test cases parallel. You can revert it.