[
https://issues.apache.org/jira/browse/AXIS2C-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dushshantha Chandradasa updated AXIS2C-719:
-------------------------------------------
Fix Version/s: 1.2.0
> v2.0.x apache module compilation error
> --------------------------------------
>
> Key: AXIS2C-719
> URL: https://issues.apache.org/jira/browse/AXIS2C-719
> Project: Axis2-C
> Issue Type: Bug
> Components: build system (Windows)
> Affects Versions: 1.1.0
> Environment: Visual Studio 2005
> apache v2.0.59
> apache v2.0.61
> DEBUG=1
> APACHE_VERSION_2_0_X = 1
> Reporter: David Klassen
> Assignee: Dushshantha Chandradasa
> Fix For: 1.2.0
>
>
> I read how to install the apache module, and naturally decided to use 2.2.x.
> Everything installed fine. However after finding the apache httpd.exe memory
> size was growing fast for 25 concurrent users (AXIS2C-717), I decided to
> install an older version of apache to make sure this was not related to some
> apache 2.2.x features interfering with axis2c. Looking on-line I remembered
> seeing that special configuration changes were needed to work with 2.0.x
> version of apache:
> http://ws.apache.org/axis2/c/docs/axis2c_manual.html#mod_axis2
> I set the configuration setting:
> APACHE_VERSION_2_0_59 = 1
> However a compilation error still occurrs:
> C:\SOAP\axis2c-src-1.1.0\axis2c-src-1.1.0\build\win32>nmake
> axis2_apache_module
> Microsoft (R) Program Maintenance Utility Version 8.00.50727.42
> Copyright (C) Microsoft Corporation. All rights reserved.
> Creating library ..\deploy\lib\mod_axis2.lib and object
> ..\deploy\lib\mod_axis2.exp
> mod_axis2.obj : error LNK2019: unresolved external symbol
> __imp__ap_real_exit_code referenced in function _axis2_module_init
> ..\deploy\lib\mod_axis2.dll : fatal error LNK1120: 1 unresolved externals
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\link.exe"' : return code '0x460'
> Stop.
> Unfortunately I am not sure of the best remedy yet. Perhaps axis2c does not
> support apache 2.0.x ? If so the on-line documentation should be updated.
> However I would like to make sure the memory leak is not constrained to 2.2.x
> alone...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
