OSB 11gR1 Cluster Environment Issues

Hi,
I installed Oracle Service Bus 11gR1 on a clustered environment with two nodes and extended the domain for OSB. (First Node: osb_server1, Second Node: osb_server2)
I am facing the problems below on this environment:
1. When I login on SB Console on second node, on "Operations" menu a warning message (Unable to obtain metrics data from the server. ) is displayed and the message below is logged on osb_server2:
<Aug 14, 2012 3:21:00 PM GMT+03:00> <Error> <ALSB Statistics Manager>
<BEA-473003> <Aggregation Server Not Available. Failed to get remote aggregator
java.lang.IllegalArgumentException: Server 'null' not found
at com.bea.alsb.platform.weblogic.WlsDomainConfigurationImpl.getServer(WlsDomainConfigurationImpl.java:98)
at com.bea.alsb.platform.weblogic.WlsDomainConfigurationImpl.getAggregationServer(WlsDomainConfigurationImpl.java:119)
at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.getRemoteAggregator(ALSBStatisticsManager.java:291)
at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.access$000(ALSBStatisticsManager.java:38)
at com.bea.wli.monitoring.statistics.ALSBStatisticsManager$RemoteAggregatorProxy.send(ALSBStatisticsManager.java:55)
Truncated. see log file for complete stacktrace
>
2. In SB Console on both nodes when "Security" menu is selected, an error message (Message The server encountered an unexpected condition which prevented it from fulfilling the request. ) is displayed and the message (
<Aug 14, 2012 3:16:03 PM EEST> <Error> <User-Management-WLI-OAM> <BEA-000000>
<[BEA-WLI-Security-UserManagement:482200]The operation searchUsers is not supported by the provider null for user/group .>
<Aug 14, 2012 3:16:03 PM EEST> <Error> <User-Management-WLI-OAM> <BEA-000000>
<[BEA-WLI-Security-UserManagement:482200]The operation searchUsers is not supported by the provider null for user/group .>
<Aug 14, 2012 3:16:03 PM EEST> <Error> <ALSB Console> <BEA-494002> <Internal error occured in OSBConsole : null
com.bea.p13n.security.management.OperationNotSupportedException
at com.bea.p13n.security.management.authentication.AtnManagerProxy.getUserNames(AtnManagerProxy.java:579)
at com.bea.alsb.console.oam.usermanagement.UserManagementHelper.getUserNames(UserManagementHelper.java:857)
at com.bea.alsb.console.oam.usermanagement.UserManagementHelper.searchUsers(UserManagementHelper.java:138)
at com.bea.alsb.console.usermanagement.user.UserManagement.viewUsersByName(UserManagement.java:244)
at com.bea.alsb.console.usermanagement.user.UserManagement.viewUsers(UserManagement.java:71)
Truncated. see log file for complete stacktrace
>
How can I solve these two issues?

For the first error - Refer to this http://tim.blackamber.org.uk/?p=975
For the second error - Looks like there is an issue loading the default ldap configuration. Please do the following:
1. Take a backup of the following folders cache+, data+ and tmp+ in each of the servers.
2. Then delete the contents of the above folders in each server
3. And restart all the servers in the cluster. This should reinitialize all the required files at startup.
Hope this helps.
Thanks,
Patrick

Similar Messages

  • Scheduling Task issue in cluster environment

    Hi All,
    Can anybody explain,In my current OSB project for exception and retry mechanism we are using java scheduling,it is working fine in single managed server but in cluster environment we got issue i.e we have two managed servers and one Database, java scheduler which polling the records from Queue and inserting into Database.In cluster environment some times same record will insert into the database.how to fix it i.e means if only one record id insert into database table.
    Thanks and Regards
    Mani

    Mani,
    I suppose you are doing this in OSB.
    Can you be more clear how you are polling the records from the queue? What mechanism you are using? I see you are using DB Adapter for writing to the database.

  • 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.

  • OSB Polling in Cluster Environiment

    Hi ,
    I created a OSB Poller which will read data from DB. When I test it in a single server it is working fine but when I move it to cluster environment with two managed servers it is polling Twice from the DB and the reports are generating twice . I have changed the JCA Property <Lock>lock-no-wait</Lock> even then it is polling twice. Any solution Please ?

    Hi:
    Maybe this link can be useful
    http://javaoraclesoa.blogspot.com.au/2012/04/polling-with-dbadapter-in-clustered.html
    Regards,
    RK
    Edited by: RK.. on Dec 16, 2012 7:54 PM
    Edited by: RK.. on Dec 16, 2012 7:55 PM

  • 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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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.

  • File polling in cluster environment

    We have a cluster environment with two servers(say, osb_server1 and osb_server2) and a proxy service is configured with file polling using HAfileAdapter.
    When executing this service immediately after activation, for first time, the server “osb_server2” throws error as,
    Caused By: BINDING.JCA-11042
    File deletion failed.
    File deletion failed.
    File : /**Path**/filename.txt as it does not exist. could not be deleted.
    But for consecutive attempts, the osb proxy service is processed by “osb1_server1” and we are not getting the above mentioned error.
    In short, We face the issue as below only when executing first time after “Activate” session but the consecutive attempts doesn’t throw error.
    Why such error occurs when executing in cluster environment?
    Thanks in advance.

    try to use the file protocol provided by osb.And select the polling server as on eof the managed server.

  • 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

  • Wsdl parsing error soa11g cluster environment

    hi,
    i clicked test in console below error is coming in 11g soa cluster environment Please help me.
    http://soadev-internal.xxx.com/soa-infra/services/default/HighwayTableUpdateProcess/highwaytableupdatebpel_client_ep?WSDL
    Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "http://soadev-internal.wlgore.com/soa-infra/services/default/HighwayTableUpdateProcess/highwaytableupdatebpel_client_ep?WSDL", caused by: java.net.SocketException. : java.net.SocketException: Connection reset
    but in browser it is parsing well.
    Regards
    janardhan

    Hi,
    If it is a problem in jdev..Make sure u set the proxy information in Tools--->Preferences-->WebBrowser and Proxy or you can remove the Use HTTP Proxy server check mark and try.
    If u also face the similar issue in the console make sure u make an entry of soadev-internal.xxx.com to the correct IP in hosts file
    Regards
    Edited by: Oraacler on Aug 16, 2010 7:45 AM

  • 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

  • Failed to replicate non-serializable object  Weblogic 10 3 Cluster environ

    Hi,
    We have problem in cluster environment, its showing all the objects in Session needs to be serialized, is there any tool to find what objects in session needs to be serialized or any way to find. There was no issue in WLS 8 when the application again setup in WLS 10, we are facing the session replication problem.
    The setup is there are two managed server instance in cluster, they are set to mulicast(and also tried with unicast).
    stacktrace:
    ####<Jun 30, 2010 7:11:16 PM EDT> <Error> <Cluster> <userbser01> <rs002> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1277939476284> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.>
    ####<Jun 30, 2010 7:11:19 PM EDT> <Error> <Cluster> <userbser01> <rs002> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1277939479750> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.>
    Thanks,

    Hi
    Irrespective of WLS 8.x or WLS 9.x, 10.x, in general any objects that needs to be synced/replicated across the servers in cluster should be Serializable (or implement serializable). The object should be able to marshall and unmarshall. Simple reason why it did not showed in WLS 8.x is may be in that version they could not show these details like Error. May be they showed as Info or Warn or Just Ignored it. Weblogic Server became more and more stable and more efficient down the lines like from its oldest version 4.x, 5.x, 6.x, 7.x to latest 10.x. So my guess is they added more logic and more functionality to capture all possible errors and scenarios. I did worked on WLS 8.1 SP4 to SP6 long time back. Could not remember if I saw or did not see these errors for cluster domain with non-serializabe objects. I vaguley remember seeing it for Portal Domains but not sure. I do not have 8.x installed, otherwise I would have given a quick shot and confirm it.
    So even though it did not showed up in WLS 8.x, still underneath rule is any object that needs to be replicated that is getting replicated in cluster needs to implement Serializable interface.
    Thanks
    Ravi Jegga

  • Routing and Remote access can cause cluster network issues?

    After enabling routing and remote access on the servers, we found lots of cluster issues on our server like<o:p></o:p>
    Cluster Service stopped
    Communication was lost and reestablished between cluster nodes
    Unable to access witness resource
    Cluster resource failed
    can RRAS enabling causes cluster network issues?
    Rahul

    Hi TwoR,
    Please offer more information about your current cluster and RRAS configuration, such as are you installed the RRAS role on any cluster node? Are your cluster in Hyper-V environment?
    Or if you want to create the RRAS cluster you can refer the following KB:
    Deploy Remote Access in a Cluster
    http://technet.microsoft.com/en-us/library/jj134175.aspx
    How to configure Network Load Balancing (NLB) based cluster of VPN Servers
    http://blogs.technet.com/b/rrasblog/archive/2009/07/02/configuring-network-load-balancing-nlb-cluster-of-vpn-servers.aspx
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Moving ECMI repository to a new location - cluster environment doesn't work

    Hello all,
    Actually, we have the "default" configuration in the ECMI properties, and we want to move to a new location the File system repository (another disk location).
    After reviewing the ECM doc's we found the way and the parameters to reconfigure (ContentStorePath) and we put an absolute path ( "H:\content ') instead "Default" value , but we have an issue on this.
    Because our system runs in cluster mode (2 node instances), this configuration only works fine with one node, and the other doesn't work, displaying the "Content Folder Doesn't Exists" error.
    Both nodes runs' on separated machines and we want to know what is the correct way to configure this feature in a cluster environment.
    Best Regards
    Julio C Leyva

    I should note that now my local users inside the office are getting outlook errors, showing 3 checkmarks 2 green one red,  regarding the cert, and the red  checked box says:  The name on the certificat is invalid or does not match the name
    of the site.
    They can  bypass the error by clicking Continue, but installing it does only work for a short time before the error comes back. I think that would result from the setup in outlook pointing towards either SRV01 or SRV01.mydomain.local  instead of
    mail.mydomain.com
    The cert error on the android devices was saying Invalid certificate, do you want to continue, or similar, except clicking continue just paused a short while and brought up the same window.
    Now I am getting an error, on the android, saying Invalid username or password - when I KNOW it is valid
    In regards to DNS being set up correctly - I never had a mail. A record setup prior to purchasing the commercial cert - we just used the router IP in the phones and were able to get activesync working. For some reason with the new IP / ISP we could not access
    by IP.  So I got the SSL, and added a mail A record to DNS, pointing to our router IP, and our router has always routed activesync/443 traffic correctly, and none of that was changed

  • Invoking OSB Proxy (cluster) from OBPMS

    Hello !
    I have 1 problem:
    I am trying to configure OBPMS to work with OSB in a cluster environment...
    OSB cluster consist 4 nodes
    Cluster address = node1:17001,node2:27001,node3:37001,node4:47001
    and SSL Listen Port Enabled = true...
    I don't understand = How I should specify host and port in the external resourse config? (host, port)
    please help me ?
    regards, Alex.

    Hi Alex,
    Regardless the number of nodes in your cluster, you should have a load balancer (usually the admin server of the cluster), that handles all the communications.
    So you should use the url of the balancer in the external resources configuration.
    You'll probably have one or more "Management Host" configuration resources. Simply use the IP address and the port of the balancer. It will do the rest.
    So for the published project in production, you'll have to configure it in the same way.
    NOTE: +(theese infos are dated to the ALBPM/ALSB products but it should be the same for OBPM/OSB)+
    If you do not have any balancer, as far as I know, there is no way to specify multiple addresses for the external resources. You cannot even use the T3 protocol. It happens tipically in development environments, just choose one of the nodes and use it but keep in mind that once in production You'll have to set the configuration to the load balancer.
    Also remember that using a specific node means that in the entire flow you must use the same node or you will apparently loose messages/processes.
    Hope that helps.
    Giuliano

  • Create secondary node on BOBJ cluster environment

    Hi All,
    I have done migration from old BOBJ server to new BOBJ server. The primary nodes has successfully completed and manage to view reports. I currently having issue to proceed installing second node on BOBJ cluster environment. i stuck at phase repository database as no database entry was found.
    Please help. I also attach my steps to install the second node.
    Thanks.
    Regards
    Aiman

    Hi,
    im guessing you do an Expand installation on the second node and want to enter the credentials of your existing CMS DB, the one you configured during the installation of Node 1. Correct?
    What is your CMS DB of a Kind? MS SQL? Oracle?
    It looks like that the ODBC DSN entries are missing on Node 2.
    Regards
    -Seb.

  • 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

Maybe you are looking for