Jms Protocol error

Hi ,
I am using Oracle 10g version 10.1.3 and Oracle AS JMS Server
I have a java client that is using the following configuration for JNDI conext.
// set the environment properties
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL,"opmn:ormi://vtun-lap.us.oracle.com:6003:home");
env.put(Context.SECURITY_PRINCIPAL,"oc4jadmin");
env.put(Context.SECURITY_CREDENTIALS,"apps10g");
QueueConnectionFactory queueConnectionFactory =util.getQueueConnectionFactory();
When I execute the following statement
QueueConnection queueConnection = queueConnectionFactory.createQueueConnection();
I am getting the following error:
[PROTOCOL ERROR] JMSRemoteServer[vtun-lap:12601]: "JMS protocol" error, expected "-559,038,735", got
Object Address: 0x529EDEC4
Thank you
Van Sioung

Your client is using old OC4J JMS classes - you need to set up your client's class-path to point to the .jar files that came with 10.1.3. The exact set of .jar files required for looking up and using OC4J JMS connection factories and destinations over RMI is covered in the 10.1.3 version of the Services Guide - in the JMS Chapter.

Similar Messages

  • JMS Protocol Fehler

    Hi forum !
    I have an J2EE Application with follow configuration:
    j2eeJavaApp1.ear consisting of
    j2eeJavaApp1-ejb.jar, j2eeJavaApp1-client.jar and META-INF.
    In META-INF there are following files: application.xml, data-sources.xml, orion-application.xml and surely MANIFEST.MF
    In application.xml are defined 2 modules:
    <application>
    <display-name>j2eeJavaApp1</display-name>
    <module>
    <ejb>j2eeJavaApp1-ejb.jar</ejb>
    </module>
    <module>
    <java>j2eeJavaApp1-client.jar</java>
    </module>
    </application>
    The contents of the j2eeJavaApp1-ejb.jar are:
    META-INF, model.
    META-INF contains ejb-jar.xml and orion-ejb-jar.xml.
    The extraction from ejb-jar.xml:
    <message-driven>
    <description>Message Driven Bean</description>
    <display-name>MessageDrivenEJB</display-name>
    <ejb-name>MessageDrivenEJB</ejb-name>
    <ejb-class>model.MessageDrivenEJBBean</ejb-class>
    <transaction-type>Container</transaction-type>
    <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
    <message-driven-destination>
    <destination-type>javax.jms.Topic</destination-type>
    </message-driven-destination>
    </message-driven>
    The extraction from orion-ejb-jar.xml:
    <message-driven-deployment name="MessageDrivenEJB" connection-factory-location="jms/theTopicConnectionFactory" destination-location="jms/theTopic"/>
    In model-directory is resided the MessageDrivenEJB-class: MessageDrivenEJBBean.
    Now the contents of the j2eeJavaApp1-client.jar:
    client-Directory:
    MDBClient-Class (the standalone client)
    META-INF-Directory:
    application-client.xml:
    <application-client>
    <display-name>j2eeJavaApp1</display-name>
    <resource-ref>
              <description>The Factory used to produce connections to the log topic...</description>
              <res-ref-name>jms/theTopicConnectionFactory</res-ref-name>
              <res-type>javax.jms.TopicConnectionFactory</res-type>
              <res-auth>Container</res-auth>
         </resource-ref>
    <resource-ref>
              <description>The log topic where log events are broadcasted...</description>
              <res-ref-name>jms/theTopic</res-ref-name>
              <res-type>javax.jms.Topic</res-type>
              <res-auth>Container</res-auth>
         </resource-ref>
    </application-client>
    orion-application-client.xml
    <orion-application-client>
    <resource-ref-mapping
    name="jms/theTopicConnectionFactory"
    location="jms/theTopicConnectionFactory">
    </resource-ref-mapping>
    <resource-ref-mapping
    name="jms/theTopic"
    location="jms/theTopic">
    </resource-ref-mapping>
    </orion-application-client>
    =========================================================
    This Application was deployed to OC4J (10.0.3.0.0) without exceptions.
    The extraction from the jms.xml from %OC4J%/j2ee/home/config directory:
    <topic name="The Demo Topic" location="jms/theTopic">
              <description>The demo topic</description>
    </topic>
    <topic-connection-factory name="The Demo Topic Factory"
    location="jms/theTopicConnectionFactory">
         <description>The demo topic connection factory</description>
    </topic-connection-factory>
    The extraction from the application.xml from the same directory:
    <resource-provider
    class="com.evermind.server.jms.Oc4jResourceProvider"
    name="oc4jjms">
    <description>oc4j-jms loop back resource provider</description>
    </resource-provider>
    =========================================================
    The client attemts to create JMS-Connection and then send a message to a topic with follow code:
    String TOPIC_NAME="jms/theTopic";
         String TOPIC_CONNECTION_FACTORY="jms/theTopicConnectionFactory";
         TopicConnectionFactory connectionFactory = (TopicConnectionFactory)getInitialContext().lookup( TOPIC_CONNECTION_FACTORY);
         TopicConnection connection = connectionFactory.createTopicConnection();
         connection.start();
         TopicSession topicSession = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
    Topic topic = (Topic)new InitialContext().lookup( TOPIC_NAME);
         TopicPublisher publisher = topicSession.createPublisher(topic);
         Message message = topicSession.createMessage();
         message.setJMSType("theMessage");
         message.setLongProperty("time", System.currentTimeMillis());
         message.setStringProperty("subject", "Subject");
         message.setStringProperty("message", "Hello");
    System.out.println("Gleich wird message abgeschickt: "+new java.util.Date());
         publisher.publish(message);
         publisher.close();
         topicSession.close();
         connection.close();
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    private static Context getInitialContext() throws NamingException
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
    //env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory");
    env.put(Context.SECURITY_PRINCIPAL, "admin");
    env.put(Context.SECURITY_CREDENTIALS, "admin");
    env.put(Context.PROVIDER_URL, "ormi://vlimar-191/j2eeJavaApp1");
    return new InitialContext(env);
    =========================================================
    =========================================================
    The line:
    TopicConnectionFactory connectionFactory = (TopicConnectionFactory)getInitialContext().lookup( TOPIC_CONNECTION_FACTORY);
    is performed without any troubles. But the next line:
    TopicConnection connection = connectionFactory.createTopicConnection();
    runs into the exception:
    javax.jms.JMSException: [PROTOCOL ERROR] JMSRemoteServer[vlimar-191:9127]: "JMS protocol" error, expected "-559.038.735", got "-559.038.734".
         at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1853)
         at com.evermind.server.jms.JMSRemoteServer.readCheck(JMSRemoteServer.java:754)
         at com.evermind.server.jms.JMSRemoteServer.protocol(JMSRemoteServer.java:769)
         at com.evermind.server.jms.JMSRemoteServer.<init>(JMSRemoteServer.java:92)
         at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:103)
         at com.evermind.server.jms.EvermindTopicConnection.<init>(EvermindTopicConnection.java:63)
         at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicConnection(EvermindTopicConnectionFactory.java:91)
         at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicConnection(EvermindTopicConnectionFactory.java:83)
         at client.MDBClient.sendMessageDirect(MDBClient.java:86)
         at client.MDBClient.main(MDBClient.java:43)
    This exception occurs with RMIInitialContextFactory as well as with ApplicationClientInitialContextFactory.
    Does anyone has an idea, how to get the JMSConnection from the standalone Java Client out of the AS to the Topic inside the AS.
    Thanks in advance!!

    I am getting the following error.
    ==========================================================
    C:\>java -classpath c:\ora10g\j2ee\home\oc4j.jar;c:\ora10g\j2ee\home\lib\jms.jar com.evermind.server.jms.JMSUtils -username admin -password oraadmin1 -host localhost -port 3201 stats
    Oracle Application Server Containers for J2EE 10g (9.0.4.0.0) (build "040317.1838"), OC4J JMS 1.0.2b
    javax.jms.JMSException: [PROTOCOL ERROR] JMSRemoteServer[localhost:3201]: "JMS protocol" error, expected "-559,038,735", got "-485,684,723".
    at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1853)
    at com.evermind.server.jms.JMSRemoteServer.readCheck(JMSRemoteServer.java:754)
    at com.evermind.server.jms.JMSRemoteServer.protocol(JMSRemoteServer.java:769)
    at com.evermind.server.jms.JMSRemoteServer.<init>(JMSRemoteServer.java:92)
    at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:103)
    at com.evermind.server.jms.EvermindConnectionFactory.createConnection(EvermindConnectionFactory.java:118)
    at com.evermind.server.jms.EvermindConnectionFactory.createConnection(EvermindConnectionFactory.java:110)
    at com.evermind.server.jms.JMSUtils.stats(JMSUtils.java:621)
    at com.evermind.server.jms.JMSUtils.main(JMSUtils.java:237)
    ==========================================================
    I only have one oc4j.jar on my system, I renamed the others. Plus, I did a search of all jars for JMSRemoteServer and it is the only one that has it. I have the 10g infrastructure installed and JDeveloper 10g.
    Any ideas?
    Ben

  • Using socket and JMS protocol in the same logic for OSB

    Hi frnds,
    In my organization...the only communication protocol used is "socket" protocol. However, I want to use JMS protocol to process incoming messages. Can somebody help me figuring out how to go about it.
    Using some nice OSB blogs, I am able to create the JMS connection factory and JMS queues in weblogic. And that works fine when I select the communication protocol as JMS while creating the BS and PS.
    What should be my message flow when the communication protocol used is "socket" for both BS and PS.
    salil

    Hi,
    Make the BS as JMS and the PS as socket, in the PS's flow do a route for the BS... Then if an external call is made to the PS via socket, it will send a messages to a JMS queue...
    Hope this helps...
    Cheers,
    Vlad

  • B-channel oos and protocol error 510

    Dear all,
    I have some some issue couple of days ago. The telephony system of my client worked well and suddenly the cannot make external calls via E1. I checked the config and for me it seems to be ok. When I checked the SDL file, I can see the B channel out of service error message following by the
    "MGCP PROTOCOL ERROR: <S1/SU1/DS1-0/[email protected]> CRCX error code: 510". They have A CUCM 6.0 and Cisco 2821 as gateway with 12.4 (25f) advance IP service IOS.
    I perform the following actions without success:
    -From the CUCM in the advance service I forced the Bchannel to bring it in service,
    - no mgcp/mgcp, -reboot the CUCM and the Gateway,
    -reset the controller throug CUCM,... in vain.
    They contacted telco and has confirm that everything seems to be ok. Find below the information that can help you to undestand better
    #sh run brief
    Building configuration...
    Current configuration : 4859 bytes
    version 12.4
    service tcp-keepalives-in
    service tcp-keepalives-out
    service timestamps debug datetime msec
    service timestamps log datetime msec localtime show-timezone
    service password-encryption
    service sequence-numbers
    hostname ATD-CCM-GW
    boot-start-marker
    boot-end-marker
    security authentication failure rate 3 log
    security passwords min-length 6
    logging buffered 51200 debugging
    aaa new-model
    aaa authentication login default local
    aaa authentication login local_authen local
    aaa authorization exec default local
    aaa authorization exec local_author local
    aaa session-id common
    clock timezone A 1
    network-clock-participate slot 1
    network-clock-select 1 E1 1/1/0
    ip cef
    ip domain name xx.xxxx.xxx
    ip host ATD-CCM1 10.10.10.100
    ip auth-proxy max-nodata-conns 3
    ip admission max-nodata-conns 3
    isdn switch-type primary-net5
    isdn logging
    voice-card 0
    dspfarm
    dsp services dspfarm
    voice-card 1
    no dspfarm
    no voice call carrier capacity active
    voice rtp send-recv
    voice class codec 1
    codec preference 1 g711ulaw
    codec preference 2 g711alaw
    codec preference 3 g729br8 bytes 40
    voice class h323 1
    h225 timeout tcp establish 3
    crypto pki trustpoint TP-self-signed-635937996
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-635937996
    revocation-check none
    rsakeypair TP-self-signed-635937996
    crypto pki certificate chain TP-self-signed-635937996
    certificate self-signed 01
    application
      service alternate Default
    controller E1 1/1/0
    framing NO-CRC4
    pri-group timeslots 1-31 service mgcp
    interface GigabitEthernet0/0
    description to_CCM
    ip address 10.10.10.254 255.255.255.0
    duplex auto
    speed auto
    interface GigabitEthernet0/1
    no ip address
    shutdown
    duplex auto
    speed auto
    interface Serial1/1/0:15
    no ip address
    encapsulation hdlc
    isdn switch-type primary-net5
    isdn overlap-receiving
    isdn incoming-voice voice
    isdn bind-l3 ccm-manager
    isdn bchan-number-order ascending
    isdn sending-complete
    no cdp enable
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 10.10..253
    ip http server
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    logging trap debugging
    control-plane
    voice-port 1/0/0
    timing hookflash-out 50
    voice-port 1/0/1
    signal groundStart
    timing hookflash-out 50
    voice-port 1/0/2
    signal groundStart
    timing hookflash-out 50
    voice-port 1/0/3
    signal groundStart
    timing hookflash-out 50
    voice-port 1/1/0:15
    ccm-manager fallback-mgcp
    ccm-manager mgcp
    no ccm-manager fax protocol cisco
    ccm-manager music-on-hold
    ccm-manager config server ATD-CCM1 
    ccm-manager config
    mgcp
    mgcp call-agent 10.10.10.100 service-type mgcp version 0.1
    mgcp dtmf-relay voip codec all mode out-of-band
    mgcp rtp unreachable timeout 1000 action notify
    mgcp modem passthrough voip mode nse
    mgcp modem passthrough voip redundancy
    mgcp package-capability rtp-package
    mgcp package-capability sst-package
    mgcp package-capability pre-package
    mgcp default-package fxr-package
    no mgcp package-capability res-package
    no mgcp timer receive-rtcp
    mgcp sdp simple
    mgcp fax t38 inhibit
    no mgcp explicit hookstate
    mgcp rtp payload-type g726r16 static
    mgcp bind control source-interface GigabitEthernet0/0
    mgcp bind media source-interface GigabitEthernet0/0
    mgcp profile default
    dial-peer voice 999101 pots
    service mgcpapp
    port 1/0/1
    forward-digits all
    dial-peer voice 999102 pots
    service mgcpapp
    port 1/0/2
    forward-digits all
    dial-peer voice 999103 pots
      service mgcpapp
    port 1/0/3
    forward-digits all
    dial-peer voice 1 pots
    service mgcpapp
    incoming called-number .
    direct-inward-dial
    port 1/1/0:15
    forward-digits all
    dial-peer voice 999100 pots
    service mgcpapp
    port 1/0/0
    gateway
    timer receive-rtp 1200
    scheduler allocate 20000 1000
    ntp clock-period 17180351
    ntp update-calendar
    ntp server 10.10.10.9 source GigabitEthernet0/0
    end
    #sh controller e1
    E1 1/1/0 is up.
      Applique type is Channelized E1 - balanced
      No alarms detected.
      alarm-trigger is not set
      Version info Firmware: 20090113, FPGA: 20, spm_count = 0
      Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
       Current port master clock:recovered from backplane
      Data in current interval (225 seconds elapsed):
         0 Line Code Violations, 0 Path Code Violations
         0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
         0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
      Total Data (last 3 15 minute intervals):
         0 Line Code Violations, 0 Path Code Violations,
         0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
         0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    #sh ccm-manager
    MGCP Domain Name: ATD-CCM-GW.xx.xxxx.xxx
    Priority        Status                   Host
    ============================================================
    Primary         Registered               10.10.10.100
    First Backup    None                    
    Second Backup   None                    
    Current active Call Manager:    10.10.10.100
    Backhaul/Redundant link port:   2428
    Failover Interval:              30 seconds
    Keepalive Interval:             15 seconds
    Last keepalive sent:            15:31:24 UTC Oct 19 2012 (elapsed time: 00:00:09)
    Last MGCP traffic time:         15:31:24 UTC Oct 19 2012 (elapsed time: 00:00:09)
    Last failover time:             None
    Last switchback time:           None
    Switchback mode:                Graceful
    MGCP Fallback mode:             Enabled/OFF
    Last MGCP Fallback start time:  None
    Last MGCP Fallback end time:    None
    MGCP Download Tones:            Disabled
    TFTP retry count to shut Ports: 2
    Backhaul Link info:
        Link Protocol:      TCP
        Remote Port Number: 2428
        Remote IP Address:  10.10.10.100
        Current Link State: OPEN
        Statistics:
            Packets recvd:   11
            Recv failures:   0
            Packets xmitted: 18
            Xmit failures:   0
        PRI Ports being backhauled:
            Slot 1, VIC 1, port 0
    Configuration Auto-Download Information
    =======================================
    Current version-id: 1350042385-8bfc9ed0-f85e-4435-8baf-3ad1ceefb55c
    Last config-downloaded:00:00:00
    Current state: Waiting for commands
    Configuration Download statistics:
               Download Attempted             : 1
                 Download Successful          : 1
                 Download Failed              : 0
                 TFTP Download Failed         : 0
               Configuration Attempted        : 1
                 Configuration Successful     : 1
                 Configuration Failed(Parsing): 0
                 Configuration Failed(config) : 0
    Last config download command: New Registration
    Configuration Error History:
    controller E1 1/1/0
    no pri-group timeslots 1-31
    FAX mode: disable
    #debug isdn q931
    #debug mgcp packet
    009112: Oct 20 12:48:50.374: MGCP Packet received from 10.10.10.100:2427--->
    CRCX 2359 S1/SU1/DS1-0/[email protected] MGCP 0.1
    C: D000000001fbf9aa000000F500000001
    X: 1f
    L: p:20, a:PCMU, s:off, t:00
    M: recvonly
    R: D/[0-9ABCD*#]
    Q: process,loop
    <---
    009113: Oct 20 12:48:50.382: MGCP Packet sent to 10.10.10.100:2427--->
    200 2359 OK
    I: 8
    v=0
    c=IN IP4 10.10.10.254
    m=audio 18274 RTP/AVP 0 100
    a=rtpmap:100 X-NSE/8000
    a=fmtp:100 192-194
    <---
    009114: Oct 20 12:48:50.386: ISDN Se1/1/0:15 Q931d: srl_send_l3_pak:
    source_id = CCM MANAGER 0x0003, dest_id = Q.921 0x0000, prim = DL_DATA_REQ 0x0240
    priv_len = 4 int_id = 0x4636A628 datasize = 64
    009115: Oct 20 12:48:50.386: ISDN Se1/1/0:15 Q931d: data =
    009116: Oct 20 12:48:50.386:           4636A628000000030240043800010000
    009117: Oct 20 12:48:50.386:           0802000105A104038090A31803A9839F
    009118: Oct 20 12:48:50.386:           280B526F6C616E64202D2049546C0601
    009119: Oct 20 12:48:50.386:           81313232307009803636393332313933
    009120: Oct 20 12:48:50.386:
    009121: Oct 20 12:48:50.434: MGCP Packet received from 10.10.10.100:2427--->
    MDCX 2360 S1/SU1/DS1-0/[email protected] MGCP 0.1
    C: D000000001fbf9aa000000F500000001
    I: 8
    X: 1f
    L: p:20, a:PCMU, s:off, t:b8, fxr/fx:t38
    M: recvonly
    R: D/[0-9ABCD*#]
    Q: process,loop
    <---
    009122: Oct 20 12:48:50.438: MGCP Packet sent to 10.10.10.100:2427--->
    510 2360 fx: setting cannot be supported
    <---
    009123: Oct 20 12:48:50.438: ISDN Se1/1/0:15 Q931d: srl_send_l3_pak:
    source_id = CCM MANAGER 0x0003, dest_id = Q.921 0x0000, prim = DL_DATA_REQ 0x0240
    priv_len = 4 int_id = 0x4636A628 datasize = 25
    009124: Oct 20 12:48:50.438: ISDN Se1/1/0:15 Q931d: data =
    009125: Oct 20 12:48:50.438:           4636A628000000030240043800010000
    009126: Oct 20 12:48:50.438:           0802000145080280AF
    009127: Oct 20 12:48:50.462: MGCP Packet received from 10.10.10.100:2427--->
    DLCX 2361 S1/SU1/DS1-0/[email protected] MGCP 0.1
    C: D000000001fbf9aa000000F500000001
    I: 8
    X: 1f
    S:
    <---
    ATD-CCM-GW#
    009128: Oct 20 12:48:50.478: MGCP Packet sent to 10.10.10.100:2427--->
    250 2361 OK
    P: PS=0, OS=0, PR=0, OR=0, PL=0, JI=0, LA=0
    <---
    009129: Oct 20 12:48:50.478: ISDN Se1/1/0:15 Q931d: srl_send_l3_pak:
    source_id = CCM MANAGER 0x0003, dest_id = Q.921 0x0000, prim = DL_DATA_REQ 0x0240
    priv_len = 4 int_id = 0x4636A628 datasize = 21
    009130: Oct 20 12:48:50.478: ISDN Se1/1/0:15 Q931d: data =
    009131: Oct 20 12:48:50.478:           4636A628000000030240043800010000
    009132: Oct 20 12:48:50.478:           080200015A
    ATD-CCM-GW#
    009133: Oct 20 12:49:03.002: MGCP Packet received from 10.10.10.100:2427--->
    CRCX 2362 S1/SU1/DS1-0/[email protected] MGCP 0.1
    C: D000000001fbf9ac000000F500000002
    X: 1e
    L: p:20, a:PCMU, s:off, t:b8, fxr/fx:t38
    M: recvonly
    R: D/[0-9ABCD*#]
    Q: process,loop
    <---
    #sh mgcp statistics
    UDP pkts rx 270, tx 270
    Unrecognized rx pkts 0, MGCP message parsing errors 0
    Duplicate MGCP ack tx 0, Invalid versions count 0
    CreateConn rx 10, successful 1, failed 9
    DeleteConn rx 1, successful 1, failed 0
    ModifyConn rx 1, successful 0, failed 1
    DeleteConn tx 0, successful 0, failed 0
    NotifyRequest rx 0, successful 0, failed 0
    AuditConnection rx 0, successful 0, failed 0
    AuditEndpoint rx 61, successful 61, failed 0
    RestartInProgress tx 4, successful 4, failed 0
    Notify tx 193, successful 193, failed 0
    ACK tx 63, NACK tx 10
    ACK rx 197, NACK rx 0
    IP address based Call Agents statistics:
    IP address 10.10.10.100, Total msg rx 270,
                      successful 260, failed 10
    System resource check is DISABLED. No available statistic
    DS0 Resource Statistics
    Utilization: 0.00 percent
    Total channels: 34
    Addressable channels: 34
    Inuse channels: 0
    Disabled channels: 0
    Free channels: 34
    sh controller e1
    #sh network-clocks
      Network Clock Configuration
      Priority      Clock Source    Clock State     Clock Type
         1          E1 1/1/0        GOOD            E1         
        10          Backplane       GOOD            PLL        
      Current Primary Clock Source
      Priority      Clock Source    Clock State     Clock Type
         1          E1 1/1/0        GOOD            E1     
    Thanks for your help

    The explanation for your syslog message is " The B-channel indicated by this alarm has gone out of service. Some of the more common reasons for a B-channel to go out of service include: Taking the channel out of service intentionally to perform maintenance on either the near- or far-end; MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Cisco Unified Communications Manager (Unified CM); MGCP gateway doesn't respond to an MGCP command sent by Unified CM three times; a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway"
    Recommended action:
    Check the Unified CM advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.

  • Need suggestion on  implementing JMS message error recovery

    Hi,
    Our application has a JMS topic where we publish application events. Now, there can be scenarios where the consumers cannot process the message due to some infrastructure issues and would error out. We need a way so that those messages can be reprocessed again later. we are thinking of the following design for JMS message error recovery
    1. Use a persistent TOPIC (this would ensure guaranteed delivery)
    2. Configure a error destination on JMS topic e.g a jms queue
    3. Have an error handling MDB listening to the Error destination. An error handling MDB would dequeue the errored messages from error destination and persist it to a Data base "error" table..
    4. Provide a mechanism to republish those messages to topic (e.g a scheduler or admin ui or a command line utility) .. The messages would deleted from database "error" table and published to topic again....
    A. Are there any issues with the above design which we need to handle?
    B. Are there any additional steps required in a Cluster environment with a distributed topic and distribute error destination? (our error mdb will have one-copy-per-application setting)
    B. From a performance angle, Is it OK to use persistent TOPIC ? Or will it better to persist the message to the db table and then publish it as a non persistent message ... ? (But i guess the performance should be more or less the same in both of these approaches)
    C. Are there any other recommended design patterns for error recovery of JMS messages
    Please advise.
    Regards,
    Arif

    Thanks Tom !
    We may not be able to go with the approach of delaying/pausing redelivery of the messsage because
    1. Pausing entire MDB approach: Our MDB application consumes messages generated by different producers and our MDB needs to continue processing the messages even if messages corresponding to one producer is erroring out
    2. Redelivery delay : This would only delay the retry of an errored message. But there would still be a problem if the message fails during all retries (i.e redelivery limit count). We don't want to lose this message. In our case, It is possible that a particular message cannot be processed due to unavailability of a third party system for hours or may be a day.
    Basically, i am looking on approaches for a robust and performant error recovery/retry framework for our application (refer details in my first post on this thread) while fully making use of all features provided by middleware (WLS). Please advise.
    Regards,
    Arif

  • Oracle.jms.AQjmsException: Error creating the db_connection( OSB PS2.)

    hi All,
    I am beginner in OSB 11g. Please excuse me if I am asking any dumb question.
    I am trying to post messages to Oracle AQ by configuring JMS Destination in OSB Alert destination
    I have configured AQ JMS in weblogic 10.3.3 ( OSB PS2) following the blog (http://jianmingli.com/wp/?p=2950)
    When i invoked my proxy OSB proxy service i am getting following exception. Can you please help if i am missing any kind of setup while configuring the JMS Module.
    Caused By: oracle.jms.AQjmsException: Error creating the db_connection
         at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:625)
         at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
         at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.getSession(JmsOutboundMessageContext.java:399)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.newMessage(JmsOutboundMessageContext.java:621)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.setRequestMetaData(JmsOutboundMessageContext.java:229)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.access$100(JmsOutboundMessageContext.java:72)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:788)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:551)
         at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:680)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
         at $Proxy111.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:489)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
         at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
         at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:345)
         at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
         at com.bea.alsb.alert.pipeline.PipelineAlertManager.processAlert(PipelineAlertManager.java:59)
         at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:125)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:102)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
         at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
         at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
         at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
         at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
         at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
         at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
         at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
         at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
         at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)

    hi All,
    Here is the actual exception while posting message into AQ ( AQ JMS) from OSB.
    Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
    at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
    at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
    Not sure what is missing in my AQ JMS configuration. Please help.
    Regards,
    Nagi

  • XI protocol error occurred in abap proxy scenario- plz

    Scenario is asynchronous
    Http -> XI ->R/3(abap server proxy)
    sender: Through http client
    receiver is abap server proxy
    <u>Repository objects:</u>
    Sender: sender_DT, sender_MT, sender_MI(outbound asynchronous)
    Receiver: imported RFC from R/3 client 550, receiver_MI(which has message type refered to the imported RFC)
    Interface mapping: source=sender_MI, receiver_MI.
    Proxy generated on R/3 client 550 for receiver_MI.
    <u>Configuartion objects:</u>
    Sender: business service, no comm channel since http sender.
    receiver: R/3 business system
    Comm channel: receiver_cc type of XI.
    transport protocol: http
    message protocol : XI 3.0, since both XI and R/3 on webas 6.4
    addressing type: URL
    target host: diamond
    service number: 8005
    path: /sap/xi/engine?type=entry
    Authentiction data:
    user name: user22
    passwrod; correct
    logon client: 400 which is the same client I developed ll the design and config objects.
    Recevr determinaion, interface determination and recevr agrrement looks fine.
    The error iam getting is:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
      <SAP:P1>is.05.diamond</SAP:P1>
      <SAP:P2>IS</SAP:P2>
      <SAP:P3>XI</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>XI protocol error occurred</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    <b>
    Please reply , your help is appreciated.</b>
    Thanks
    KK

    Stefan thanks,
    I tried as you suggesetd putting the info of R/3 for
    server: diamond
    port: 8005
    client: 550
    user id: user05
    pwd: correct
    But I get the below error, suggest me what permission should this userid have?
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN"><html><head><title>Logon Error

  • Fatal two-task communication protocol error (when using  db link)

    I have created the db link betwen two databases of oracle version 9i 9.0.2
    the db link connects to specific user
    when i access the table with same name as user then recieve following message
    ORA-03106: fatal two-task communication protocol error
    when i access the other tables having different name that the user to which the db link connects
    that works alright
    so what is solution of problem in this particular case?

    What is your Oracle release? Is it 9.0.1.2 or 9.2.0?
    What version of Sql*Plus client are you using?

  • ORA-27023: skgfqsbi: media manager protocol error

    can some one please tell me what to do regarding this error, and how can i solve it. the result log is stated below...
    Recovery Manager: Release 10.2.0.1.0 - Production on Tue Oct 16 15:26:49 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN>
    connected to target database: MOT (DBID=2759813257)
    using target database control file instead of recovery catalog
    RMAN>
    echo set on
    RMAN> run {
    2> allocate channel oem_sbt_backup type 'sbt_tape' format '%U';
    3> backup as BACKUPSET current controlfile tag '10162007032648';
    4> restore controlfile validate from tag '10162007032648';
    5> release channel oem_sbt_backup;
    6> }
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on oem_sbt_backup channel at 10/16/2007 15:26:50
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_connect: Internal error - could not connect to obproxyd (Oracle Secure Backup error: 'bad port name specified (OB SBT proxy manager)').
    RMAN> allocate channel for maintenance type 'sbt_tape' ;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on ORA_MAINT_SBT_TAPE_1 channel at 10/16/2007 15:26:51
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_connect: Internal error - could not connect to obproxyd (Oracle Secure Backup error: 'bad port name specified (OB SBT proxy manager)').
    RMAN> delete noprompt backuppiece tag '10162007032648';
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=125 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 10/16/2007 15:26:51
    RMAN-06168: no backup pieces with this tag found: 10162007032648
    RMAN> exit;
    Recovery Manager complete.

    can some one please tell me what to do regarding this error, and how can i solve it. the result log is stated below...
    Recovery Manager: Release 10.2.0.1.0 - Production on Tue Oct 16 15:26:49 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN>
    connected to target database: MOT (DBID=2759813257)
    using target database control file instead of recovery catalog
    RMAN>
    echo set on
    RMAN> run {
    2> allocate channel oem_sbt_backup type 'sbt_tape' format '%U';
    3> backup as BACKUPSET current controlfile tag '10162007032648';
    4> restore controlfile validate from tag '10162007032648';
    5> release channel oem_sbt_backup;
    6> }
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on oem_sbt_backup channel at 10/16/2007 15:26:50
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_connect: Internal error - could not connect to obproxyd (Oracle Secure Backup error: 'bad port name specified (OB SBT proxy manager)').
    RMAN> allocate channel for maintenance type 'sbt_tape' ;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on ORA_MAINT_SBT_TAPE_1 channel at 10/16/2007 15:26:51
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_connect: Internal error - could not connect to obproxyd (Oracle Secure Backup error: 'bad port name specified (OB SBT proxy manager)').
    RMAN> delete noprompt backuppiece tag '10162007032648';
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=125 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 10/16/2007 15:26:51
    RMAN-06168: no backup pieces with this tag found: 10162007032648
    RMAN> exit;
    Recovery Manager complete.

  • Important!!! ldap_rename_s: Protocol error with ldapmoddn

    When I use "ldapmoddn" to move a user in Active Directory, I have the error:
    "ldap_rename_s: Protocol error
    ldap_rename_s: additional info: 00000057: LdapErr: DSID-0C09080A, comment: Error in attribute conversion operation, data 0, v893"
    And the command line is:
    ldapmoddn -p 389 -h 190.57.160.24 -D "CN=administrateur,CN=USERS,DC=xxx,DC=org" -w taaze -b "CN=a,OU=test,dc=xxx,dc=org" -N "dc=xxx,dc=org"
    But the user have minimum information...
    It's very important for me because it's for my training periode to validate my master!!
    Thanks you very much...

    If I use only the -N option without -R option
    ex:ldapmoddn -p 389 -h 190.57.160.24 -D "CN=administrateur,CN=USERS,DC=xxx,DC=org" -w xxx -b "CN=a,OU=test,dc=xxx,dc=org" -N "dc=xxx,dc=org"
    I have this error:
    "ldap_rename_s: Protocol error
    ldap_rename_s: additional info: 00000057: LdapErr: DSID-0C09080A, comment: Error in attribute conversion operation, data 0, v893"
    Can you help me please?????
    Matthieu

  • TT12241: Backup stream protocol error

    Hi there,
    I get the following error when replicating TT 6.04 datastore:
    $ /data/TimesTen/6.04/bin/ttRepAdmin -duplicate -from UsageCollector -host NODE_B -setMasterRepStart -delXla -localhost NODE_A UsageCollector
    TT12241: Backup stream protocol error: bad log data packet length -- file "restore.c", lineno 2865, procedure "restoreLogFileNS"
    Unfortunately this error, TT12241, is not described in the documentation. Oracle Support and Google searches don’t return any relevant information.
    Have any one came across this problem before?
    Thanks,
    Igor

    I can't find any previous SR reports of the TT12241. No probable candidate bugs are returned either. However I have not seen the -delXla option being used before, so it may have something to do with using this option. Are you able to exclude this option from the ttRepAdmin -duplicate, and allow the bookmarks to be copied over? You could then connect to the newly created datastore and try to manually delete the bookmarks using "xladeletebookmark".

  • RosettaNet Protocol error

    Hi All,
    Here is the scenario. Trading Partner (TP) A is sending a RosettaNet business
    message (PIP3A2) to TP B. When the weblogic Integration server for TP B receives
    this message, I get the following error message,
    ####<Dec 4, 2001 4:00:33 PM PST> <Error> <B2B> <erpsystem> <myserver> <ExecuteThread:
    '9' for queue: 'default'> <> <19:c285badb981bb8b8> <000000> <<RN-Protocol> ERROR:
    Cannot locate CA for URI http://localhost:7001/Quantum, Business Identifier 987654321,
    Role Product Supplier, in Coversation 3A2, version 1.3.>
    It is referring to Conversation 3A2 eventough it has been deleted and should be
    using the Conversation called PIP3A2. Can anyone tell me where and how this conversation
    is referenced and how it can be fixed?
    --Krish.

    Hi All,
    Here is the scenario. Trading Partner (TP) A is sending a RosettaNet business
    message (PIP3A2) to TP B. When the weblogic Integration server for TP B receives
    this message, I get the following error message,
    ####<Dec 4, 2001 4:00:33 PM PST> <Error> <B2B> <erpsystem> <myserver> <ExecuteThread:
    '9' for queue: 'default'> <> <19:c285badb981bb8b8> <000000> <<RN-Protocol> ERROR:
    Cannot locate CA for URI http://localhost:7001/Quantum, Business Identifier 987654321,
    Role Product Supplier, in Coversation 3A2, version 1.3.>
    It is referring to Conversation 3A2 eventough it has been deleted and should be
    using the Conversation called PIP3A2. Can anyone tell me where and how this conversation
    is referenced and how it can be fixed?
    --Krish.

  • Net8 protocol error

    I'm currently upgrading from Weblogic 8.1 to Weblogic 9.1 on a Windows environment (Windows XP on my dev box) with an Oracle 8.1.6 database.
    During the upgrade, we switched from BEA's Oracle OCI driver ( weblogic.jdbc.oci.Driver ) in Weblogic 8.1 to their Type 4 JDBC driver in Weblogic 9.1 which resulted in a "Net8 protocol error".
    Does anybody know what's causing this error and how to resolve this?
    Thanks
    Stack trace:
    ####<16-Jun-2006 9:37:35 o'clock AM PDT> <Error> <HTTP> <HY119402> <HY119402.CM-Fleet-Admin> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1150475855789> <BEA-101020> <[weblogic.servlet.internal.WebAppServletContext@681e45 - name: 'CMWeb', context-path: '/CMWeb'] Servlet failed with Exception
    com.abs.cmweb.main.MainRuntimeException: CMWeb: INTERNAL RUNTIME EXCEPTION: EJB Exception: ; nested exception is:
         com.westech.jade.service.entity.EntityRuntimeException: INTERNAL RUNTIME EXCEPTION: INTERNAL RUNTIME EXCEPTION: <b>[BEA][Oracle JDBC Driver]Internal error: Net8 protocol error.SQL Failed</b>: SELECT OID, BOUNDARY_NAME, USER_ID, PREFERENCE_VALUE FROM CMWEB_BOUNDARY_PREFERENCE WHERE BOUNDARY_NAME = ? AND USER_ID = ?
         at com.abs.cmweb.main.control.boundaryUserPreferenceController.BoundaryUserPreferenceControllerRIProxy.findBoundaryUserPreference(BoundaryUserPreferenceControllerRIProxy.java:148)
         at com.abs.cmweb.main.util.boundaryUserPreferenceHelper.BoundaryUserPreferenceHelper.getBoundaryUserPreference(BoundaryUserPreferenceHelper.java:50)
         at com.abs.cmweb.waterConveyance.boundary.viewingWCInstructionsAndImplementations.ViewingWCInstructionsAndImplementationsUseBean.applyUserPreference(ViewingWCInstructionsAndImplementationsUseBean.java:275)
         at com.abs.cmweb.waterConveyance.boundary.viewingWCInstructionsAndImplementations.ViewingWCInstructionsAndImplementationsUseBean.processBoundaryEvent(ViewingWCInstructionsAndImplementationsUseBean.java:179)
         at com.abs.cmweb.waterConveyance.boundary.viewingWCInstructionsAndImplementations.ViewingWCInstructionsAndImplementationsFromHomeUseBean.processBoundaryEvent(ViewingWCInstructionsAndImplementationsFromHomeUseBean.java:32)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.fireEvent(HtmlBoundaryController.java:1303)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processHtmlBoundaryAction(HtmlBoundaryController.java:337)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processHttpServletRequest(HtmlBoundaryController.java:255)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processRequestResponse(HtmlBoundaryController.java:152)
         at jsp_servlet._waterconveyance._viewingwchome.__viewingwchome._jspService(__viewingwchome.java:329)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:380)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:298)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:496)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.doForward(HtmlBoundaryController.java:833)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.doForward(HtmlBoundaryController.java:966)
         at com.abs.cmweb.main.boundary.navigatingCMWeb.NavigatingCMWebUseBean.doRedirectToBoundary(NavigatingCMWebUseBean.java:290)
         at com.abs.cmweb.main.boundary.navigatingCMWeb.NavigatingCMWebUseBean.processBoundaryEvent(NavigatingCMWebUseBean.java:234)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.fireEvent(HtmlBoundaryController.java:1303)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processHtmlBoundaryAction(HtmlBoundaryController.java:337)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processHttpServletRequest(HtmlBoundaryController.java:255)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processRequestResponse(HtmlBoundaryController.java:152)
         at jsp_servlet._main._viewingcmwebhome.__navigatingcmweb._jspService(__navigatingcmweb.java:470)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:496)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:426)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:152)
         at jsp_servlet._main._viewingapplicationmessages.__viewingapplicationmessages._jspService(__viewingapplicationmessages.java:298)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

    Doug Chew wrote:
    I'm currently upgrading from Weblogic 8.1 to Weblogic 9.1 on a Windows environment (Windows XP on my dev box) with an Oracle 8.1.6 database.
    During the upgrade, we switched from BEA's Oracle OCI driver ( weblogic.jdbc.oci.Driver ) in Weblogic 8.1 to their Type 4 JDBC driver in Weblogic 9.1 which resulted in a "Net8 protocol error".
    Does anybody know what's causing this error and how to resolve this?
    ThanksHi, yes. Our old, deprecated and now removed type-2 driver used OCI (whatever version
    you have installed) to talk to Oracle. Our new drivers use the wire-level protocol for
    all supported DBMS versions. Oracle 8.1.6 is extremely old. I don't think it's even
    supported by Oracle anymore, is it? I think you have two options:
    1 - Try using Oracle's driver, in the type-2 mode so it also uses OCI.
    2 - If (1) doesn't work, you probably have to upgrade your DBMS.
    Joe
    >
    >
    Stack trace:
    ####<16-Jun-2006 9:37:35 o'clock AM PDT> <Error> <HTTP> <HY119402> <HY119402.CM-Fleet-Admin> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1150475855789> <BEA-101020> <[weblogic.servlet.internal.WebAppServletContext@681e45 - name: 'CMWeb', context-path: '/CMWeb'] Servlet failed with Exception
    com.abs.cmweb.main.MainRuntimeException: CMWeb: INTERNAL RUNTIME EXCEPTION: EJB Exception: ; nested exception is:
         com.westech.jade.service.entity.EntityRuntimeException: INTERNAL RUNTIME EXCEPTION: INTERNAL RUNTIME EXCEPTION: <b>[BEA][Oracle JDBC Driver]Internal error: Net8 protocol error.SQL Failed</b>: SELECT OID, BOUNDARY_NAME, USER_ID, PREFERENCE_VALUE FROM CMWEB_BOUNDARY_PREFERENCE WHERE BOUNDARY_NAME = ? AND USER_ID = ?
         at com.abs.cmweb.main.control.boundaryUserPreferenceController.BoundaryUserPreferenceControllerRIProxy.findBoundaryUserPreference(BoundaryUserPreferenceControllerRIProxy.java:148)
         at com.abs.cmweb.main.util.boundaryUserPreferenceHelper.BoundaryUserPreferenceHelper.getBoundaryUserPreference(BoundaryUserPreferenceHelper.java:50)
         at com.abs.cmweb.waterConveyance.boundary.viewingWCInstructionsAndImplementations.ViewingWCInstructionsAndImplementationsUseBean.applyUserPreference(ViewingWCInstructionsAndImplementationsUseBean.java:275)
         at com.abs.cmweb.waterConveyance.boundary.viewingWCInstructionsAndImplementations.ViewingWCInstructionsAndImplementationsUseBean.processBoundaryEvent(ViewingWCInstructionsAndImplementationsUseBean.java:179)
         at com.abs.cmweb.waterConveyance.boundary.viewingWCInstructionsAndImplementations.ViewingWCInstructionsAndImplementationsFromHomeUseBean.processBoundaryEvent(ViewingWCInstructionsAndImplementationsFromHomeUseBean.java:32)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.fireEvent(HtmlBoundaryController.java:1303)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processHtmlBoundaryAction(HtmlBoundaryController.java:337)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processHttpServletRequest(HtmlBoundaryController.java:255)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processRequestResponse(HtmlBoundaryController.java:152)
         at jsp_servlet._waterconveyance._viewingwchome.__viewingwchome._jspService(__viewingwchome.java:329)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:380)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:298)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:496)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.doForward(HtmlBoundaryController.java:833)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.doForward(HtmlBoundaryController.java:966)
         at com.abs.cmweb.main.boundary.navigatingCMWeb.NavigatingCMWebUseBean.doRedirectToBoundary(NavigatingCMWebUseBean.java:290)
         at com.abs.cmweb.main.boundary.navigatingCMWeb.NavigatingCMWebUseBean.processBoundaryEvent(NavigatingCMWebUseBean.java:234)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.fireEvent(HtmlBoundaryController.java:1303)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processHtmlBoundaryAction(HtmlBoundaryController.java:337)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processHttpServletRequest(HtmlBoundaryController.java:255)
         at com.westech.jade.service.boundary.html.HtmlBoundaryController.processRequestResponse(HtmlBoundaryController.java:152)
         at jsp_servlet._main._viewingcmwebhome.__navigatingcmweb._jspService(__navigatingcmweb.java:470)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:496)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:426)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:152)
         at jsp_servlet._main._viewingapplicationmessages.__viewingapplicationmessages._jspService(__viewingapplicationmessages.java:298)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

  • ORA-12560-TNS PROTOCOL ERROR

    SIR,
    i hadbeen installed oracle aplication server.but i m not connecting to database.when i use the sql*plus.i use the user name-scott &password-tiger.i got an error ORA-12560=TNS PROTOCOL ERROR.
    I M NOT ABLE TO RECTIFY ITS PROBLEM,how can i create host string in oracle application server 10g.please send reply its very urgent.
    thanx ranjeet

    Although this question is completely off topic of the Personalization you can learn how to configure the SQL*Net connect from the manual by reading the topic "Configure the Client to Use a Net Service Name" found at the following link:
    http://download-west.oracle.com/docs/cd/A91202_01/901_doc/network.901/a90154/gettings.htm#483215

  • JMS adapter error in MQSeries connection

    Dear All,
    i am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
    Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
         at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
         at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
    com.ibm.mq.MQException:  Message catalog not found
         at com.ibm.mq.MQManagedConnectionJ11.&lt;init&gt;(MQManagedConnectionJ11.java:171)
         at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
    i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
    i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
    So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
    Thanks and Regards,
    Rajeev Gupta
    Edited by: RAJEEV GUPTA on Jan 29, 2008 2:32 PM
    Edited by: RAJEEV GUPTA on Jan 29, 2008 2:39 PM

    Hi,
    Check this as well [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fjm35210_.htm]
    Regards,
    Venkata S Pagolu

Maybe you are looking for