Consumer is not getting listed for JMS Queue

Sometimes even though the JMS Queue and ConnectionFactory is existing in the JMS Module and the JMSAdpater Outbound connection pool JNDI  rightly points to the ConnectionFactory, still we may encounter issues like the consumer is not getting listed for the queue even after the BPEL consumer code deployed properly

In such cases follow this below rules

• Check the persistent store is created and targeted to the SOA Managed Server
• Check the JMS server is referring to the above persistent store and targeted to the SOA Managed Server
• Ensure the JMS Module has a subdeployment , which is targetted to the above JMSServer
• Ensure the ConnectionFactory/Queue/Topic has targettted to the above subdeployment
• Finally ensure the queue is existing in the JNDI tree. (console->Environment->Servers->SOAManagedServer->JNDI tree Icon)

Only if the Queue/Topic/ConnectionFactory exist in the Managed Servers JNDI tree , the consumer component can connect to it

this unique/primary key is referenced by some foreign keys

Sometimes while trying to drop the constraint we may encounter some issues as described below

SQL Error: ORA-02273: this unique/primary key is referenced by some foreign keys
02273. 00000 -  "this unique/primary key is referenced by some foreign keys"
*Cause:    Self-evident.
*Action:   Remove all references to the key before the key is to be dropped.

This issue can be fixed by adding the keyword 'CASCADE' at the end of the contraint drop statement

ALTER TABLE USER DROP CONSTRAINT USER_CON CASCADE;

Ant script works in one machine but not working on another machine. Log says use JDK instead of JRE. : error: null

Sometimes we may get error while running ANT scripts . The same ANT script is running in one machine and not on another machine. The error will be just NULL. If we look at the logs sometime the log will say Error says user JDK instead of JRE.

This is due to the java version mismatch between two systems.

Try to set the JAVA_HOME and PATH variable on the command prompt and then execute the ant task.

The java versions must match

BINDING.JCA-12141 ERRJMS_CONN_FAC_NOT_FOUND

Sometimes JCA Adapter throw this exception. In such situations my observation is the weblogic-ra.xml file in the corresponding adapter.rar may not have updated with the JNDI we configured from weblogic console.

In such situations  we can try copying the adapter rar file to a new location and unzip the file. Then we can manually add the connection-instance detail in the weblogic-ra.xml and zip it again.

From the weblogic admin console, goto deployments and delete that adapter and re install from the new location where we kept the new adapter rar file

The Adapters will be located under <MiddlewareHome>/Oracle_SOA1/soa/connectors/

Sample connection instance section for JMS Adapter

<connection-instance>
<jndi-name>eis/jms/MyJMSAdapter</jndi-name>
<connection-properties>
<properties>
<property>
<name>ConnectionFactoryLocation</name>
<value>MYJMSConnectionFactory</value>
</property>
<property>
<name>FactoryProperties</name>
<value></value>
</property>
<property>
<name>AcknowledgeMode</name>
<value>AUTO_ACKNOWLEDGE</value>
</property>
<property>
<name>IsTopic</name>
<value>false</value>
</property>
<property>
<name>IsTransacted</name>
<value>false</value>
</property>
<property>
<name>Username</name>
<value></value>
</property>
<property>
<name>Password</name>
<value></value>
</property>
</properties>
</connection-properties>
</connection-instance>

Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: ERRJMS_ERR_CR_QUEUE_PROD

Sometimes eventhough we configured the JMSAdapter properly we might encounter the following error

Produce_Message' failed due to: ERRJMS_ERR_CR_QUEUE_PROD

Due to this we cannot post any message to JMS Queue.

This happens due to the invalid target option for the JMSServer.

So if you are using your own JMSServer in the weblogic console , go to the configuration and click on the subdeployment and verify the target is proper. It might be pointing to a jms server which might be pointing to a different target server.

In short the JMSServer Target Server and the corresponding Persistent Store Target Server should be the same.

Alternatively instead of using your own JMSServer, try changing the target for subdeployment to 'SOAJMSSERVER'.

This must solve this issue

Why does sometime the Application Server connection Test Fails in JDeveloper

Normally if the configuration values are proper the Application Server connection test will give the result as "Success" for every item

But often the same connection gives the Test Results as Failed and we will not be in a position to deploy the composite.

In such situations verify the proxy settings in the JDEV and if proxy is checked, just uncheck it and restart the JDEV. This problem will disappear

Caused By: java.sql.SQLException: JDBC LLR, table verify failed for table 'DEV2_SOAINFRA.WL_LLR_ADMINSERVER', row 'JDBC LLR Domain//Server' record had unexpected value

Some times this issue appears during server startup.

In such cases just execute the following query against the SOAINFRA Schema

select * from WL_LLR_ADMINSERVER;

Check the value for RECRORDSTR column

If it is not matching to the current domain , update the value using the below sql script

update DEV2_SOAINFRA.WL_LLR_ADMINSERVER set RECORDSTR = 'health_domain//AdminServer' where  XIDSTR  = 'JDBC LLR Domain//Server';

commit;

Another way is :

Goto  <MiddlewareHome>\user_projects\domains\<your_domain>\config

and remove the following section from the config.xml file

  <jdbc-system-resource>
    <name>wlsbjmsrpDataSource</name>
    <target>AdminServer,osb_server1</target>
    <descriptor-file-name>jdbc/wlsbjmsrpDataSource-jdbc.xml</descriptor-file-name>
  </jdbc-system-resource>