"Your request produced an error."

[objectwerks inc]

I have an app I am hosting for someone. I do not have the source. He does not have the source either (it was written for him by some consultants long ago).

It had been running fine last I heard but yesterday the guy for whom the app is running came to me and said that you got an error when you tried to actually do anything. It has a direct action to login with and when you do that the browser says

"Your request produced an error."

The output log has one line: [2013-9-11 23:43:59 MDT] <WorkerThread2> An exception occurred while trying to open a channel: N/A

I checked the connection dictionary and it is correct (I can use the info to log in using sql92 for example)

I cannot find any exceptions or anything. I tried running the app by hand at the command line and when I connect to it through the browser I get nothing but that line in the output log. No exceptions on screen or in the log.

The database is a FrontBase 5 on Linux. Wo is running on FreeBSD with Java7

I am not sure what to do at this point. It has been a while since I debugged this sort of issue.

Thanks
Chad

[Chuck Hill]

Hi Chad,

My first guess given that nothing has change is that the database is
corrupt or stopped. Can you connect with FrontBase Manager?


Chuck
--
Chuck Hill
Executive Managing Partner, VP Development and Technical Services


Practical WebObjects - for developers who want to increase their overall
knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/gvc/practical_webobjects

Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest
Growing Companies in B.C!

Global Village Consulting ranks 44th in 25th annual PROFIT 500 ranking of
Canada¹s Fastest-Growing Companies by PROFIT Magazine!

Post by objectwerks inc
I have an app I am hosting for someone. I do not have the source. He
does not have the source either (it was written for him by some
consultants long ago).
It had been running fine last I heard but yesterday the guy for whom the
app is running came to me and said that you got an error when you tried
to actually do anything. It has a direct action to login with and when
you do that the browser says
"Your request produced an error."
The output log has one line: [2013-9-11 23:43:59 MDT] <WorkerThread2> An
exception occurred while trying to open a channel: N/A
I checked the connection dictionary and it is correct (I can use the info
to log in using sql92 for example)
I cannot find any exceptions or anything. I tried running the app by
hand at the command line and when I connect to it through the browser I
get nothing but that line in the output log. No exceptions on screen or
in the log.
The database is a FrontBase 5 on Linux. Wo is running on FreeBSD with
Java7
I am not sure what to do at this point. It has been a while since I
debugged this sort of issue.
Thanks
Chad
_______________________________________________
WebObjects-dev mailing list
http://www.omnigroup.com/mailman/listinfo/webobjects-dev

[objectwerks inc]

Post by Chuck Hill
Hi Chad,
My first guess given that nothing has change is that the database is
corrupt or stopped. Can you connect with FrontBase Manager?
Chuck

Hi Chuck

Yes, I can log in to the db using FrontBase Manager (my FB manager is messed up on my Mac so after logging in I don't get a window, but this happens with all the DBs I have on the db server, and is not related I think since the other DBs and apps work fine though they exhibit the same issue when I log in throgh FB Manager -- I can log in using the command line sql92 and it shows a FB Manager connection and I can also interact with the DB using sql92 command line tool).

So the DB is running and does not appear to be corrupt since I can access and query it in sql92.

I've been trying to get the app to show my whatever exception is causing the error, to no avail.

Chad

[Chuck Hill]

You are certain that no one has changed anything? The app server can talk
to the db server? I might be worth trying to connect to the db server
using sql92 on the app server. Did the app's configuration file get
corrupted? I can't think of much else that would cause this.



Chuck

Post by objectwerks inc

Post by Chuck Hill
Hi Chad,
My first guess given that nothing has change is that the database is
corrupt or stopped. Can you connect with FrontBase Manager?
Chuck

Hi Chuck
Yes, I can log in to the db using FrontBase Manager (my FB manager is
messed up on my Mac so after logging in I don't get a window, but this
happens with all the DBs I have on the db server, and is not related I
think since the other DBs and apps work fine though they exhibit the same
issue when I log in throgh FB Manager -- I can log in using the command
line sql92 and it shows a FB Manager connection and I can also interact
with the DB using sql92 command line tool).
So the DB is running and does not appear to be corrupt since I can access
and query it in sql92.
I've been trying to get the app to show my whatever exception is causing
the error, to no avail.
Chad

[objectwerks inc]

There are other apps on the same server (in different freebsd jails) that talk to the same db server. (Both are VMs on the same HW).

As fasr as I can tell the app config file has not been corrupted. Visually dumping out the text files as well as looking in the JavaMonitor it looks ok, and the eo connection dictionary is ok (that is how I got the info to log in to the db using sql92).

I have not tried using sql92 on the app server as it is not installed. I'll see if I can install it (there was an issue that FB support for FreeBSD dropped and it did not work on newer versions of FreeBSD, though that might not affect the sql92 component).

I grabbed the latest frontbase jdbs driver and put that on the app server but it did not help.

I wish that WO would actually let me see the exception somewhere so I could see what it is complaining about.

I will go recheck all the config files and connection dictionaries etc, to make sure they are all 100% correct and my brain is not mentally seeing what it wants to see versus what is there...

Thanks for all your help
Chad

Post by Chuck Hill
You are certain that no one has changed anything? The app server can talk
to the db server? I might be worth trying to connect to the db server
using sql92 on the app server. Did the app's configuration file get
corrupted? I can't think of much else that would cause this.
Chuck

Post by objectwerks inc

Post by Chuck Hill
Hi Chad,
My first guess given that nothing has change is that the database is
corrupt or stopped. Can you connect with FrontBase Manager?
Chuck

Hi Chuck
Yes, I can log in to the db using FrontBase Manager (my FB manager is
messed up on my Mac so after logging in I don't get a window, but this
happens with all the DBs I have on the db server, and is not related I
think since the other DBs and apps work fine though they exhibit the same
issue when I log in throgh FB Manager -- I can log in using the command
line sql92 and it shows a FB Manager connection and I can also interact
with the DB using sql92 command line tool).
So the DB is running and does not appear to be corrupt since I can access
and query it in sql92.
I've been trying to get the app to show my whatever exception is causing
the error, to no avail.
Chad

[Chuck Hill]

Any news on this?

Chuck

Post by objectwerks inc
There are other apps on the same server (in different freebsd jails) that
talk to the same db server. (Both are VMs on the same HW).
As fasr as I can tell the app config file has not been corrupted.
Visually dumping out the text files as well as looking in the JavaMonitor
it looks ok, and the eo connection dictionary is ok (that is how I got
the info to log in to the db using sql92).
I have not tried using sql92 on the app server as it is not installed.
I'll see if I can install it (there was an issue that FB support for
FreeBSD dropped and it did not work on newer versions of FreeBSD, though
that might not affect the sql92 component).
I grabbed the latest frontbase jdbs driver and put that on the app server
but it did not help.
I wish that WO would actually let me see the exception somewhere so I
could see what it is complaining about.
I will go recheck all the config files and connection dictionaries etc,
to make sure they are all 100% correct and my brain is not mentally
seeing what it wants to see versus what is there...
Thanks for all your help
Chad

Post by Chuck Hill
You are certain that no one has changed anything? The app server can
talk
to the db server? I might be worth trying to connect to the db server
using sql92 on the app server. Did the app's configuration file get
corrupted? I can't think of much else that would cause this.
Chuck

Post by objectwerks inc

Post by Chuck Hill
Hi Chad,
My first guess given that nothing has change is that the database is
corrupt or stopped. Can you connect with FrontBase Manager?
Chuck

Hi Chuck
Yes, I can log in to the db using FrontBase Manager (my FB manager is
messed up on my Mac so after logging in I don't get a window, but this
happens with all the DBs I have on the db server, and is not related I
think since the other DBs and apps work fine though they exhibit the
same
issue when I log in throgh FB Manager -- I can log in using the command
line sql92 and it shows a FB Manager connection and I can also interact
with the DB using sql92 command line tool).
So the DB is running and does not appear to be corrupt since I can
access
and query it in sql92.
I've been trying to get the app to show my whatever exception is
causing
the error, to no avail.
Chad