AWS
Quick guide on aws for beginners Understanding network concepts in aws How to achieve CI/CD in aws CI/CD in aws managed resources with Jenkins Push Image to aws ECR Using GitHub Actions Setup an EventBridge Rule in aws How ECS & ECR works in aws EKS with Fargate Profile Launch EKS using eksctl in aws Container insight for EKS-Fargate in cloudwatch Deploy aws resources with CloudFormation AWS secrets scanning by GitHub Setup Site to Site VPN Connection in AWS
AZURE
Gateways in Azure Understanding network concepts in Azure Ingress in Azure Kubernetes Service
GCP
Architecting hybrid infrastructure with Anthos

ANSIBLE
Ansible a configuration management tool Runbook Automation tool for playbooks
DOCKER
Docker a containerization Tool Networking in Docker Multi-stage build in Docker what is docker-compose All about Docker swarm
GITHUB
CLI instruction to work with GitHub Integrating Jenkins with GitHub Push Image to ECR Using GitHub Actions
JENKINS
Jenkins a continuous integration tool Acheive CI/CD using Jenkins in AWS Configuring weblogic deployer plugin in Jenkins
KUBERNETES
Kubernetes an orchestration framework Launch kubernetes cluster in Different ways Debugging your kubernetes cluster Certificates renewal of kubernetes cluster Deploying application on Kubernetes cluster api versions to use in manifest file RBACs in Kubernetes Health check of containers in Kubernetes Rancher a cluster management platform Understanding ISTIO as a service mesh
TERRAFORM
Deploying IaC using Terraform Terraform module EKS cluster using Terraform

APACHE
Things to know in Apache How to Configure Apache-httpd Server Setup httpd as os-service on OL8 SiteMinder and its Integration with WebServer Apache SSL Installation Instructions NO_RESOURCES Errors in APACHE with WLS
WEBLOGIC
Installing WebLogic 12.1.3 without GUI WebLogic Server as a managed Azure service WLS domain extension to include JRF template All about OPatch in WLS How to define WorkManager in Weblogic Some known Weblogic exceptions Different OutOfMemory issues Some known Weblogic exceptions Play with WLST Persistent store in WLS Configuration of NodeManager

JAVA
JAVA_OPTIONS Study on JAVA_HEAP Native OOM in Java Heap Types of Threads Various Java-options to use in Java apps How to run Java Flight Recorder dbping a java-weblogic utility
SSL
When & why to use SSL certificates SSLv3 to TLS1.* SHA2 on Oracle https Server Weblogic SSL Renewal Steps
CHEATSHEETs
Linux Cheatsheet Linux Log parsing cheetsheet SSL Cheatsheet MySQL Cheatsheet PostgreSQL Cheatsheet WebLogic Cheatsheet Python Cheatsheet Kubernetes Cheatsheet Terraform Cheatsheet Hashicorp-vault Cheatsheet GCP Cheatsheet
OTHER
All about Messaging Queue small guide on Python WLSDM monitoring agent in WLS Register driver for MSSqlServer Understanding YAML

30 August 2016

Study on JMS Bridge

The WebLogic JMS adapter is being used for JMS bridge configuration. When the JMS
source/destination is restarted, the adapter is not able to reconnect to the restarted instance.
Only a redeployment of the JMS resource adapter resolves the problem.
We suspect that the connections in the resource adapter connection pool are never being refreshed since WebLogic is not able to detect the invalid connections.
In order to make the resource adapter detect invalid connections, we need to make the resource adapter connections testable.
For this to happen, the JMS adapter's ManagedConnectionFactory should implement the javax.resource.spi.ValidatingManagedConnectionFactory.

The JMS bridge is failing to refresh the consumer connections after a DB failover.
The JMS adapter is not responsible for the failover activities. It is the JMS bridge which is responsible for refreshing the connections.

The problem can be resolved by changing the JMS Connection Factory configuration. Change the client reconnect policy to be "all" (the default is producer). See the following XML example:

|reconnect-policy|all|/reconnect-policy|


When the destination domain is restarted, the source bridge was failing to connect with the following exception:
 
com.mslv.oms.automation.AutomationException: com.mslv.oms.automation.AutomationException: Destination not found

The Messaging Bridge stops processing messaging and a server thread dump reveals the bridge is stuck waiting on ConnectionWrapper.invoke(). This issue is addressed by BUG 8066979

On the destination domain, disable Server Affinity on the Target Connection Factory to allow proper load balancing on both Distributed Queue members. To do this, go to JMS Modules -> ConnectionFactory ->Configuration ->Load Balance.
On the Source domain, apply the patch for BUG 8066979 as specified below to the Bridge host domain and retest.

Br

Labels:

No comments:

Post a Comment