openx 2.8.1“会话 ID 无效” 当使用 XMLRPC api 时 红宝石 openx 宝石

发布于 2024-07-24 07:46:26 字数 293 浏览 9 评论 0原文

有时,当通过 XMLRPC api(使用 ruby​​ 'openx' gem)访问 OpenX 2.8.1 时,我会收到以下错误消息:

会话 ID 无效

我在 OpenX 论坛中找不到任何关于此问题的内容,也无法通过 Google 搜索找到任何内容。

我开始怀疑这是红宝石宝石本身的错误或其他问题。

有其他人遇到过这样的错误吗?如果有,解决办法是什么? 在运行 OpenX 的维护脚本后,它确实似乎可以自行解决。

Occasionally when accessing OpenX 2.8.1 via its XMLRPC api (using the ruby 'openx' gem), I will get this error message:

Session ID is invalid

I cannot find anything in OpenX's forums about this, nor via some Google searching.

I am starting to suspect that it is a bug or other issue in the ruby gem itself.

Has anyone else encountered such an error, and if so, what is the fix? It does seem to resolve itself after running OpenX's maintenance scripts.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

丶视觉 2024-07-31 07:46:27

使用 OpenX 2.6 我的服务器连接将在大约 25 分钟后超时。 不确定我能否找到它的当前参考,但它可以跟踪连接时间并在超时后简单地重新建立连接。

def openx_connection
  return @connection if (@timeout && Time.now < @timeout) 
  OpenX::Services::Base.connection=nil   # clear any remaining connection
  OpenX::Services::Base.configuration = {
    'username'  => @username,
    'password'  => @password,
    'url'       => @url }
  @timeout = Time.now + 25.minutes
  @connection = OpenX::Services::Base.connection  # establish a new connection
end

Using OpenX 2.6 my server connection would time out after about 25 minutes. Not sure I could ever find a current reference for it, but it worked to track the connection time and simply re-establish the connection after a timeout.

def openx_connection
  return @connection if (@timeout && Time.now < @timeout) 
  OpenX::Services::Base.connection=nil   # clear any remaining connection
  OpenX::Services::Base.configuration = {
    'username'  => @username,
    'password'  => @password,
    'url'       => @url }
  @timeout = Time.now + 25.minutes
  @connection = OpenX::Services::Base.connection  # establish a new connection
end
离旧人 2024-07-31 07:46:26

在将 OpenX 与 JSP 应用程序一起使用时,我们发现应用程序和 OpenX 之间的不活动时间过长会导致 OpenX 使会话 ID 无效。 目前,我们的应用程序无法为自己获取新会话,我们的解决方法是重新启动应用程序。

In using OpenX with a JSP application, we've found that too long a period of inactivity between the application and OpenX will cause the OpenX to invalidate the session ID. Currently our application was unable to get itself a new session, our workaround has been a restart of the application.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文