SessionContext contains wrong caller identity on cluster environment

I have follwoing problem.
I need to process first anonymous call to EJB from client and next calls should be not-anonymous.
I create InitialContext with Context.SECURITY_PRINCIPAL and Context.SECURITY_CREDENTIALS set to value "anonymous". To make second call to EJB I close explicitly previous InitialContext and create new one passing real values in Context.SECURITY_PRINCIPAL and Context.SECURITY_CREDENTIALS
If I work with standalone AppServers everything works fine but as I switch to Oracle AS cluster I SOMETIMES get from SessionContext.getCallerPrincipal() real value which was passed on client side to InitialContext and SOMETIMES I get this "anonymous".
It looks like some kind of caching makes it wrong. But I have no idea in which direction to go. Can anybody help me?
One remark to this: I get such behaviour even in the case if all calls from client go to the same server (I see it in rmi debug on client).

Hi Prashant,
Thank you for your posting!
Since the issue is related to Azure, I suggest you refer to the experts on Azure forums to get more efficient support:
Azure Active Directory Forum
http://social.technet.microsoft.com/Forums/windowsazure/en-US/home?forum=windowsazureaditpro&filter=alltypes&sort=lastpostdesc
Managing Services on Azure Forum
http://social.technet.microsoft.com/Forums/windowsazure/en-US/home?forum=windowsazuremanagement
Thank you for your understanding and support!
Amy

Similar Messages

Web Services Session /Singleton cluster environment

Hi!
I am having trouble figuring out how to do sessions in web services.
I am trying to build an app that uses multiple GUI's in different languages (not java) and we want to implement our business layer with web services.
I need a session to save user settings, and user info so that I can avoid going to the database and ldap in every call.
So far my idea is to have a web service that deals with the authentication. If the user is valid, the web service will save in a singleton that has hashmap the user setting and return to the client the hashmap key as a token.
The client has the responsibility to save the token and to use it in later calls.
The problem that I have is that a singleton would not work in a cluster environment! And I really don't want to be passing all the user information between calls
Any ideas how can I solve this???

Hi Gaurav,
Yes, the currently running session will be taken care of by the another server node which is up and running.
Your question: Does this mean that the a session of WebDynpro application will continue to work or the changes are lost and the user needs to login again?
"The state of the session is maintained in the persistent storage after the last successfully ended request." Which means that for example a user was filling up a form and haven't saved the changes and the server crashes then the data on that form will be lost when the second server node starts processing the request. But if the user had saved the data before the server crashes that state of the session will be stored and the data of the form will be saved and user need not fill it up again. If the Server crashes in between the HTTP request session then the request is assinged to the another server node to generate the response. In none of the case user needs to login again.
Your question: Fundamentally the question is what WebDynpro uses behind the scenes for maintaining session?
It uses Java Serialization to serialize the HTTP Sessions
"Serialization involves saving the current state of an object to a stream, and restoring an equivalent object from that stream. The stream functions as a container for the object. The information stored in the container can later be used to construct an equivalent object containing the same data as the original."
Edited by: Aishwarya Sharma on Oct 7, 2008 8:07 AM

Scheduling,Email Setup in cluster environment and multiple job servers

Hello All,
I have to schedule and email instances of crystal reports to users in PDF and excel format. A Clustered environment of Business Objects 3.1 SP3 is been setup on 2 servers. There is 2 instances of crystal reports Job server been created.
My question is If there are multiple instances of job servers then should we have to configure mail settings on both instances of job server or not?
And secondly, in cluster environment the email settings and scheduling of the reports should be setup on both CMS servers( CMS server 1 and CMS server 2) or should CMS server 1 should be enough?
Thanks in advance.

You have a couple of options here.
1. You can either set up email on all of the job servers on both CMS' in the cluster. This is actually the easiest to manage.
2. You can set up email on some of the job servers on one or the other CMS. However, at this point you would also have to set up a server group that contains the job servers that are set up for email, plus the RAS server - you might also have to include the Crystal Cache server and the Crystal Processing server. Then ALL of the reports that are sent via email would have to be scheduled run ONLY on the server group that contains the email-enabled job server(s).
-Dell

ADS Configuration issue in HA cluster environment

Hi All,
We have HA cluster environment in which we have installed primary node, secondary node and additional application server. We have configured ADS in HA cluster but when we execute "fp_test_00" program in SE38 it throws "ADS: com.adobe.ProcessingException: com.adobe.Processin(200101)" exception. As well as RFC destination "FP_ICF_DATA_<SID>" in java system throws "Error during ping operation: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connection refused: connect" while we ping destination.
I have checked URL,Port and Logon data all information provided for RFC is fine. Please help me to resolve this issue.
Thanks

Hi Reagan
As you suggested I have checked the URL(http://hostname:8000) has been used for connection, logon data is also fine. Below I have attached dev_icm trace file and there I can see that system throwing error while "reading data from message server"
dev_icm
Thr 14116] Mon May 19 01:11:29 2014
[Thr 14116] {0000a598} Traffic Control: Nettimeout (30) exceeded by peer: 10.15.212.11:23327 [icxxthr.c 4303]
[Thr 16228] Mon May 19 03:51:29 2014
[Thr 16228] *** ERROR => MsINiRead: NiBufReceive failed (NIECONN_BROKEN) [msxxi.c      2829]
[Thr 16228]
[Thr 16228] *****************************************************************************
[Thr 16228] *
[Thr 16228] * ERROR       Reading data from the message server (hostname / 3901)
[Thr 16228] *              failed.
[Thr 16228] *              Please check the trace file of the message server.
[Thr 16228] *
[Thr 16228] * TIME        Mon May 19 03:51:29 2014
[Thr 16228] * RELEASE     721
[Thr 16228] * COMPONENT   MS (message handling interface, multithreaded)
[Thr 16228] * VERSION     4
[Thr 16228] * RC          -36
[Thr 16228] * MODULE      msxxi.c
[Thr 16228] * LINE        2848
[Thr 16228] * COUNTER     173
[Thr 16228] *
[Thr 16228] *****************************************************************************
[Thr 16228]
[Thr 16228] *** ERROR => MsIReadFromHdl: NiRead (rc=NIECONN_BROKEN) [msxxi.c      1867]
[Thr 16228] JNCMIMsConnBrokenCallback: Message server connection broken
[Thr 16228] IcmJncmConnBrokenCallback called
[Thr 16228] JNCMReconnectAsync: Start Message Server reconnect, command MS_J2EE_RECO(2), allow 3600 sec for reconnect
[Thr 16228] JNCMReconnectAsync: Allow 30 sec for consistent cluster reconnect
[Thr 16228] Mon May 19 03:51:30 2014
[Thr 16228]
[Thr 16228] *****************************************************************************
[Thr 16228] *
[Thr 16228] * ERROR       The connection to the specified message server
[Thr 16228] *              (hostname / 3901) failed. Please check the trace file
[Thr 16228] *              of the message server. If a network filter has
[Thr 16228] *              been activated (see message server parameters
[Thr 16228] *              ms/acl_file_...) please check the configuration
[Thr 16228] *
[Thr 16228] * TIME        Mon May 19 03:51:30 2014
[Thr 16228] * RELEASE     721
[Thr 16228] * COMPONENT   MS (message handling interface, multithreaded)
[Thr 16228] * VERSION     4
[Thr 16228] * RC          -35
[Thr 16228] * MODULE      msxxi.c
[Thr 16228] * LINE        2783
[Thr 16228] * COUNTER     176
[Thr 16228] *
[Thr 16228] *****************************************************************************
[Thr 16228]
[Thr 16228] *** ERROR => MsIAttachEx: MsINiWrite (rc=-35) [msxxi.c      884]
[Thr 16228] JNCMIMsConnBrokenCallback: Message server connection broken during reconnect
[Thr 16228] JNCMReconnectAsync: cannot reconnect to message server [cmd=MS_J2EE_RECO(2),loop=1], rc=-35(-35)
dev_server0
[Thr 10444] Mon May 19 03:51:30 2014
M [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 26/sock 4824
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 42/sock 8104
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 50/sock 368
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 7128
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M
M [Thr 6832] Mon May 19 03:51:32 2014
M [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 19208] Mon May 19 03:51:32 2014
M [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 10444] Mon May 19 03:51:32 2014
M [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 4680] Mon May 19 03:51:32 2014
M [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 368
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 27/sock 7592
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 43/sock 8104
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 51/sock 4824
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M
M [Thr 6832] Mon May 19 03:51:35 2014
M [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 10444] Mon May 19 03:51:35 2014
M [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 44/sock 7780
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M
M [Thr 4680] Mon May 19 03:51:35 2014
M [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 368
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M
M [Thr 19208] Mon May 19 03:51:35 2014
M [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 52/sock 8104
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 28/sock 7592
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M
M [Thr 19208] Mon May 19 03:51:40 2014
M [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 6832] Mon May 19 03:51:40 2014
M [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 53/sock 7128
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 45/sock 7952
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M
M [Thr 4680] Mon May 19 03:51:40 2014
M [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 10444] Mon May 19 03:51:40 2014
M [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 29/sock 4824
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 8508
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M
M [Thr 19208] Mon May 19 03:51:49 2014
M [Thr 19208] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 10444] Mon May 19 03:51:49 2014
M [Thr 10444] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 4680] Mon May 19 03:51:49 2014
M [Thr 4680] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M
M [Thr 6832] Mon May 19 03:51:49 2014
M [Thr 6832] ***LOG Q0I=> NiPConnect2: IP-address:3301: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
M [Thr 19208] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 30/sock 4824
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 10444] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 54/sock 7592
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 4680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 46/sock 7128
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
M [Thr 6832] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 7952
    (SI_ECONN_REFUSE/10061; I4; ST; IP-address:3301) [nixxi.cpp    3285]
Please see these logs and let me how I can resolve this issue.

OSB Email Transport polling in multi cluster environment

Hi,
I have following scenario: email needs to be read by OSB proxy using the Email transport. The proxy service service will poll the IMAP mail box and processes messages, upon reading a message message is deleted.
The email transport works fine in a cluster environment by using a dedicated managed node for polling, so no duplicate messages will occur.
However, we have two clusters in our environment pointing to one mailbox. In this case, two clusters have no visibility of each other. So, two pollers may poll the same mailbox.
Please, advice if there any configuration on OSB, Weblogic or IMAP can be done to solve this issue.
thanks,
Djail

Dont think it will work in an Active-Active setup. If you have both clusters listening to same email address then both will receive a copy (just like you receive same email on your desktop's email client and also on your mobile's email client) because SMTP servers distribute to clients similar to how a JMS Topic works.
Dont know if there is a setup in IMAP which will allow an email to be sent to only one client (in this case one of the OSB clusters).
If you want to make it work in Active-Active then you will need to do it at functional level, for ex. after receiving an email if you have any unique id then log that in a transaction table, before calling the backend, check if the same email was already processed by the other cluster. Alternatively, check at the backend before processing it.

Managed SOA Server not started in cluster environment.

Hi,
I am trying to make a SOA cluster environment on Linux based machines. After doing domain configuration which also involved packing of domain on machine 1 and unpacking on machine2, I tried to start the servers. I'm able to start AdminServer successfully and also the managed soa server on the same machine. When I'm trying to start managed soa server on other machine, I'm getting the following error..
*<Unable to establish JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://192.168.122.1:7001/jndi/weblogic.management.mbeanservers.domainruntime.*
java.io.IOException>
My machine IP is XXX.XX.XXX.41 for Admin and XXX.XX.XXX.42 for Machine2. I guess the IP 192.168.122.1 is being used for cluster connection by Machine2 to make connection to Machine1. the managed soa server is getting started after the chain of error logs but it is not starting as a part of the entire cluster and comes as shutdown in WLS Console.
I'm using Linux 5 Update 7 OS and SOA 11.1.1.5.0. Any help will be appreciated for resolving this issue.
Please find the logs below.
*<Unable to establish JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://192.168.122.1:7001/jndi/weblogic.management.mbeanservers.domainruntime.*
java.io.IOException
*     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)*
*     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
*     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
*     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
*     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
*Caused By: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://192.168.122.1:7001: Destination unreachable; nested exception is:*
*     java.net.ConnectException: Connection refused; No available router to destination]*
*     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)*
*     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)*
*     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)*
*     at weblogic.jndi.Environment.getContext(Environment.java:315)*
*     at weblogic.jndi.Environment.getContext(Environment.java:285)*
*     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
*     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
*     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
*     at javax.naming.InitialContext.init(InitialContext.java:223)*
*     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
*     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
*     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
*     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
*     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
*     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
Caused By: java.net.ConnectException: t3://192.168.122.1:7001: Destination unreachable; nested exception is:
*     java.net.ConnectException: Connection refused; No available router to destination*
*     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)*
*     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)*
*     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)*
*     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)*
*     at weblogic.jndi.Environment.getContext(Environment.java:315)*
*     at weblogic.jndi.Environment.getContext(Environment.java:285)*
*     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
*     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
*     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
*     at javax.naming.InitialContext.init(InitialContext.java:223)*
*     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
*     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
*     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
*     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
*     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
*     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
Caused By: java.rmi.ConnectException: Destination unreachable; nested exception is:
*     java.net.ConnectException: Connection refused; No available router to destination*
*     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)*
*     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)*
*     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)*
*     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)*
*     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)*
*     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)*
*     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)*
*     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)*
*     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)*
*     at weblogic.jndi.Environment.getContext(Environment.java:315)*
*     at weblogic.jndi.Environment.getContext(Environment.java:285)*
*     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)*
*     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)*
*     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)*
*     at javax.naming.InitialContext.init(InitialContext.java:223)*
*     at javax.naming.InitialContext.<init>(InitialContext.java:197)*
*     at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)*
*     at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)*
*     at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)*
*     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.notifyDomainRuntime(RegisterWithDomainRuntimeService.java:137)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.start(RegisterWithDomainRuntimeService.java:91)*
*     at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeServiceLate.start(RegisterWithDomainRuntimeServiceLate.java:17)*
*     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)*
*     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)*
*     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
*     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)*
*>*
Cheers,
Varun

hi,
I was able to resolve this issue. I haven't given Listen IP address for Admin Server as I have selected All Local Addresses during domain creation. As per some blog this allows Managed Server on remote machine to use any of the Address to speak to Admin Server. In this case it is using 192.168.122.1 rather than so called IP Address.
Simple fix will be giving DNS Name of Machine or IP Address.
Cheers,
Varun

How do i setup WTC in cluster environment using WLS6.1 sp3?

Hello:
the situation is:
(1)Two solaris machines.
(2)one WLS domain.
(3)one admin server and four managed servers in this domain.
(4)we cluster these 4 managed servers.
(5)each machine contains 2 managed server.
Here is the problem,
when we start managed servers in the same machine, the wtc is ok, but when we start managed servers in diffent machine, the wtc fail.
here is the error message:
[Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound from 10.64.32.188 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.]
[Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound from 10.64.32.187 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.]
So, how can i setup wtc in cluster environment using WLS 61. sp3?
Regards,
cjyang

cjyang <[email protected]> writes:
[Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound from 10.64.32.188 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.] I believe that this is a known problem and that WTC clustering is not
supported in WLS 6.1.
andy

Does OWF Support a Cluster environment?????

I have a Cluster environment. I have an IP for Node 1 (xxx.xxx.xxx.001), another IP for Node2 (xxx.xxx.xxx.002), another IP for the Cluster (xxx.xxx.xxx.003) and another IP for the Database (xxx.xxx.xxx.004)
I have installed OWF in both nodes and I created the OWF repository in Oracle (user OWF_MGR). Its right?
Does OWF Support a Cluster environment?????
What do I have to configure if I want High availability for Oracle Workflow????
Thanks in advance!

Hi,
Every servernode runs in its own java process.
Every java process has its own heap where it works in, with normal use its not possible to share memory between servernodes so also not caches that are stored in memory.
The only components that are shared in a Java "cluster" are the SCS instance that contains the Message and Enqueue Server, the DB, and the shared file system /sapmnt.
Try investigating JNI... search for "Java JNI Shared Memory"... this will need custom development and seems to be very low level and complex... If it was easy I guess SAP might had implemented in there WAS Java I gues.
Also take a look at:
http://www.google.nl/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Figuanaworks.net%2F~shucker%2Fppt%2FJaDiSM.ppt&ei=3OqmSY6pF8Ov-QakpJnGAg&usg=AFQjCNFZCeSE-PIRpVIN39TDtGaeXMAKHA&sig2=mSGrGSf-5hT7roefFDj0lw
and
http://www.google.nl/url?sa=t&source=web&ct=res&cd=2&url=http%3A%2F%2Figuanaworks.net%2F~shucker%2Fpapers%2FJaDiSMPaper.doc&ei=3OqmSY6pF8Ov-QakpJnGAg&usg=AFQjCNF0cozxeRsKdOoHlynHWCdCv1zDmA&sig2=upwiB0HKiyxYJHaCZWiIeg
Good luck!
Benjamin Houttuin

Need help with "class file contains wrong class"

I have a dbUtil package as
package dbUtil;
public class dbConfig {
public String getHost(String db) {
This file called dbConfig.java has been compiled with -d option and rthe class files resides in dir <install_dir>/webapps/test/WEB-INF/classes/eb/dbUtil/
I have a jsp file in <install_dir>/webapps/test/test.jsp which imports the dbUtil package
<%@ page import="eb.dbUtil.dbConfig" %>
and I am getting this error:
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Compiling 1 source file
/opt/hpws/tomcat/work/Standalone/localhost/test/test_jsp.java:12: cannot access eb.dbUtil.dbConfig
bad class file: /opt/hpws/tomcat/webapps/test/WEB-INF/classes/eb/dbUtil/dbConfig.class
class file contains wrong class: dbUtil.dbConfig
Please remove or make sure it appears in the correct subdirectory of the classpath.
import eb.dbUtil.dbConfig;
^
1 error
Can anyone tell me what am I doing wrong? I am using tomcat 4.1
Thanks!
L.

Given your java file, the fully qualified name of the class is dbUtil.dbConfig.
What you are importing is eb.dbUtil.dbConfig
These things are not the same.
The root of the classpath for the webapp is the classes directory.
So either
1 - specify dbConfig.java to be in package eb.dbUtil
2 - move the class file into web-inf/classes/dbUtil/dbConfig.class, and import dbUtil.dbConfig.
Also, by convention, classnames should start with a capital letter ie dbUtil.DbConfig.
Cheers,
evnafets

A transaction problem in cluster environment,help!

          I need to take a complicated data operation which will have to call sevearl SQL
          sentences to add datas into DB in a circle. In order to minimize the cost of DB
          connection, I use one connection to create 5 statements,which are used to add
          datas repeatedly. You can read the corresponding codes below. These codes run
          very well in stand-alone environment,but problem occurs when changed to cluster
          environment. The console shows that it's timeout because the transaction takes
          too long time. But when it runs in stand-alone environment,it completes in less
          than one second! In both situations I use the same TX data source. I guess when
          changed to cluster environment,the transaction processing becomes very complicated
          and then it leads to dead-lock. Anybody agrees with this, or has any experience
          about it before? Help,thanks a lot!
          conn = getConnection();
          pstmt3 = conn.prepareStatement
          (DBInfo.SQL_RECEIPTPACK_CREATE);
          pstmt4 = conn.prepareStatement
          (DBInfo.SQL_RECEIPT_CREATE);
          pstmt5 = conn.prepareStatement
          (DBInfo.SQL_RECEIPTPACKAUDIT_INSERT_ALL);
          pstmt6 = conn.prepareStatement
          (DBInfo.SQL_RECEIPTAUDIT_INSERT_ALL);
          int count = (endno+1-startno)/quantity;
          for(int i=0;i<count;i++)
          int newstartno = startno +
          i*quantity;
          int newendno = newstartno +
          quantity - 1;
          String newStartNO =
          Formatter.formatNum2Str(newstartno,ConstVar.RECEIPT_NO_LENGTH);
          String newEndNO =
          Formatter.formatNum2Str(newendno,ConstVar.RECEIPT_NO_LENGTH);
          pstmt1 = conn.prepareStatement
          (DBInfo.SQL_RECEIPTPACK_SEQ_NEXT);
          rs1 = pstmt1.executeQuery();
          if(!rs1.next()) return -1;
          int packid = rs1.getInt(1);
          cleanup(pstmt1,null,rs1);
          pstmt3.setInt(1,packid);
          pstmt3.setString(2,newStartNO);
          pstmt3.setString(3,newEndNO);
          pstmt3.setInt(4,quantity);
          pstmt3.setLong(5,expiredt);
          pstmt3.setInt
          (6,ConstVar.ID_UNIT_TREASURY);
          pstmt3.setInt
          (7,Status.STATUS_RECEIPTPACK_REGISTERED);
          pstmt3.setLong(8,proctm);
          pstmt3.setInt(9,procUserid);
          pstmt3.setInt
          (10,ConstVar.ID_UNIT_TREASURY);
          pstmt3.setInt(11,typeid);
          pstmt3.addBatch();
          //audit
          pstmt5.setInt(1,procUserid);
          pstmt5.setInt(2,packid);
          pstmt5.setInt
          (3,OPCode.OP_RCT_RGT_RECEIPTPACK);
          pstmt5.setLong(4,0);
          pstmt5.setLong(5,proctm);
          pstmt5.addBatch();
          for(int
          j=newstartno;j<=newendno;j++)
          String receiptNO =
          Formatter.formatNum2Str(j,ConstVar.RECEIPT_NO_LENGTH);
          pstmt2 =
          conn.prepareStatement(DBInfo.SQL_RECEIPT_SEQ_NEXT);
          rs2 =
          pstmt2.executeQuery();
          if(!rs2.next()) return -
          1;
          int receiptid =
          rs2.getInt(1);
          cleanup
          (pstmt2,null,rs2);
          pstmt4.setInt
          (1,receiptid);
          pstmt4.setString
          (2,receiptNO);
          pstmt4.setInt
          (3,Status.STATUS_RECEIPT_REGISTERED);
          pstmt4.setDouble
          (4,00.0);
          pstmt4.setInt(5,0);
          pstmt4.setDouble
          (6,00.0);
          pstmt4.setDouble
          (7,00.0);
          pstmt4.setDouble
          (8,00.0);
          pstmt4.setInt
          (9,procUserid);
          pstmt4.setLong
          (10,proctm);
          pstmt4.setLong
          (11,expiredt);
          pstmt4.setInt(12,0);
          pstmt4.setInt
          (13,packid);
          pstmt4.setInt
          (14,typeid);
          pstmt4.addBatch();
          //audit
          pstmt6.setInt
          (1,procUserid);
          pstmt6.setInt
          (2,receiptid);
          pstmt6.setInt
          (3,OPCode.OP_RCT_RGT_RECEIPTPACK);
          pstmt6.setLong(4,0);
          pstmt6.setLong
          (5,proctm);
          pstmt6.addBatch();
          pstmt3.executeBatch();
          cleanup(pstmt3,null);
          pstmt5.executeBatch();
          cleanup(pstmt5,null);
          pstmt4.executeBatch();
          cleanup(pstmt4,null);
          pstmt6.executeBatch();
          cleanup(pstmt6,null);


Hello,
Are you using any kind of Load Balancer, like an F5. I am currently troubleshooting this issue for one of our ADF apps and I originally suspected the F5 was not sending traffic correctly. We have not set the adf-config file for HA and the dev team will fix that. But my concern is that will just hide my F5 issue.
Thanks,
-Alan

Using Optimistic Concurrency in a cluster environment

Hi,
In weblogic 8.1 sp3 cluster environment, I deployed CMP Entity Beans with the following settings:
In weblogic-ejb-jar.xml:
<entity-cache>
<concurrency-strategy>OptimistÂic</concurrency-strategy>
<cache-between-transactions>trÂue</cache-between-transactionsÂ>
</entity-cache>
In weblogic-cmp-rdbms-jar.xml:
<verify-columns>Version</verifÂy-columns>
<optimistic-column>VERSION</opÂtimistic-column>
And I deployed the CMP Entity beans into a cluster which has two managed servers.
When I only do findByPrimaryKey, on both managed servers, the cache-between-transaction functions well and only call ejbLoad() when it first loads that Entity Bean Instance.
However, If I do any updates to this bean, the performance change. After the updates, I issued a lot findByPrimaryKey calls for this bean to test. If the call reach the managed server where the update for the
bean happens, it is fine and still perform like cache-between-transaction. But if the call reach other managed servers, the ejbLoad() get called for that bean in every transactions; and cache-between-transaction seems to be disabled on the other managed servers since the updates.
I test this senario a lot of times and the problem is very consistant. According to my understanding, the other managed servers should only do ejbLoad() at the first time after the updates happened, and the transactions after that shouldn't call ejbLoad everytime.
Does anyone encounter the same problem like this? And is there anyway to optimize it?
Thanks!!

Did you figure out how to do this? We ended up having to track the number of sessions using the service and close it only when there were none. However, this did not solve the problem completely. There seems to be a conflict when running our servlet app (which uses PAPI) on different machines talking to the same BPM. A thread on one machine opens, uses, closes a session and service while a thread on another machine opens a session and in the middle of using it, it dies.

Session Problem With Cluster Environment

Issue:
To test our web application, we build a simply cluster environment containing 2 nodes, web server and admin. server. if we start all related servers and nodes in the following manner, the web server can not maintain the correct session ID, and mirror them across the nodes due to which the first session/request goes to the first node (node1) and the second request goes to the second (Node2). But Node2 does not have a successful session ID. Thus, our deployed application get a Session Time Out message.
1.     Start WebLogic Application server
2.     Started the nodes.
3.     First start the Webserver
However, when we change the start sequence as follows, the issue will disappear.
1.     First start the WebServer
2.     Start WebLogic Application server
3.     Lastly started the nodes.
Question:
Why does the different start sequences effect the different result of Session Affinity in the cluster environment?
Thanks for any responses!

Hmmm... Never thought about it.
Somehow I always start the environment in this sequence:
- Admin Server
- WebServer
- Cluster
I assume you are using the Apache HTTP server with the WebLogic proxy plug-in as your WebServer.
Here you can configure
- WebLogicCluster - which is a static starting point for the server list, and
- DynamicServerList - enables that WebLogic automatically adds new servers to the server list when they become part of the cluster.
What I can think of is that the last option is set to OFF in which case when new servers are added to the cluster, the plug-in cannot proxy requests to the new server.
This could explain why the start-up sequence matters, i.e., when you first start the WebServer than the cluster nodes, the static list will do its work.
When on the other hand, the cluster nodes are started before the WebServer the starting point for the server list is not created, because somehow
to WebServer is not receiving notifications.
One remark is in order, is that when you did not alter the DynamicServerList property, the default is ON.
Hope the above makes some sense to you. (http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/index.html)

Is there a way to add to the existing values in a container when a LabVIEW prototype (cluster) changes?

Is there a way to add to the existing values in a container when a LabVIEW prototype (cluster) changes?
I have a cluster with 90 values.. ninety! yes that many.
Change one bloody value and the prototype changes in the TestStand step... Reload the prototype and guess what happens??!!??
All the bloody values get reset to defaults! AAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGGGHHHHHHHHHHHH!
If it was in one place, I could survive the ordeal. But I have to change bloody prototypes in many places!!!!
more AAAAAAAAAAARRRRRRRRRRRGGGGGGGGGGGHHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!!!!
I can't even copy the bloody values!!!!!!! AAAAAAAAAAAARRRRRRRRRRRRRRGGGGGGGGGGGHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!
Are there any tricks that I am not aware of, or have forgotten over the years, or... ... something??!!??!???!!
If there are none, I will have to post an improvement to TestStand.. I should mention I am using an older version (4.1).

Hmmmmmmmmmmmmmmmm,
I am not not very famous with LV and its cluster types.
So no idea if this works (it works for DataTypes updates very well and a LV cluster is Data Type so.... maybe)
Make a copy of the step that has to be modified to an new sequencefile.
Make modifications the in the copy.
Now you should have the same DataType Name but other contents in the container. Save it.
Normally there should be a message box that tells you that version has been incremented. - Accept it.
Set in StationOptions-File "Allow Automatic ...." to Never.
Open original sequencefile. Now the there must be a type conflict. Accept/Apply to all "Use Current Loaded.."
You have updated the type.....
Hope this worked,
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

SBO Mailer in a cluster environment

Hi,
I am currently facing an issue where when I install SBO Mailer on a cluster environment, the installation removes applications and license manager for some reason gets uninstalled.. When I want to uninstall the SBO Mailer, I do not see it under the Control Panel and neither do I see it in running in services. But if i look at the Service Manager the SBO Mailer Service is running.
The strange part is that after this installation, there is an add-on that stopped working.
Has anyone come across such a scenario?

Hi,
To uninstall you have to first run the Server tools and there you can uncheck the sbo mailer. There is not way you can uninstall SBO mailer service and you cannot find it under control panel its a service...not an applicaiton.
Run the server tools and then choose repair.
Regards,
Rakesh N

Deploying Java Web Application (WAR-File) into a cluster environment

Hi,
we have a web application which has to read from and write to the file system.
Since a short time we have a cluster environment (2 parallel servers) and since thisa time we have the problem, that files are worked double in the cluster. The application is working on both servers now and so we have this problem.
Does anybody know how we have to deploy the application correctly in a cluster environment or do we have to change anything in our source code of the application?
I didn't find any documentation about this.
At the moment we have deployed the application on one of the two servers only, but I think there must be a better way to solve this problem.
Thanks for your replies.
Regards
Thorsten

Hi,
I think first you need to wrap it into an EAR file, then you can deploy it.
As far as I know standalone deployment of WAR is deprecated as of 640.
similar threads:
How to deploy .war on NWDI
Deploying an existing WAR file into the Portal
Hopefully this tutorial also gives some idea:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/70/13353094af154a91cbe982d7dd0118/frameset.htm
Regards,
Ervin

SessionContext contains wrong caller identity on cluster environment

Similar Messages

Maybe you are looking for