Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] jetty-users Digest, Vol 19, Issue 23 
Hi Kevin,

It seems that we need to update the documentation for the jdbc session
setup.

The <Property> element no longer supports setting of objects, and
should be substituted with the use of <Ref> element instead.

Here's an example that would go in a context xml file:

  <Ref id="Server">
    <Call id="jdbcIdMgr" name="getAttribute">
      <Arg>jdbcIdMgr</Arg>
    </Call>
  </Ref>

FYI the bug to track the documentation correction is:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=333905

Jan


On 10/01/11 18:42, Kevin Jordan wrote:

Have you figured out anything on this?  I'm moving from 7.1.6 to 7.2.2
and I'm having the same problem.  I'm moving up versions due to the
fix for http://jira.codehaus.org/browse/JETTY-1259 although I notice
that scavenge also needs the same fix.

    Date: Wed, 22 Dec 2010 11:22:53 -0500
    From: Bob Obringer <bobringer@xxxxxxx <mailto:bobringer@xxxxxxx>>
    To: jetty-users@xxxxxxxxxxx <mailto:jetty-users@xxxxxxxxxxx>
    Subject: [jetty-users] JdbcSessionIdManager & Jetty 7.2.2
    Message-ID: <2B4A95F5-94BB-428F-AAA8-5F8BAA4E4660@xxxxxxx
    <mailto:2B4A95F5-94BB-428F-AAA8-5F8BAA4E4660@xxxxxxx>>
    Content-Type: text/plain; charset="us-ascii"

    Recently upgraded from hightide-7.1.5 to hightide-7.2.2.

    I am using JDBCSessionIdManager to store my session ID's in MySQL
    so they can be used across webapps and server restarts.

    After upgrading from 7.1.5 to 7.2.2 I started receiving this
    (being thrown from the webapp's context.xml file):

    2010-12-22 03:47:53.496:INFO::Deployable added:
    /home/qa/opt/jetty-hightide-7.2.2.v20101205/contexts/link-core-webapp.xml
    2010-12-22 03:47:53.526:WARN::Config error at <Set
    name="idManager">|??????<Ref id="jdbcIdMgr"/>|?????</Set>
    java.lang.IllegalStateException: No object for id=jdbcIdMgr
    2010-12-22 03:47:53.526:WARN::Config error at <Set
    name="sessionHandler">|??<New
    class="org.eclipse.jetty.server.session.SessionHandler"><Arg>|????<New
    id="jdbcmgr"
    class="org.eclipse.jetty.server.session.JDBCSessionManager"><Set
    name="idManager">|??????<Ref
    id="jdbcIdMgr"/>|?????</Set></New>|???</Arg></New>|?</Set>
    java.lang.IllegalStateException: No object for id=jdbcIdMgr
    2010-12-22 03:47:53.526:WARN::Unable to reach node goal: started
    java.lang.IllegalStateException: No object for id=jdbcIdMgr
            at
    org.eclipse.jetty.xml.XmlConfiguration.refObj(XmlConfiguration.java:685)


    In my jetty.xml I've got:

    <Set name="sessionIdManager">
    <New id="jdbcIdMgr"
    class="org.eclipse.jetty.server.session.JDBCSessionIdManager">
    <Arg>
    <Ref id="Server" />
    </Arg>
    <Set name="workerName">qa</Set>
    <Set name="DatasourceName">jdbc/mysql/session</Set>
    <Set name="scavengeInterval">60</Set>
    </New>
    </Set>
    <Call name="setAttribute">
    <Arg>jdbcIdMgr</Arg>
    <Arg>
    <Ref id="jdbcIdMgr" />
    </Arg>
    </Call>


    The DSN points to a JNDI resource set up immediately before this
    in jetty.xml.  When I remove the JDBCSessionManager config from my
    context's xml file, the server starts up fine.  I've confirmed
    it's not a JNDI issue as my other JNDI resources are working properly.


    Any ideas?


    Thanks in advance...



_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users


--
Jan Bartel, Webtide LLC | janb@xxxxxxxxxxx | http://www.webtide.com

Back to the top