We have a large number of objects created for org.jboss.vfs.spi.JavaZipFileSystem ,
We are using 6.4.0.GA with jre 1.7.0_40-b43 and Windows Server 2008 R2
Below is screenshot from yourkit :
huge number of objects
Related
I experienced the following error after installing Information Server Console 8.1 on my windows xp sp2 workstation when I try to log on Information Server Console:
"Internal Error: - Failed to load the Java Virtual Machine. The most common cause of this error is a failure of Java virtual machine to allocate enough memory" Check the memory settings in ......\proxy xml.
I attached proxy.xml for your documentation. Besides my workstation has 4 Gb RAM and Sun Java Runtime Environment v 6.0_11.
"Other possible reasons for this failure are that one or more JARS are not present or some other configuration problem exists." Not very disclosing I suppose ...
I set the environment variables : XMOG_TRACE_LEVEL= Verbose and XMOG_TRACE_FILE=c:\xmogtrace.txt, tried to log on again, but no file or information is generated on c:\xmogtrace.txt and the error is the same.
Please see the following technote in ibm.com which discusses solution for this issue:
http://www-01.ibm.com/support/docview.wss?rs=14&uid=swg21370513
We are having an issue with SQL Server 2008 R2 64 responding to stored procedure call. About every 2 weeks or so, the database stops responding to stored procedures called from an ADO connection/Command set (4.0 framework). We have been working on this for several months now, with little improvement.
System changes:
We upgraded an existing vendor product from SQL Server 2005 to SQL Server 2008 R2 via their upgrade method. The database instance moved from a 32-bit Windows 2003 Server to 64-bit Windows 2008 Server.
The pattern of failure:
The application is run throughout the day, executed by different users via Citrix without issue. Every few weeks, the application stops responding around the same time frame. Once the database stops responding to the hosted instance of the application, any execution of the procedure from the application hangs (installed on CITRIX server, installed on varied physical systems, or debugging in VStudio 2010). After an hour of checking logs, server status, SQL Monitoring tools, tracing the repeated execution attempts, the server decides to respond to the application without intervention.
Strange thing is, when the server is not responding to ADO.Net calls, we execute the stored procedure from SQL Server Management Studio and receive results in 1 to 2 seconds. We are using the same login to access SQL Server Management Studio, and executing the stored procedure with the same parameters.
Looking at the connection string passed to the ADO connection, I don’t see anything unusual:
connectionString="Data Source=myserver\myinstance;Initial Catalog=databaseName;Persist Security Info=True;User ID=xxxxx;Password=yyyyy;Connect Timeout=45"
Tried so far:
Added extra 2gb of RAM to the OS: no change
Added extra tempdb file, expanded size of tempdb log file from 1 to 5gb: reduced the issue from weekly to every 2nd or 3rd week.
Installed SQL Server 2008 R2 SP3: no change.
The black cloud:
To me, the repeating time pattern of failure implies an issue at the database host (server or resource), but the DBAs do not see load or resource issue. If it were purely a host issue, why does it respond to SQL Server Management calls, and not ADO.NET calls?
The last occurrence lasted over two hours, and was resolved after rebooting the database server. Not a great fallback, but desperate times and all…..
Updating the ADO.NET connection to use named pipes has resolved the issue for our application. Prefixing the database name with "np:" has the connection using named pipes.
connectionString="Data Source=np:myserver\myinstance;Initial Catalog=databaseName;Persist Security Info=True;User ID=xxxxx;Password=yyyyy;Connect Timeout=45"
The issue returned on 5/14. This query timeout posting gave us hints how to force SQL Management Studio to behave like the ADO.NET connection and allowed us to recognize this is a "parameter sniffing" issue. We have applied changes to disable the parameter sniffing within the stored procedure.
I have built a asp.net mvc 2 app, using the .NET framework 4.
It runs OK on my windows 7 (64 bit) machine, but when deploying to the server it gives me the following error:
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
I suspect it has something to do with mixing 64 bit and 32 bit, but I have no clue whatsoever. This happens on different windows 2008 r2 servers, so it's not server (hardware) specific.
I did a BIN deployment of mvc 2 (copying system.web.dll, System.ComponentModel.DataAnnotations.dll, and system.web.routing to the BIN folder)
Update
The error occurs as soon as I try to access the database, a MS SQL 2008 server, via Linq-to-SQL.
Who can help me?
I found out why it crashed.
Most of the time a CLR.DLL error is caused by an infinite loop or something like that, just something really stupid.
In my case an unreachable SQL server (or rather: incorrect configured connection string) was causing the error. In my code, when reading or writing to the database failed the application tried write a log error to the same database. Which, of course, failed as well and caused an endless loop.
Yes, too stupid.
I have a report which has 15 Parameters and out of 15 params,2 have 1000 list of values.
When i run this report on SQL Server 2008 r2 report server it is taking 2 minutes of time.
I have installed CU 7 as suggested in MS forum but unfortunately it didn't fixed my Problem.
Why CU 7 is not working for me?any idea?help....
Thanks in advance.
Thanks,
Praveen
Hot fix that installed only works on Windows 7/2008 not on Win XP!!!!!!!
Thanks....
I have a Windows Service application (developed in C++) running under Local System account. Operating system is Windows Server 2008 Standard - Service Pack 2 - 32-bit - 4Gb RAM.
Also running Office 2003 with Service Pack 3.
This service takes a RTF file and using DDE prints it with Microsoft Word. However Word fails to perform the print issuing an error (I can see the error if I enable interaction with desktop). The error is
"Run-time error '1001':
There is insufficient memory. Save the document now.
C:...\file.rtf"
A screenshot can be seen here: http://img804.imageshack.us/img804/9550/worderror.png
It used to work on Windows 2003.
Any idea? Suggestions? Could be permission related?
This is actually not supported by Microsoft: http://support.microsoft.com/kb/257757