Thanks Aaron, Will certainly give that a go and no the box has been left alone in isolation since the original install.
Will come back to the group with my findings but thank you for taking the time to reply, very much appreciated. Regards, Lee On Friday, August 1, 2014 1:24:54 PM UTC+2, Aaron J. White wrote: > > Never happened to me. So I can't help you there. Since it looks like an > SSL error of some sort I guess you confirmed whatever SSL certs, etc you > are using are up to date and in order? Have you upgraded box since > heartbleed? > > > Also, there is no "already made image" for Amazon specifically, but > OpenBDJam <http://openbd.org/jam/> is really good. It is essentially a > pre-configured install for OpenDB that can be used on most linux boxes. > If you get to the point you want to update OpenBD to see if it fixes your > error I would probably go about it this way. > > 1. Check if openbdjam was used to configure your box: Is /opt/openbdjam/ > available? /opt/openbdjam is the default install location and I think many > people leave this alone. > 2. If so, now let’s test how the app operates on the latest version of > OpenBD: We can use Jetty Launcher for this. (Runs app code on any windows > box for development/testing) > > - Copy the web app files from your linux box to a local PC. The app > files could all be at */opt/openbdjam/webroot/* or > */opt/openbdjam/webroot/yoursite* > - Download the Jetty Launcher from the downloads page > <http://openbd.org/downloads/> - Choose a folder and unzip/extract > contents. I believe Jetty Launcher is portable app and can run where ever > you put it. > - Download the J2EE Standard War from the downloads page. Might as > well use the nightly if this application will not be messed with often > - Rename the current WEB-INF folder in your web app files to something > else like WEB-INF_original > - Open the J2EE standard war with any zip archive tool like 7-zip and > move the WEB-INF folder to your web app. > - Run Jetty Launcher -> Click Web App -> add webapp -> Enter a > name, select your port, and for web folder choose location you have the > web > app code -> click ok > - Select your new web app from the web app menu in Jetty Launcher --> > Click start web app --> wait a few seconds --> then open web app > > 3. You can now test your app on the desktop for errors. Depending on what > the app is doing errors may show in the Jetty Launcher console or in the > browser. We replaced the whole WEB_INF folder earlier so if your app has a > lot of custom libs or bluedragon.xml settings then you may want to use the > original WEB-INF folder. You can try just copying the jars from the OpenBD > 3.2 WEB-INF/lib folder to your original WEB_INF/lib folder and then re-run > it through Jetty Launcher. > > > > 4. If the desktop test work out then you probably want to move to testing > the web app on a test EC2 box that has similar settings to production > > > > 5. At this point, you can use the openbdjam upgrade command to update your > version of OpenBD on the server or just manually upgrade the web apps > WEB-INF or WEB-INF/lib files like we covered in steps 2 and 3. > > > > So I hope what I put above is helpful in some way. I can’t tell how much > working knowledge you have about OpenBD so I tried being pretty descriptive > in my explanation on how you could test an OpenBD upgrade if you get to > that point. If you put some code examples up about what’s causing your > errors I’m sure one of the more experienced devs may help. > > > > Also, @Alan: Is it called "Jetty Launcher" or "Jetty Desktop". The name is > not consistent on the site. > -- -- 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.
