JMS... Anyone :-)

The Scenario: JMS (MQ) --> XI --> JMS (MQ)
On our current project we have many scenarios which deal with the JMS Adapter.
Namely we are talking about MQ Series.
Now the question is the following in many scenarios we receive files from the MQ Series Queue and they have a specific file name.
How do we insure that when these messages are then routed through the XI pipeline and sent back into an MQ Series Queue using the JMS Adapter that the Original File Names Remain?
I know with a file adapter you can use adapter specific message attribute --> File name to achieve this, but it there something similar with the JMS Adapter or is it automatic.
As I can see there is nothing anywhere in the receiver or sender comm channel for that fact that allows you to determine a File Name.

please visit the link
/people/kan.th/blog/2007/02/05/exploring-jms-and-sap-xi-jms-adaper
J2SE Adapter Engine / JMS Adapter
http://help.sap.com/saphelp_nw04s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
JMS receiver adapter file content conversion issue
Jms to File

Similar Messages

  • Good Java System Directory Server book?

    Does anyone know of a good book (or books) for getting up to speed on the Sun Java System stack? I am migrating from Linux and Windows-based apps to the Sun stack and need to hit the books hard to get up to speed, but can't find much of anything newer than 2002 on Amazon.
    Specifically looking for:
    - Directory Server
    - Web Application server
    - Messaging Server
    - JMS
    Anyone have any ideas?

    Well, the first place I go is http://docs.sun.com where I can either search or browse the html versions or download the PDFs of the product manuals. Beyond that I do like Michael Haines and Tom Bialaski's LDAP in the Solaris Operating Environment: Deploying Secure Directory Services book. It came out in 2004 and covers Directory Server 5.2 (I think it was patch 2 then, now we run patch 4 here...)

  • Configuring JMS and loadbalancer with SSL termination? Has Anyone done it?

    Hi all,
    I'm having a problem getting JMS or even any JNDI lookup to work with a hardware load balancer and SSL termination. Has anyone used such a configuration? The load balancer in question is a Cisco CSS 11500 Series which has an SSL module. A client communicates with the CSS over SSL, the SSL module decrypts the packets and sends it for content switching and on to WebLogic as cleartext.
    Without SSL termination everthing works fine. With SSL termination active, Web service and web content all work fine, but I can't get SSL tGetting Initial context from ms01
    <29-Sep-2006 16:07:22 o'clock IST> <Debug> <TLS> <000000> <SSL/Domestic license found>
    <29-Sep-2006 16:07:22 o'clock IST> <Debug> <TLS> <000000> <Not in server, Certicom SSL license found>
    <29-Sep-2006 16:07:23 o'clock IST> <Debug> <TLS> <000000> <SSL Session TTL :90000>
    <29-Sep-2006 16:07:23 o'clock IST> <Debug> <TLS> <000000> <Trusted CA keystore: D:/eclipse/workspace/LoadBalancerTest/ssl/keystores/cssKeyS
    ore.keystore>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <Filtering JSSE SSLSocket>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <SSLIOContextTable.addContext(ctx): 886220>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <SSLSocket will NOT be Muxing>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <write SSL_20_RECORD>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <3941240 SSL3/TLS MAC>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <3941240 received HANDSHAKE>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: ServerHello>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <3941240 SSL3/TLS MAC>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <3941240 received HANDSHAKE>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: Certificate>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <validationCallback: validateErr = 0>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> < cert[0] = [
    Version: V3
    Subject: EMAILADDRESS="[email protected] ", CN=10.51.0.200, OU=Web Administration, O=Revenue Commissioners, L=Dublin, ST=Dublin,
    =IE
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: SunJSSE RSA public key:
    public exponent:
    010001
    modulus:
    a8f60248 b87c5860 229b9044 a666a9ae 27eb488c 424d9e67 e7b9d6d0 c292f081
    cfa76c04 f3d89b28 1bf544f9 5de2b66d 576ebeca 5dc5ca8a fceead9a 52e2ce6c
    2b91afef e4da5071 49b8784c 12d7f5f3 99f76482 79efe1d8 0a24f664 4c8d6e9e
    b0bc63be 1faf8319 eeb23e8a 019b65b2 59dd086d 1b714d4c 01618804 66f416bb
    Validity: [From: Fri Sep 08 11:44:28 BST 2006,
                   To: Mon Sep 05 11:44:28 BST 2016]
    Issuer: CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE
    SerialNumber: [    0131]
    Certificate Extensions: 4
    [1]: ObjectId: 2.16.840.1.113730.1.13 Criticality=false
    Extension unknown: DER encoded OCTET string =
    0000: 04 1F 16 1D 4F 70 65 6E 53 53 4C 20 47 65 6E 65 ....OpenSSL Gene
    0010: 72 61 74 65 64 20 43 65 72 74 69 66 69 63 61 74 rated Certificat
    0020: 65 e
    [2]: ObjectId: 2.5.29.14 Criticality=false
    SubjectKeyIdentifier [
    KeyIdentifier [
    0000: 0E 6E 72 2E B1 3B B6 A3 59 79 5A C5 41 26 B7 B6 .nr..;..YyZ.A&..
    0010: A2 39 4C 73 .9Ls
    [3]: ObjectId: 2.5.29.35 Criticality=false
    AuthorityKeyIdentifier [
    KeyIdentifier [
    0000: D2 66 DD FC 06 C2 BC 7E 18 D5 64 38 AD 6E D0 0A .f........d8.n..
    0010: AA 97 05 0D ....
    [CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE]
    SerialNumber: [    00]
    [4]: ObjectId: 2.5.29.19 Criticality=false
    BasicConstraints:[
    CA:false
    PathLen: undefined
    Algorithm: [MD5withRSA]
    Signature:
    0000: 2C A0 0C 34 4E 0D CA 24 A5 C3 03 3A 71 A1 2D D3 ,..4N..$...:q.-.
    0010: 65 A2 FA EF C1 5D D4 4A 28 8C 1A 70 5F 92 73 5E e....].J(..p_.s^
    0020: 7B 13 D4 AE 36 A8 86 EA 60 7F A5 E3 86 6E 84 1F ....6...`....n..
    0030: 5E 5F 30 06 B4 AA 2E 5C A7 65 74 32 09 0A 91 14 ^_0....\.et2....
    ]>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> < cert[1] = [
    Version: V3
    Subject: CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: SunJSSE RSA public key:
    public exponent:
    010001
    modulus:
    bc61b29f a830c97a 7a76883e 1665a241 a68b891f 8e4167eb 62e578ac 9e342c3e
    53c9de8b e756634b e364010f 4d36c1c5 21a65b37 b64b4861 6f4dda29 b932191f
    Validity: [From: Mon May 31 15:22:15 BST 2004,
                   To: Thu May 29 15:22:15 BST 2014]
    Issuer: CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE
    SerialNumber: [    00]
    Certificate Extensions: 3
    [1]: ObjectId: 2.5.29.14 Criticality=false
    SubjectKeyIdentifier [
    KeyIdentifier [
    0000: D2 66 DD FC 06 C2 BC 7E 18 D5 64 38 AD 6E D0 0A .f........d8.n..
    0010: AA 97 05 0D ....
    [2]: ObjectId: 2.5.29.35 Criticality=false
    AuthorityKeyIdentifier [
    KeyIdentifier [
    0000: D2 66 DD FC 06 C2 BC 7E 18 D5 64 38 AD 6E D0 0A .f........d8.n..
    0010: AA 97 05 0D ....
    [CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE]
    SerialNumber: [    00]
    [3]: ObjectId: 2.5.29.19 Criticality=true
    BasicConstraints:[
    CA:true
    PathLen:2147483647
    Algorithm: [MD5withRSA]
    Signature:
    0000: 3C 64 7C 9E 0B 90 48 9D 70 74 06 80 7F 2C AF 73 <d....H.pt...,.s
    0010: 92 1C C3 39 DD C3 45 B6 A4 8E 11 27 8E 21 18 4B ...9..E....'.!.K
    0020: FD AA 31 5E 35 FC DF 9E 70 42 F4 65 5C DF 56 9A ..1^5...pB.e\.V.
    0030: DD 8C 6B B7 3B BE E5 A7 D5 4A 16 23 C1 91 07 CA ..k.;....J.#....
    ]>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <SSLTrustValidator returns: 0>
    <29-Sep-2006 16:07:24 o'clock IST> <Debug> <TLS> <000000> <Trust status (0): NONE>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <Performing hostname validation checks: 10.51.0.200>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <3941240 SSL3/TLS MAC>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <3941240 received HANDSHAKE>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: ServerHelloDone>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 134>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <write CHANGE_CIPHER_SPEC, offset = 0, length = 1>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 16>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <3941240 SSL3/TLS MAC>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <3941240 received CHANGE_CIPHER_SPEC>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <3941240 SSL3/TLS MAC>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <3941240 received HANDSHAKE>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: Finished>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 0>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 272>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <3445873 read(offset=0, length=2048)>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3941240 SSL3/TLS MAC>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3941240 received APPLICATION_DATA: databufferLen 0, contentLength 372>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3445873 read databufferLen 372>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3445873 read A returns 372>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 0>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 339>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3445873 read(offset=372, length=1676)>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <Filtering JSSE SSLSocket>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLIOContextTable.addContext(ctx): 6771926>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLSocket will NOT be Muxing>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 93>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3840954 SSL3/TLS MAC>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3840954 received HANDSHAKE>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: ServerHello>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3840954 SSL3/TLS MAC>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3840954 received CHANGE_CIPHER_SPEC>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3840954 SSL3/TLS MAC>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3840954 received HANDSHAKE>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: Finished>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write CHANGE_CIPHER_SPEC, offset = 0, length = 1>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 16>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 0>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 402>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 0>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 1707>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <23328673 read(offset=0, length=2048)>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3840954 SSL3/TLS MAC>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <3840954 received APPLICATION_DATA: databufferLen 0, contentLength 174>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <23328673 read databufferLen 174>
    <29-Sep-2006 16:07:29 o'clock IST> <Debug> <TLS> <000000> <23328673 read A returns 174>
    <29-Sep-2006 16:07:44 o'clock IST> <Debug> <TLS> <000000> <NEW ALERT with Severity: WARNING, Type: 0
    java.lang.Exception: New alert stack
    at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
    at javax.net.ssl.impl.SSLSocketImpl.close(Unknown Source)
    at weblogic.net.http.HttpClient.closeServer(HttpClient.java:466)
    at weblogic.net.http.KeepAliveCache$1.run(KeepAliveCache.java:120)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)
    >
    <29-Sep-2006 16:07:44 o'clock IST> <Debug> <TLS> <000000> <avalable(): 23328673 : 0 + 0 = 0>
    <29-Sep-2006 16:07:44 o'clock IST> <Debug> <TLS> <000000> <write ALERT, offset = 0, length = 2>
    <29-Sep-2006 16:07:44 o'clock IST> <Debug> <TLS> <000000> <SSLIOContextTable.removeContext(ctx): 6771926>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <3941240 SSL3/TLS MAC>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <3941240 received APPLICATION_DATA: databufferLen 0, contentLength 98>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <3445873 read databufferLen 98>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <3445873 read A returns 98>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <Filtering JSSE SSLSocket>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLIOContextTable.addContext(ctx): 8406772>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLSocket will NOT be Muxing>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 93>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <21830977 SSL3/TLS MAC>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <21830977 received HANDSHAKE>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: ServerHello>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <21830977 SSL3/TLS MAC>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <21830977 received CHANGE_CIPHER_SPEC>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <21830977 SSL3/TLS MAC>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <21830977 received HANDSHAKE>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: Finished>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <write CHANGE_CIPHER_SPEC, offset = 0, length = 1>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 16>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 0>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 339>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <5618579 read(offset=0, length=2048)>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:08:13 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    Exception in thread "main" javax.naming.CommunicationException [Root exception is java.net.ConnectException: https://10.51.0.200:8143: Boot
    trap to: 10.51.0.200/10.51.0.200:8143' over: 'https' got an error or timed out]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:636)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.init(Unknown Source)
    at javax.naming.InitialContext.<init>(Unknown Source)
    at TestAllManagedServers.main(TestAllManagedServers.java:54)
    Caused by: java.net.ConnectException: https://10.51.0.200:8143: Bootstrap to: 10.51.0.200/10.51.0.200:8143' over: 'https' got an error or t
    med out
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:200)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
    ... 7 more
    o work for a simple JNDI lookup. With SSL debugging turned on, the following output is given:
    When I compare the Server HTTP logs I see that an initial context lookup involves 3 HTTP requests, e.g.
    25.2.1.210 - - [29/Sep/2006:16:29:12 +0100] "GET /bea_wls_internal/HTTPClntLogin/a.tun?wl-login=https+dummy+WLREQS+8.1.5+dummy+%0A&r
    and=3018901804201457976&AS=255&HL=19 HTTP/1.1" 200 17
    25.2.1.210 - - [29/Sep/2006:16:29:12 +0100] "GET /bea_wls_internal/HTTPClntRecv/a.tun?connectionID=0&rand=7332722597180897050 HTTP/1
    .1" 200 2341
    25.2.1.210 - - [29/Sep/2006:16:29:12 +0100] "POST /bea_wls_internal/HTTPClntSend/a.tun?connectionID=0&rand=3415396992694182025 HTTP/
    1.1" 200 17
    When my request goes through the load balancer I see the following in the HTTP logs:
    10.51.0.200 - - [29/Sep/2006:16:31:33 +0100] "GET /bea_wls_internal/HTTPClntLogin/a.tun?wl-login=https+dummy+WLREQS+8.1.5+dummy+%0A&
    rand=8279752507152372405&AS=255&HL=19 HTTP/1.1" 200 17
    10.51.0.200 - - [29/Sep/2006:16:31:33 +0100] "POST /bea_wls_internal/HTTPClntSend/a.tun?connectionID=0&rand=1051450669479197885 HTTP
    /1.1" 200 17
    10.51.0.200 - - [29/Sep/2006:16:32:28 +0100] "GET /bea_wls_internal/HTTPClntRecv/a.tun?connectionID=0&rand=6035654607615870287 HTTP/
    1.1" 200 5
    10.51.0.200 - - [29/Sep/2006:16:33:13 +0100] "GET /bea_wls_internal/HTTPClntRecv/a.tun?connectionID=0&rand=8245112057388607005 HTTP/
    1.1" 200 5
    Notice the time delay in some of the messages.
    The following error appears in the WebLogic server log, however I've verified that all IP addresses referenced by the load balancer configuration match those in the WebLogic configuration:
    <29-Sep-2006 16:31:43 o'clock IST> <Error> <RJVM> <BEA-000572> <The server rejected a connection attempt JVMMessage from: '266014296
    868812899C:25.2.1.210R:2462711729186814398S:10.51.0.2:[8113,8113,8114,8114,8113,8114,-1,0,0]:10.51.0.1:8103,10.51.0.1:8105,10.51.0.1
    :8107,10.51.0.2:8109,10.51.0.2:8111,10.51.0.2:8113:risIntCluster01:ms06' to: '0S:10.51.0.200:[-1,-1,-1,8143,-1,-1,-1,-1,-1]' cmd: 'C
    MD_IDENTIFY_REQUEST', QOS: '102', responseId: '0', invokableId: '0', flags: 'JVMIDs Sent, TX Context Not Sent', abbrev offset: '228'
    probably due to an incorrect firewall configuration or admin command.>
    When a JNDI lookup is made directly to a WebLogic server on the https port, the client gives the following output:
    Getting Initial context from ms01
    <29-Sep-2006 16:29:22 o'clock IST> <Debug> <TLS> <000000> <SSL/Domestic license found>
    <29-Sep-2006 16:29:22 o'clock IST> <Debug> <TLS> <000000> <Not in server, Certicom SSL license found>
    <29-Sep-2006 16:29:23 o'clock IST> <Debug> <TLS> <000000> <SSL Session TTL :90000>
    <29-Sep-2006 16:29:23 o'clock IST> <Debug> <TLS> <000000> <Trusted CA keystore: D:/eclipse/workspace/LoadBalancerTest/ssl/keystores/cssKeySt
    ore.keystore>
    <29-Sep-2006 16:29:23 o'clock IST> <Debug> <TLS> <000000> <Filtering JSSE SSLSocket>
    <29-Sep-2006 16:29:23 o'clock IST> <Debug> <TLS> <000000> <SSLIOContextTable.addContext(ctx): 7860099>
    <29-Sep-2006 16:29:23 o'clock IST> <Debug> <TLS> <000000> <SSLSocket will NOT be Muxing>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <write SSL_20_RECORD>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <32915800 SSL3/TLS MAC>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <32915800 received HANDSHAKE>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: ServerHello>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <32915800 SSL3/TLS MAC>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <32915800 received HANDSHAKE>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: Certificate>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <validationCallback: validateErr = 0>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> < cert[0] = [
    Version: V3
    Subject: CN=10.52.0.3, OU=Revenue Integration Server, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: SunJSSE RSA public key:
    public exponent:
    010001
    modulus:
    ac47cae5 45e55fe4 8ec06362 84aab923 af35d7f1 8b7e8aaa 32772d8a d8185106
    0ba91363 07162207 6eaa33b4 db8a3fbb 1e228e93 841ff322 e319242a 04ae7447
    Validity: [From: Mon May 31 16:45:21 BST 2004,
                   To: Thu May 29 16:45:21 BST 2014]
    Issuer: CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE
    SerialNumber: [    05]
    Certificate Extensions: 4
    [1]: ObjectId: 2.16.840.1.113730.1.13 Criticality=false
    Extension unknown: DER encoded OCTET string =
    0000: 04 1F 16 1D 4F 70 65 6E 53 53 4C 20 47 65 6E 65 ....OpenSSL Gene
    0010: 72 61 74 65 64 20 43 65 72 74 69 66 69 63 61 74 rated Certificat
    0020: 65 e
    [2]: ObjectId: 2.5.29.14 Criticality=false
    SubjectKeyIdentifier [
    KeyIdentifier [
    0000: D7 B3 92 7B C7 4E 2F 5D F3 97 CB 3B F9 FB 0A 1E .....N/]...;....
    0010: 97 C5 DD F1 ....
    [3]: ObjectId: 2.5.29.35 Criticality=false
    AuthorityKeyIdentifier [
    KeyIdentifier [
    0000: D2 66 DD FC 06 C2 BC 7E 18 D5 64 38 AD 6E D0 0A .f........d8.n..
    0010: AA 97 05 0D ....
    [CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE]
    SerialNumber: [    00]
    [4]: ObjectId: 2.5.29.19 Criticality=false
    BasicConstraints:[
    CA:false
    PathLen: undefined
    Algorithm: [MD5withRSA]
    Signature:
    0000: 57 B6 54 4E 1A 54 91 66 5C A8 FE AF B6 50 AB 23 W.TN.T.f\....P.#
    0010: 6A 32 42 77 06 44 D5 7D 40 81 E4 DD 84 E3 7B 55 [email protected]
    0020: 96 A6 BC E9 E9 51 96 B9 E4 01 56 F9 41 B7 0C C3 .....Q....V.A...
    0030: 0A 92 C0 17 6E 6B 9D D6 9A 87 6D 6E 15 5A 86 F4 ....nk....mn.Z..
    ]>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> < cert[1] = [
    Version: V3
    Subject: CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: SunJSSE RSA public key:
    public exponent:
    010001
    modulus:
    bc61b29f a830c97a 7a76883e 1665a241 a68b891f 8e4167eb 62e578ac 9e342c3e
    53c9de8b e756634b e364010f 4d36c1c5 21a65b37 b64b4861 6f4dda29 b932191f
    Validity: [From: Mon May 31 15:22:15 BST 2004,
                   To: Thu May 29 15:22:15 BST 2014]
    Issuer: CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE
    SerialNumber: [    00]
    Certificate Extensions: 3
    [1]: ObjectId: 2.5.29.14 Criticality=false
    SubjectKeyIdentifier [
    KeyIdentifier [
    0000: D2 66 DD FC 06 C2 BC 7E 18 D5 64 38 AD 6E D0 0A .f........d8.n..
    0010: AA 97 05 0D ....
    [2]: ObjectId: 2.5.29.35 Criticality=false
    AuthorityKeyIdentifier [
    KeyIdentifier [
    0000: D2 66 DD FC 06 C2 BC 7E 18 D5 64 38 AD 6E D0 0A .f........d8.n..
    0010: AA 97 05 0D ....
    [CN=Revenue CA, OU=Revenue Certificate Authority, O=Office Of The Revenue Commissioners, L=Dublin, ST=Dublin, C=IE]
    SerialNumber: [    00]
    [3]: ObjectId: 2.5.29.19 Criticality=true
    BasicConstraints:[
    CA:true
    PathLen:2147483647
    Algorithm: [MD5withRSA]
    Signature:
    0000: 3C 64 7C 9E 0B 90 48 9D 70 74 06 80 7F 2C AF 73 <d....H.pt...,.s
    0010: 92 1C C3 39 DD C3 45 B6 A4 8E 11 27 8E 21 18 4B ...9..E....'.!.K
    0020: FD AA 31 5E 35 FC DF 9E 70 42 F4 65 5C DF 56 9A ..1^5...pB.e\.V.
    0030: DD 8C 6B B7 3B BE E5 A7 D5 4A 16 23 C1 91 07 CA ..k.;....J.#....
    ]>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <SSLTrustValidator returns: 0>
    <29-Sep-2006 16:29:24 o'clock IST> <Debug> <TLS> <000000> <Trust status (0): NONE>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <Performing hostname validation checks: 10.51.0.1>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <32915800 SSL3/TLS MAC>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <32915800 received HANDSHAKE>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: ServerHelloDone>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 70>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <write CHANGE_CIPHER_SPEC, offset = 0, length = 1>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 16>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <32915800 SSL3/TLS MAC>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <32915800 received CHANGE_CIPHER_SPEC>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <32915800 SSL3/TLS MAC>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <32915800 received HANDSHAKE>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: Finished>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 0>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <write APPLICATION_DATA, offset = 0, length = 270>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <30340343 read(offset=0, length=2048)>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TLS> <000000> <32915800 SSL3/TLS MAC>
    <29-Sep-2006 16:29:28 o'clock IST> <Debug> <TL

    You will need an AAM set with the internal (http) address.
    http://blogs.msdn.com/b/ajithas/archive/2009/09/11/alternate-access-mapping-in-reverse-proxy-configuration.aspx
    Dimitri Ayrapetov (MCSE: SharePoint)

  • Anyone successfully deployed BPEL + JMS Adapter (for MQ) to WebSphere?

    Anyone successfully deployed BPEL Process Manager + JMS Adapter (for MQ) to WebSphere (i.e not OAS/OC4J)?
    If you have - I would love to see a valid example of the ra.xml and oc4j-ra.xml files in your jca/JmsAdapter.rar file - to see how you configured access for the JMS Adapter to your remote MQ queues.
    Thank you
    Dennis

    Hi Garima,
    Please check the following:
    1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
    2. Check the existence of your JMS drivers.
    3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
    https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
    Any of the above solutions should help you solve the problem.
    Regards,
    Abhy

  • How to create OEMS JMS In-Memory and File-Based Persistence ? Anyone?

    Anyone knows how to create OEMS JMS In-Memory and File-Based Persistence? Any help it is appreciated. I m working with Oracle BAM 11g TP4 and I want to test the capability of connecting directly to a JMS queue, and reading Oracle´s "complex" documentation I couldnt find the right way to make this happen.
    tks

    Hi Mario
    This is explained in the soa developer's guide. Chapter 43 "Enterprise message source"should help you. You will find how to connect OEMS or JMS in-memory/file based to your BAM data objects with or without xpath transformation.
    You can find sample of advanced XML formating in the 10g tech note: "Oracle BAM 10.1.3 configuration for BPEL 10.1.2 using JMS sensors" (useful even if you don't plan to use BPEL).
    Anyway, if you plan to use BPEL, forget JMS and use the BAM adapter (chapter 42), it's quicker & easier.
    Dominique

  • JMS over MQ : could anyone recommend resources / advanced tutorials ?

    Hi,
    Would anyone please happen to have good resources for using JMS over Ibm's MQ implementation ?
    I've just started using JMS over MQ.
    I've read through 3 IBM redbooks on the subject, copied their "hello world" examples, and they basically work.
    But sadly I've found no documentatino on real-world problems, and performaces in particular.
    Some random Examples:
    1. Transactions affect on performance.
    Eg: suppose you post a 1000 large messages, all under the same transaction. Obviously they need to queue up somewhere - but where: the sender machine or the receiver ?
    2. Is it true there's a performance problem when a Receiver uses a selector ? I hear it works well if you select by MessageId , but performance deteriorates if the selector is based on user-defined properties.
    These are just examples - the bottom line being, you can't just rely on the pure JMS spec... implementation details could be important.
    Would anyone have recommendations on relevant resources ?
    Thanks very mcuh.

    When you ask about software for creating HDR photos? a big question is whether you want special-effects-like imagery HDR or whether you want to realistically simply improve dynamic range of otherwise well-shot images.
    The best way to improve the dynamic range of otherwise well-shot images is to buy a Nikon D3. For those without the $5k for a D3, Photoshop layers are an excellent solution. You make duplicate lightening screen or darkening multiply layers and erase and adjust opacity of various layer parts to achieve what you want.
    Photomatrix is probably the most popular for special-effects-like HDR imagery. There is a good thread among Photoshop pros discussing HDR, with examples, at
    <http://www.adobeforums.com/webx/.59b52953/128>
    -Allen Wicks

  • Can anyone help me how to work with jms server in osb?

    Hi,
    I am new in osb. I have requirement in osb listeners.
    I want to put some data in to jms server using osb in one project and then consume that data using osb in diffrent projects.
    how to configure jms server to work above scenario?
    how to construct business and proxy sevices?
    jms protocal format?
    My requirement is topic in jms server
    Regards,
    Raju..

    Hi,
    The below link will help you to create simple JMS in weblogic
    https://blogs.oracle.com/soaproactive/entry/how_to_create_a_simple
    How to push message and consume message
    http://rangarb.wordpress.com/2012/04/18/working-with-jms-in-osb-11g/
    Another example of subscription of jms
    http://oraclesoaandoim.blogspot.co.uk/2012/04/oracle-service-11116-consume-jms.html
    Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.
    Thanks,
    Vijay

  • Anyone can explain com.evermind.server.jms.JMSObject$ActivationRecord

    Hi,
    Recently i did heap dump on my application oc4j and find out lots of com.evermind.server.jms.JMSObject$ActivationRecord are created and causing the JVM restarted (because FULL GC was taken too much time and opmn ping timeout).
    My application is an ADF JSF/Toplink application. I have configured Toplink cache synchronization between different servers (using session customizer class).
    It also has several MDB which integrated with some BPEL Processes (Using JMS Adapter).
    Platform Solaris Sparc 5.10, Oracle Application Server 10g 10.1.3 SOA Suite.
    Why and What process creates this object? i know it's part of oc4j-internal.jar.
    Appreciate any helps.
    Regards,
    Ricky

    These objects are created on the server when the oc4j.jms.debug property is true. They are used to track DMS phases that have been started but not yet completed. DMS phases are started (and these objects created) when operations on various OC4J JMS server-side objects (representing JMS connections, sessions, producers, consumers, browsers) are started, and are (supposed to be) ended (and these objects released) when those operations complete. Specifically, allocation is done via JMSObject.lock and release is via JMSObject.unlock. It's possible that you are hitting some case where one of these operations is calling lock() and then failing to call unlock(). Note that, despite the name, in most cases the lock() method doesn't check that the given JMS object isn't already locked, so multiple calls to lock() without an unlock() will typically not generate any kind of error or warning (but will produce a memory leak).
    At least for debugging purposes, a modified JMSObject.class file could be used which had a member variable isLocked, set isLocked in lock(), cleared it in unlock(), and verified it is clear before setting it (throwing/logging otherwise). If you are unable (or are legally prevented) from doing such a temporary modification yourself, you should suggest that support provide you with such a modified class file as it will likely be the fastest way to find the root cause. (Note that it would not necessarily flag an error on the faulty operation, but rather on the next attempted operation on the given object or one of its "children", so you would need to backtrack to figure out what the last operation was. "children" is defined as "session is child of connection" and "consumer/producer/browser" are child of session" -- locking/unlocking a child also locks/unlocks the parent.)
    As a workaround, you might try just not using oc4j.jms.debug.
    -Jeff

  • JMS connection from SAP PI to Oracle AQ via JNDI...

    Hi,
    I am currently working on a project that requires connections between PI and Oracle AQ. It was advised that we shoule use PI JMS adpater with JNDI driver. However, it seems that not many people have tried this approach.
    Has anyone had similar solutions in production ? How repliable it is ?
    Your help is very much appreciated
    Tim

    Hi Tim,
    We implemented a similar scenario and now itu2019s still working.
    You have to configure a JNDI connection, but not directly with the Oracle AQ. The Oracle AQ are just queues, and you need a JMS provider in order to establish the connection with these queues. The solution we implemented was:
    1. Configure one OC4J server as JMS provider for the Oracle AQ queues.
    2. Configure JMS communication channels in SAP PI to establish the connection with the OC4J server.
    Maybe you can use a different and newer JMS provider, as BEA Weblogic or SAP WAS (I donu2019t know if itu2019s possible).
    We implement the scenario in SAP PI 7.0, and with this version we had a problem: When the communication between JMS adapter and the queues was broken (the DDBB fell down for example), the channel failed, itu2019s normal. But when the DDBB was already running the channel stayed in an error state, and we had to restart the channel manually. The response of SAP to this issue was that the channel behavior was correct because the connection failed.
    But this problem occurred rarely, maybe once a month. The solution is very reliable, we exchange a lot of message with this solution, and support messages of any size with an excellent performance.
    Best Regards,
    Roberto

  • Using MySQL DB on Weblogic 10.3.2 for JMS Store and etc.

    Hi,
    I am planning to use MySQL DB w Weblogic 10.3.2 server.
    I am planning to use Persistent JMS Destinations and planning to use MySQL Datasource for JMS store.
    Can anyone please help me understand any serious issues or considerations of this combination?
    Thanks
    Sagar

    Hi,
    I am planning to use MySQL DB w Weblogic 10.3.2 server.
    I am planning to use Persistent JMS Destinations and planning to use MySQL Datasource for JMS store.
    Can anyone please help me understand any serious issues or considerations of this combination?
    Thanks
    Sagar

  • JMS JDBC store failed to open after switched to a different database machine

              Hi,
              I'm running WebLogic 6.1 sp3/Oracle 8.1.6 and I configure the JMS JDBC store for
              persistent messaging. I was working fine until I switched to use a different database
              machine which has the same software configuration as the old one. It was giving
              me "failed to create tables" error at start up time. But I checked the database
              and found out the two tables (<prefix>JMSSTORE and <prefix>JMSSTATE) were both
              created and I was able to query although they don't contain any data. By the way,
              I'm using thin client.
              Anyone can help? Thanks a lot!
              Here's the exception:
              <Jul 23, 2003 4:33:10 PM PDT> <Alert> <JMS> <JMSServer "notifyServer", store failed
              to open, java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix
              = <qa.JMS_SERVER_>: failed to create tables.
              java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
              failed to create tables
              at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
              at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
              at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
              at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
              at weblogic.jms.backend.BEStore.open(BEStore.java:180)
              at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
              at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy39.updateDeployments(Unknown Source)
              at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
              at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
              at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy58.start(Unknown Source)
              at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              at weblogic.management.Admin.finish(Admin.java:644)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              at weblogic.Server.main(Server.java:35)
              >
              <Jul 23, 2003 4:33:10 PM PDT> <Error> <JMS> <Failed to deploy JMS Server "notifyServer"
              due to weblogic.jms.common.ConfigurationException: JMS can not open store.
              weblogic.jms.common.ConfigurationException: JMS can not open store
              at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:395)
              at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy39.updateDeployments(Unknown Source)
              at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
              at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
              at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy58.start(Unknown Source)
              at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              at weblogic.management.Admin.finish(Admin.java:644)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              at weblogic.Server.main(Server.java:35)
              ----------- Linked Exception -----------
              java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
              failed to create tables
              at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
              at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
              at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
              at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
              at weblogic.jms.backend.BEStore.open(BEStore.java:180)
              at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
              at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy39.updateDeployments(Unknown Source)
              at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
              at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
              at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy58.start(Unknown Source)
              at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              at weblogic.management.Admin.finish(Admin.java:644)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              at weblogic.Server.main(Server.java:35)
              >
              

    Hi Michelle,
              I suspect a permission problem where the new tables are created
              using the JDBC driver's default schema, but the prefix
              specifies another schema "qa". So the tables are getting
              created, but aren't found.
              Work-around one:
              manually extract, edit, and run the ddl that creates
              the tables to specify the schema. Prepend
              "qa.JMS_SERVER_" to all table names
              (This is fairly simple to do.)
              http://edocs.bea.com/wls/docs61/jms/appb.html#999286
              Work-around two:
              Don't include "qa." in the prefix.
              (i'm not sure if this will work)
              Work-around three:
              Change the username of the JDBC pool to "qa".
              (i'm not sure if this will work)
              Work-around four:
              Change the schema for the tables that were created
              under the JDBC driver's default schema to "qa".
              (I'm not sure how this is done, or even
              if it is possible. Database specific.)
              Tom
              Michelle Lian wrote:
              > Hi,
              >
              > I'm running WebLogic 6.1 sp3/Oracle 8.1.6 and I configure the JMS JDBC store for
              > persistent messaging. I was working fine until I switched to use a different database
              > machine which has the same software configuration as the old one. It was giving
              > me "failed to create tables" error at start up time. But I checked the database
              > and found out the two tables (<prefix>JMSSTORE and <prefix>JMSSTATE) were both
              > created and I was able to query although they don't contain any data. By the way,
              > I'm using thin client.
              >
              > Anyone can help? Thanks a lot!
              >
              > Here's the exception:
              >
              > <Jul 23, 2003 4:33:10 PM PDT> <Alert> <JMS> <JMSServer "notifyServer", store failed
              > to open, java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix
              > = <qa.JMS_SERVER_>: failed to create tables.
              > java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
              > failed to create tables
              > at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
              > at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
              > at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
              > at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
              > at weblogic.jms.backend.BEStore.open(BEStore.java:180)
              > at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
              > at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
              > at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
              > at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
              > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
              > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
              > at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
              > at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > at $Proxy39.updateDeployments(Unknown Source)
              > at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
              > at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
              > at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > at $Proxy58.start(Unknown Source)
              > at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
              > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              > at weblogic.management.Admin.finish(Admin.java:644)
              > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              > at weblogic.Server.main(Server.java:35)
              >
              > <Jul 23, 2003 4:33:10 PM PDT> <Error> <JMS> <Failed to deploy JMS Server "notifyServer"
              > due to weblogic.jms.common.ConfigurationException: JMS can not open store.
              > weblogic.jms.common.ConfigurationException: JMS can not open store
              > at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:395)
              > at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
              > at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
              > at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
              > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
              > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
              > at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
              > at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > at $Proxy39.updateDeployments(Unknown Source)
              > at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
              > at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
              > at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > at $Proxy58.start(Unknown Source)
              > at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
              > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              > at weblogic.management.Admin.finish(Admin.java:644)
              > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              > at weblogic.Server.main(Server.java:35)
              > ----------- Linked Exception -----------
              > java.io.IOException: JMS JDBC store, connection pool = <jmsPool>, prefix = <qa.JMS_SERVER_>:
              > failed to create tables
              > at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:311)
              > at weblogic.jms.store.JDBCIOStream.rebuildTables(JDBCIOStream.java:1400)
              > at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:376)
              > at weblogic.jms.store.JMSStore.open(JMSStore.java:110)
              > at weblogic.jms.backend.BEStore.open(BEStore.java:180)
              > at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
              > at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
              > at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
              > at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
              > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
              > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
              > at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
              > at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > at $Proxy39.updateDeployments(Unknown Source)
              > at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
              > at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
              > at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
              > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
              > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > at $Proxy58.start(Unknown Source)
              > at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
              > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              > at weblogic.management.Admin.finish(Admin.java:644)
              > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              > at weblogic.Server.main(Server.java:35)
              >
              

  • MDB behavior with Foreign JMS Provider

              I am experiencing some MDB behavior which I do not quite understand. I would appreciate
              if someone could tell me what might be happening.
              An application on WebLogic 8.1 SP1 (also tried it with SP2) has MDB's which listen
              on a MQ Queue. If I put a large XML message on the MQ Queue (say around 600 KB),
              the onMessage execution is very random, For the large messages only 1 MDB gets
              invoked and the other messages just sit on the MQ Queue. Even though I have defined
              an weblogic execute queue for the MDB's and they have 15 threads allocated.
              The other messages get picked up after the first one gets completed. The problem
              is the whole transaction (which is XA) can take a while (upto 10 minutes). This
              is not intended, but for some reason it takes that long.
              Also, while monitoring the MDB execute queues, I noticed that none of the threads
              from that queue are performing the work and a thread dump shows that the weblogic.ejb20.internal.JMSPoller
              thread has invoked the MDB and is currently waiting for the database to finish
              some processing.
              When the message size is smaller, the MDB's fire concurrently and are executed
              on the MDB execute queue.
              Thanks,
              Ketan.
              

    When we're using MDBs against a foreign JMS provider with XA, the EJB
              container tries to reduce the number of threads that are blocked waiting for
              a message. You should see lots of threads working when there are lots of
              messages on the queue, a few threads (or only one) working when the queue is
              empty or nearly so, and there should be some ramp-up and ramp-down time in
              between. It sounds like the ramp-up takes longer in your case because
              receiving the very first message takes a long time.
              If this behavior is causing big problems for you, you might want to contact
              product support and file an enhancement request.
              greg
              "Ketan" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Here is some more information regarding this issue.
              >
              > When I place sufficiently large messages (such that the parsing and
              processing
              > of these messages takes longer than it does for normal size messages), I
              notice
              > the following behavior.
              >
              > Lets say I put 6 large messages on the MQ Queue. The server immediately
              picks
              > up 1 message and starts processing it. The other 5 messages are sitting on
              the
              > MQ Queue, while the MDB execute queue has all 15 idle threads.
              >
              > After the processing of the message is done, 2 messages get picked up.
              This time,
              > 1 thread in the MDB execute queue gets the message and the other is
              processed
              > by the JMSPoller thread. After these 2 messages are processed, 3 Messages
              get
              > picked up and this time 2 messages are on the MDB execute queue and 1 is
              processed
              > by the JMSPoller.
              >
              > So based on this the question is ..Is this the expected behavior? I was
              under
              > the impression that the poller would simply dispatch messages to the
              execute queue,
              > and as a result, I was expecting all the messages would get picked up from
              the
              > MQ queue pretty fast and would not have to wait for 1 or more MDB's to
              finish
              > processing.
              >
              > I would really appreciate any suggestions anyone may have for me.
              >
              > Again the environment is WLS 8.1 SP2, MQ 5.3
              >
              > thanks,
              > Ketan
              

  • How do i develop a chat application using jms over web based

    I want to develop a chat application using jms with mailing,file transfer and audio facilities
    can anyone help me to how to go abt that

    There is a good article from Sun on a simple example of what you want - it could serve as a basis for you.
    http://developer.java.sun.com/developer/technicalArticles/peer/

  • While deploying Campaign Optimizer test , Getting JMS Exception.

    Getting below error when test is deployed to satging but it fails to start.
    Below port is defined in DynamoMessagingDSSGlobal.xml and entries looks fine in XML and scenario Manager, Is anyone having any idea how to resolve this and why its coming.
    CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    Complete Log trace is:
    info Wed May 23 18:40:07 CDT 2012 1337816407980 /atg/epub/cache/SelectiveCacheInvalidator Deployment 204100073 contains no repository items. Not flushing any caches
    ed May 23 18:40:07 CDT 2012' dynamo.log G-Data/servers/AdminServer/logs$ grep 'W
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407688 /atg/epub/DeploymentAgent state changing : new = DONE_APPLY : current = ACTIVE_APPLY : previous = DONE_PREPARE
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407689 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407706 /atg/epub/DeploymentAgent state changing : new = ACTIVE_ACTIVATE : current = DONE_APPLY : previous = ACTIVE_APPLY
    **** info Wed May 23 18:40:07 CDT 2012 1337816407798 /atg/epub/cache/SelectiveCacheInvalidator Found 0 repository item(s) in this deployment
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407799 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407801 /atg/epub/DeploymentAgent refreshing/updating VFS : /atg/epub/file/ConfigFileSystem
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager Error adding process /CampaignOptimizer/tests/CO_05232012-abt90002.sdl; rolling back the transaction CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14849)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager Caused by :javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.dms.patchbay.ElementManager.getOutputPort(ElementManager.java:245)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.dms.patchbay.ElementManager.createObjectMessage(ElementManager.java:496)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14822)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407886 /atg/scenario/ScenarioManager
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor --- CONTAINER:atg.process.ProcessException; SOURCE:javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14849)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor Caused by :javax.jms.JMSException: There is no output port named "SegmentStartTimers"
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.dms.patchbay.ElementManager.getOutputPort(ElementManager.java:245)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.dms.patchbay.ElementManager.createObjectMessage(ElementManager.java:496)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendMessage(ProcessManagerService.java:14822)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14595)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.sendCollectiveTimerMessage(ProcessManagerService.java:14562)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9134)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.startProcessSegments(ProcessManagerService.java:9072)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.addProcessGlobal(ProcessManagerService.java:6514)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcessGlobal(ProcessManagerService.java:6239)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.process.ProcessManagerService.updateProcess(ProcessManagerService.java:6137)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ScenarioConfigurationMonitor.processServiceConfigurationEntry(ScenarioConfigurationMonitor.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processEntry(ConfigurationMonitor.java:124)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processJournal(ConfigurationMonitor.java:143)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.processUpdate(ConfigurationMonitor.java:183)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.service.configuration.ConfigurationMonitor.handleUpdate(ConfigurationMonitor.java:213)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.vfs.journal.JournalingFileSystemService.handleUpdate(JournalingFileSystemService.java:378)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.refreshVFSes(DeploymentAgent.java:2502)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.activateDeployment(DeploymentAgent.java:2280)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.DeploymentAgent.handleCommand(DeploymentAgent.java:1027)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at atg.deployment.agent.RMIClientAgentTransport.sendCommand(RMIClientAgentTransport.java:163)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.GeneratedMethodAccessor691.invoke(Unknown Source)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.reflect.Method.invoke(Method.java:597)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:303)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport$1.run(Transport.java:159)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.security.AccessController.doPrivileged(Native Method)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor at java.lang.Thread.run(Thread.java:662)
    **** Error Wed May 23 18:40:07 CDT 2012 1337816407933 /atg/epub/monitor/ScenarioConfigurationMonitor
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407974 /atg/commerce/claimable/ClaimableRepository invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407975 /atg/commerce/catalog/ProductCatalog invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** info Wed May 23 18:40:07 CDT 2012 1337816407975 /atg/search/repository/RefinementRepository Starting invalidateCaches(): /atg/search/repository/RefinementRepository
    **** info Wed May 23 18:40:07 CDT 2012 1337816407976 /atg/search/repository/RefinementRepository Starting premierInvalidateCaches(): /atg/search/repository/RefinementRepository
    **** info Wed May 23 18:40:07 CDT 2012 1337816407977 /atg/search/repository/RefinementRepository Completed premierInvalidateCaches(): /atg/search/repository/RefinementRepository
    **** Warning Wed May 23 18:40:07 CDT 2012 1337816407978 /atg/commerce/pricing/priceLists/PriceLists invalidateCaches() called, but no cache invalidation will happen because it's been disabled by something
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407979 /atg/epub/DeploymentAgent state changing : new = DONE_ACTIVATE : current = ACTIVE_ACTIVATE : previous = DONE_APPLY
    **** info Wed May 23 18:40:07 CDT 2012 1337816407980 /atg/epub/cache/SelectiveCacheInvalidator Deployment 204100073 contains no repository items. Not flushing any caches
    **** debug Wed May 23 18:40:07 CDT 2012 1337816407981 /atg/epub/SecondaryCacheInvalidator Returning because this service is not active

    Can you post the dynamoMessaging.xml if you still have this issue

  • Invoking Jms Adapter from BPEL with enque stoped

    Hi guys, I have an issue.
    In my BPEL flowI have an invoke activity which has a jms adapter as a partner link.
    The thing is that if you stop the enque in the DB, your flow in BPEL continues like nothing happened. It just passes the payload to the jms adapter. From it's point of view is asynchronous , but I want to make sure that the payload is in the queue before I continue the flow.
    Any ideas?

    Hi Oracler,
    I don't understand what you mean by XML schema inline? Where do you define that in a JMS adapter ? Can you be more specfic when you say Try including both the elements(TEXT_LOB , TEXT_VC ) in the schema? I don't have those elements in my schema at all. I have tried the opaque option I still get the same Translator NULL error.
    Please anyone help....

Maybe you are looking for