On Tue, Mar 18, 2025 at 4:37 AM Bill Blough <[email protected]> wrote:

>
> Hi Robert,
>
> On Mon, Mar 17, 2025 at 11:08:30AM -1000, robertlazarski wrote:
> > The patch to fix json support helped a lot, thanks! I think I am going to
> > commit it.
> >
> >  I see what appears to be an obvious problem to in the json test code
> when
> > adding --enable-json=yes to build_for_tests.sh
> > , am I reading this correctly that it should be m_env instead of env? It
> > compiles after making that change.
>
> Yes, I think you're correct.
>
> >
> > test_http_transport.cc: In member function ‘virtual void TestHTTPTranspo
> > rt_test_json_Test::TestBody()’:
> > test_http_transport.cc:368:20: error: ‘env’ was not declared in this sco
> > pe; did you mean ‘m_env’?
> >  368 |         AXIS2_FREE(env->allocator, xml_str);
> >
> > Are you able to run build_for_tests.sh ? I get the error below. I'd like
> to
> > see the JSON test complete as referenced above, but it seems like this
> > error happens before that.
> >
> >
> > [       OK ] TestHTTPTransport.test_url (0 ms)
> > [ RUN      ] TestHTTPTransport.test_http_client
> > AddressSanitizer: CHECK failed: sanitizer_thread_arg_retval.cpp:57
> > "((!t->second.detached)
> > ) != (0)" (0x0, 0x0) (tid=304564)
> >    #0 0x70c61fd08a47 in CheckUnwind
> > ../../../../src/libsanitizer/asan/asan_rtl.cpp:69
> >
> > With or without setting export AXIS2C_HOME to the deploy dir seemed to
> > help.
>
> When I run run-tests.sh, all the tests pass individually, including
> test_http_client where you're seeing the failure.
>
> (side note: I say individually, because while the tests themselves pass,
> the whole suite run is failed due to memory leaks that ASAN detects in
> the newly-enabled JSON code.  It's not related to the issue you're
> seeing, but I wanted to mention it because you'll probably see it once
> your other issue is resolved).
>
> I suspect that the error is due to test_http_client failing to get a good
> response from the local axis server.  I suggest verifying that:
>
> 1. samples are being built correctly
> 2. samples are being installed correctly into the deploy directory
>     (deploy/services/echo should have libecho.so, plus various soname
> symlinks and services.xml)
> 3. you don't already have something running on the port that the local
> axis server uses (9090)
> 4. you don't have firewall software blocking local traffic (particularly
> to 9090)
>
> Hope that helps.
>
> Bill
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
I was able to run the json tests successfully today.

I have some time again for Axis2/C and I made some commits today - please
review, I got some help from modern AI tools.

https://github.com/apache/axis-axis2-c-core/commit/580af19055cf77b47602d8f5443784efb7555bdd

I reviewed the open Jira issues. Many are stale from over a decade ago,
though some have patches never applied and those have my attention.

Anyways, I have some time in the next week and any guidance on what needs
to happen before a 2.0.0 release would be helpful.

Reply via email to