Topic
  • 7 replies
  • Latest Post - ‏2013-03-25T23:30:04Z by KaranBal
KunalD
KunalD
10 Posts

Pinned topic Export Job throwing exception of SearchQueryParserException

‏2013-03-22T14:03:38Z |
Hi,

With context to MDM Collaboration server v 10.0.0 we have a Custom Tool application which generate the BODL Files(xml) with respect to each country catalog. But the requirement is changed to direct the BODL export through scheduled export job. While running the export job an exception is throwing of SearchQueryParserException. But in the same environment when the export is running through the Custom Tool or through sand box it is running fine. We have monitored the export job and during the execution we have 3GB of memory free.

Any suggestion is appretiated.
Updated on 2013-03-25T23:30:04Z at 2013-03-25T23:30:04Z by KaranBal
  • KaranBal
    KaranBal
    108 Posts

    Re: Export Job throwing exception of SearchQueryParserException

    ‏2013-03-22T23:51:12Z  
    MDMCS is a collection of 6 services including appserver and custom tool. Custom tools and sandbox scripts are run in the appserver while the export runs in the scheduler service. The appserver runs on application server, usually WebSphere Application Server, but scheduler isn't. This means that it is possible that there are differences like classpath, heapsize, etc between the two. I assume you did not find anything obvious wrong with it.

    As such, we do not have enough information to say why the job failed. But it would help if you check the entire error stack under $TOP/logs/scheduler_xyz/exception.log and paste the entire error stack here; maybe there are clues in it.
  • SystemAdmin
    SystemAdmin
    648 Posts

    Re: Export Job throwing exception of SearchQueryParserException

    ‏2013-03-25T04:54:17Z  
    Hi,

    As said Karan, check the memory setting for the scheduler service. You need SCHEDULER_MEMORY_FLAG in $TOP/bin/conf/service_mem_settings.ini
  • SystemAdmin
    SystemAdmin
    648 Posts

    Re: Export Job throwing exception of SearchQueryParserException

    ‏2013-03-25T06:09:28Z  
    Hi,

    As said Karan, check the memory setting for the scheduler service. You need SCHEDULER_MEMORY_FLAG in $TOP/bin/conf/service_mem_settings.ini
    Hi Alexander/Karan,

    I updated the minimum memory for Scheduler service to 256 as of the appserver service and restarted the env. Still I am getting the exception with the job.

    ADMIN_MEMORY_FLAG=-Xmx64m -Xms48m
    APPSVR_MEMORY_FLAG=-Xmx1024m -Xms256m
    EVENTPROCESSOR_MEMORY_FLAG=-Xmx64m -Xms48m
    QUEUEMANAGER_MEMORY_FLAG=-Xmx64m -Xms48m
    SCHEDULER_MEMORY_FLAG=-Xmx1024m -Xms256m
    WORKFLOWENGINE_MEMORY_FLAG=-Xmx1024m -Xms48m

    Also attaching the sheduler exception logs for reference.
  • SystemAdmin
    SystemAdmin
    648 Posts

    Re: Export Job throwing exception of SearchQueryParserException

    ‏2013-03-25T06:22:55Z  
    Hi Alexander/Karan,

    I updated the minimum memory for Scheduler service to 256 as of the appserver service and restarted the env. Still I am getting the exception with the job.

    ADMIN_MEMORY_FLAG=-Xmx64m -Xms48m
    APPSVR_MEMORY_FLAG=-Xmx1024m -Xms256m
    EVENTPROCESSOR_MEMORY_FLAG=-Xmx64m -Xms48m
    QUEUEMANAGER_MEMORY_FLAG=-Xmx64m -Xms48m
    SCHEDULER_MEMORY_FLAG=-Xmx1024m -Xms256m
    WORKFLOWENGINE_MEMORY_FLAG=-Xmx1024m -Xms48m

    Also attaching the sheduler exception logs for reference.
    Hi,

    Well, at first look the WQL is good. Create a dynamic selection with this query and check if it will work.
    Try to simplify the query. For example, remove one or both WHERE condition. Take an item object in select, not an item attribute value.
    Are the attributes in the query indexed?
  • SystemAdmin
    SystemAdmin
    648 Posts

    Re: Export Job throwing exception of SearchQueryParserException

    ‏2013-03-25T06:26:26Z  
    Hi,

    Well, at first look the WQL is good. Create a dynamic selection with this query and check if it will work.
    Try to simplify the query. For example, remove one or both WHERE condition. Take an item object in select, not an item attribute value.
    Are the attributes in the query indexed?
    Also I would suggest to apply the latest fixpack.
  • SystemAdmin
    SystemAdmin
    648 Posts

    Re: Export Job throwing exception of SearchQueryParserException

    ‏2013-03-25T06:55:56Z  
    Also I would suggest to apply the latest fixpack.
    Hi Alexander,

    As Kunal told earlier too, the queries are fine and the logic is working without any issues by calling the logic from a Custom tool and Sandbox.
    Also yes the attributes in the query are indexed.

    One thing is that the job is not failing in a specific query everytime. The job is failing randomly in any query and data each time its run.

    Thanks,
    Chetan
  • KaranBal
    KaranBal
    108 Posts

    Re: Export Job throwing exception of SearchQueryParserException

    ‏2013-03-25T23:30:04Z  
    Hi Alexander,

    As Kunal told earlier too, the queries are fine and the logic is working without any issues by calling the logic from a Custom tool and Sandbox.
    Also yes the attributes in the query are indexed.

    One thing is that the job is not failing in a specific query everytime. The job is failing randomly in any query and data each time its run.

    Thanks,
    Chetan
    This is getting to the point where it might be better to open a Service Request. But from the description, it might be one of the following:
    1. The usage of one of your script operations is not correct.
    There are some special functions which should be used in one instance but not in others e.g. getCtgItemDiffStatus can not be run directly in sandbox or in custom tools, it returns NULL if done so.
    2. Data Corruption.
    You run the WQL to get the item but when you try to get a different attribute of the same item, the corresponding entry doesn't exist in ITA table(where indexed attributes are stored).