Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-dev] Session storage with Redis

I am using jetty-runner-9.4.9.v20180320.jar to run my war and would like to use Redis for session storage inplace of JDBC. I think Jetty-Redis https://github.com/cloudbees/jetty-redis should work but I can't seem to configure it correctly.

Here is my Jetty base:

├── lib

│   ├── com

│   │   └── fasterxml

│   │       └── jackson

│   │           └── core

│   │               ├── jackson-annotations

│   │               │   └── jackson-annotations-2.9.9.jar

│   │               ├── jackson-core

│   │               │   └── jackson-core-2.9.9.jar

│   │               └── jackson-databind

│   │                   └── jackson-databind-2.9.9.jar

│   ├── org

│   │   ├── acegisecurity

│   │   │   └── acegi-security

│   │   │       └── acegi-security-1.0.7.jar

│   │   ├── apache

│   │   │   └── commons

│   │   │       └── commons-pool2

│   │   │           ├── commons-pool2-${commons-pool2.version}.jar

│   │   │           └── commons-pool2-2.8.0.jar

│   │   └── jenkinsci

│   │       └── plugins

│   │           ├── pubsub

│   │           └── ssegateway

│   └── redis

│       └── clients

│           └── jedis

│               └── jedis-3.2.0.jar

└── start.d

    └── session-store-redis-remote.ini


I updated session-store-redis-remote.ini but I can't find any keys in Redis after my app starts and I login. Should I see any log messages when session storage initializes?


Any suggestions are.


JR



John Ruggentaler​
Principal Engineer
Signify Health
office (512) 431‑6849
signifyhealth.com
Signify Health on TwitterSignify Health on FacebookSignify Health on LinkedIN
This e-mail, including attachments, may include CONFIDENTIAL AND PRIVILEGED information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
​
​#bitmap


Back to the top