lua_code_cache on or off

jijilu · 2013-07-10T02:55:40+00:00

非常感谢您的回信！ Best regards Foyon------...

lua_code_cache on or off

jijilu

when I turn lua_code_cache on , 

			local uri = "url";
			local res = ngx.location.capture(uri);
			if res.status == 200 then
				-- ngx.print(res.body);
				local tbody = res.body;
				-- search for substatement having the tag "RequestResponse"
				local idx1 = string.find(tbody, "<RequestResponse");
				local idx2 = string.find(tbody, "</RequestResponse>");
				local prdata = string.sub(tbody, idx1, idx2+17);
				local pr_xml = xml.eval(prdata);

local pr_xml = xml.eval(prdata); this line will be wrong to echo server 500 error.

but turn  lua_code_cache off, the same error is gone.


@jijilu

agentzh

Hello!

On Tue, Jul 9, 2013 at 3:07 AM, jijilu wrote:
>
> local pr_xml = xml.eval(prdata); this line will be wrong to echo server 500 error.
>

I didn't see how you initialize the "xml" Lua variable here.

> but turn  lua_code_cache off, the same error is gone.
>

That usually means you didn't "require" the Lua module in the right
way. The correct syntax for loading a Lua module is

    local foo = require "foo"

rather than just

    require "foo"

BTW, English posts are better for the openresty-en mailing list:
https://groups.google.com/group/openresty-en

Best regards,
-agentzh

jijilu

hi,agentzh

sorry for my delay.

On Wednesday, July 10, 2013 3:05:30 AM UTC+8, agentzh wrote:
> Hello!
> 
> 
> 
> On Tue, Jul 9, 2013 at 3:07 AM, jijilu wrote:
> 
> >
> 
> > local pr_xml = xml.eval(prdata); this line will be wrong to echo server 500 error.
> 
> >
> 
> 
> 
> I didn't see how you initialize the "xml" Lua variable here.
> 
> 
> 
> > but turn  lua_code_cache off, the same error is gone.
> 
> >
> 
> 
> 
> That usually means you didn't "require" the Lua module in the right
> 
> way. The correct syntax for loading a Lua module is
> 
> 
> 
>     local foo = require "foo"
> 
> 
> 
> rather than just
> 
> 
> 
>     require "foo"
> 
> 
> 
> BTW, English posts are better for the openresty-en mailing list:
> 
> https://groups.google.com/group/openresty-en
> 
> 
> 
> Best regards,
> 
> -agentzh

After turn lua_code_cache on,

local xml = require("LuaXml");
local uri = "";
local res = ngx.location.capture(uri);
if res.status == 200 then
  local pr_xml = xml.eval(prdata);
  local xscene = pr_xml:find("DomesticFlightRoute");
  local rcs = tonumber(xscene[1][1]);

rcs will be nil when system load in case of high concurrent rate.

agentzh

Hello!

On Tue, Jul 23, 2013 at 12:01 AM,  jijilu wrote:
>
> After turn lua_code_cache on,
>
> local xml = require("LuaXml");
> local uri = "";
> local res = ngx.location.capture(uri);
> if res.status == 200 then
>   local pr_xml = xml.eval(prdata);
>   local xscene = pr_xml:find("DomesticFlightRoute");
>   local rcs = tonumber(xscene[1][1]);
>
> rcs will be nil when system load in case of high concurrent rate.
>

By looking at the source code of LuaXML 1.7.4 (as seen here:
http://viremo.eludi.net/LuaXML/#download ), one obvious mistake in the
xml.eval function's implementation (i.e., the Xml_eval C function) is
use of lua_getglobal to access the "xml" global variable. Descent Lua
modules should never assume that such a global variable exists (nor
polluting the global environment for any reasons). You should ask the
author of LuaXML to fix this issue on his side or you can look for a
better Lua library that can do XML.

BTW, please join the mailing list before posting. Otherwise, your
posts always require manual moderation.

Best regards,
-agentzh