You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Frank Huebbers (JIRA)" <ji...@apache.org> on 2008/02/20 19:03:43 UTC

[jira] Created: (AXIS2C-999) Disable logger prints an endless loop of "please check your log and buffer"

Disable logger prints an endless loop of "please check your log and buffer"
---------------------------------------------------------------------------

                 Key: AXIS2C-999
                 URL: https://issues.apache.org/jira/browse/AXIS2C-999
             Project: Axis2-C
          Issue Type: Bug
          Components: util
    Affects Versions: Current (Nightly)
            Reporter: Frank Huebbers


In our deployment scenario we would like to inhibit the generation of the log file. To this end, I am initiating the environment as follows:

m_axisEnv = NULL;
axutil_error_t *error = NULL;
axutil_allocator_t *allocator = NULL;
axutil_thread_pool_t *thread_pool = NULL;   
allocator = axutil_allocator_init(NULL);
error = axutil_error_create(allocator);
thread_pool = axutil_thread_pool_init(allocator);    
m_axisEnv = axutil_env_create_with_error_log_thread_pool(allocator, error, NULL, thread_pool);
axutil_env_enable_log(m_AxisEnv, AXIS2_FALSE);    
m_axisEnv->ref = 1;

This works in not generating an error report.

The problem that I still see, however, is that I seem to get an almost infinite amount of statements which read "please check your log and buffer". When tracking down the origin of this message, I saw that it comes from the log.c where it basically reads:

if (log)
{ 
 ...
}
else
    fprintf(stderr, "please check your log and buffer")

This basically means that if the log is not enabled, I'm going to be hamered with stderr messages even though this is my intended use case. There should probably be another test that if the log is not desired then the error is not printed.

For now, I solved it for my use case by simply returning if the "log" variable is not set and then recompiled, i.e.,:

if (!log)
   return;

Frank

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Reopened: (AXIS2C-999) Disable logger prints an endless loop of "please check your log and buffer"

Posted by "Frank Huebbers (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frank Huebbers reopened AXIS2C-999:
-----------------------------------


I just looked at the code for the logger with the new #ifndef and I think there should be one more change. Specifically, I can see the following now:

if (..)
{
}
else
#ifndef AXIS2_NO_LOG_FILE
        fprintf(stderr, "please check your log and buffer");
#endif

I think it should read the following instead:

if (..)
{
}
else
{
#ifndef AXIS2_NO_LOG_FILE
        fprintf(stderr, "please check your log and buffer");
#endif
}

or:

if (..)
{
}
#ifndef AXIS2_NO_LOG_FILE
else
        fprintf(stderr, "please check your log and buffer");
#endif


Otherwise, it won't compile when defining AXIS2_NO_LOG_FILE.

> Disable logger prints an endless loop of "please check your log and buffer"
> ---------------------------------------------------------------------------
>
>                 Key: AXIS2C-999
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-999
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: util
>    Affects Versions: Current (Nightly)
>            Reporter: Frank Huebbers
>            Assignee: Senaka Fernando
>             Fix For: 1.3.0
>
>
> In our deployment scenario we would like to inhibit the generation of the log file. To this end, I am initiating the environment as follows:
> m_axisEnv = NULL;
> axutil_error_t *error = NULL;
> axutil_allocator_t *allocator = NULL;
> axutil_thread_pool_t *thread_pool = NULL;   
> allocator = axutil_allocator_init(NULL);
> error = axutil_error_create(allocator);
> thread_pool = axutil_thread_pool_init(allocator);    
> m_axisEnv = axutil_env_create_with_error_log_thread_pool(allocator, error, NULL, thread_pool);
> axutil_env_enable_log(m_AxisEnv, AXIS2_FALSE);    
> m_axisEnv->ref = 1;
> This works in not generating an error report.
> The problem that I still see, however, is that I seem to get an almost infinite amount of statements which read "please check your log and buffer". When tracking down the origin of this message, I saw that it comes from the log.c where it basically reads:
> if (log)
> { 
>  ...
> }
> else
>     fprintf(stderr, "please check your log and buffer")
> This basically means that if the log is not enabled, I'm going to be hamered with stderr messages even though this is my intended use case. There should probably be another test that if the log is not desired then the error is not printed.
> For now, I solved it for my use case by simply returning if the "log" variable is not set and then recompiled, i.e.,:
> if (!log)
>    return;
> Frank

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Resolved: (AXIS2C-999) Disable logger prints an endless loop of "please check your log and buffer"

Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Senaka Fernando resolved AXIS2C-999.
------------------------------------

    Resolution: Fixed

Fixed Issue. Sorry for not noticing this before.

> Disable logger prints an endless loop of "please check your log and buffer"
> ---------------------------------------------------------------------------
>
>                 Key: AXIS2C-999
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-999
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: util
>    Affects Versions: Current (Nightly)
>            Reporter: Frank Huebbers
>            Assignee: Senaka Fernando
>             Fix For: 1.3.0
>
>
> In our deployment scenario we would like to inhibit the generation of the log file. To this end, I am initiating the environment as follows:
> m_axisEnv = NULL;
> axutil_error_t *error = NULL;
> axutil_allocator_t *allocator = NULL;
> axutil_thread_pool_t *thread_pool = NULL;   
> allocator = axutil_allocator_init(NULL);
> error = axutil_error_create(allocator);
> thread_pool = axutil_thread_pool_init(allocator);    
> m_axisEnv = axutil_env_create_with_error_log_thread_pool(allocator, error, NULL, thread_pool);
> axutil_env_enable_log(m_AxisEnv, AXIS2_FALSE);    
> m_axisEnv->ref = 1;
> This works in not generating an error report.
> The problem that I still see, however, is that I seem to get an almost infinite amount of statements which read "please check your log and buffer". When tracking down the origin of this message, I saw that it comes from the log.c where it basically reads:
> if (log)
> { 
>  ...
> }
> else
>     fprintf(stderr, "please check your log and buffer")
> This basically means that if the log is not enabled, I'm going to be hamered with stderr messages even though this is my intended use case. There should probably be another test that if the log is not desired then the error is not printed.
> For now, I solved it for my use case by simply returning if the "log" variable is not set and then recompiled, i.e.,:
> if (!log)
>    return;
> Frank

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Resolved: (AXIS2C-999) Disable logger prints an endless loop of "please check your log and buffer"

Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Senaka Fernando resolved AXIS2C-999.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.0
         Assignee: Senaka Fernando

Hi Frank,

Fixed Issue. Define the CFLAG AXIS2_NO_LOG_FILE, to stop the error message saying that there is no log.

Regards,
Senaka

> Disable logger prints an endless loop of "please check your log and buffer"
> ---------------------------------------------------------------------------
>
>                 Key: AXIS2C-999
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-999
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: util
>    Affects Versions: Current (Nightly)
>            Reporter: Frank Huebbers
>            Assignee: Senaka Fernando
>             Fix For: 1.3.0
>
>
> In our deployment scenario we would like to inhibit the generation of the log file. To this end, I am initiating the environment as follows:
> m_axisEnv = NULL;
> axutil_error_t *error = NULL;
> axutil_allocator_t *allocator = NULL;
> axutil_thread_pool_t *thread_pool = NULL;   
> allocator = axutil_allocator_init(NULL);
> error = axutil_error_create(allocator);
> thread_pool = axutil_thread_pool_init(allocator);    
> m_axisEnv = axutil_env_create_with_error_log_thread_pool(allocator, error, NULL, thread_pool);
> axutil_env_enable_log(m_AxisEnv, AXIS2_FALSE);    
> m_axisEnv->ref = 1;
> This works in not generating an error report.
> The problem that I still see, however, is that I seem to get an almost infinite amount of statements which read "please check your log and buffer". When tracking down the origin of this message, I saw that it comes from the log.c where it basically reads:
> if (log)
> { 
>  ...
> }
> else
>     fprintf(stderr, "please check your log and buffer")
> This basically means that if the log is not enabled, I'm going to be hamered with stderr messages even though this is my intended use case. There should probably be another test that if the log is not desired then the error is not printed.
> For now, I solved it for my use case by simply returning if the "log" variable is not set and then recompiled, i.e.,:
> if (!log)
>    return;
> Frank

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org