JMS 6.1 vs 7.0 interoperability

          Hello
          I can't conntect to jms topic running on true64/weblogic6.1sp3 from windows2000/weblogic7.0
          if on windows2000 i use weblogic 6.1 it works fine.
          Here are stack traces i got:
          Client side :
          Exception in thread "main" javax.naming.CommunicationException. Root exception
          is java.net.ConnectException: t3://192.168.12.11:7619: Bootstrap to: '192.168.12.11/192.168.12.11:7619'
          over: 't3' got an error or timed out
          at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:173)
          at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:262)
          at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:324)
          at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:222)
          at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
          at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          at javax.naming.InitialContext.init(InitialContext.java:217)
          at javax.naming.InitialContext.<init>(InitialContext.java:193)
          at TopicReceive.getInitialContext(TopicReceive.java:139)
          at TopicReceive.main(TopicReceive.java:115)
          Server side :
          <Apr 17, 2003 2:12:08 PM CEST> <Error> <ConnectionManager>
          <Closing: 'weblogic.rjvm.t3.T3JVMConnection@9553fa0' because of:
          'Server expected to route a message received over an uninitialized connection:
          'JVMMessage from: '-5910079264777171652C:192.168.1.49R:4262005167119958508S:10.66.2.132:[7619,7619,7002,7002,7619,7002,-1]:compaq:eventmgr'
          to: '0S:192.168.12.11:[7619,-1,-1,-1,-1,-1,-1]' cmd: 'CMD_IDENTIFY_REQUEST', QOS:
          '101', responseId: '0', invokableId: '0', flags: 'JVMIDs Sent, TX Context Not
          Sent', abbrev offset: '358'''>
          thanks in advance
          gusano

          Tom Barnes <[email protected]> wrote:
          >JMS is not even involved yet as the initial context setup
          >is failing. I suggest checking to see if true64 is supported
          >for 6.1, perhaps posting to the jndi and/or rmi newsgroup, and
          >contacting customer support.
          >
          >Tom
          true64 is supported and it works fine as i wrote with weblogic 6.1 on both computers.
          but you have right i should post it to jndi /rmi newsgroup
          gusano
          >
          >gusano wrote:
          >> Hello
          >> I can't conntect to jms topic running on true64/weblogic6.1sp3 from
          >windows2000/weblogic7.0
          >> if on windows2000 i use weblogic 6.1 it works fine.
          >>
          >> Here are stack traces i got:
          >>
          >> Client side :
          >>
          >> Exception in thread "main" javax.naming.CommunicationException. Root
          >exception
          >> is java.net.ConnectException: t3://192.168.12.11:7619: Bootstrap to:
          >'192.168.12.11/192.168.12.11:7619'
          >> over: 't3' got an error or timed out
          >> at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:173)
          >> at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:262)
          >> at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:324)
          >> at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:222)
          >> at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
          >> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          >> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          >> at javax.naming.InitialContext.init(InitialContext.java:217)
          >> at javax.naming.InitialContext.<init>(InitialContext.java:193)
          >> at TopicReceive.getInitialContext(TopicReceive.java:139)
          >> at TopicReceive.main(TopicReceive.java:115)
          >>
          >>
          >> Server side :
          >> <Apr 17, 2003 2:12:08 PM CEST> <Error> <ConnectionManager>
          >> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@9553fa0' because of:
          >> 'Server expected to route a message received over an uninitialized
          >connection:
          >> 'JVMMessage from: '-5910079264777171652C:192.168.1.49R:4262005167119958508S:10.66.2.132:[7619,7619,7002,7002,7619,7002,-1]:compaq:eventmgr'
          >> to: '0S:192.168.12.11:[7619,-1,-1,-1,-1,-1,-1]' cmd: 'CMD_IDENTIFY_REQUEST',
          >QOS:
          >> '101', responseId: '0', invokableId: '0', flags: 'JVMIDs Sent, TX Context
          >Not
          >> Sent', abbrev offset: '358'''>
          >>
          >>
          >> thanks in advance
          >>
          >> gusano
          >

Similar Messages

JMS Interoperability between vendors

Hi,
I have been tasked with providing a number or proposals for connecting our enterprise to a number of external partners via a queueing mechanism. i.e. a B2B hub.
I am pretty familiar with JMS, but concerns have been voiced over the interoperability between vendors; something I have no direct experience of.
For example as part of my proposal I may suggest that we send out messages to JMS servers hosted on the partners sites. These partners use a variety of technologies including WebMethods, BizTalk, IBM etc. which we can assume all support JMS (including IBM MQ as I have been told).
Has anyone ever come across interoperability issues with regards to JMS? If I send out JMS messages from one vendor will they be seamlessly received by the target vendors JMS server?
Any shared experience would be appreciated.

Hi Joe,
Thanks for your response. The thing is that this refers to SOAP over JMS, i.e. JMS is the underlying transport protocol not SOAP which brings me back to the original problem interoperability of JMS vendors.
In fact the specification (taken from your first link) states:
"It does NOT provide any mechanism for interoperation between two different JMS providers. In the example above, VendorA and VendorB are different providers of a Web services infrastructure, but the customer must still use a single implementation of JMS at both client and service side."
However your input has highlighted something I was unaware of; that is that there are also interoperability issues within SOAP between different vendors. This is dissapointing; I assumed that SOAP worked without any interoperablity issues whatsover.

JMS interoperability

Hi,
Is it possible to use JMS from another languages? For example, writing a C++ or C# program than produce and consume messages.

Hi Joe,
Thanks for your response. The thing is that this refers to SOAP over JMS, i.e. JMS is the underlying transport protocol not SOAP which brings me back to the original problem interoperability of JMS vendors.
In fact the specification (taken from your first link) states:
"It does NOT provide any mechanism for interoperation between two different JMS providers. In the example above, VendorA and VendorB are different providers of a Web services infrastructure, but the customer must still use a single implementation of JMS at both client and service side."
However your input has highlighted something I was unaware of; that is that there are also interoperability issues within SOAP between different vendors. This is dissapointing; I assumed that SOAP worked without any interoperablity issues whatsover.

SOA Suite 11g - dynamic JNDI destination JMS adapter

hi there soa suite users,
im currently using oracle soa suite 11g,
my use case having a bpel process processing something
and then route the result to several queue.
like this:
jms/adminduk/queue/mks1
jms/adminduk/queue/pdg1,
etc...
so the destination name can be build dynamically in the bpel,
and i stored in a string variable "destName".
(im using WLS 10.3 jms)
now i need to invoke a jms adapter service with produce operation,
but the queue destination needs to be using the variable "destName".
i already tried using assigning to property "jca.jms.JMSDestinationName"
in the invoke activity.
<invoke ...>
<bpelx:inputProperty name="jca.jms.JMSDestinationName"
variable="destName"/>
</invoke>
but it seems not working, and im getting this error:
Caused by: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation
'SendSinkBioWniFromDaerahResponse' failed du
e to: ERRJMS_ERR_CR_QUEUE_PROD.
ERRJMS_ERR_CR_QUEUE_PROD.
Unable to create Queue producer due to JMSException.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>[JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer
requested. The linked
exception may contain more information about the reason for failure.</detail>
,code=<code>null</code>
this is a basic use case of jms interoperability,
anyone have answers to this ??
thank you :)

Hi,
If someone is looking to dynamically set the JMSqueue name here is the solution.
in the Invoke activity set "jca.jms.JMSDestinationName"
value to "JMSHeaderVariable"
set the type to "input"
in the JMSHeaderVariable set the queue name dynamically.
and in the JMSadapter give any valid queue name, still the message will be routed to the queue which you have set in the invoke adapter.

Foreign jms queue binding problem

          Hi,
          I am on the way to wls7.0 from wls5.1, but I got a probelm when I tried to rebind
          the jms queue to weblogic jndi.
          [javax.naming.ConfigurationException [Root exception is java.rmi.MarshalException:
          failed to marshal rebind(Ljava.lang.String;Ljava.lang.Object;Ljava.util.Hasht
          able;); nested exception is: java.io.NotSerializableException]]
          Can I bind the queue to wls jndi? Anybody has silimar situation?
          Thanks


Hi Jen,
          As TOM said, in your case weblogic interaoperabilty supports only from
          weblogic 5.1 to 6.1, that to specified service packs. you can go through the
          following url
          http://e-docs.bea.com/wls/docs61/interop/interop.html
          So you better go by using message bridges for foreign jms providers. The
          document has how you can configure about JNDI provider either File based Or
          Ldap based.
          Thanks
          Kumar
          "Je" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Thanks, actually I am trying to rebind the jms queue from Fiorano
          > MQ. It works fine in wls5.1. Is there special requirement for jndi for
          wls7.1,
          > does the object needs to be serilizable to be bind into jndi?
          >
          > Tom Barnes <[email protected]> wrote:
          > >
          > >It seems you are trying to access 5.1 JMS from 7.0. WebLogic did not
          > >
          > >support interoperability between versions until 6.1. The classes are
          > >
          > >not compatible. So interop requires a good bit of class-loader magic.
          > >
          > > The only way to interop between JMS 5.1 and 7.0 is to use the
          > >messaging bridge (which does the magic for you).
          > >
          > >FYI: I think that it may be possible to invoke remote 5.1 methods from
          > >
          > >7.0 using the IIOP protocol.
          > >
          > >Tom
          > >
          > >Jen wrote:
          > >> Hi,
          > >> I am on the way to wls7.0 from wls5.1, but I got a probelm when I tried
          > >to rebind
          > >> the jms queue to weblogic jndi.
          > >>
          > >> [javax.naming.ConfigurationException [Root exception is
          java.rmi.MarshalException:
          > >> failed to marshal
          rebind(Ljava.lang.String;Ljava.lang.Object;Ljava.util.Hasht
          > >> able;); nested exception is: java.io.NotSerializableException]]
          > >>
          > >> Can I bind the queue to wls jndi? Anybody has silimar situation?
          > >> Thanks
          > >
          >

JMS Selector problem

Hi,
          My problem is so easy, that i'm sure i'm making some simple mistake.
          I have one message in my JMS queue, and I can see it using the WL 9.2 console:
          ID,CorrId,Time Stamp,State String
          ID:P<315390.1173718045000.0>,,Mon Mar 12 17:47:25 CET 2007,visible
          After applying a selector to the console
          JMSMessageId = 'ID:P<315390.1173718045000.0>'
          I don't see the message above !!
          I'm quite sure that the selector is ok, isn't it ??
          At first I used it in my application by the result was the same (the message was not selected).
          What can be the reason ?
          The other problem is that after putting incorrect selector I got the error in the console:
          Error creating message cursor for CISRT JMS Module!Q_DATA_IN_E
          and I cannot do anything about it (I cannot enter the 'Show Messages' screen again without server restart).
          I use Weblogic 9.2 MP1 on Windows.
          Thanks in advance for help.
          Marcin Stanski.

Hi Marcin,
          Thanks for posting. I'll try see if its possible to fix things so other customers don't run into the same problem. Its possible that the interoperability consequences weren't considered when "Id" was fixed to be "ID" in 9.x.
          I'll file internal requests to have 10.0 and 9.x fixed so that they support both the nominally non-standard "Id" in addition to the standard "ID". If you want to track the requests, you can contact customer support and mention that "Tom Barnes has filed an Essex CR for the problem."
          Tom Barnes
          WebLogic JMS Dev Team

JMS Drivers for PI7.1

Right now we are on XI3.0 and using JMS Version 6.40.0 (which I can see in my Visual Admin).
Soon we will be upgrading to PI7.1 So I need to know if the existing JMS drivers will support to our new PI7.1 or do we have to upgrade our MQ as well?
Also can anyone please tell me the version of JMS drivers if they are using JMS with PI7.1 system.

Hi Sarveesh,
I think it would work in the new versions of PI.
Refer the below blogs which may help you regarding JMS adapter:
/people/michal.krawczyk2/blog/2010/01/27/pixi-activemq--free-but-yet-powerful-jms-provider
/people/william.li/blog/2010/02/05/ibm-mq-53-60-70-interoperability-with-pi
Thanks,

JMS Exception - unable to connect to the JMS destination

Hi,
I've configured WebLogic10R3 Cluster with one Admin Server and 2 Managed Servers.
I deployed the application to the Cluster. (Ie. both Managed 1 and Managed Server 2.)
I am geeting the following JMS destination not found exception while starting the Second Managed Server.
There are no errors occurred in the First Managed Server.
{color:#ff0000}<Warning> <EJB> <BEA-010061>
<The Message-Driven EJB: SysAuditLogger is unable to connect to the JMS destination: topic/efpAuditTopic.
The Error was: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server efpserver_man2
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:efpserver_man2.
Resolved 'weblogic .messaging.dispatcher'; remaining name 'S:efpserver_man2>{color}
Configuration Details:
##config.xml:
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/wls [http://www.bea.com/ns/weblogic/90/security/wls.xsd] [http://www.bea.com/ns/weblogic/920/domain] [http://www.bea.com/ns/weblogic/920/domain.xsd] [http://www.bea.com/ns/weblogic/90/security/xacml] [http://www.bea.com/ns/weblogic/90/security/xacml.xsd] [http://www.bea.com/ns/weblogic/90/security] [http://www.bea.com/ns/weblogic/90/security.xsd]">
<name>efpdomain</name>
<domain-version>10.3.0.0</domain-version>
<security-configuration>
<name>efpdomain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{3DES}hcdd+yZGXk5DHgRKqCM7E86l4+VxPcZ9Ut7rB6WaXqMyvbtDjDUKNCKbMQdCN/BEYCv5E0N4Hms9kntfqhaduDO1WGMtbmJL</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{3DES}Q2xO0EiChbay/HkRiorTjg==</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<listen-address>192.168.12.240</listen-address>
</server>
<server>
<name>efpserver_man1</name>
<listen-port>8011</listen-port>
<cluster>efpcluster</cluster>
<listen-address>192.168.12.240</listen-address>
<xml-registry>XMLEFP</xml-registry>
<jta-migratable-target>
<user-preferred-server>efpserver_man1</user-preferred-server>
<cluster>efpcluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>efpserver_man2</name>
<listen-port>8012</listen-port>
<cluster>efpcluster</cluster>
<listen-address>192.168.12.240</listen-address>
<xml-registry>XMLEFP</xml-registry>
<jta-migratable-target>
<user-preferred-server>efpserver_man2</user-preferred-server>
<cluster>efpcluster</cluster>
</jta-migratable-target>
</server>
<cluster>
<name>efpcluster</name>
<cluster-address>192.168.12.240:8011,192.168.12.240:8012</cluster-address>
<multicast-address>239.192.0.0</multicast-address>
</cluster>
<embedded-ldap>
<name>efpdomain</name>
<credential-encrypted>{3DES}q/XQGirHcAcgi4iwPiXIkRHP8xte4xVBgJwjM+qMwbk=</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.0.0</configuration-version>
<app-deployment>
<name>efp</name>
<target>efpcluster</target>
<module-type>ear</module-type>
<source-path>applications\efp.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<xml-registry>
<name>XMLEFP</name>
<document-builder-factory>weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl</document-builder-factory>
<sax-parser-factory>weblogic.apache.xerces.jaxp.SAXParserFactoryImpl</sax-parser-factory>
<transformer-factory>weblogic.apache.xalan.processor.TransformerFactoryImpl</transformer-factory>
</xml-registry>
<jms-server>
<name>eFpJMSServer</name>
<target>efpserver_man1 (migratable)</target>
<persistent-store>eFpJMSJDBCStore</persistent-store>
</jms-server>
<jms-server>
<name>eFpJMSServer2</name>
<target>efpserver_man2 (migratable)</target>
<persistent-store>eFpJMSJDBCStore2</persistent-store>
</jms-server>
<migratable-target>
<name>efpserver_man1 (migratable)</name>
<notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
<user-preferred-server>efpserver_man1</user-preferred-server>
<cluster>efpcluster</cluster>
</migratable-target>
<migratable-target>
<name>efpserver_man2 (migratable)</name>
<notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
<user-preferred-server>efpserver_man2</user-preferred-server>
<cluster>efpcluster</cluster>
</migratable-target>
<jdbc-store>
<name>eFpJMSJDBCStore</name>
<prefix-name>WLJMS_</prefix-name>
<data-source>eFpNonXADataSource</data-source>
<target>efpserver_man1 (migratable)</target>
</jdbc-store>
<jdbc-store>
<name>eFpJMSJDBCStore2</name>
<prefix-name>WLJMS2_</prefix-name>
<data-source>eFpNonXADataSource</data-source>
<target>efpserver_man2 (migratable)</target>
</jdbc-store>
<jms-system-resource>
<name>eFPJMS</name>
<target>efpcluster</target>
<sub-deployment>
<name>eFPServer</name>
<target>eFpJMSServer</target>
</sub-deployment>
<sub-deployment>
<name>eFPServer2</name>
<target>eFpJMSServer2</target>
</sub-deployment>
<descriptor-file-name>jms/efpjms-jms.xml\JMS Description-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>eFpDataSource</name>
<target>efpcluster</target>
<descriptor-file-name>jdbc/eFpDataSource-2004-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>eFpNonXADataSource</name>
<target>efpcluster</target>
<descriptor-file-name>jdbc/eFpNonXADataSource-6172-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
##JMS Description-jms.xml
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms [http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd]">
<connection-factory name="ConnectionFactory">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>jms/ConnectionFactory</jndi-name>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<connection-factory name="XAConnectionFactory">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>jms/XAConnectionFactory</jndi-name>
<transaction-params>
<transaction-timeout>3600</transaction-timeout>
<xa-connection-factory-enabled>true</xa-connection-factory-enabled>
</transaction-params>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<uniform-distributed-queue name="ActiveActivityQueue">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>queue/efpActiveActivityQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
<reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
</uniform-distributed-queue>
<uniform-distributed-topic name="AdminTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpAdminTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="AuditTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpAuditTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="ErrorTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpErrorTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="FreeTextTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpFreeTextTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
<uniform-distributed-topic name="ReportingTopic">
<default-targeting-enabled>true</default-targeting-enabled>
<jndi-name>topic/efpReportingTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
</weblogic-jms>
-----

Getting the following exception while trying to connect the JMS destination I am using weblogic 10.3.3 connecting to oracle AQ. The config has been done as per the 'Interoperating with Oracle AQ JMS' document from oracle. I could see that while deploying the application the number of connections in the database increasing to 15 and getting the following error message.
<Jun 15, 2011 4:14:29 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: SampleEJBBean is unable to connect to the JMS destination: jms/propQueue. Th
e Error was:
oracle.jms.AQjmsException: Internal error: Cannot obtain XAConnection weblogic.c
ommon.resourcepool.ResourceLimitException: No resources currently available in p
ool TestDataSource to allocate to applications, please increase the size of the
pool and retry..
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal
(ResourcePoolImpl.java:555)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
ePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
ePoolImpl.java:322)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
ava:438)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
ava:317)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
nPoolManager.java:93)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
nPoolManager.java:61)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:
1670)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
468)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:355)
at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
at oracle.jms.AQjmsXAConnection.createXAQueueSession(AQjmsXAConnection.j
ava:214)
at weblogic.ejb.container.internal.JMSConnectionPoller.setUpQueueSession
s(JMSConnectionPoller.java:1545)
at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnecti
on(JMSConnectionPoller.java:2047)
at weblogic.ejb.container.internal.JMSConnectionPoller.connect(JMSConnec
tionPoller.java:787)
at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPo
lling(MDConnectionManager.java:244)
at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDriv
enManager.java:584)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.mdManagerSt
art(MessageDrivenBeanInfoImpl.java:1334)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessa
geDrivenBeans(MessageDrivenBeanInfoImpl.java:1314)
at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDrivenBeans(
EJBDeployer.java:1669)
at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:14
93)
at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:614)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(Module
ListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
teDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:43)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
eDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartMod
ulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.ja
va:1269)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:43)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.
java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleM
oduleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(Deploym
entStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(Ap
pContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.ac
tivate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.ac
tivateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Commit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.co
mmit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeplo
ymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(
DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.com
mit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

How to read mq message through jms

Hi
can anyone tell me how we can read an mq message through jms transport or by using jms adapter.
Thanks in advance.

A JMS program will be written typically to lookup administered objects ( namely connection factory and destination) from a jndi tree and use these to connect to the jms provider and read/write message to the destination. So administrators of the JMS provider usually create these objects and bind it to a jndi , which then can be used by the jms applications by doing a lookup from the jndi tree.
Websphere MQ is a messaging provider which provides a native MQ API in many languages including Java for applications to talk to it. This is a IBM proprietary API and is not same as JMS. Later when JMS became more interoperable and the standard for java based messaging applications, IBM introduces the MQ JMS API which is a wrapper around the native MQ API, so that now java clients can talk to MQ using the JMS API. Since jms applications need to lookup the administered objects, IBM came up with the utility called JMSAdmin which allows MQJMS administers to create and bind JMS administered objects. The utility is flexible that it allows the objects to be binded to different type of JNDI trees - file based, ldap based etc. But the most widely used and robust one is the file based.
So as part of configuration the first thing is to create the queue and queue manager objects by the MQ Administrator.
A MQ JMS administrator will then create the JMS wrapper objects using the JMSAdmin utility and bind it to the file based jndi tree ( a file called .bindings)
Now we need the application running in weblogic server ( the JMS Adapter ) to lookup these objects from the file based jndi tree. So for this we create a foreign jms server. A foreign jms server allows to create local jndi links (in weblogic's server jndi tree) for objects in a remote jndi provider (the .bindings file).
Finally the application will look up the local jndi name from the local jndi which will automatically resolve to the remote provider and use it.
The steps in the IBM developer work link folliows this sequence.
Hope this helps.

URGENT: JMS Adapter With BPEL: Reply Only Scenario

Gurus,
I have the following scenario to be implemented:
1) BPEL Process A invokes an Async web-service (on some other SOA)
2) Process A then does some processing.
3) Then, process A waits for a reply message. The reply is sent in a JMS queue by the async Webservice.
4) I have an intermediate receive activity within the same BPEL process A that connects to the JMS Adapter. JMS Adapter is set up to consume messages from the queue.
I see messages pending in the queue but my receive doesn't continue.
Thanks-
Ashish

Hello,
There are interoperability issues between the Mid-tier and the RDBMS at present because the the mid-tier is using older version of the AQ jar files. At present the mid-tier is based on 10.1.0.5 and the backend will be whatever the backend is. Your issue sounds like a NLS issue given that bytes are fine but text is not. The characterset of the database will probably be important in this situation. So you check if the issue reproduces with different charactersets if possible. What characterset are you using and what is the Payload that the queue table is built on?
I would also suggest you try and build a standalone java application which reproduces the problem. You could most likely achieve this by creating a 10.1.0.5 RDBMS home and using the jar files from that install and then run it against your database to see if it reproduces the issue.
Anything that you can do to break down the problem will help Oracle Support identify what the issue is.
Thanks
Peter

Jms.bridge.TemporaryResourceException

Folks,
          I would very grateful if anyone has seen this one:
          I'm attempting to connect to a remote weblogic server, my bridge destination is configured (as best I can see, correctly, as its a clone of a working environment on another server).
          I am receiving the following error when the server tries to connect to the Bridge destination.
          Some Points:
          1. The remote WLE has a username/password on it, they've been configured.
          2. The domain credentials have been changed to match those of the remote server.
          3. The interoperability mode are the same across the domains.
          4. The remote server is active, I have sent messages across on a client tester.
          LOG
          ####<25-Jan-2007 14:02:45 o'clock GMT> <Info> <MessagingBridge> <serverName> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1169733765045>
          <BEA-200043> <Bridge "aTOb" failed to connect to the target destination and will try again in 60 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: weblogic.jms.bridge.TemporaryResourceException
          at weblogic.jms.adapter.JMSBaseConnection.throwTempResourceException(JMSBaseConnection.java:14
          31)
          at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:390)
          at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:242)
          at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
          at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
          at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
          at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1057)
          at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:346)
          at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294)
          at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:277)
          at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:606)
          at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:271)
          at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
          at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:
          307)
          at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.
          java:115)
          at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.
          java:123)
          at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:854)
          at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1042)
          at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
          at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
          )>
          ####<25-Jan-2007 14:02:46 o'clock GMT> <Info> <Console> <serverName> <AdminServer> <[ACTIVE] ExecuteThread
          : '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <

Enable debug flags for message bridge to capture more details:
-Dweblogic.Debug.DebugMessagingBridgeStartup=true
-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
Edited by: atheek1 on 07-Jul-2010 03:21

Sun MQ - WebSphere MQ Interoperability

Hi,
I am working for a company that has an Enterprise Messaging Cluster comprised of WebSphere MQ (v5.3) and would like to know if Sun MQ includes any functionality that provides interoperability with WebSphere MQ, such as the JMS-to-JMS bridge provided by ActiveMQ. Also, does SunMQ provide any transformation and/or routing capabilities or is it necessary to look at an ESB (or Message Broker) to obtain this functionality?, thanks!

Currently (3.0.1 and 3.5) you must manage the ACLs
of each broker separately and the only way to do that
is via the accesscontrol.properties file.

JMS bridge and MQSeries. looking for statistics

          Hi !
          I have to use Weblogic 7 SP4 in cluster with a distant MQSeries queue manager.
          I know I can't have a "exactly once" quality of service. I use a MDB (deplyed
          on each instance of the server).
          I'm looking for statistics about how often a message can be treated 2 (or more)
          times.
          Thanks a lot for any help !
          Florent


Hi Florent,
          Since these are MQ messages, it might be possible to find
          such statistics in MQ. Also, I think that MQ stores a
          redelivery count in their messages - so you can likely
          instrument your application code to get at the count.
          Note that 7.0 actually does support exactly once with WL MDBs driven
          by MQ. If you use transactions you can infer some stats on redeliveries
          by checking the relevant transaction statistics for rollback counts.
          I'm attaching some notes on JMS integration for your
          convenience.
          Tom
          florent wrote:
          > Hi !
          >
          > I have to use Weblogic 7 SP4 in cluster with a distant MQSeries queue manager.
          > I know I can't have a "exactly once" quality of service. I use a MDB (deplyed
          > on each instance of the server).
          >
          > I'm looking for statistics about how often a message can be treated 2 (or more)
          > times.
          >
          > Thanks a lot for any help !
          >
          > Florent
          JMS Integration of Foreign Vendors with BEA WebLogic Server
          The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
          For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
          JMS Integration Overview
          - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
          - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
          - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
          - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
          - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
          - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
          - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
          Integration with 8.1 Details
          A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
          http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
          This document refers to helpful new 8.1 features, which simplify integration. These include:
          http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
          http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
          And are also summarized here (under interoperability):
          http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
          Also read the extensive MDB documentation, which extensively covers integrating foreign vendors:
          http://edocs.bea.com/wls/docs81/ejb/message_beans.html
          The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
          Integration with 6.1 and 7.0 Details
          Read the "Using Foreign JMS Providers With WLS" white-paper:
          http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
          Note that this white-paper does not take into account 8.1 features.
          For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
          http://edocs.bea.com/wls/docs81/ejb/message_beans.html
          Non-Java Integration Options
          - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
          http://e-docs.bea.com/wls/docs61/jcom.html
          http://e-docs.bea.com/wls/docs70/jcom/
          http://e-docs.bea.com/wls/docs81/jcom/
          - Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
          http://e-docs.bea.com/wls/docs81/rmi_iiop/
          http://e-docs.bea.com/wls/docs70/rmi_iiop/
          http://e-docs.bea.com/wls/docs61/rmi_iiop/
          Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
          - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
          - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
          http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
          - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
          - Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
          Notes on MQ Remote Capable XA Clients
          Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
          http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
          The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
          - Required on WLS where MQ objects are bound into JNDI:
          com.ibm.mq.jar, com.ibm.mqjms.jar
          - Required only if MQ objects are bound into JNDI on a different server:
          com.ibm.mq.jar
          If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
          Notes on Oracle AQ Integration
          If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
          http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
          Caveats:
          The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
          Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
          The solution doesn't seem to support transactions, it may be possible to extend it to do so.
          MDB Thread Pool Notes
          WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
          http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
          (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
          MDB Concurrency Notes
          Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
          Design Guide-Lines and Performance Tuning Notes
          The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
          http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp

WebLogic JMS 10 and 7 Compatibility

Hi,
Is there a way to transfer JMS messages from WebLogic 7 to WebLogic 10?
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/compatibility/compatibility.html
Based on the protocol compatibility section in above link, am I to assume that I cannot use JMS to drop a message into WLS 10 from 7?
Regards,
Anand.
Edited by: user653362 on Feb 5, 2009 9:55 PM

If you are considering to send messages from WLS 10.0 and WLS 7 or vice versa then its possible but refer to the following :-
Interoperability between WebLogic Server 7.0 and WebLogic Server 10.0 is supported in the following scenarios. You will need the WebLogic Server 7.0 patch that is associated with CR295275 for this interoperability to work. This patch is applicable to WLS 7.0 SP6 and WLS 7.0 SP7. You can request this patch by contacting BEA support and requesting the patch associated with CR295275. Additionally, for RMI/IIOP interoperability support, start the WLS 7.0 client using the following flag: -Dweblogic.system.iiop.enableClient=true
A WebLogic Server 7.0 client can invoke RMI-based applications hosted on a WebLogic Server 10.0 server using T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.
A WebLogic Server 10.0 client can invoke RMI-based applications hosted on a WebLogic Server 7.0 server using T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.
A WebLogic Server 10.0 Web server plug-in can proxy to the latest service pack release of a 7.0 server.
Link : [http://e-docs.bea.com/wls/docs100/compatibility/compatibility.html]

Sun ONE Message Queue and JMS

Is Sun ONE Message Queue software a reference implementation or a
product?

Sun ONE Message Queue is a product. It is a production implementation of the JMS
specification. Sun ONE Message Queue software performs the function of a message
broker, essentially serving as a common denominator enabling the exchange of
information between applications. A number of competing products perform this same
function, but Sun ONE Message Queue software adds the availability of JMS APIs to
promote an open, industry-standard interface to messaging middleware, thus
promoting the platform interoperability of Java while also enabling developers of
business applications to write to only a single interface. In and of itself, this does not
make Sun ONE Message Queue software unique since other MOM products also
conform to the JMS specification. However, the combination of JMS with high
performance, low cost, ease of use, and Sun's world class distribution and support
channels makes Sun ONE Message Queue software a highly competitive product.

JMS 6.1 vs 7.0 interoperability

Similar Messages

Maybe you are looking for