JMS Version in Weblogic 6.1

Hi all,
Can any body tell me which version of JMS API is included with Weblogic
Server 6.1 Windows2000/NT download ?
Thanks in advance
Bhavin Raichura

HI
Weblogic 6.1 implements JMS specification 1.0.2
regards
Sasikanth
"Weblogic" <[email protected]> wrote:
Hi all,
Can any body tell me which version of JMS API is included with Weblogic
Server 6.1 Windows2000/NT download ?
Thanks in advance
Bhavin Raichura

Similar Messages

Need help please ... ASAP Possible attempt to access newer JMS version then current version....java.io.StreamCorruptedException

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
          <HTML><HEAD>
          <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
          <META content="MSHTML 6.00.2900.2627" name=GENERATOR>
          <STYLE></STYLE>
          </HEAD>
          <BODY bgColor=#ffffff>
          <DIV><FONT face=Arial size=2>I am getting these error after changing table space
          size for my database ...</FONT></DIV>
          <DIV><FONT face=Arial size=2></FONT> </DIV>
          <DIV><FONT face=Arial size=2>I made changes in Database side for table space and
          restart server.. </FONT></DIV>
          <DIV><FONT face=Arial size=2></FONT> </DIV>
          <DIV><FONT face=Arial size=2></FONT> </DIV>
          <DIV><FONT face="Courier New" size=2><Jun 7, 2005 3:44:44 PM EDT>
          <Info> <JMS> <BEA-040321> <JMSServer "ss1 JMS Server" is
          resuming.><BR><Jun 7, 2005 3:44:45 PM EDT> <Alert> <JMS>
          <BEA-040052> <JMSServer "ss1 JMS Server" store failed to open
          java.io.StreamCorrup<BR>tedException: Unsupported class version 2.
          Expected a value between 1 and 1 inclusive. Possible attempt to access
          newer JMS<BR> version then current
          version..<BR>java.io.StreamCorruptedException: Unsupported class version
          2. Expected a value between 1 and 1 inclusive. Possible
          attempt<BR> to access newer JMS version then current
          version.<BR>        at
          weblogic.jms.common.JMSUtilities.versionIOException(JMSUtilities.java:111)<BR>
          at
          weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:438)<BR>
          at
          weblogic.jms.store.JMSStore.open(JMSStore.java:224)<BR>
          at
          weblogic.jms.backend.BEStore.open(BEStore.java:262)<BR>
          at
          weblogic.jms.backend.BEStore.start(BEStore.java:151)<BR>
          at
          weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)<BR>
          at
          weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)<BR>
          at
          weblogic.jms.JMSService.addJMSServer(JMSService.java:2241)<BR>
          at
          weblogic.jms.JMSService.addDeployment(JMSService.java:2012)<BR>
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)<BR>
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)<BR>
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)<BR>
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)<BR>
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
          Method)<BR>        at
          sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)<BR>
          at
          sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<BR>
          at
          java.lang.reflect.Method.invoke(Method.java:324)<BR>
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)<BR>
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)<BR>
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)<BR>
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)<BR>
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)<BR>
          at
          weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)<BR>
          at
          weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)<BR>
          at weblogic.management.internal.MBeanProxy.invoke</FONT></DIV></BODY></HTML>

Hi
          I am also getting the similar error when I restart the server and my JMSSTORE table has some records, Here is the exception I am getting
          java.io.StreamCorruptedException: Unknown object stream version. 5505025
               at weblogic.jms.store.BufferDataInputStream.readObject(BufferDataInputStream.java:167)
               at weblogic.jms.store.JDBCIOStream.doRecoverBodies(JDBCIOStream.java:979)
               at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:871)
               at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:1090)
               at weblogic.jms.store.JMSStore.recover(JMSStore.java:315)
               at weblogic.jms.backend.BEStore.open(BEStore.java:264)
               at weblogic.jms.backend.BEStore.start(BEStore.java:151)
               at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
               at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
               at weblogic.jms.JMSService.addJMSServer(JMSService.java:2241)
               at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:331)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:591)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:569)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:324)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:731)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:710)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:484)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
               at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:985)
               at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:943)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
               at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
               at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7351)
               at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
               at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
               at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
               at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
               at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
               at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
               at weblogic.Server.main(Server.java:32)

Which version of Weblogic on Solaris is compatible with Oracle 8.1.7 - Unicode?

Hi folks,
We want upgrade WLS 4.5.1 to one of the last version of WLS, but also we are
planing upgrade Oracle to 8.1.7 version and migrate the character set of the
database to UTF8 (Unicode),
so we need to know which versions of WLS are compatible with Oracle 8.1.7
and Unicode as Character Set.
Thanks in advance.
Moises Moreno.

Hi Moises Moreno
The latest version of weblogic server is 6.1 with service pack 1. This version
supports oracle 8.1.7 on major unix platforms viz., solaris(2.6,2.7,2.8),
hp-unix(11.0,11.0i), linux7.1, Aix4.3.3 and on windows platforms viz.,
NTwithsp5, 2000.
BEA jdrivers are having Multibyte character set support (UTF8).
Note : Weblogic server 5.1 with SP10 also supports oracle 8.1.7.
FMI : http://www.weblogic.com/platforms/index.html#jdbc
Thanks & Regards
BEA Customer Support
Moises Moreno wrote:
Hi folks,
We want upgrade WLS 4.5.1 to one of the last version of WLS, but also we are
planing upgrade Oracle to 8.1.7 version and migrate the character set of the
database to UTF8 (Unicode),
so we need to know which versions of WLS are compatible with Oracle 8.1.7
and Unicode as Character Set.
Thanks in advance.
Moises Moreno.

Does anyone have any idea how to find out the version of weblogic plugin

Does anyone have any idea about how to find out the current version of weblogic plugin used to connect from webserver to weblogic server?
I could not find version in plugin directory.
it's the same one that came prepackaged with Weblogic 9.2. we haven't change it.
Sun One 6.1 SP6
Weblogic 9.2
Solaris 5.10
Edited by: 985608 on 01-feb-2013 8:20
Edited by: 985608 on 04-feb-2013 6:25
Edited by: 985608 on 04-feb-2013 6:27

Hi,
You can find version of weblogic plugin using below command.
strings <plugin module file> | grep -i wlsplugins
Mark if this helps.
Regards,
Kishore

Can you specify third party JMS Provider in Weblogic appserver configuration

          Can you specify third party JMS Provider in Weblogic appserver configuration ???
          Only place i know of is that you can specify third party JMS Provider in MDB configuraion.
          DOES Weblogic has some kind of configuration files where you specify JMS Provider
          info (Like you can do that in JBOSS)


You can also specify a third-party JMS provider using the Messaging Bridge,
          which transfers messages from one queue or topic to another.
          And in general, inside WLS you can use any JMS provider you wish anywhere
          that you can also use WLS JMS. In an upcoming release, there will also be
          some support to make foreign JMS providers a little easier to configure.
          But why would you want to use another JMS provider anyway? ;-)
          greg
          "Neeru Munjal" <[email protected]> wrote in message
          news:[email protected]..
          >
          > Can you specify third party JMS Provider in Weblogic appserver
          configuration ???
          >
          > Only place i know of is that you can specify third party JMS Provider in
          MDB configuraion.
          > DOES Weblogic has some kind of configuration files where you specify JMS
          Provider
          > info (Like you can do that in JBOSS)

JMS users on Weblogic

Hi All,
We have created JMS queue on weblogic server which is file base persistent .
Now my query is if any external code wants to publish a message into the queue they need user name to connect .
Which user they can connect other than weblogic user OR what user I can create so that he doesn’t has Admin rights and can publish to Queue.
Thanks
AK

I'm not familiar it, but apparently there's a feature in the security subsystem that allows propagating security information for "L2 Caches" via JMS, and it is this feature that's generating the Warning -- not JMS itself.
I do not happen to know how this feature works, what kind of JMS configuration it expects, or if the Warning is simply a natural ephemeral part of the boot/initialization process of the security feature that can be ignored.
You might want to try posting to the "WebLogic Server - Security" newsgroup.
Tom

Foreign JMS QCF and Weblogic Sever Session Pool

          Hi!
          We have Weblogic 6.1 SP2 installation.
          We are trying to use JMS Server session pool and connection consumer configuration
          with MQSeries QCF registered to weblogic JNDI via startup class.
          Upon server startup weblogic is throwing ClassCast exception for QueueConnection.
          It seems weblogic is expecting QueueConnection implementation by weblogic.
          Any suggestions or alternative way of doing it.
          Thanks
          Jay PArikh


Hi Jay,
          Server session pools do not support foreign providers.
          The preferred way to integrate foreign providers is via MDBs or
          via the Messaging Bridge (bridge available in SP3). For a
          comprehensive write-up on integrating foreign providers with
          WL see the whitepaper "Using Foreign JMS Providers with
          WebLogic Server" on dev2dev.bea.com.
          Tom
          Jay Parikh wrote:
          > Hi!
          >
          > We have Weblogic 6.1 SP2 installation.
          >
          > We are trying to use JMS Server session pool and connection consumer configuration
          > with MQSeries QCF registered to weblogic JNDI via startup class.
          >
          > Upon server startup weblogic is throwing ClassCast exception for QueueConnection.
          > It seems weblogic is expecting QueueConnection implementation by weblogic.
          >
          > Any suggestions or alternative way of doing it.
          >
          > Thanks
          > Jay PArikh

How to configure JMS server in weblogic

Hi,
I want to configure JMS server in weblogic.So please send me needful link.
Regards
Anup

Hi Anup,
1. The first thing you have to do is create a filestore where messages will be stored. Look at the below link for more detailed instructions:
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/stores/CreateFileStores.html
2. Next create a JMS server. Look at the below link for more detailed instructions
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_servers/ConfigureJMSServers.html
3. Now, create a JMS System Module to hold the JMS resources like Queues, Topics, Connection Factory, SAF agents etc..
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/modules/ConfigureJMSModules.html
4. Now, create a resource like connection factory OR queue etc.
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/modules/ConfigureJMSModuleResources.html
For now, lets stick to the basics and create a basic queue using the below documentation unless you exactly know what resource you want to create
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/queues/CreateQueues.html
5. You will also need to create a connection factory to use the resource. See below documentation
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/connection_factories/CreateConnectionFactories.html
Please go through the below JMS architecture diagram as well as documentation that will tell you what JMS on WebLogic is all about in terms of configuration
http://docs.oracle.com/cd/E23943_01/web.1111/e13738/overview.htm#i1084283
Arun

Deployment warning -- Compiled by different version of Weblogic Server?

####<Aug 23, 2001 12:17:54 PM PDT> <Warning> <EJB> <alpha> <admin>
<main> <system> <> <010004> <The EJB deployment named: registration
was compiled by a different version of the WebLogic Server.>
I'm using WLS 6.0 SP1.
I'm getting the above warning messages for every jar file within my
EAR file that I try and deploy. I can't figure out the source of this
warning. I get this message in any of the following compilation
cases:
* compiling with BEA's default javac (Sun's JDK version 1.3.0)
* compiling with Sun's javac (Sun's JDK version 1.3.0_02)
* compiling with jikes
The message seems misleading and doesn't make sense to me. Anyone
know why I'm getting this error message? Anyone else getting these
warning messages?
Regards,
JD

Mihir Kulkarni <[email protected]> wrote in message news:<[email protected]>...
Could you please post this message on the ejb newsgroup.
The message does not seem to mean a different version of the java
compiler, but different version of Weblogic's ejb compiler -
weblogic.ejbc.
Were these EJB's compiled by a previous version of ejbc, say, the one from
51 ?
No, these EJBs were never compiled against a previous version of ejbc.
They were only created and deployed with WLS 6.0 SP1.
Also, please check the generated file inside the build\ejbcgen directory:
WLGENERATED to check which version of WL ejbc was used to compile it.
Here's contents of the WLGENERATED file:
#Wed Aug 29 11:04:33 PDT 2001
WLVERSION=WebLogic Server Build\:\t6.0 Service Pack 1 03/04/2001
22\:05\:05 \#
101616\nWebLogic XML Module\:\tNot installed\n
JD
>
JD Fagan wrote:
####<Aug 23, 2001 12:17:54 PM PDT> <Warning> <EJB> <alpha> <admin>
<main> <system> <> <010004> <The EJB deployment named: registration
was compiled by a different version of the WebLogic Server.>
I'm using WLS 6.0 SP1.
I'm getting the above warning messages for every jar file within my
EAR file that I try and deploy. I can't figure out the source of this
warning. I get this message in any of the following compilation
cases:
* compiling with BEA's default javac (Sun's JDK version 1.3.0)
* compiling with Sun's javac (Sun's JDK version 1.3.0_02)
* compiling with jikes
The message seems misleading and doesn't make sense to me. Anyone
know why I'm getting this error message? Anyone else getting these
warning messages?
Regards,
JD

What versions of Weblogic currently have Subject Alternative Name support?

I would like to visit a comment I saw in an old forum thread from 2010
Certificate hostname verification error with 10.3
that "WebLogic currently does not support the Subject Alternative Name field." Can someone please let me know what versions of Weblogic currently have Subject Alternative Name support? We are currently on 10.3. Is there anything near that version that has support, or a patch available for it?
Regards,
John

The KM number is the article number on the support site. Logon to Oracle support and paste the number into the knowledge search and you will get your answer. The article is called "How to Develop Custom Hostname Verifier for Subject Alternative Name (SAN) Certificates" and applies to WLS 10.3.3 and later.

What is the association between JMS Server and JMS Module in weblogic 10?

Hi,
I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
And I have created a JMS Server and Targetted to the current running server (Admin Server).
But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
queue = (Queue) initialContext.lookup("jndi_queue");
Exception:
javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
How JMS Module and JMS server are associated.
My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
Please advice.
Thanks....

Hi,
Once you have JMS servers configured:
Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
For more information, reference the "best practices" chapter of the JMS configuration guide:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
Hope this helps,
Tom

How to find the version of weblogic and ADR from the zip file

Can someone please tell me what version of weblogic is this => wls1034_generic.jar? And what version of ADR libaries are these ? => ofm_appdev_generic_11.1.1.2.0_disk1_1of1.zip ???
and ofm_appdev_generic_11.1.1.3.0_disk1_1ofzip ???

So is WLS 10.3.4. is compatible with ADR libs 11.1.1.2 and 11.1.1.3?
Edited by: user9021545 on Jun 17, 2011 1:33 PM

Does anybody deployed petstore 1.1.2 version on weblogic 6.x?

If any body deployed the petstore 1.1.2 version on weblogic 6.x, would you please
send me the deployment descriptors and any other instructions?
Thanks a lot.
-Jay

To deal with the WebLogic issue:
<Apr 8, 2009 5:01:23 PM PDT> <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
See:
http://www.javaoracleblog.com/java/WLS_on_Mac.jsf
You can add:
-Dweblogic.management.username=<user name> -Dweblogic.management.password=<password> weblogic.Server to the end of your USER_MEM_ARGS in your startWeblogic.sh in the bin directory of your domain. Bad practice here to put the password in cleartext here. I'm sure those extraordinary Oracle Engineers and gurus will probably port WebLogic to OS X.

Feature comparison bet. diff. versions of Weblogic Server starting 5.1 to 8

I am looking for features comparison matrix between different versions of weblogic server from v5.1 to 8.1. Can anyone help?

a matrix I have never seen, but release notes usually sums it up pretty well.

JMS Warning on weblogic startup

The JMS experts may here know better. Looking hard to resolve this issue relaated to JMS. can anyone help here.
Re: JMS Warning on weblogic startup

I'm not familiar it, but apparently there's a feature in the security subsystem that allows propagating security information for "L2 Caches" via JMS, and it is this feature that's generating the Warning -- not JMS itself.
I do not happen to know how this feature works, what kind of JMS configuration it expects, or if the Warning is simply a natural ephemeral part of the boot/initialization process of the security feature that can be ignored.
You might want to try posting to the "WebLogic Server - Security" newsgroup.
Tom

JMS Version in Weblogic 6.1

Similar Messages

Maybe you are looking for