I am facing an issue with weblogic server - GC monitor. Sometimes the application running in weblogic is not responding and get stuck. I have to restart the managed server to restore it.When checked the managed server logs , the logs is getting appended till GC monitor log as below
< weblogic.GCMonitor> << anonymous>> <> <> <1234123456795> <83% of the total memory in the server is free.>
After that there is no logs is getting recorded. Is there any way to monitor the logs in weblogic and send email to me when the logs is not getting recorded. So that i will restart server immediately.
Related
One of my Windows login is trying to connect to SQL Server 2008 R2 Express; he is facing this issue:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding
This Issue appears only once a day i.e. when the initial request is made to connect to the server.
I have tried with my SA login but I didn’t find any issue for the first time login in a day.
He has tried connecting to SQL Server with server name as well as IP address but that hasn’t solved the issue.
Can anyone please resolve this issue?
Thanks in advance.
This thread seems to describe your problem:
http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/58bd9c4d-0572-4567-8e32-82a7fd600022
Yes, i have fixed this problem.
My windows server 2008 was configured to reject SASL LDAP binds (see
warning 2886).
Since i have configured my server to not reject such binds, sql server
2008 connections work correct.
or
I was able to solve the problem of not being able to connect on the
first attempt by configuring the instance of SQL Server to listen on a
static port and adding an exception for that port to the firewall.
You could look here for info.
Less likely, but it's also possible you have Auto_Close enabled.
When set to ON, the database is shut down cleanly and its resources
are freed after the last user exits. The database automatically
reopens when a user tries to use the database again.
When set to OFF, the database remains open after the last user exits.
I have a dotnet exe app in a server which runs in sql server. during the factory production time my application were unable to connect to db for 1 to 2 minutes and then it gains connectivity at this unresponsive time when i accessed sql server management studio, i got the below error:
Taken from the answer over here.
This usually happens when there are too many open transactions that are blocking read access to your database server. You can try restart your server which will usually solve the issue.
The weblogic 12c admin server is shutting down automatically after getting started so the gui web page start giving error that the page cannot be displayed but the managed servers are running the whole time even when the admin server goes down.......plz suggest any fix for this
You may have a problem with your JVM space, check if you have enougth memory to start.
I have RabbitMQ 3.5.5 installed on a Windows 2008 R2 server as a Windows service. Everything is as default. The log location is at C:\Users\myuser\AppData\Roaming\RabbitMQ\log and I can see 2 log files:
rabbit#HOSTNAME.log
rabbit#HOSTNAME-sasl.log
However, they are always empty though RabbitMQ seems to be working fine; i.e., I can log into the web management console, add/delete users, publish/get messages.
Why are the logs empty? What am I missing?
I have some SSIS jobs running in the production server which we usually take that server by Windows' Remote Desktop Connection to monitor the jobs. The problem in our case is If we sign out the server in remote connection, all the sql server jobs getting failed until we reestablish a remote connection but the jobs work fine if we close the remote connection explicitly by the (x) mark on the Remote Connection interface
Any idea on this issue
Presumably those jobs are being executed under the current users account rather than a system service account ? I suspect the problem is that "signing out" essentially logs the current user off the box, terminating all their current processes, whereas just closing the RDP session does not log them out and so the job continues running.