Hi Jarl, At last I'm making progress. Your fix didn't help directly but in applying it I noticed that I had a "copy of arsys.xml" in my tomcat conf/catalina/localhost directory. This obviously caused the 2 instances of the arsys application to be loaded. Removing it an restarting tomcat gave me a clean startup for the first time on this server.
Now the mid-tier is still not working fully but at least the double loading problem is gone. I will try and re-install the mid tier now that the main issue seems to have been resolved. Thanks for the help from both you and Joe, Rod On 26 February 2010 17:08, Jarl Grøneng <[email protected]> wrote: > Try copy the file arsys_sample.xml to the Tomcat lib directroy > (common\lib if tomcat 5.5), and rename the file to: arsys_api.xml. > > Change the line: > <jniLoadMode>1</jniLoadMode> > to: > <jniLoadMode>0</jniLoadMode> > > Then restart tomat. Then the jni should never be loaded. > > Regards, > Jarl > > 2010/2/26 Rod Harris <[email protected]>: >> Hi Joe, >> >> I think you're on the right track with thinking that there are 2 >> Tomcats running. From a close examination of the log file it appears >> that Tomcat is getting halfway through its startup and then starting >> again. Not sure why its doing that but I guess that is causing the >> duplicate load error. My new questions are why is Tomcat trying to >> start twice and how do I fix it? >> >> Here is the Tomcat logfile stdout.log down to the error that now >> seems less important than it did before. My older server is similar >> only it throws the same error about mime multipart and then moves on >> to creating Proxy 3 etc. not back to the start again. >> >> Thanks for your help, >> >> Rod >> >> >> >> - Trying to load configuration arsys_api.xml >> - Could not load optional configuration arsys_api.xml >> - Trying to load configuration default.xml >> - jrpcMode: true >> - jniLoadMode: 1 >> - apiRecordingMode: 0 >> - maxProxiesPerServer: 10 >> - minimumSupportedServerRpcVersion: 12 >> - connectionMaxRetries: 0 >> - timeLagBetweenRetriesMillSec: 1000 >> - stringizeFieldAssignments: false >> - stringizeSetIfQualification: false >> - useLegacyQualParser: false >> - useLegacyAssignParser: false >> - useLegacyQualFormatter: false >> - useLegacyAssignFormatter: false >> - Client sets connection limits per server to :80 >> - Client sets useConnectionPooling to : true >> - fipsProviderJsafeJCE installed = false >> - Connects to ARServer audcaapp26 through com.bmc.arsys.api.proxyj...@1ca1588 >> - Created proxy 1 by Tid_9 for server audcaapp26:50100 >> - Connects to ARServer audcaapp26 through com.bmc.arsys.api.proxyj...@4bb369 >> - Created proxy 2 by Tid_9 for server audcaapp26:50100 >> - Unable to find required classes (javax.activation.DataHandler and >> javax.mail.internet.MimeMultipart). Attachment support is disabled. >> - Trying to load configuration arsys_api.xml >> - Could not load optional configuration arsys_api.xml >> - Trying to load configuration default.xml >> - jrpcMode: true >> - jniLoadMode: 1 >> - apiRecordingMode: 0 >> - maxProxiesPerServer: 10 >> - minimumSupportedServerRpcVersion: 12 >> - connectionMaxRetries: 0 >> - timeLagBetweenRetriesMillSec: 1000 >> - stringizeFieldAssignments: false >> - stringizeSetIfQualification: false >> - useLegacyQualParser: false >> - useLegacyAssignParser: false >> - useLegacyQualFormatter: false >> - useLegacyAssignFormatter: false >> - Client sets connection limits per server to :80 >> - Client sets useConnectionPooling to : true >> - Could not load native library >> java.lang.UnsatisfiedLinkError: Native Library C:\Program Files\BMC >> Software\ARSystem\midtier\WEB-INF\lib\arutiljni75.dll already loaded >> in another classloader >> >> On 26 February 2010 00:51, Joe D'Souza <[email protected]> wrote: >>> Try to verify if Tomcat is being used by anything else that may be already >>> loading that dll before you attempt to start the Tomcat service.. One way to >>> find out is running a netstat and see if the Tomcat port is in use while the >>> service appears to be down.. The default port would be 8080 unless otherwise >>> configured. >>> >>> If this port seems to be in use, then it means that an instance of Tomcat is >>> already running and has been started by some other application. You will >>> need to find what that application is.. >>> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" >> > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
