Just an idea - since a lot of bugs and inconsistencies discussed in this
forum are related to version (stable/nightly), application server
(tomcat/jetty etc - including IIS issues) and jvm settings - how about
setting up a box in the administrator with all relevant information that the
user can just copy and paste into an e-mail?
On Mon, Apr 30, 2012 at 5:16 AM, Hugo Ahlenius <fraxi...@oxel.net> wrote:
> how about
> setting up a box in the administrator with all relevant information that
> the
> user can just copy and paste into an e-mail?
Already there under server / system info. Seems to copy/paste well enough
to read anyway.
| From: openbd@googlegroups.com [mailto:openbd@googlegroups.com] On Behalf
Of
| Matthew Woodward
| Sent: Monday, April 30, 2012 14:47
| To: openbd@googlegroups.com
| Subject: simplifying support
| | On Mon, Apr 30, 2012 at 5:16 AM, Hugo Ahlenius <fraxi...@oxel.net>
| wrote:
| | | how about
| setting up a box in the administrator with all relevant
| information that the
| user can just copy and paste into an e-mail?
| | | | Already there under server / system info. Seems to copy/paste well
| enough to read anyway.
| | Open BlueDragon Product Version 2,0,2
| Open BlueDragon Build Date 2012-01-01 10:14:17 GMT
| Operating System Linux amd64 (3.0.0-13-generic)
| Application Server Apache Tomcat/7.0.22
| Java Virtual Machine Sun Microsystems Inc. 1.6.0_29 (JVM Properties
| <http://openbd.local/bluedragon/administrator/settings/jvmproperties.cfm | > )
| | --
| Matthew Woodward
| m...@mattwoodward.com
| http://blog.mattwoodward.com | identi.ca / Twitter: @mpwoodward
| | Please do not send me proprietary file formats such as Word, PowerPoint,
| etc. as attachments.
| http://www.gnu.org/philosophy/no-word-attachments.html | | | --
| online documentation: http://openbd.org/manual/ | google+ hints/tips: https://plus.google.com/115990347459711259462 | http://groups.google.com/group/openbd?hl=en
+1 on including what memory settings OpenBD is actually running
under.
Not to be confused with the settings I think it's running
under, due to my lame attempts to set the JVM accordingly.
Al
On 4/30/2012 5:58 AM, Hugo Ahlenius wrote:
Sure, but maybe in a more compact format, and with jvm memory settings
included?
--
Hugo Ahlenius
On Mon, Apr 30, 2012 at 7:42 PM, Alan Holden <alhol...@akh.com> wrote:
> +1 on including what memory settings OpenBD is *actually running under*.
> Not to be confused with the settings *I think* it's running under, due to
> my lame attempts to set the JVM accordingly.
It shows that as well but I'll add a ticket for an easy copy/pasta button.
Oh crap, lookie there it is now - at the bottom of the 2.0.2 admin
system info page!
Man, I need roller skates to keep up with you guys.
Al
On 4/30/2012 8:08 PM, Matthew Woodward wrote:
On Mon, Apr 30, 2012 at 7:42 PM, Alan Holden <alholden@akh.com>
wrote:
+1 on including what
memory settings OpenBD is actually running under.
Not to be confused with the settings I think it's
running under, due to my lame attempts to set the JVM
accordingly.
It shows that as well but I'll add a ticket for an easy
copy/pasta button.
On Fri, May 4, 2012 at 11:22 PM, Alan Holden <alhol...@akh.com> wrote:
> What does it mean when your running OpenBD desktop sends this message to
> the console?
> 2012-05-04 23:14:45.827:WARN:oejh.**HttpGenerator:Ignoring extra content
> What qualifies as "extra content"?
What container are you running in?
-- Matthew Woodward
m...@mattwoodward.com
http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward
Should I have said something beyond "OpenBD desktop"?
This is my Win7 Alienware laptop, running AW's 2.0.2 downloaded on
4-13-12
The message appears under the "Console" tab while the desktop server
is running, I'm guessing at the same time the app is sending some
cookie update in the header. FYI The cookie's content is an appx 260
character string (some encrypted stuff). That cookie could be a red
herring, because it is set at other places without issue.
FYI Turning on CFML's - client cookies - setting seems to vanquish
the message. So that's my fix.
Al
On 5/5/2012 7:46 AM, Matthew Woodward wrote:
On Fri, May 4, 2012 at 11:22 PM, Alan Holden <alholden@akh.com>
wrote:
What does it mean when your running OpenBD desktop sends this
message to the console?
2012-05-04 23:14:45.827:WARN:oejh.HttpGenerator:Ignoring extra
content
On Sat, May 5, 2012 at 4:01 PM, Alan Holden <alhol...@akh.com> wrote:
> Should I have said something beyond "OpenBD desktop"?
Apparently you should have had that in flashing 80pt red letters. ;-) Sorry
I missed that.
> FYI Turning on CFML's - client cookies - setting seems to vanquish the
> message. So that's my fix.
Interesting -- reason I asked about the container is that I found both some
Jetty and Tomcat related info that might have been applicable with some
additional digging, but sounds like you got it sorted.
2012-05-05 19:59:32.826:WARN:oejh.HttpGenerator:Ignoring extra
content
The first one happened some time while I was away for dinner. The
next one was when I returned to the app - and my next request sent
me to my own login page.
I think these things might be tied to session activity: perhaps
expiration and creation respectively?
(there's no explicit sessionTimeout in this app, fwiw. The
ApplicationTimeout is 2 days)
On Sat, May 5, 2012 at 4:01 PM, Alan Holden <alholden@akh.com>
wrote:
Should I have said
something beyond "OpenBD desktop"?
Apparently you should have had that in flashing 80pt red
letters. ;-) Sorry I missed that.
FYI Turning on CFML's -
client cookies - setting seems to vanquish the message. So
that's my fix.
Interesting -- reason I asked about the container is that I
found both some Jetty and Tomcat related info that might have
been applicable with some additional digging, but sounds like
you got it sorted.
On Sat, May 5, 2012 at 8:13 PM, Alan Holden <alhol...@akh.com> wrote:
> They don't appear to affect this app. The only close discussion I could
> find on this message was here:
That's the most relevant one I found as well, which ain't sayin' much.
Maybe someone else will have more insight but good that it's not affecting
the application.
Well, I'll just document that - before SetClientCookies was true -
it apparently happened on every request.
Since it's been true, it only seems to happen onSessionStart.
Al
On 5/5/2012 8:14 PM, Matthew Woodward wrote:
On Sat, May 5, 2012 at 8:13 PM, Alan Holden <alholden@akh.com>
wrote:
That's the most relevant one I found as well, which ain't
sayin' much. Maybe someone else will have more insight but
good that it's not affecting the application.
