Issue: Unable to See Subscription Requests and Responses in the emaLog

Hi, We recently encountered an issue with PAM24-U24 where we were unable to receive snapshot responses when sending subscription requests. We were advised to enable emaLogs to log the subscription requests and responses for all our subscriptions. However, even after enabling emaLogs, we still cannot see log information related to subscription requests and responses. Please assist us in resolving this issue

Find more posts tagged with

ema-api

#technology

Accepted answers

Jirapongse

@johnson

Thank you for reaching out to us.

Please enble verbose log and trace log in the API by using the following configurations.

<ConsumerGroup>
    <DefaultConsumer value="Consumer_1"/>
    <ConsumerList>
        <Consumer> 
            <Name value="Consumer_1"/>
            <ChannelSet value="Channel_1"/>
            <Logger value="Logger_1"/>
            <Dictionary value="Dictionary_2"/>
            <XmlTraceToFile value="1"/>
        </Consumer>
...
     </ConsumerList>
</ConsumerGroup>
...
<LoggerGroup>
    <LoggerList>
        <Logger>
            <Name value="Logger_1"/>
            <LoggerType value="LoggerType::File"/>
            <LoggerSeverity value="LoggerSeverity::Verbose"/>
        </Logger>
...
   </LoggerList>
</LoggerGroup>
...

Wit these configurations, the emaLog and EmaTrace files will be created in the working directy.

We may be able to verify what the problem is after invetigating these log files.

All comments

Jirapongse

@johnson

Is it EMA C++, Java, or C#?

Please also share the ema log.

wasin.w

Hello @johnson

Is it EMA C++, Java, or C#?

Please also share the ema log.

It is C++.

It is C++.

Thank you for reaching out to us.

Please enble verbose log and trace log in the API by using the following configurations.

<ConsumerGroup>
    <DefaultConsumer value="Consumer_1"/>
    <ConsumerList>
        <Consumer> 
            <Name value="Consumer_1"/>
            <ChannelSet value="Channel_1"/>
            <Logger value="Logger_1"/>
            <Dictionary value="Dictionary_2"/>
            <XmlTraceToFile value="1"/>
        </Consumer>
...
     </ConsumerList>
</ConsumerGroup>
...
<LoggerGroup>
    <LoggerList>
        <Logger>
            <Name value="Logger_1"/>
            <LoggerType value="LoggerType::File"/>
            <LoggerSeverity value="LoggerSeverity::Verbose"/>
        </Logger>
...
   </LoggerList>
</LoggerGroup>
...

Wit these configurations, the emaLog and EmaTrace files will be created in the working directy.

We may be able to verify what the problem is after invetigating these log files.

EXPLORE OUR SITES