Purging Queue/Topic messages

Purging Queue/Topic messages.

1.Find out stuck messages are reside on which JMS server

2.Go to that JMS server->monitoring->Active Destinations.

3.Select JMSserver@Queue/Topic

4.Click Consumption and Pause

5.Go to the Queue/Topic Message and delete

6.Resume consumption for that JMSserver@Queue/Topic

Script to Ping and Telnet Hosts

List DB Sessions and Kill

Query to list DB Sessions:

Login as sys  user.

SELECT s.inst_id,
       s.sid,
       s.serial#,
       p.spid,
       s.username,
       s.program
FROM   gv$session s
       JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id
WHERE  s.type != 'BACKGROUND';

Kill DB Session:

SQL>ALTER SYSTEM KILL SESSION 'sid,serial#';                                                                

VBOX_E_FILE_ERROR (0x80BB0004) Component: Appliance Interface

Problem:

Could not open the current file in the archive (VERR_TAR_CHKSUM_MISMATCH). Result Code: VBOX_E_FILE_ERROR (0x80BB0004) Component: Appliance Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}

Scenario:

When trying to import oracle prebuilt VM into Oracle virtual box.  We encouter this exception.

Solution:

1. Check md5 checksum on the downloaded files.
2. Uncheck disk drive, usb while import.
3. Make sure Oracle virtual box version.  Make sure you import appliance into the Virtual Box mentioned on the website.

Oracle SOA Testing utilities: Wiki

Oracle SOA Testing utilities: Wiki: Home — Project Kenai



Oracle SOA Testing utilities: Wiki: ByPassExternalReferences — Project Kenai



Oracle SOA Testing utilities: Wiki: CheckoutAndRun — Project Kenai



Oracle SOA Testing utilities: Wiki: CornerCases — Project Kenai



Oracle SOA Testing utilities: Wiki: UseItFromOpenScript — Project Kenai

Can not build schema ..located at

Exception:

Exception: Can not build schema 'http://xmlns.oracle.com/ias/pcbpel/NotificationService' located at 'file:/C:/JDeveloper/mywork/SamplePOC/Project1/NotificationService.xsd'

NotificationService WSDL in MDS:

<definitions name="NotificationService_WSDL" targetNamespace="http://xmlns.oracle.com/ias/pcbpel/NotificationService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://xmlns.oracle.com/ias/pcbpel/NotificationService" xmlns:ns1="http://IWSDLDocument1.xsd" xmlns:java="http://schemas.xmlsoap.org/wsdl/java/" xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<types>
<schema targetNamespace="http://xmlns.oracle.com/ias/pcbpel/NotificationService1" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<import namespace="http://xmlns.oracle.com/ias/pcbpel/NotificationService" schemaLocation="NotificationService.xsd"/>
</schema>
<schema targetNamespace="http://xmlns.oracle.com/ias/pcbpel/NotificationService" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<element name="faultMessage" type="xsd:string"/>
</schema>
</types>
<message name="IMNotificationRequest">
<part name="IMPayload" type="tns:IMPayloadType"/>
</message>


Changed NotificationService WSDL in MDS:

<definitions name="NotificationService_WSDL" targetNamespace="http://xmlns.oracle.com/ias/pcbpel/NotificationService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://xmlns.oracle.com/ias/pcbpel/NotificationService" xmlns:tns1="http://xmlns.oracle.com/ias/pcbpel/NotificationService/xsd" xmlns:ns1="http://IWSDLDocument1.xsd" xmlns:java="http://schemas.xmlsoap.org/wsdl/java/" xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<types>
<xsd:schema>
<xsd:import namespace="http://xmlns.oracle.com/ias/pcbpel/NotificationServicexsd" schemaLocation="../../xsd/v1/NotificationService.xsd"/>
</xsd:schema>
<xsd:schema elementFormDefault="qualified">
<xsd:element name="faultMessage" type="xsd:string"/>
</xsd:schema>
</types>
<message name="IMNotificationRequest">
<part name="IMPayload" type="tns1:IMPayloadType"/>
</message>

Cause:

SOA is very strict in namespaces.  

•   Open the wsdl in JDEV to find cause of the issues.
•   Check the import schema elements for discrepencies.
•   Check if Schema being imported has same targetNamespace as the WSDL's      targetNameSpace.  Then import the same targetNamespace.

java.lang.UnsupportedOperationException: Remote JDBC disabled.

Problem:

<RuntimeException thrown by rmi server: weblogic.jdbc.common.internal.RmiDataSource.getConnection()
 java.lang.UnsupportedOperationException: Remote JDBC disabled.
java.lang.UnsupportedOperationException: Remote JDBC disabled
        at weblogic.jdbc.common.internal.JDBCServerHelperImpl.<clinit>(JDBCServerHelperImpl.java:36)
        at weblogic.jdbc.common.internal.JDBCService.initialize(JDBCService.java:91)
        at weblogic.jdbc.common.internal.JDBCService.start(JDBCService.java:137)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        Truncated. see log file for complete stacktrace

Solution:

1) Go to the Weblogic Domain Directory and edit the setDomainEnv.sh file
2) Modify WLS_JDBC_REMOTE_ENABLED value false to true.
WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true"
3) Restart the WebLogic Servers

Reference:

http://idmoim.blogspot.com/2011/07/javalangunsupportedoperationexception.html