We have 2 servers which used to run FactorySQL for the past 2 years, We recently upgraded to Ignition. Following are the server specs
Windows 2003 R2 Standard Edition SP2
Quad Core 2.26 Xeon, 4 GB Ram
Java 6 Update 33
Apart from Ignition, I have Rockwell’s FactoryTalk Gateway and FactoryTalk Service Platform Installed on the servers.
The Ignition project has 402 groups with around 40000 tags in Total
Ignition conencts with 4 SQL Server 2005 databases and only 1 FactoryTalk Gateway OPC Server
Now, since we upgraded to ignition, many a times, the ignition has stopped working with the following messages flooding the wrapper logs.
Failed to post the message to the thread. ThreadID = 3780, errorCode = 1816
com.jniwrapper.win32.LastErrorException: Not enough quota is available to process this command. (Refer to WraperLog1 attached to see the full message which is repeated 1000s of time)
While in this state, the gateway webpage doesnt open nor does it give an error, it just goes into waiting. No groups seem to be running and neither is any data being cached.
Suffice to say, it has been frustrating to run the same project upgraded from FactorySQL in ignition. There is sufficient C Drive space as well as I have monitored the server while this error is being logged into the wrapper logs and the JAVA.exe is cose to 350 MB memory and the remaining server is functioning fine. Please any help on this would be great.
Another thing is that similarly, many a times, when the server is restarted, the master will ask the backup node to become inactive but would not startup itself properly also or take too long to startup, which causes data loss. Is there anyway for the Master to only take control, after it has started up correctly? I was looking at the startup conenction allowance but from the manual, I dont think I really understand what effect it has. The backup becomes the master quickly because it is set to Warm backup but when the master is restarted, the backup becomes inactive after being “asked” by the master , even though the master hasnt started up correctly.
Refering to Wrapper Log, it stops at random messages. I am attaching WrapperLog2 which has a typical startup but pelase note that it stopped at 2012/06/26 13:19:05 ie. it wasnt becoming active and had made the backup inactive long ago, so I had to restart it again.
I had to setup a group to log time every minute and then had to write an app to monitor and force restart the server if it gets stuck. I upgraded Java6 update 31 to update 33 today and still on some restarts, ignition has failed to become running properly. My users are at their patience limit and I am thinking about going back to FactorySQL, since the project is the same which ran in FactorySQL fine for years.
wrapperLog2.log (33.9 KB)
wrapperLog1.log (3.02 KB)