Forum Discussion

FICO's avatar
FICO
Community Manager
17 years ago

Null pointer exception while trying to precompile

Null pointer exception while trying to precompile

Hi,

    Am migrating from Blaze 6.5 to Blaze 6.7. While trying to precompile using this statement --

java -Xms256m -Xmx1000m com.blazesoft.server.deploy.tools.NdAdvisorProjectCompiler -server %1.server >%SCRIPTDIR%\%1_CompilerOutput.txt

The code compiles on the IDE but does not precompile into an .adb file and the error is mentioned here --

An exception occured during jndi lookup

Exception while compiling and serializing the Advisor project

java.lang.NullPointerException Possible cause java.lang.NullPointerException

Any pointers in resolving this error will be appreciated.

Thanks,

NR.

4 Replies

  • FICO's avatar
    FICO
    Community Manager

    Unfortunately, nullpointers can mean a number of things when working with the precompiler (or other tools that use the rom/prom apis).

    I would start by verifying that you have the correct repository path in your .server file. Start by using an absolute repository path, for example, instead of a relative path. An error in the project path (in the server file) will also generate a nullpointer. 

    It can also be caused by classpath issues, but I would start by checking out the paths - they are easier to diagnose :-) 

    Regards, 

    Jostein 

  • FICO's avatar
    FICO
    Community Manager

    sorry repiled to wrong post

    Message Edited by rgodthi on 10-14-2009 10:17 AM
  • FICO's avatar
    FICO
    Community Manager

    Hi again,

    Could it be that you have a provider etc that is looking up some jndi resource that is not found on the system where you are compiling your sources? 

    Regards, 

    Jostein 

  • FICO's avatar
    FICO
    Community Manager

    This eventually turned out to be a weird issue. There is a "EngineOptimizations" attribute in the .adv file. This was set to 18 and was generating a null pointer exception. When this was changed to 23 (achieved by re-engineering the project), the precompilation worked smoothly. No changes to the code, no changes to the architecture or availability of jars.

    Thanks for all your inputs.