Although the .net error, The type initializer for 'Oracle.DataAccess.Types.OracleDecimal' threw an exception., is recorded to a log, the app ONLY does this every couple days and it continues to do it unless you get the error to go away(more on that below).
While I'm not very familiar with pools in IIS, I know our company recently organized ALL its .net applications into separate app pools. Shortly after doing this, we encountered this issue, and it's caused our .net apps to not work which use the OracleDecimal
reference. This has happened since 12/14/2009 (it's now 2/15/2010), and what's our current solution you ask? The magic of IIS reset every couple days. As you would expect, this isn't a popular solution but it works until we can determine the root cause.
Could this be a memory leak issue? I certainly don't think it's code since we didn't release any major changes that would cause the application to fail every couple days. Also, I heard if left to its default app pool setting, the memory will be recycled
if 50% or more is used up, can anyone confirm this at least?
Has anyone had an issue similar to this?
Thanks, and I appreciate any reply regarding this issue.
kentstate12
0 Points
3 Posts
The type initializer for 'Oracle.DataAccess.Types.OracleDecimal' threw an exception.
Feb 15, 2010 06:52 PM|LINK
Although the .net error, The type initializer for 'Oracle.DataAccess.Types.OracleDecimal' threw an exception., is recorded to a log, the app ONLY does this every couple days and it continues to do it unless you get the error to go away(more on that below). While I'm not very familiar with pools in IIS, I know our company recently organized ALL its .net applications into separate app pools. Shortly after doing this, we encountered this issue, and it's caused our .net apps to not work which use the OracleDecimal reference. This has happened since 12/14/2009 (it's now 2/15/2010), and what's our current solution you ask? The magic of IIS reset every couple days. As you would expect, this isn't a popular solution but it works until we can determine the root cause. Could this be a memory leak issue? I certainly don't think it's code since we didn't release any major changes that would cause the application to fail every couple days. Also, I heard if left to its default app pool setting, the memory will be recycled if 50% or more is used up, can anyone confirm this at least?
Has anyone had an issue similar to this?
Thanks, and I appreciate any reply regarding this issue.
Bryan
druidprieste...
Member
2 Points
1 Post
Re: The type initializer for 'Oracle.DataAccess.Types.OracleDecimal' threw an exception.
Jan 03, 2013 06:08 PM|LINK
We are having this issue too. Was a solution ever found?