If your running mongodb 3.2 I would use OpenBD nightly/version 3.2, it has 
the newer mongodb.java driver and I believe the obd crew updated the 
functions.
Make sure your running java 8, also does your mongo.conf have authorization 
enabled?



On Monday, December 28, 2015 at 11:36:34 PM UTC-6, John Moss wrote:
>
> Further update:
>
> Apparently I don't even have to login to the bluedragon 
> administrator--simply bringing up the page fixes something for me.
> Any ideas?
>
>
> On Monday, December 28, 2015 at 9:07:17 PM UTC-7, John Moss wrote:
>>
>> I'm trying to convert my session management to use MongoDB and I'm not 
>> sure what I'm doing wrong.
>>
>> Here's what I've done so far (Ubuntu 14.04 LTS/Tomcat7/OpenBD 3.1):
>>
>> 1. "sudo apt-get install mongodb"
>> 2. Edit /etc/mongodb.conf and un-comment the line: "#port = 27017"
>> 3. Go to /bluedragon/administrator and change "Use J2EE Sessions" to "No"
>> 4. Edit Application.cfc and add the following line: <cfset 
>> this.sessionstorage 
>> = "mongo://127.0.0.1:27017" />
>> 5. "sudo service mongodb restart"
>> 6. "sudo service tomcat7 restart"
>>
>> Everything looks good up to this point and mongo now shows an "openbd" 
>> database with a "sessions" collection.
>> My thinking is that if I can get this working correctly on localhost I 
>> should be able to move the mongodb to another location, update the ip 
>> address and this will allow me to add additional web servers for 
>> load-balancing without having to worry about sticky sessions.
>>
>> The problem is that only the first client seems to get a session.
>> Every subsequent attempt seems to fail.
>>
>> I'm a complete novice when it comes to MongoDB but it looks very 
>> promising if I can figure it out!
>> Any ideas on what I need to do?
>>
>> Thanks!
>>
>>
>>

-- 
-- 
online documentation: http://openbd.org/manual/
 http://groups.google.com/group/openbd?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Open 
BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to