Failure Of Web Server Bridge Weblogic | Weblogic Deployments 인기 답변 업데이트

당신은 주제를 찾고 있습니까 “failure of web server bridge weblogic – WebLogic Deployments“? 다음 카테고리의 웹사이트 https://chewathai27.com/you 에서 귀하의 모든 질문에 답변해 드립니다: https://chewathai27.com/you/blog. 바로 아래에서 답을 찾을 수 있습니다. 작성자 VSMinds IT Services 이(가) 작성한 기사에는 조회수 1,534회 및 좋아요 25개 개의 좋아요가 있습니다.

Table of Contents

failure of web server bridge weblogic 주제에 대한 동영상 보기

여기에서 이 주제에 대한 비디오를 시청하십시오. 주의 깊게 살펴보고 읽고 있는 내용에 대한 피드백을 제공하세요!

여기에서 동영상 보기

d여기에서 WebLogic Deployments – failure of web server bridge weblogic 주제에 대한 세부정보를 참조하세요

Deployment in WebLogic 12c

failure of web server bridge weblogic 주제에 대한 자세한 내용은 여기를 참조하세요.

Failure of Web Server bridge: No backend server available for …

Failure of Web Server brge: No backend server available for connection: timed out after 10 seconds or empotent set to OFF or method not …

+ 여기에 자세히 보기

Source: doyensys.com

Date Published: 9/20/2022

WebLogic Bridge Message: “Failure of Web Server bridge: No …

The reason behind this issue is, your application might be trying to connect to other servers outse of WebLogic server. In my case, WebLogic …

+ 더 읽기

Source: stackoverflow.com

Date Published: 11/16/2022

Troubleshooting the Error “Failure of server APACHE bridge”

This generic error is seen in the end user browser. It occurs when there is some sort of ‘disconnect’ between the Oracle HTTP Server (OHS) mod_wl_ohs module and …

+ 여기에 보기

Source: renaps.com

Date Published: 6/5/2022

Failure of web server bridge – IFS Community

Failure of Web Server BrgeNo backend server available for connection: timed out after 10 seconds or empotent set to OFF or method not …

+ 더 읽기

Source: community.ifs.com

Date Published: 12/27/2022

Hyperion — Failure of Webserver Bridge — After SSL/TLS …

After Upgrading Oracle HTTP Server to 11.1.1.9 SSL Connection to Weblogic Fails with Error “Failure of Web Server brge” and “wl_ssl_open …

+ 자세한 내용은 여기를 클릭하십시오

Source: ermanarslan.blogspot.com

Date Published: 1/17/2022

Apache – Failure of Web Server bridge – iTecNote

I am getting Failure of Web Server brge, while uploading file from my application through Apache server with weblogic server.

+ 더 읽기

Source: itecnote.com

Date Published: 1/2/2022

How to fix failure of web server bridge jobs – Freelancer

Search for jobs related to How to fix failure of web server brge or hire on the world’s largest freelancing marketplace with 21m+ jobs.

+ 더 읽기

Source: www.freelancer.com

Date Published: 12/19/2021

Failure of Web Server bridge – CopyProgramming

I am getting ssl handshake failure when i try to invoke https service call within weblogic.

+ 여기에 표시

Source: copyprogramming.com

Date Published: 6/14/2021

주제와 관련된 이미지 failure of web server bridge weblogic

주제와 관련된 더 많은 사진을 참조하십시오 WebLogic Deployments. 댓글에서 더 많은 관련 이미지를 보거나 필요한 경우 더 많은 관련 기사를 볼 수 있습니다.

주제에 대한 기사 평가 failure of web server bridge weblogic

Author: VSMinds IT Services
Views: 조회수 1,534회
Likes: 좋아요 25개
Date Published: 2021. 4. 3.
Video Url link: https://www.youtube.com/watch?v=jE4VFuk0G6o

What does failure of Web Server bridge mean?

No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent. To recover from this error, a user needs to delete the Portal session cookie manually or restart their browser.

What is WebLogic Bridge message?

What Is a Messaging Bridge? The WebLogic Messaging Bridge allows you to configure a forwarding mechanism between any two messaging products—thereby, providing interoperability between separate implementations of WebLogic JMS, or between WebLogic JMS and another messaging product.

How does OHS integrate with WebLogic?

Creating Oracle HTTP Server instance

Open the WebLogic Server Domain menu and select Administration then Create/Delete OHS. …
Click Lock & Edit in the Change Center. …
Click Create on the the OHS Instances page. …
On the Create OHS Instance page, enter/select the following values and click OK:

What is JMS bridge?

A JMS bridge can be used to bridge any two JMS 1.1 compliant JMS providers and uses the JMS API. A core bridge) is used to bridge any two Apache ActiveMQ Artemis instances and uses the core API. Always use a core bridge if you can in preference to a JMS bridge.

Is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable?

This only occurs when the configured quality of service is unreachable and the bridge is configured to allow the degradation of quality of service.
…
MessagingBridge Subsystem Messages.

Description	This message indicates that the quality of service of this bridge is allowed to be downgraded if the required one is unreachable.
Action	No action required.

How do I check my WebLogic OHS status?

Manually check status of Oracle HTTP Server (OHS)

Use DCMCTL to find out if OHS is up or not. …
Use OPMNCTL to find out if OHS is up or not. …
Use DMSTOOL to determine whether OHS is alive or not. …
Check for the PID and count the number of processes. …
Check if the port is listening.

How do I stop OHS in WebLogic 12c?

As you can see in this picture, the only way to stop the Oracle HTTP Server in a Standalone Domain installation is by sending the stop message to the Node Manager (1). The Node Manager will stop the Oracle HTTP Server (OHS) (2).

How do I check OHS version?

To determine the version of Oracle HTTP Server you have, try the following: Navigate to your {OHS_INSTANCE}/bin directory. In this directory, there should be an httpd file.

What is Mod_wl_ohs conf?

mod_wl_ohs provides features that are identical to those of the plug-in for Apache HTTP Server. You can configure mod_wl_ohs either by using Fusion Middleware Control or by editing the mod_wl_ohs. conf configuration file manually.

How do I install Ohs?

Install Oracle HTTP Server 12c

Launch a terminal window as oracle and enter the following commands to install OHS: Copy cd /stage/OHS12c ./fmw_12.2.1.4.0_ohs_linux64.bin.
Follow the table below to guide you through the installation screens: Step. Window Description. Choice or Values. Welcome. Click Next. Auto Updates.

What is WebLogic Server 12c?

WebLogic Server 12c R2 is a fully compatible Java EE 7 implementation, which provides availability of all the API’s and features of Java EE 7 to simplify application development using lightweight web-based protocols, such as REST, WebSocket, and Server-Sent Events.

Failure of Web Server bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

ERROR

———————–

Failure of Web Server bridge:

No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

Cause

—————————–

We have installed ECC on same application server . so we could not open the EBS page when ecc is running.

EBS LOG : $IAS_ORACLE_HOME

VirtualHost: main] ap_proxy: trying GET /OA_HTML/AppsLogin at backend host ‘XXX.XXX.XX.XX/7201; got exception ‘NO_RESOURCES: [os error=115, line 1611 of URL.cpp]: apr_socket_connect call failed with error=70007, host=XXX.XXX.XX.XX, port=7201

Solution

————————–

Please follow the process:

Note: Do not start and stop ECC from console.

1.shut down EBS application

2.shut all ECC admin and managed server from backend

sh /home/Oracle/qiuckinstall/bin/stopAllEcc.sh

3.make sure all serevives are properly down

4.Now start your EBS(don’t start ECC)

5.start all ECC admin and managed server from backend

sh /home/Oracle/qiuckinstall/bin/startAllEcc.sh

Now your EBS and ECC will be running smoothly.

Failure Of Server APACHE Bridge Error When Opening Oracle Portal Pages After A Long Period Of Inactivity

Failure Of Server APACHE Bridge Error When Opening Oracle Portal Pages After A Long Period Of Inactivity (Doc ID 1559052.1)

Last updated on MARCH 09, 2022

Applies to:

Symptoms

The portal session cleanup job removes session records from the wwctx_sso_session$ table when they are older than 168 hours.

This is normally no issue at all as most Portal users close there browsers at the end of the day. When Oracle Portal is accessed from a new browser session, a new session record is created.

Problems occur when navigating to the Portal pages in the same browser instance after 168 hours. Portal will read the browsers session cookie and attempt to match it with a row in the session table. As the row has been deleted, an error will be generated:

Failure of server APACHE bridge:

No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

To recover from this error, a user needs to delete the Portal session cookie manually or restart their browser.

Whilst this issue is normally not a problem for desktop users (who tend to close their browsers when they finish working with their computers), tablets and smart phones are more of a challenge. Browser instances on these devices tend to be kept up an running until a device reboot. Device reboots may not occur within the period of 168 hours and as such, users of mobile devices are more likely to encounter this error condition than users who user a browser on a standard computer.

Note:

By default, the session cleanup job will remove sessions older than 168 hours. Portal administrators can change the value with the script ctxjsub using the parameter hours_old. More information is available in the section By default, the session cleanup job will remove sessions older than 168 hours. Portal administrators can change the value with the script ctxjsub using the parameter hours_old. More information is available in the section Managing the Session Cleanup Job in the Portal Administrators Guide.

Cause

Sign In To view full details, sign in with your My Oracle Support account. Register Don’t have a My Oracle Support account? Click to get started!

Messaging Bridge

eDocs Home > BEA WebLogic Server 8.1 Documentation > Administration Console Online Help > Messaging Bridge

Administration Console Online Help

Messaging Bridge
[Attributes and Console Screen Reference for Messaging Bridge]
The following sections explain how to configure and manage a WebLogic Messaging Bridge:

You may also want to refer these WebLogic JMS sections:

What Is a Messaging Bridge?

The WebLogic Messaging Bridge allows you to configure a forwarding mechanism between any two messaging products—thereby, providing interoperability between separate implementations of WebLogic JMS, or between WebLogic JMS and another messaging product. You can use the Messaging Bridge to integrate your messaging applications between:

Any two implementations of WebLogic JMS, including those from separate releases of WebLogic Server.

WebLogic JMS implementations that reside in separate WebLogic domains.

WebLogic JMS with a third-party JMS product (for example, MQSeries).

WebLogic JMS with non-JMS messaging products (only by using specialized connector adapters that are not provided with WebLogic Server).

A messaging bridge consists of two destinations that are being bridged: a source destination that the bridge reads messages from and a target destination where the bridge sends the messages that it receives from the source destination. For WebLogic JMS and third-party JMS products, a messaging bridge communicates with source and target destinations using the resource adapters provided with WebLogic Server. For non-JMS messaging products, a custom connector adapter must be obtained from a third-party OEM vendor or by contacting BEA Professional Services in order to access non-JMS source or target destinations.

Source and target bridge destinations can be either queues or topics. You can also specify a quality of service (QOS), as well as message filters, transaction semantics, and connection retry policies. Once a messaging bridge is configured, it is easily managed from the Administration Console, including temporarily suspending bridge traffic whenever necessary, tuning the execute thread pool size to suit your implementation, and monitoring the status of all your configured bridges.

In addition to this document, BEA Systems provides messaging bridge examples that are available for download. Follow the links on the JMS Technology page at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/messaging.html. These examples are distributed as .zip files that you can unzip into an existing WebLogic Server samples directory structure.

About the Bridge’s Resource Adapters

A messaging bridge uses resource adapters to communicate with the configured source and target JMS destinations. You need to associate both the source and target JMS destinations with a supported resource adapter in order for the bridge to communicate with them. The JNDI name for the adapter is configured as part of the resource adapter’s deployment descriptor.

Note: Although WebLogic JMS includes a “General Bridge Destination” framework for accessing non-JMS messaging products, WebLogic Server does not provide supported connector adapters for such products. Therefore, you must obtain a custom connector adapter from a third-party OEM vendor and consult their documentation for configuration instructions. You can also contact BEA Professional Services for information about obtaining a custom connector adapter.

The supported resource adapters are located in the WL_HOME\server\lib directory and are described in the following table.

You will specify the appropriate resource adapter by its JNDI name when you configure each source and target bridge destination.

Configuring a Messaging Bridge

Configuring a messaging bridge consists of the following tasks:

When you initially create a message bridge, many attributes are set with the default value. You may need to change message bridge settings to better suit your environment. For example, you may wish to select QOS Degradation Allowed rather than have the messaging bridge use the initially configured QOS.

Create a Messaging Bridge

Creating a messaging bridge consists of the following tasks:

Create source and target bridge destinations. Deploy a resource adaptor. Create a messaging bridge instance. Deploy the messaging bridge.

To simplify these tasks, the Administration Console assists you in creating a messaging bridge by deploying an appropriate resource adaptor and setting the values of some attributes. You may need to review the message bridge configuration and modify some attribute settings to better suit your environment. See Modify a Messaging Bridge Configuration for Your Environment for more information on how to modify an existing messaging bridge.

Note: Click the Help button to access detailed information for each panel.

Use the following steps to configure a messaging bridge instance:

Click to expand the Services and Message Bridge nodes. Click the Bridges node. Click Configure a new Messaging Bridge link. Configure the source destination.

To create a new source destination, click the Create a New Bridge Destination button. Next, follow the instructions at Create a New Destination to create a source destination.

If you have already configured a source destination, click the Use an Existing Bridge Destination button. Next, follow the instructions at Use an Existing Bridge Destination to configure the source destination for a bridge instance.

Configure the target destination.

To create a new target destination, click the Create a New Bridge Destination button. Next, follow the instructions at Create a New Destination to create a target destination.

If you have already configured a target destination, click the Use an Existing Bridge Destination button. Next, follow the instructions at Use an Existing Bridge Destination to configure the target destination for a bridge instance.

Modify the configuration attributes for your messaging bridge instance. Click the Help button to see detailed information about the attributes on this panel.

Click Continue.

Select the servers and/or clusters on which you want to deploy your new bridge. See Targeting a Messaging Bridge to a Server, a Cluster, or a Migratable Target for general information on targeting a messaging bridge.

Click Continue.

A messaging bridge instance is created. The console checks your configuration and lists any tasks you must perform manually. You may need to perform one or more of the following tasks:

At least one of the destinations is in a remote Weblogic domain. The “Guest Disabled” check box must not be checked on that domain.

The “Enable Generated Credential” check box must not be checked. Use the same password as the credential on all Weblogic domains that participate in the bridge.

The “Enable Generated Credential” check box must not be checked. Use the “system” user’s password as the credential on all Weblogic domains that participate in the bridge.

The “system” user must be configured in all domains with the same password. The “system” must be a member of the Administrators group in the domain where the bridge resides.

The XA connection factory must be enabled for all domains.

The jms51-interop.jar file must be in the CLASSPATH of the Weblogic Server 8.1 server instance.

Click Finish.

Create a New Destination

Use the following instructions to create a new destination for your messaging bridge instance:

Click the Drop-down arrow to view a list of message providers. Select the message provider for your destination. Click Continue. Modify the configuration attributes for your destination. Click the Help button to see detailed information about the attributes on this panel. Click Create the bridge destination.

Use an Existing Bridge Destination

Use the following instructions to configure your messaging bridge instance for an existing destination:

Click the Drop-down arrow to view a list of destinations. Select the destination for your messaging bridge. Click Continue. Click the Drop-down arrow to view a list of message providers. Select the message provider for your destination. Click Continue.

Modify a Messaging Bridge Configuration for Your Environment

The following sections provide information on how to modify the configuation of individual message bridge components:

Deploying the Bridge’s Resource Adapters

Before you configure the messaging bridge destinations, deploy the appropriate resource adapters in the WebLogic Server domain that is hosting the messaging bridge, as follows:

Select the domain in which you will deploy the adapters (for example, Examples). Select the Deployments —> Connector Modules option to open the Resource Connectors page. Follow the deployment assistant instructions to deploy the appropriate resource adapter, as defined in Table 119-1.

You must target the resource adapter to the same WebLogic Server instance that the messaging bridge will be targeted to. For more information, see Targeting a Messaging Bridge to a Server, a Cluster, or a Migratable Target.

For more information on deploying resource adapters, see “Packaging and Deploying Connectors” in Programming WebLogic Server J2EE Connectors.

Configuring Source and Target Bridge Destinations

A messaging bridge connects two actual destinations that are mapped to bridge destinations: a source destination from which messages are received, and a target destination to which messages are sent. Depending on the messaging products that need to be bridged, there are two types of bridge destinations:

JMS Bridge Destination – For JMS messaging products, whether it is a WebLogic JMS implementation or a third-party JMS provider, you need to configure a JMSBridgeDestination instance for each actual source and target JMS destination being mapped to a messaging bridge.

instance for each actual source and target JMS destination being mapped to a messaging bridge. General Bridge Destination – For non-JMS messaging products, you need to configure a generic BridgeDestination instance for each actual source and target destination being mapped to a messaging bridge.

Before starting the procedures in this section, refer to the Using the Messaging Bridge to Interoperate with Different WebLogic Server Releases and Domains or Using the Messaging Bridge to Access a Third-Party Messaging Provider sections for specific configuration requirements and guidelines.

Note: When configuring third-party JMS provider bridge destination, you can use the Foreign JMS Server feature to quickly configure multiple source or target destinations. For more information, see Simple Access to Remote or Foreign JMS Providers.

Configuring JMS Bridge Destinations

A JMSBridgeDestination instance defines a unique name for a bridge’s source and target destinations within a WebLogic domain, the name of the adapter used to communicate with the specified destination, property information to pass to the adapter (Connection URL, Connection Factory JNDI Name, etc.), and, optionally, a user name and password.

You need to configure a JMSBridgeDestination instance for each actual source and target JMS destination to be mapped to a messaging bridge. Therefore, when you finish defining attributes for a source JMS bridge destination, repeat these steps to configure a target JMS bridge destination, or vice versa. You will designate the source and target JMS Bridge Destinations in Modifying an Existing Messaging Bridge Instance.

To configure a source or target JMS bridge destination, follow these steps.

Expand the Services —> Messaging Bridge node. Click the JMS Bridge Destinations node to open the JMS Bridge Destinations page in the right pane. Click the Configure a new JMS Bridge Destination link. A Configuration dialog shows the tabs associated with configuring a new JMS bridge destination. On the Configuration General tab, define the general configuration attributes for a JMS bridge destination:

Enter a JMS bridge destination name for the actual JMS destination being mapped to the bridge. This name must be unique across a WebLogic domain. For example, if you are bridging between WebLogic Server releases 6.1 and 8.1, for the source destination you could change the default bridge destination name to “61SourceDestination”. Then, when you create the corresponding target destination, you could name it as “81TargetDestination”. Once the bridge destinations are configured, these names are listed as options in the Source Destination and Target Destination attributes on the Bridges —> General tab.

General tab. Specify the JNDI name of the resource adapter used to communicate with the messaging bridge destinations:

eis.jms.WLSConnectionFactoryJNDIXA (default) — QOS is Exactly-once eis.jms.WLSConnectionFactoryJNDINoTX — QOS is Atmost-once or Duplicate-Okay For more information on which resource adapter name to use, see Messaging Bridge Resource Adapters and JNDI Names. Leave the Adapter Classpath field blank when connecting to source and target destinations that are both running on WebLogic Server 6.1 or later. When connecting to a third-party JMS provider, the bridge destination must supply the provider’s CLASSPATH in the WebLogic Server CLASSPATH .

in the WebLogic Server . Specify the URL of the JNDI provider used to look up the connection factory and destination.

Specify the context factory used to get the JNDI context.

Specify the JMS connection factory used to create a connection for the actual JMS destination being mapped to the JMS bridge destination.

Note: In order to use the Exactly-once QOS for transactions, the JMS connection factory has to be an XA connection factory. For more information about connection factory and QOS requirements, refer to the Attributes table in Messaging Bridge –> Configuration –> General. Specify the JNDI name of the actual JMS destination being mapped to the JMS bridge destination.

Indicate whether the destination type is either a Queue or Topic.

Optionally, enter the user name and password that the messaging bridge will give to the bridge adapter. Note: All operations done to the specified destination are done using that user name and password. Therefore, the User Name/Password for the source and target destinations must have permission to access the underlying JMS destinations in order for the messaging bridge to work.

For more information about JMS bridge destination attributes, see JMS Bridge Destination –> Configuration.

Click Create to create an instance of the bridge destination with the name you specified in the Name field. The new instance is added under the JMS Bridge Destination node in the left pane.

When you finish defining attributes for a source JMS bridge destination, repeat these steps to configure a target JMS bridge destination, or vice versa. Then follow the instructions for Modifying an Existing Messaging Bridge Instance.

Configuring General Bridge Destinations

A general BridgeDestination instance defines a unique name for the actual source and target general bridge destinations within the WebLogic domain, the name of the adapter used to communicate with the specified destination, a list of properties to pass to the adapter, and, optionally, a user name and password.

Note: Although WebLogic JMS includes a “General Bridge Destination” framework for accessing non-JMS messaging products, WebLogic Server does not provide supported connector adapters for such products. Therefore, you must obtain a custom connector adapter from a third-party OEM vendor and consult their documentation for configuration instructions. You can also contact BEA Professional Services for information about obtaining a custom connector adapter.

You need to configure a BridgeDestination instance for each actual source and target destination to be mapped to a messaging bridge. Therefore, when you finish defining attributes for a source general bridge destination, repeat these steps to configure a target general bridge destination, or vice versa. You will designate the source and target general Bridge Destinations in Modifying an Existing Messaging Bridge Instance.

To configure a source or target general bridge destination, follow these steps.

Expand the Services —> Messaging Bridge node. Click the General Bridge Destinations node to open the General Bridge Destinations page in the right pane. Click the Configure a new General Bridge Destination link. A Configuration dialog shows the tabs associated with configuring a new general bridge destination. On the Configuration General tab, define the general configuration attributes for a general bridge destination:

Enter a general bridge destination name that is unique across a WebLogic Server domain. For example, if you are bridging between WebLogic Server releases 6.1 and 8.1, for the source destination you could change the default destination name to “61SourceDestination”. Then when you create the corresponding target destination, you could name it as “81TargetDestination”. Once the bridge destinations are configured, these names are listed as options in the Source Destination and Target Destination attributes on the Bridges —> General tab.

General tab. Specify the JNDI name of the adapter used to communicate with the bridge destinations.

eis.jms.WLSConnectionFactoryJNDIXA (default) — QOS is Exactly-once eis.jms.WLSConnectionFactoryJNDINoTX — QOS is Atmost-once or Duplicate-Okay For more information on which resource adapter name to use, see Messaging Bridge Resource Adapters and JNDI Names. Note: WebLogic Server does not provide adapters for non-JMS messaging products. Therefore, you must use a specialized adapter from a third-party OEM vendor, or contact BEA Professional Services to obtain a custom adapter. Leave the Adapter Classpath field blank when connecting to source and target destinations that are both running on WebLogic Server 6.1 or later. When connecting to a third-party JMS provider, the bridge destination must supply the provider’s CLASSPATH in the WebLogic Server CLASSPATH .

in the WebLogic Server . Specify all the properties defined for a bridge destination. Each property must be separated by a semicolon (for example, DestinationJNDIName=myTopic;DestinationType=topic;). For a complete listing of the required properties for JMS implementations, refer to the Attributes table in General Bridge Destination –> Configuration.

Note: For non-JMS messaging products that use adapters provided by a third-party OEM vendor, you should consult the vendor’s documentation for property configuration instructions. Optionally, enter the user name and password that the messaging bridge will give to the bridge adapter. Note: The User Name/Password for the source and target destinations must have permission to access the underlying source and target destinations in order for the Messaging Bridge to work.

For more information about the general bridge destination attributes, see General Bridge Destination –> Configuration.

Click Create to create an instance of the general bridge destination with the name you specified in the Name field. The new instance is added under the General Bridge Destination node in the left pane.

When you finish defining attributes for a source general bridge destination, repeat these steps to configure a target general bridge destination, or vice versa. Then follow the instructions for Modifying an Existing Messaging Bridge Instance.

Modifying an Existing Messaging Bridge Instance

Note: Before starting the procedure in this section, refer to the Using the Messaging Bridge to Interoperate with Different WebLogic Server Releases and Domains or Using the Messaging Bridge to Access a Third-Party Messaging Provider sections for specific configuration requirements and guidelines.

To modify a messaging bridge, follow these steps:

Targeting a Messaging Bridge to a Server, a Cluster, or a Migratable Target

You can choose the servers, clusters, or migratable targets in your domain on which you would like to deploy a messaging bridge. You can also reconfigure deployment targets later if you wish.

Expand the Messaging Bridge —> Bridges node to show the list of messaging bridges defined in your domain. Click the messaging bridge that you want to assign to a server, cluster, or migratable target. A dialog displays in the right pane showing the tabs associated with the messaging bridge instance. Click the Target and Deploy tab to display the following targeting options.

Independent Servers—you can select a server or servers where the messaging bridge will be deployed. The messaging bridge will be available on all the selected servers.

Clusters—you can select a cluster where the messaging bridge will be deployed. The messaging bridge will be available on all servers in the selected cluster. You can also target an individual server or servers within a cluster.

Migratable Targets—you can select a WebLogic Server migratable target where the messaging bridge will be deployed. When WebLogic Server is first booted, the messaging bridge is initially available only on the user-preferred server. After that, the bridge can be migrated to another server listed in the migratable target. Note: This must be the same target where the bridge’s resource adapter was deployed. For more information, see Deploying the Bridge’s Resource Adapters.

Click Apply to save your assignments.

Using the Messaging Bridge to Interoperate with Different WebLogic Server Releases and Domains

The following interoperability guidelines apply when using the messaging bridge to access JMS destinations on different releases of WebLogic Server and in other WebLogic domains.

Note: When the messaging bridge is used to communicate between two domains running different releases of Weblogic Server, a best-practice recommendation is for the messaging bridge to be configured to run on the domain using the latest release of Weblogic Server.

Resource Naming Rules for Inter-Domain Interoperability Using the Messaging Bridge

Within a domain, each server instance must be named uniquely and must not use the same name as the domain. This unique naming rule also applies to all configurable JMS objects, such as JMS servers, stores, templates, connection factories, session pools, and connection consumers. Additionally, in order for Weblogic domains to successfully interoperate using the Messaging Bridge, all participating resources (except connection factories) must have unique names across the interoperating domains. This rule includes domains from different releases of WebLogic Server.

For example, you cannot create a WebLogic Server instance named myserver in a version 8.1 domain named mydomain81 if there is already a server instance named myserver in a version 7.0 domain named mydomain70. On the JMS subsystem level, you cannot have two similarly named JMS servers (e.g., myJMSServer) residing in separate interoperating domains.

Therefore, you must adhere to the following rules when using the Messaging Bridge to interoperate between domains:

All domain names must be unique across your enterprise.

All WebLogic Server instance names must be unique within a domain and across all interoperating domains.

All JMS server names must be unique within a domain and across all interoperating domains.

If a JMS store (file or JDBC) is being used for persistent messages, all store names must be unique within a domain and across all interoperating domains.

Message Properties

Message properties are inherited from the Default Delivery Mode attribute on the connection factory used when a message is forwarded to its target destination. If the Default Delivery Mode is Persistent , a non-persistent message is forwarded as a persistent message resulting in a significant performance loss.

If you configure a bridge instance to forward non-persistent messages, configure and use a connection factory that has the Default Delivery Mode set to Non-Persistent .

Configuring Interoperability for WebLogic Domains

Unless the Exactly-once QOS (quality of service) is required for handling two-phase transactions sent across the messaging bridge, there are no special security configuration requirements for the bridge to interoperate between two release 6.1 or later domains.

However, you must follow these steps when a bridge running on release 7.0 domain must handle transactional messages (using the Exactly-once QOS) between two release 6.1 or later domains

For each server participating in the transaction, set the Security Interoperability Mode flag according to Using Security Interoperability Mode before rebooting. Note: When Security Interoperability Mode is set to performance, you are not required to set domain trust between the domains. Configure domain trust for the all participating bridge domains. In all participating WebLogic Server 6.x domains, change the password for the system user to the same value in all participating domains on the Security —> Users tab in the Administration Console. See Changing the System Password. Establish domain trust by setting a security credential for all domains to the same value in all participating domains. If you have participating 6.x domains, set the security credential for all domains to the same value as the system password in all participating WebLogic Server 6.x domains.

Using the Messaging Bridge To Access Destinations In a Release 6.1 or Later Domain

Use these guidelines when configuring a messaging bridge on a release 8.1 domain to provide “Exactly-once” transactional message communication between two release 6.1 or later domains.

Note: The Exactly-once quality of service for two-phase transactions is only supported for release 6.1 or later.

Using the Messaging Bridge to Access a Third-Party Messaging Provider

When configuring a messaging bridge involves interoperability with a third-party messaging provider, you must configure the following:

Before starting WebLogic Server:

Supply the provider’s CLASSPATH in the WebLogic Server CLASSPATH .

in the WebLogic Server .

Include the PATH of any native code required by the provider’s client-side libraries in the WebLogic Server system PATH . (This variable may vary depending on your operating system.)

of any native code required by the provider’s client-side libraries in the WebLogic Server system . (This variable may vary depending on your operating system.) In the JMSBridgeDestination instance for the third-party messaging product being bridged, provide vendor-specific information in the following attributes:

instance for the third-party messaging product being bridged, provide vendor-specific information in the following attributes: Connection URL

Initial Context Factory

Connection Factory JNDI Name

Destination JNDI Name

Note: The messaging bridge cannot provide the “Exactly-once” quality of service when the source and target bridge destinations are located on the same resource manager (that is, when the bridge is forwarding a global transaction that is using the XA resource of the resource manager). For example, when using MQ Series, it is not possible to use the same Queue Manager for the source and target bridge destinations.

For more information on configuring the remaining attributes for a JMS Bridge Destination, see Configuring JMS Bridge Destinations.

Managing a Messaging Bridge

Once a messaging bridge is up and running, it can managed from the console.

Monitoring All Messaging Bridges

To monitor the status of all configured messaging bridges in your domain:

Expand the Server node. Select the server instance where the messaging bridges are configured. A dialog displays in the right pane showing the tabs associated with the selected server instance. Select the Services —> Bridge tab. Click the Monitor all Messaging Bridge Runtimes text link. A table displays showing all the messaging bridge instances for the server and their status (either as running or not running).

Stopping and Restarting a Messaging Bridge

To temporarily suspend and restart an active messaging bridge:

Expand the Messaging Bridge node. Select the messaging bridge instance that you want to suspend. On the Configuration —> General tab, clear the Started check box to suspend the bridge. To restart the bridge, select the Started check box.

Configuring the Messaging Bridge Execute Thread Pool Size

You can configure the default execute thread pool size for your messaging bridges. For example, you may want to increase or decrease the default size to reduce competition from the WebLogic Server default thread pool. Entering a value of -1 disables this thread pool and forces a messaging bridge to use the WebLogic Server default thread pool.

WebLogic Server 12c (12.2.1): Configuring Oracle HTTP Server as a Cluster Proxy

Purpose

In this OBE tutorial, you will configure the WLS proxy plug-in for an Oracle HTTP Server. This proxy is configured to load balance incoming requests to your existing cluster. Finally, you verify proper load balancing and failover by using a supplied JavaEE Web application.

Time to Complete

Approximately 30 minutes

Background

Plug-ins enable WebLogic Server to integrate with applications deployed on Oracle HTTP Server. This includes load balancing HTTP requests across a WebLogic cluster, and automatically failing over failed requests due to a server not being available. These plug-ins also integrate with the HTTP session replication features of WebLogic.

The plug-in for the Oracle HTTP Server proxies requests based on the URL of the request (or a portion of the URL). This is called proxying by path. You can also proxy requests based on the Multipurpose Internet Mail Extensions (MIME) type of the requested file. Alternatively, you can use a combination of the two methods.

What Do You Need? (Optional)

Operating System and Software Requirements

A Linux machine with version 6 or greater of Oracle Linux or Red Hat Linux

JDK 1.8 update 51 and above

Oracle WebLogic Server 12c (12.2.1) software

Prerequisites

You should have completed the HTTP Server 12c (12.2.1): Using the Configuration Wizard tutorial.

WebLogic Bridge Message: “Failure of Web Server bridge: No backend server available for connection…”

I have an application (packaged software from a vendor) that runs on Oracle WebLogic.

There are few operations that, if I try them, I consistently get the following error page:

(WebLogic Bridge Message) Failure of Web Server bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

The error occurs consistently almost exactly five minutes after I try the operation.

The page does not look like the typical error page you get when the application logic fails. It looks like something to do with the infrastructure (e.g., WebLogic configuration).

I am pursuing the issue with the software vendor, but that’s not going well.

Has anyone seen this message and/or suggest an approach for diagnosing the root cause here?

Oracle Fusion Middleware 11g – Troubleshooting the Error

TROUBLESHOOTING STEPS – Failure of server APACHE bridge

“Failure of server APACHE bridge” Explained

This generic error is seen in the end user browser.

It occurs when there is some sort of ‘disconnect’ between the Oracle HTTP Server (OHS) mod_wl_ohs module and Oracle WebLogic Server. (The error can also be seen if you are front ending WebLogic Server with native Apache using mod_wl. This support document will focus on troubleshooting the error when using Oracle HTTP Server’s mod_wl_ohs module.)

The following Middleware 11g products – Portal / Forms / Reports / Discoverer – by default configured ‘out of the box’ to use mod_wl_ohs.

Below is an example diagram showing how OHS front ends Forms Services via mod_wl_ohs.

Therefore, if you are using Portal / Forms / Reports or Discoverer you may encounter the ‘Failure of server APACHE bridge’ error as OHS attempts to communicate with the managed servers WLS_PORTAL, WLS_FORMS, WLS_REPORTS and/or WLS_DISCO.

The use of mod_wl_ohs is not, however, exclusive to Portal / Forms / Reports and Discoverer. It is possible to configure Oracle HTTP Server to be a ‘front end’ for Oracle WebLogic Server based applications e.g.

· WebLogic JEE applications

· SOA

· WebCenter

· Webgate for Oracle Access Manager

When Oracle HTTP Server is manually configured as a front end to such applications, the ‘Failure of server APACHE bridge’ may be seen.

Common causes are:

· The target WebLogic Managed Servers are simply not started

· The target WebLogic Managed Servers are hanging or not responsive

· There is a problem with the mod_wl_ohs syntax which an administrator has added to the HTTP Server configuration file

· There is an underlying network error or misconfiguration

The module mod_wl_ohs is based on the WebLogic Server Apache HTTP Server Plug-In – mod_wl . This Apache Plug-In is discussed in this document

Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server 11g Release 1

Chapter 3 Installing and Configuring the Apache HTTP Server Plug-In

If, however, you are using Fusion Middleware 11g Web Tier refer to:

Oracle Fusion Middleware Administrator’s Guide for Oracle HTTP Server 11g Release 1

Chapter 3 Understanding Oracle HTTP Server Modules

3.10 mod_wl_ohs

Oracle Fusion Middleware Administrator’s Guide for Oracle HTTP Server 11g Release 1 (11.1.1)

Section 4.4.4 Configuring the mod_wl_ohs Module

Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server 11g Release 1 (10.3.5)

Chapter 4 Configuring the Plug-In for Oracle HTTP Server

Common Causes / Solutions

Have the WebLogic Managed Server(s) or Cluster been started?

Unlike OracleAS10g Rel 2 and Rel 3 , java components of the technology stack are not managed by OPMN.

(In OracleAS 10.1.2 and 10.1.3, the java component – OC4J – could be managed by OPMN and/or AS / EM Console).

In Fusion Middleware 11g the java components – running in WebLogic – are managed by WebLogic Server administration tools (e.g. WLST, WebLogic Admin Console) and/or Fusion Middleware Control.

For example, if you only issue the command

opmnctl startall

System / non java components (e.g HTTP Server, EM Agent.) should be up and running, but the WebLogic based java components will still be down.

Therefore you must ensure that the WebLogic Managed Servers or Cluster (depending on the choices made at AS Instance configuration time) are started.

For example:

· Using Oracle Portal? WLS_PORTAL must be started

· Using Oracle Forms? WLS_FORMS must be started

· Using Oracle Reports? WLS_REPORTS must be started

· Using Oracle Discoverer? WLS_DISCO must be started

The intuitive way to check and control the WebLogic Servers is to use Fusion Middleware Control. The screenshot below shows a snippet of the Fusion Middleware Control Forms Home Page.

The WebLogic Managed Server – WLS_FORMS – has a status of UP. If the status was showing as DOWN the WLS_FORMS would need to be started to avoid the ‘Failure of server APACHE bridge’ error.

Here are the documentation references to find out more about starting and managing the products which use a combination of System (Web Tier) and Java Components (Weblogic) components.

General

Oracle Fusion Middleware Administrator’s Guide 11g Release 1 (11.1.1)

Chapter 4 Starting and Stopping Oracle Fusion Middleware

Portal

Oracle Fusion Middleware Administrator’s Guide for Oracle Portal 11g Release 1

Chapter 8 Monitoring and Administering Oracle Portal

Forms

Oracle Fusion Middleware Forms Services Deployment Guide 11g Release 1

Chapter 4 Configuring and Managing Forms Services

Reports

Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services 11g Release 1

Chapter 7 Administering Oracle Reports Services Using Oracle Enterprise Manager

Discoverer

Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer

11g Release 1

Chapter 4 Managing and Configuring Discoverer

Oracle Access Manager

Oracle Fusion Middleware Administrator’s Guide for Oracle Access Manager

11g Release 1

Chapter 2 Getting Started with OAM Administration and Navigation

Tip: On MS Windows the WebLogic Managed Servers do not, by default, get automatically started after a machine reboot. This is because WebLogic Managed Servers are not configured as MS Windows Services. If you wish to set up MS Windows Services for the individual WebLogic Managed Servers review the advice given in

How to Install MS Windows Services For Oracle Middleware 11g Rel 1 WebLogic Admin and Managed Servers? (Document 1060058.1)

Are the WebLogic Managed Servers Responsive?

If the managed servers are up and running, the error can still occur if there is an underlying issue which is causing the server to hang or respond slowly. For example, a hang may be caused by an application or related to an interaction with the Database.

There is no easy way to tell whether this is the case. Suggestions are:

· Check the managed server logs for any errors / warnings or unusual output which may have occurred leading up to the appearance of the “Failure of Apache Bridge”.

· Can you successfully stop and restart the managed server?

Also a managed server functions as a lightweight HTTP Listener. Therefore, can you reach the managed server via its own port.

For example, if a managed server is listening on port 7004, what does the following URL return

http://machinehostingWLS.oracle.com:7004

If the WebLogic Managed Server is running and response you should at least see

Some products like Oracle Forms will allow you to test a more specific URL against the managed server listen port – such as

http://machinehostingWLS.oracle.com:7004/forms/lservlet

If WLS_FORM is responsive you will see:

Note: The advice in this support document does not extend to troubleshooting issues / errors related to the WebLogic Managed Servers of individual products

In the event that:

· the managed server are up and running

· there are no errors in the logs or signs of hanging

check the network configuration of the WebLogic Managed Server. For more detail refer to the “Network Diagnosis” section under “Diagnostic Tips”.

Is MOD_WL_OHS front ending a cluster?

Review the following documentation

Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server 11g Release 1 (11.1.1)

6.4 Understanding Connection Errors and Clustering Failover

Be prepared to investigate the performance and behaviour of your application / system. If necessary tune mod_wl_ohs by explicitly setting appropriate values for parameters which influence failover and timing.

· WLSocketTimeoutSecs

· WLIOTimeoutSecs (new name for HungServerRecoverSecs)

· Idempotent

· DynamicServerList

· WLCookieName

· WLDNSRefreshInterval

· MaxSkipTime

· ConnectTimeoutSecs

· ConnectRetrySecs

· KeepAliveSecs

· KeepAliveEnabled

· AcceptBacklog parameter

For more information about this parameters, refer to 7.1 General Parameters for Web Server Plug-Ins

Example which shows how to insert / set values for these parameters

SetHandler weblogic-handler WebLogicCluster demohost.us.oracle.com:9013 WLSocketTimeoutSecs 30 WLIOTimeoutSecs 500

1. Useful reference for OBIEE users:

Note 1476458.1 OBIEE 11.1.1.x – Avoid Error “Failure of server APACHE bridge” by Increasing Timeouts in Oracle HTTP Server Plug-in

2. The parameter Idempotent by default is set to ON. If, for some reason, it has been changed to OFF, plug-in clustering fail over will not work – making “Failure of server APACHE bridge” more likely.

Has MOD_WL_OHS been correctly configured?

If you are using Portal / Forms / Reports and/or Discoverer the mod_wl_ohs configuration should be correct.

Note: It is not recommended to change the mod_weblogic configuration which has been put in place the Configuration Assistant.

If you are manually configuring mod_wl_ohs for a JEE application or service – whether this be a custom application, SOA or WebCenter, then be sure to carefully follow the relevant documentation e.g.

Oracle Fusion Middleware Using Web Server Plug-Ins with Oracle WebLogic Server 11g Release 1

Chapter 3 Installing and Configuring the Apache HTTP Server Plug-In

Additional Useful Reference:

Note 1316142.1 How To Configure mod_wl_ohs with Oracle HTTP Server and Oracle WebLogic Server

The file containing the specific mod_wl_ohs configuration varies depending on the product. Portal / Forms / Reports / Discoverer mod_wl_ohs examples (as put in place by the Configuration Assistant) are shown below:

Product -> Portal

File Location -> $ORACLE_INSTANCE/config/OHS//moduleconf/portal.conf

WLS Cluster ->

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9001

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9001

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9001

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9001

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9001

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9001

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9001

No Cluster ->

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9001

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9001

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9001

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9001

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9001

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9001

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9001

Product -> Forms

File Location -> $ORACLE_INSTANCE/config/OHS//moduleconf/forms.conf

WLS Cluster ->

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9001

DynamicServerList ON

No Cluster ->

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9012

Product -> Reports

File Location -> $ORACLE_INSTANCE/config/OHS//moduleconf/reports_ohs.conf

WLS Cluster ->

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com

WebLogicPort 9013

DynamicServerList ON

No Cluster ->

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9013

Product -> Discoverer

File Location -> $ORACLE_INSTANCE/config/OHS//moduleconf/module_disco.conf

WLS Cluster ->

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9002

DynamicServerList ON

No Cluster ->

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 9014

Product -> General

File Location -> $ORACLE_INSTANCE/config/OHS//httpd.conf OR in an HTTP Server “include” .conf file. By default, a Fusion Middleware 11g Web Tier configuration creates a $ORACLE_INSTANCE/config/OHS//mod_wl_ohs.conf file.

WLS Cluster ->

SetHandler weblogic-handler

WebLogicCluster demohost.us.oracle.com:9013

No Cluster ->

SetHandler weblogic-handler

WebLogicHost demohost.us.oracle.com

WebLogicPort 7001

Tips:

1. The Port numbers shown in the table above are just examples. When reviewing the mod_wl_ohs configuration lines double check that the port values match up with the port values assigned to the WebLogic Managed Server or WebLogic Managed Servers in a WebLogic Cluster.

A WebLogic Cluster consists of one or more WebLogic Managed Servers that reside in the same WebLogic Domain. If there is more than one WebLogic Managed Server in a WebLogic Cluster then typically these Managed Servers reside on different host machines. All the WebLogic Managed Servers in a WebLogic Cluster have the same port value.

For example:

· No Cluster

o WLS_FORMS – demohost1.us.oracle.com:7004

· Cluster

o WLS_FORMS_CLUSTER:

§ WLS_FORMS – demohost1.us.oracle.com:7004

§ WLS_FORMS – demohost2.us.oracle.com:7004

2. Be aware that the value of the directive DynamicList affects the behaviour of the weblogic plug-in regards clusters. If DynamicList is set to OFF, it can lead to the “Failure of SERVER Apache Bridge” error, for example:

Reference:

Note 1380762.1 Forms / Reports 11g Intermittent “Failure of Server APACHE Bridge” – OHS Log Shows “apr_socket_connect call failed”

If you do not know how to check the port values or you think they may have changed, review the advice given in:

Oracle Fusion Middleware Administrator’s Guide 11g Release 1

Chapter 5 Managing Ports

The chapter does advise an administrator to review and amend the mod_wl_ohs configuration in the relevant Oracle HTTP Server .conf file should a WebLogic Managed Server port value be changed post running the Configuration Assistant.

2. Incorrect syntax or typos in the mod_wl_ohs configuration can result in an “APACHE Bridge Failure”.

Example: If you are configuring mod_wl_ohs to use SSL parameters (e.g. WLSSLWallet ) an incorrectly specified attribute value or typo causes the wallet not to be found. The browser throws “APACHE Bridge Failure” and the HTTP Server logs report “Internal error: WL SSL Init failed for path”.

Is the Network correctly configured?

There is a known issue if you are working with Fusion Middleware 11g on MS Windows and wish to use IPv6 addresses:

apr_socket_connect call failed Logged in OHS 11.1.1.2 / 11.1.1.3 Running on Windows (Document 1083385.1)

The issue is fixed if apply the latest Fusion Middleware 11g patchset, refer to:

Steps to Maintain Oracle Fusion Middleware 11g (11.1.1) (Document 1073776.1)

If this issue does not apply to your circumstances read on, work through the network checks described in the Diagnostic Tips.

Are you configuring SSL?

Be aware that “Failure of Server APACHE Bridge” can be seen if the parameter “WlSSLWallet” has not been configured correctly. Refer to the problem described in

“Internal error: WL SSL Init failed” and APACHE Bridge Failures After Configuring SSL for OHS/mod_wl_ohs and WLS (Document 1531143.1)

Review Logs

There are no specific mod_wl_ohs logs. Instead, check the Oracle HTTP Server error log. For more information about viewing the HTTP Server’s logs read

Oracle Fusion Middleware Administrator’s Guide for Oracle HTTP Server 11g Release 1

Section 7.4, “Viewing Oracle HTTP Server Logs”

It may also be necessary to check the WebLogic Managed Server logs for errors i.e ////logs e.g

MIDDLEWARE_HOME/user_projects/domains/Forms_Domain/servers/WLS_FORMS/logs

Diagnostic Tips

Viewing mod_wl_ohs Routing and Debug Info

Follow the advice given in

How to View FMW 11g Web Tier mod_wl_ohs Routing and Other Debug Information? (Document 967889.1)

and review the mod_wl_ohs routing and debug information

Network Diagnosis

The mod_wl_ohs configuration lines include a reference to the hostname. If the hostname cannot be resolved you will see the error ‘Failure of server APACHE bridge’.

If the Oracle HTTP Server and WebLogic Server Managed Servers are residing on different machines, it is important to check that there is network connectivity between the two machines – going in both directions

machinehostingOHS.oracle.com <---> machinehostingWLS.oracle.com

Before you investigate the network, take a look at the HTTP Server error_log. Errors found in this file,like the ones below, indicate a network misconfiguration or problem.
[2010-05-28T09:37:55.0919+02:00] [OHS] [WARNING:32] [OHS-9999] [core.c] [host_id: FMW11g] [host_addr: x.x.x.x] [pid: 3532] [tid: 1668] [user: SYSTEM] [VirtualHost: main] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed. [2010-05-28T09:37:55.0919+02:00] [OHS] [WARNING:32] [OHS-9999] [core.c] [host_id: FMW11g] [host_addr: x.x.x.x] [pid: 3532] [tid: 1668] [user: SYSTEM] [VirtualHost: main] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed. [2010-05-28T09:40:26.2871+02:00] [OHS] [ERROR:32] [OHS-9999] [mod_weblogic.c] [host_id: FMW11g] [host_addr: x.x.x.x] [pid: 3532] [tid: 1640] [user: SYSTEM] [VirtualHost: main] ap_proxy: trying GET /forms/frmservlet/admin at backend host ‘::1/9001; got exception ‘NO_RESOURCES: [os error=0, line 1787 of ../nsapi/URL.cpp]: apr_socket_connect call failed ‘ [2010-05-28T09:40:29.2979+02:00] [OHS] [ERROR:32] [OHS-9999] [mod_weblogic.c] [host_id: FMW11gr: x.x.x.x] [pid: 3532] [tid: 1640] [user: SYSTEM] [VirtualHost: main] ap_proxy: trying GET /forms/frmservlet/admin at backend host ‘::1/9001; got exception ‘NO_RESOURCES: [os error=0, line 1787 of ../nsapi/URL.cpp]: apr_socket_connect call failed ‘

To check whether a network misconfiguration is causing the error, work through the following steps:

Note: In a high availability architecture you may multiple machines hosting Oracle HTTP Server and multiple machines hosting WebLogic Server Managed Servers. So the checks described below may be many.

1. What hostname / ip address is the WebLogic Managed Server configured to listen against?

To quote from:

Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1

Servers: Configuration: General

The IP address or DNS name this server uses to listen for incoming connections.

Servers can be reached through the following URL:

protocol://listen-address:listen-port

Any network channel that you configure for this server can override this listen address.

If a server’s listen address is undefined, clients can reach the server through an IP address of the computer that hosts the server, a DNS name that resolves to the host, or the localhost string. The localhost string can be used only for requests from clients that running on the same computer as the server.

If you want to limit the valid addresses for a server instance, specify one of the following:

· If you provide an IP address, clients can specify either the IP address or a DNS name that maps to the IP address. Clients that specify an IP address and attempt to connect through an SSL port must disable hostname verification.

· If you provide a DNS name, clients can specify either the DNS name or the corresponding IP address.

Do not leave the listen address undefined on a computer that uses multiple IP address (a multihomed computer). On such a computer, the server will bind to all available IP addresses.

Notes:

To resolve a DNS name to an IP address, WebLogic Server must be able to contact an appropriate DNS server or obtain the IP address mapping locally. Therefore, if you specify a DNS name for the listen address, you must either leave a port open long enough for the WebLogic Server instance to connect to a DNS server and cache its mapping or you must specify the IP address mapping in a local file. If you specify an IP address for ListenAddress and then a client request specifies a DNS name, WebLogic Server will attempt to resolve the DNS name, but if it cannot access DNS name mapping, the request will fail.

Note also that you are using the demo certificates in a multi-server domain, Managed Server instances will fail to boot if you specify the fully-qualified DNS name. For information about this limitation and suggested workarounds, see “Limitation on CertGen Usage” in Securing Oracle WebLogic Server.

MBean Attribute:

ServerMBean.ListenAddress

Changes take effect after you redeploy the module or restart the server.

Check the WebLogic Managed Server network configuration in the WebLogic Admin Server console.

Reference:

Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1

Configure listen addresses

If an explicit hostname / ip address has been configured for the WebLogic Managed Server, the details need to match up with the hostname / ip address mapping as configured in mod_wl_ohs.

2. Does the hostname in the mod_wl_ohs configuration resolve to an IP address?

From the OHS machine:

ping machinehostingWLS.oracle.com

From the WLS machine(s):

ping machinehostingOHS.oracle.com

Furthermore, is the IP address returned by ping the one you expect to be associated with the hostname?

3. Is the hostname / ip address mapping held in a DNS Server and/or in the machine’s local hosts file?

Check the following:

a) Review the output from ‘nslookup’ – run this command e.g

From the OHS machine:

nslookup machinehostingWLS.oracle.com

From the WLS machine(s):

nslookup machinehostingWLS.oracle.com

b) Collect the IP address configuration – run these commands on each machine hosting Oracle HTTP Server and WebLogic Managed Servers.

MS Windows: ipconfig -a Unix: ifconfig -a

c) Review the local hosts files on the machines hosting Oracle HTTP Server and WebLogic Managed Servers. If hostname / ip address mappings are held in these files ensure there are no mistakes

· the IP addresses referenced by the hostname in the hosts file should match up with the information returned by the ipconfig/ifconfig commands

· the hostname should NOT be used as an alias for the loopback address 127.0.0.1 e.g

127.0.0.1 localhost machinehostingWLS 11.22.33.44 machinehostingWLS.oracle.com machinehostingWLS

· ideally the hostname should NOT be used as an alias for multiple IP addresses as this can cause confusion e.g

11.22.33.44 machinehostingWLS.oracle.com machinehostingWLS 66.77.88.99 anothermachine.oracle.com machinehostingWLS

4. As a troubleshooting test backup and edit the HTTP Server conf file containing the mod_wl_ohs configuration lines. Change the hostname reference to be the explicit IP address.

In the case of Forms for example, edit

$ORACLE_INSTANCE\config\OHS\ohs1\moduleconf\forms.conf and change the hostname to the IP address of the machine hosting the WebLogic Managed Servers.

Change

SetHandler weblogic-handler WebLogicHost machinehostingWLS WebLogicPort 9001

to:

SetHandler weblogic-handler WebLogicHost 11.22.33.44 WebLogicPort 9001

Save the file, and stop/ restart HTTP Server for the change to take effect.

5 Can you ping the port value using a tool like ‘telnet’

telnet demohost.us.oracle.com 9001

If the telnet fails (and the WebLogic Managed Server is up and listening to the specified port value) there is likely to be a network misconfiguration.

6. FIREWALLS?

Are there any firewalls between the machine hosting the Oracle HTTP Server(s) and the WebLogic Managed Servers. If so, ensure that the Firewall has rules to allow traffic through on the ports values configured in mod_wl_ohs.

MoS Community Discussions

Still have questions? Use Oracle Application Server Community in My Oracle Support to search for similar discussions or start a new discussion on this subject.