parse error while reading log-file

Help
2004-03-30
2004-04-21
  • I have just started using omniEvents and encountered the following problem :

    When I restart omniEvents I sometimes get a parse error.
    Here is a log-file :

    <<<< logfile start
    channelFactory
    {
        PORT    2810
        KEY    4069371f0000052500000001

        eventChannel
        {
            KEY    4069371f0000052500000002
            MAXQUEUELENGTH    0
            MAXEVENTSPERCONSUMER    0
            PULLRETRYPERIOD    1
            supplierAdmin
            {
                KEY    4069371f0000052500000005
                pxyPushConsumer
                {
                    KEY    4069371f0000052500000006
                    IOR    IOR:010000002a00000049444c3a6f6d672e6f72672f436f734576656e74436f6d6d2f50757368537570706c6965723a312e30000000010000000000000064000000010102000d0000003139322e3136382e312e3131000065050e000000fe3537694000000159000000000100000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
                }
            }
            consumerAdmin
            {
                KEY    4069371f0000052500000007
                pxyPushSupplier
                {
                    KEY    4069371f0000052500000008
                    IOR    IOR:010000002a00000049444c3a6f6d672e6f72672f436f734576656e74436f6d6d2f50757368436f6e73756d65723a312e30000000010000000000000060000000010102000d0000003139322e3136382e312e313100006b050c0000004069373f000001e7000000010200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
                }
            }
            consumerAdmin
            {
                KEY    4069371f0000052500000003
                pxyPushSupplier
                {
                    KEY    4069371f0000052500000004
                    IOR    IOR:010000002a00000049444c3a6f6d672e6f72672f436f734576656e74436f6d6d2f50757368436f6e73756d65723a312e30000000010000000000000064000000010102000d0000003139322e3136382e312e3131000065050e000000fe3537694000000159000000000000000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
                }
            }
            consumerAdmin
            {
                KEY    406937480000034200000009
            }
        }

    }
    <<<<< log-file end

    The parse error occures at the last KEY-line.

    What I did :
    - I opened a connection as a PushSupplier and as PullConsumer.
    - Then I killed the application.

    After a restart of omniEvents I encountered the parse error.

    Any ideas ?

    Regards
    J.Kartnaller

     
    • Alex Tingle
      Alex Tingle
      2004-04-21

      I'm sorry I didn't notice your post earlier. I'm monitoring this forum now, so I shouldn't miss future cries for help.

      You don't mention which version of omniEvents you are using. Clearly it's 2.4.x or 2.5.0, since the file format changed in 2.5.1. You also don't mention which platform you are using.

      I suggest that you download the latest 2.5.x release - it generally performs much better than the older versions and I'll be able to give you more informed support.

      Perhaps you are using Windows. If you need a pre-built binary then let me know & I'll see what I can do.

      -Alex