Hi ESI Champions / Gurus,
We are using Windchill with Oracle Fusion Middleware. It is a Windchill
cluster environment, and i am able to see that for any invoke to
ESIExportJMS.xml is hitting the background method server and not the
foreground MS.
Cluster Env:
1) There are 2 app node, 1 Background MS, 1 Server Manager.
2) On both App nodes, the background MS is NOT running
3) wt.queue.executeQueues=true is ONLY on Background MS on other App nodes
it is wt.queue.executeQueues=false
4) The properties of username/password work if the background method server
is switched off
Stack on Background MethodSever:-
javax.naming.NamingException: Lookup error:
javax.naming.AuthenticationException: Not authorized; nested exception is:
INFO [SessionThread-10] wt.system.out -
javax.naming.AuthenticationException: Not authorized [Root exception is
javax.naming.AuthenticationException: Not authorized]
INFO [SessionThread-10] wt.system.out - at
com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:69)
INFO [SessionThread-10] wt.system.out - at
javax.naming.InitialContext.lookup(InitialContext.java:392)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.messaging.MsgService.lookupAdminObject(MsgService.java:1328)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.messaging.MsgService.lookupConnectionFactory(MsgService.java:1413)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.messaging.MsgService.getConnectionFactory(MsgService.java:495)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.messaging.MsgService.initializeQueueSupport(MsgService.java:369)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.messaging.MsgService.getMsgService(MsgService.java:276)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.webject.msg.CreateObject.invoke(CreateObject.java:23)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.procunit.webject.WebjectProcessor.invokeWebject(WebjectProcessor.java:624)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.procunit.webject.WebjectProcessor.processTask(WebjectProcessor.java:210)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.SAK.Webject.invoke(Webject.java:491)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.compiledTasks.file.opt.Windchill_10.Windchill.tasks.com.ptc.windchill.esi.export.exporttojmsqueue$2exml.invoke(exporttojmsqueue$2exml.java:241)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.SAK.Task.invoke(Task.java:1806)
INFO [SessionThread-10] wt.system.out - at
com.infoengine.SAK.Task.invoke(Task.java:1714)
INFO [SessionThread-10] wt.system.out - at
com.ptc.windchill.esi.txn.ESIResponseSender.run(ESIResponseSender.java:149)
INFO [SessionThread-10] wt.system.out - at
wt.session.SessionThread.run(SessionThread.java:165)
INFO [SessionThread-10] wt.system.out - Caused by:
javax.naming.AuthenticationException: Not authorized
INFO [SessionThread-10] wt.system.out - at
oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:100)
INFO [SessionThread-10] wt.system.out - at
oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:69)
INFO [SessionThread-10] wt.system.out - at
com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:700)
INFO [SessionThread-10] wt.system.out - at
com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:244)
INFO [SessionThread-10] wt.system.out - at
com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:228)
INFO [SessionThread-10] wt.system.out - at
com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:302)
INFO [SessionThread-10] wt.system.out - at
com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:56)
INFO [SessionThread-10] wt.system.out - ... 15 more
Questions:
1) Can Background MethodServer do a lookup for the ESI properties
configured in the Windchill Adapter or esi.properties?
2) Since it is cluster, and Background MS is on other application node, how
do we handle this in Windhcill ? is there any properties or any
configuration on Windhcill Adpater which we have to do?
Observations:
1) When we switch off the background MS on different app node and make it
monolithic. Keep Background MS ON on the same app node. it works fine
2) Is there any communication between Server Manager to background MS
without request going to foreground? Any RMI Calls?
3) Any Windchill properties to take care of?
Regards,
Arunkumar Nadar
