WebLogic 10.3 and JDK 1.5

Is WebLogic 10.3 certified to run on JDK 1.5 ? The Support Matrix here
lists only JDK 1.6 , anyone used WL 10.3 with JDK 1.5 ?

Honestly, why should I use JDK 1.5? It is end-of-life (or you pay money for additional support) and JDK 1.6 is faster...
Just my 2 cts,
--olaf

Similar Messages

Oracle 8.1.5 and JDK 1.2 Thin Driver

We are doing some prototyping with Oracle 8.1.5, BEA WebLogic
6.1, and JDK 1.3. We needed to know what is the latest version
supported by the oracle thing client drivers for that
configuration.
Or are we the only users doing this and is it mandatory that we
migrate to Oracle 8.1.7?
Thanks,
Nikhil Kumar
Lead Architect
Delta Dental Plan of Michigan
[email protected]

Check out the SQLJ FAQ at:
http://technet.oracle.com/tech/java/sqlj_jdbc/htdocs/faq.html
"ExceptionInInitializerError: NullPointerException"
(This is likely a general configuration issue, not something specific to your code.)
If you see the following stack trace:
unexpected error occurred... java.lang.ExceptionInInitializerError: java.lang.NullPointerException
at sqlj.framework.ClassFileReader.attribute_info(Compiled Code) ...
at sqlj.tools.Sqlj.statusMain(Compiled Code)
at sqlj.tools.Sqlj.main(Sqlj.java:117)
then you are likely running SQLJ version 8.1.5 or earlier under JDK 1.2.x or later.
You need to download the SQLJ 8.1.6 SDK patch, which contains a new translator.zip
version that you can use to replace the translator.zip from 8.0.5/7.3.4 or from JDeveloper 3.0.
null

How to identify the installed Weblogic Server and JDK are 32bit or 64bit?

Hi everyone,
I have a question ~
Both Weblogic Server and JAVA JDK are installed on the server already, but I only know the Weblogic Server is 10.3.4.0 and JAVA JDK version is 1.6.0_25.
I know the 64bit Weblogic Server installation file is a wlsXXXX_generic.jar package and 64bit JAVA JDK needed also.
But, since the Weblogic installed already, there are no such installation files on the Linux Server now.
I have tried the "java -version" for java version and check the Weblogic version from Weblogic console.
How to identify the installed Weblogic Server and JDK are 32bit or 64bit with Linux command? Or is there any way to check it?

What you can try to do is use WLST (or an MBean browser, such as JConsole or JRockit Mission Control) and connect to the adminserver.
For example when using WLST:
# set the environment by using setWLSEnv.sh (located in the ${WL_HOME}/server/bin directory).
# start WLST by using: java weblogic.WLST
# connect to the adminserver
connect('adminusername','adminpassword');
# change to the serverruntime environment
serverRuntime();
# show the attributes
ls();
# Here an attribute is shown called WebLogicVersion that shows the version of WebLogic
-r-- WeblogicVersion WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638
# Note that this does not show if is 32 bits or 64 bits to retrieve this information you have obtain the JVM version
# change the directory
cd('JVMRuntime/AdminServer');
# show the attributes
ls();
-r-- Version R28.0.1-21-133393-1.6.0_20-20100512-2126-linux-x86_64
# when you have something like x86 at the you are running a 32 bit version, if you have something like x86_64 you are running a 64 bits versionAs mentioned above you can also retrieve this information by using a MBean browser.

Error while parsing JSP with WebLogic 5.1/SP9/JDK 1.2.2

Hello everybody,
          I get the error given below when calling a JSP in a WebLogic
          application which seems to work fine in all other (non-JSP) parts:
          java.lang.NullPointerException:
               at weblogic.servlet.jsp.JspLexer.addSetPropertyValue(JspLexer.java:1432)
               at weblogic.servlet.jsp.JspLexer.mXML_SET_PROPERTY(JspLexer.java,
          Compiled Code)
               at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1726)
               at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
               at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
          Code)
               at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
               at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
               at weblogic.servlet.jsp.JspParser.parse(JspParser.java:159)
               at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
               at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
          Compiled Code)
               at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
          Code)
               at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
               at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
               at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
               at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
               at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
          Code)
          I know that this error has been reported more than once in these
          discussion groups, and all people who solved it say
          - that it occurs only wen running WebLogic 5.1 with JDK 1.3 instead of
          1.2.2
          - that it may also be caused by bad jsp code
          But in my case, it has to be another reason, because
          - I am using jdk 1.2.2
          - the same JSP file is running withour errors on WebLogic 6
          I wonder if it could have something to do with the operating system:
          the parsing error is produced on a Windows version of WL 5.1, while my
          WL 6 which doesn't cause errors is running with Linux.
          Many thanks in advance for any help,
          Eckhard Beisswenger


Once again me!
          After a long time, I stumbled by accident across the answer that solves the problem I described above. It is explained at
          http://support.bea.com/application;JSESSIONID_WLCS_DEFAULT=2R2lzQfEBxFRMX2z0AxeU1Un3N1522I9fCIUI7GfjnjsiSYkPscz
          The clue is that weblogic complains about corresponding get and set methods, when the type of the set methods parameter is different from the return type of the corresponding get method. Unfortunately, the weblogic lexer class gives only a NullPointerException without any hint.

WebLogic 5.1 & IBM JDK 1.1.8 on RedHat Linux 6.2

Hello
I am trying to get WebLogic 5.1 to run with IBM JDK 1.1.8 on a RedHat 6.2 machine. When I start the sample server, it always SIGEV in the native thread (something like that).
I do not have any problems with the Blackdown 1.2.X JDK. I would like to evaluate the IBM JDK as that is the preferred solution in my group.
Please reply
Thanks you
Narayanan Iyer
[email protected]

Hi Michael
It appears to be a bug in the IBM JDK 1.1.8 release version built on May ??
,2000. I downloaded the newer version IBM JDK 1.1.8 built on July 13,2000
and it appears to be fine with SP4.
I am curious as to the status of IBM JDK1.3 on RedHat 6.2 and well as the
SUN JDK1.3. Both appear to crash. I would really like to take advantage of
the performance features offered.
Thanks
"Michael Girdley" <[email protected]> wrote in message
news:[email protected]..
>
>
Could you please post the error?
You should also make sure that you are using a certified JVM. Theplatform
support page for WebLogic Server is located at:
http://www.weblogic.com/platforms/index.html
This page has the latest and greatest information on the platforms that
WebLogic is certified and supported on.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Narayanan Iyer" <[email protected]> wrote in message
news:[email protected]..
Hello
I am trying to get WebLogic 5.1 to run with IBM JDK 1.1.8 on a RedHat
6.2
machine. When I start the sample server, it always SIGEV in the native
thread (something like that).
I do not have any problems with the Blackdown 1.2.X JDK. I would like toevaluate the IBM JDK as that is the preferred solution in my group.
Please reply
Thanks you
Narayanan Iyer
[email protected]

How to change weblogic 10.3 's JDK version

I installed weblogic 10.3 and its default JDK version is 1.6.0_05, but I want to update the JDK to 1.6.0_18, how should I do it?
I tried to create a new domain and in "JDK Selection", I select option "Other JDK",path is "C:\Program Files (x86)\Java\jre6", but when start admin server, error "you wrongly used \Java\jre6 "(Which is translated from Japanese).
How should I do?

Hi,
Please refer to the Post: http://weblogic-wonders.com/weblogic/2010/09/03/why-and-how-oracle-jrockit/
If you want to use a Different Version of Sun JDK then please change the JAVA_VENDOR=Sun as well....in the folowing Image:
http://weblogic-wonders.com/weblogic/wp-content/uploads/2010/09/setting_JAVA_JOME_In_script.jpg
Example : (setDomainEnv.cmd) for WINDOWS OS
set JAVA_HOME=C:\myJDKs\jdk1.6.0_18
set JAVA_VENDOR=Sun
=-- = = = = = =-- = = = = = =-- = = = = = =-- = = = = =
<b><font color=red>Just in case if you still face the same problem then do the following:</font></b>
In your Windows OS box...
RightClick on MyComputer ---> Advanced(Tab)---> Envirunment Variables (Button)---->User Variables (Section) add a new variable:
Variable Name : PATH
Variable Value : C:\myJDKs\jdk1.6.0_18;%PATH%;
OK
Just to verify this now open a fresh command prompt and then Just run the following command:
java -version
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic(WebLogi Wonders Are Here)

Communicating between Weblogic 8.1 and Weblogic 10.3

Hi,
I have a requirement where in I need to access Queues in Weblogic 10.3 from Weblogic 8.1 and viceversa.
Weblogic 8.1 :
This has a proxy/web application that needs to put request to a Queue exposed in weblogic 10.3
And will again poll for a Response Queue in weblogic 10.3
Is it feasible, knowing the fact that jdk version in 8.1 is 1.4 & Jdk version is 1.6 in 8.1 ?
Can we lookup for Queue defined in 8.1 in Weblogic 10.3 ? Can we use JMS adapter in 10.3 for acheiving this.
Any help is greatly appreciated.
Thanks !!

Avoid using Message Bridges to receive messages.
See the best practice: http://download.oracle.com/docs/cd/E15051_01/wls/docs103/jms/interop.html#wp1009272
Q. When should I avoid using a messaging bridge?
A. Other methods are preferred in the following situations:
    * Receiving from a remote destination—use a message driven EJB or implement a client consumer directly.
    * Sending messages to a local destination—send directly to the local destination.
    * Environment with low tolerance for message latency. Messaging Bridges increase latency and may lower throughput. Messaging bridges increase latency for messages as they introduce an extra destination in the message path and may lower throughput because they forward messages using a single thread.
    * Forward messages between WebLogic 9.0 domains—Use WebLogic Store-and-Forward.

Weblogic 10.3 and ServiceControl

Hello,
we have a serious problem using ServiceControl with Weblogic 10.3
From a servlet we programmaticaly instantiate a control like this :
ImportTemplateControlBean mImportTemplateControl = (ImportTemplateControlBean)
               Controls.instantiate (Thread.currentThread().getContextClassLoader(),
                         "com.mesmessages.ImportTemplateControlBean", null);
ImportTemplateControl is a simple java control. In this control we instantiate a ServiceControl like this :
@Control
MessagesServiceControl
There are no problem on compilation and deployment. But at the runtime with the following error :
com.bea.control.servicecontrol.util.ServiceAnalyzerException: Cannot find types
jar based on application URL file:/Z:/.metadata/.plugins/org.eclipse.core.resour
ces/.projects/portalApplication/beadep/portalDomain/portalApplication/ and jar n
ame typegen__tylar__com__mesmessages__MesMessagesContr
act.jar. typesJarFile = Z:\.metadata\.plugins\org.eclipse.core.resources\.projec
ts\portalApplication\beadep\portalDomain\portalApplication\APP-INF\lib\typegen__
tylar__com__MesMessagesContract.jar
Wath can cause this ?
Thanks for help

Honestly, why should I use JDK 1.5? It is end-of-life (or you pay money for additional support) and JDK 1.6 is faster...
Just my 2 cts,
--olaf

Weblogic12c and JDK 7 together not using login configuration file properly

Hello,
Little puzzled by this.
I ve installed JDK 7 along with Weblogic 12c and made a custom installation of Weblogic to use JDK 7 as the Local JDK
as mentioned in this doc
http://docs.oracle.com/cd/E24329_01/doc.1211/e24492/jdk7.htm
The JAVA_HOME is pointing to JDK 7
When i configure the login.config.url.1 under JAVA_HOME/jre/lib/security/java.security file to use our own specific file which is used for authentication against LDAP,
deploy the app and try to login, authentication fails(LoginException is thrown), like as if it s not understanding this file or the path or similar.
When i configure the same to use the JDK 6 that comes along with Weblogic 12c, everything is fine.....
Not sure where the problem lies.
Is there any other setting i need to do?
Any help is greatly appreciated.
The Exception thrown is
javax.security.auth.login.LoginException: java.util.MissingResourceException: Can't find resource for bundle sun.security.util.AuthResour
ces, key username: at java.util.ResourceBundle.getObject(ResourceBundle.java:393)
at java.util.ResourceBundle.getString(ResourceBundle.java:353)
at ........
Edited by: 902337 on Jan 6, 2012 11:08 AM

Just adding here that if i install JDK 6 outside of weblogic 12 and point to it, that also works fine.
The problem seems to be weblogic 12 pointing to JDK 7 only ...

Weblogic 7.0 and Sun's sdk 1.4.1_01

I'm involved in a project which is composed of Weblogic application server
and later a rich Java client (Swing).
I dislike having a lot of Java sdk(s) on multiple places in my computer and
I wish to use the Java most recent version.
My questions are:
- Is Java sdk 1.4 supported on Weblogic 7?
- If not, do you have any experience/problems with it?
- In the worst case, I won't upgrade to the most recent Java version on the
server side.
What implications, if any, does this have on the rich client?
Should I use for client side development the same Java version as Weblogic
does or can I get by with 1.4?

Why do you recommend 1.3.1_06, not 1.3.1_07? I just tried _07 (on WinXP) and I'm
not sure but I think the error I'm getting now about "libmuxer not found" didn't
happen with _06. Is that a known problem?
-greg.
"Wayne W. Scott" <[email protected]> wrote:
Oh Gawd, here we go again. Please don't yell at me like so many others
have done when
they get answers that they did not want to hear.
Java SDK 1.4 has NOT been certified with any BEA product yet. The plans
are for the
first one to be the Olympic release, probably to be called WLS 8.1, due
this Summer.
AFAIK, the biggest problems have been in the integration of Security
products with 1.4.
I do not know all the nitty-gritty details. The latest JDK I would
use is 1.3.1_06.
I have no further guidance on other related topics.
Best Wishes,
Wayne Scott
Yonatan Taub wrote:
I'm involved in a project which is composed of Weblogic applicationserver
and later a rich Java client (Swing).
I dislike having a lot of Java sdk(s) on multiple places in my computerand
I wish to use the Java most recent version.
My questions are:
- Is Java sdk 1.4 supported on Weblogic 7?
- If not, do you have any experience/problems with it?
- In the worst case, I won't upgrade to the most recent Java versionon the
server side.
What implications, if any, does this have on the rich client?
Should I use for client side development the same Java version asWeblogic
does or can I get by with 1.4?

Weblogic 6.1 and JVM 1.4 on Solaris

I know this combination is not officially supported, but I would like to be
able to try it in a test system for comparative purposes.
I saw a previous mail on this subject indicating it was possible (reproduced
below). I tried creating the Solaris equivalent of the file as
/usr/j2sdk1.4.0/jre/lib/security/login.config with the contents:
ServerLoginModule {
com.sun.security.auth.module.UnixLoginModule required debug=true;
This made no difference to the output (also reproduced below)
I have two questions:
- Have I done something wrong (file owner/permissions?) or is there
something else I need to do to make this work?
- Is there anywhere else I can place this file - on the CLASSPATH perhaps -
I tried this a bit but I didn't get anywhere.
Thanks,.
Roger Broadbent
Technical Consultant
Wilco International Ltd
From: "dominik" <[email protected]>
Sender: "dominik" <[email protected]>
Reply-To: "dominik" <[email protected]>
Subject: Re: Support for JDK 1.4 -> works on Suse 7.2 & 7.3
Newsgroups: weblogic.support.install
X-User-Info: 80.254.173.142
References: <[email protected]> <[email protected]>
NNTP-Posting-Host: 80.254.173.142
X-Original-NNTP-Posting-Host: 80.254.173.142
Message-ID: <[email protected]>
Date: 7 Apr 2002 03:19:19 -0800
X-Trace: newsgroups.bea.com 1018174759 80.254.173.142 (7 Apr 2002
03:19:19 -0800)
Organization: BEA SYSTEMS Inc
Lines: 42
XPident: Unknown
Hi
It works for me on Suse Linux 7.2 & 7.3 with JDK
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
This is my login configuration:
#/usr/lib/jdk1.4/jre/lib/security > cat login.config
ServerLoginModule {
com.sun.security.auth.module.UnixLoginModule required debug=true;
I had to pass the weblogic system password on the commandline
(with -Dweblogic.management.password=$WLS_PW).
The password in password.ini somehow didn't work ... (I was
prompted for the guest password, was able to boot the server but
had some weblogic.management.NoAccessRuntimeException later on.
Yeshwant <[email protected]> wrote:
>
Try the pdf document that I have attached. Please note that using 1.4
JVM
is currently not supported by BEA
let me know if it works.
Aamir Baig wrote:
Will weblogic 5.1, 6.0 or 6.1 work with jdk 1.4 ? has anyone tried
and
succeeded ?
Thanks in advance
Kind Regards,
Aamir Baig
Etilize, Inc.
Phone : 310-767-4001 x 205
Fax: 310-767-1548Output:
% startWebLogic_JVM1.4.sh
LD_LIBRARY_PATH=.:/usr/sybase/OCS-12_0/lib:/local/upm/bea/wlserver6.1/lib/so
laris:/local/upm/bea/wlserver6.1/lib/solaris/oci816_8
* To start WebLogic Server, use the password *
* assigned to the system user. The system *
* username and password must also be used to *
* access the WebLogic Server console from a web *
* browser. *
java.lang.SecurityException: Unable to locate a login configuration
at com.sun.security.auth.login.ConfigFile.<init>(ConfigFile.java:97)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
sorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
torAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:296)
at java.lang.Class.newInstance(Class.java:249)
at
javax.security.auth.login.Configuration$3.run(Configuration.java:221)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.security.auth.login.Configuration.getConfiguration(Configuration.java:
215)
at
javax.security.auth.login.LoginContext$1.run(LoginContext.java:170)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.security.auth.login.LoginContext.init(LoginContext.java:167)
at
javax.security.auth.login.LoginContext.<init>(LoginContext.java:393)
at
weblogic.security.internal.ServerAuthenticate.main(ServerAuthenticate.java:8
1)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:195)
at weblogic.Server.main(Server.java:35)
Caused by: java.io.IOException: Unable to locate a login configuration
at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:206)
at com.sun.security.auth.login.ConfigFile.<init>(ConfigFile.java:95)
... 16 more

Hi Janne,
You may want to check this link:
http://e-docs.bea.com/wls/docs70/compatibility/compatibility.html
"janne" <[email protected]> wrote in message
news:[email protected]..
Are WebLogic 6.1 and 7.0 EJBs interoperable? Can a client EJB on 6.1
call another EJB on 7.0 and vice versa?
Weblogic 5.1 and 6.0 were not interoperable. Interoperability was
achieved with versions 5.1 sp12 and 6.1 sp 3.
http://e-docs.bea.com/wls/docs61/interop/interop.html
Regards,
Slava Imeshev

WebLogic 6.0 and NT security – HOW?

WebLogic 6.0 and NT security – HOW?
Info
- Windows NT 4.0 SP6
- WebLogic 6.0
- JDK 1.3
The WebLogic instance is running as a service under the system account, c:\bea\wlserver6.0\bin
is in the path.
We have several Primary Domain Controllers, so we made a NTRealm entry per PDC. We
rebooted the server.
Now, I would expect to see the NT users and groups in the security tab but I only
see the filerealm users and groups. Is this normal that they don’t show up?
I understand that you have to use the NT Admin tools for creating users and groups,
but I would expect to SEE them in the security tab.
We created an NT group BEA_TEST on that machine and we would like to give only members
of that group access to our application. (See files below.) It doesn’t work.
If we create a filerealm group it works fine, NTRealm not.
What are we missing here?
Regards,
Merg
----- web.xml -----
<security-constraint>
<web-resource-collection>
<web-resource-name>TEST</web-resource-name>
<description>Test</description>
<url-pattern>*</url-pattern>
<http-method>POST</http-method>
<http-method>GET</http-method>
</web-resource-collection>
<auth-constraint>
<description>Test</description>
<role-name>TESTUSERS</role-name>
</auth-constraint>
<user-data-constraint>
<description>SSL not required</description>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
<security-role>
<description>TESTUSERS</description>
<role-name>TESTUSERS</role-name>
</security-role>
----- weblogic.xml -----
<security-role-assignment>
<role-name>TESTUSERS</role-name>
<principal-name>BEA_TEST</principal-name>
</security-role-assignment>

Darkit,
I have the same problem. Let me know if you find a solution to this problem.
Thanks,
Bharathi

Weblogic 7.0 and 6.1 javax.servlet.filter implementation

          Hi All,
          I was using weblogic 6.1 and as my organization wants to go for 7.0, we
          are in the process of evaluating 7.0 ver.
          WL6.1 javax.servlet.filter interface provides the methods doFilter(), setFilterConfig(),
          getFilterConfig(). We have an implementation for the Filter which also contains
          a private method init(FilterCongig filterConfig).
          In 7.0 javax.servlet.filter interface the methods are doFilter(), init(), destroy().
          Because of the obvious reason i have a private implementation of init(FilterConfig
          )in my code the build does not succeed. When i checked the java specifications
          from Sun site I found 1.3.1 and 1.4(beta) specs provide doFilter(), init() and
          destroy().
          Question is: Is weblogic 6.1, JDK 1.3.1 compliant, if so why there is not init()
          method in the filter interface??. (Otherwise its a bug)
          Because of this the porting has become a serious issue as in some cases we need
          to support both 6.1 and 7.0


6.1 did not implement the final version of the Servlet 2.3 specification, that's
          why you see differences.
          http://edocs.bea.com/wls/docs61/notes/new.html#1064420
          Sanjeev <[email protected]> wrote:
          > Hi All,
          > I was using weblogic 6.1 and as my organization wants to go for 7.0, we
          > are in the process of evaluating 7.0 ver.
          > WL6.1 javax.servlet.filter interface provides the methods doFilter(), setFilterConfig(),
          > getFilterConfig(). We have an implementation for the Filter which also contains
          > a private method init(FilterCongig filterConfig).
          > In 7.0 javax.servlet.filter interface the methods are doFilter(), init(), destroy().
          > Because of the obvious reason i have a private implementation of init(FilterConfig
          > )in my code the build does not succeed. When i checked the java specifications
          > from Sun site I found 1.3.1 and 1.4(beta) specs provide doFilter(), init() and
          > destroy().
          > Question is: Is weblogic 6.1, JDK 1.3.1 compliant, if so why there is not init()
          > method in the filter interface??. (Otherwise its a bug)
          > Because of this the porting has become a serious issue as in some cases we need
          > to support both 6.1 and 7.0
          Dimitri

Help!.... XA error: using Weblogic 6.1 and Oracle 8.1.6

          Hi,
          I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
          to use Container Managed Transaction through a Session Bean.
          Connection Pool Settings: -------------------------
          Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
          TXDataSource Settings : -----------------------
          Name - myXADS
          JNDIName - myXADS
          PoolName - myXAPool
          Everything works fine but once in a while I get the following exception:
          java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
          in the transaction branch start() failed on resource 'myXAPool' Unexpected error
          during start for XAResource 'myXAPool': null
          The connection pool size is 30 and the number connections high reached was 5,
          which means there are enough connections in the pool available at all time.
          It would be really great if you can help me out.
          Thanks in Advance, Sudhir.


Hi Slava,
Sorry about that Oracle instance I am using is 8.1.7.
For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
And my Weblogic version 6.1 Sp3.
Thanks,
Sudhir.
"Slava Imeshev" <[email protected]> wrote:
Hi Sudhir,
Are you using an instance of 8.1.6 or 8.1.7? In the message header you
say
8.1.6.
Regards,
Slava Imeshev
"Sudhir Babu" <[email protected]> wrote in message
news:[email protected]..
Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured
in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reachedwas
5,
which means there are enough connections in the pool available at alltime.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

XA error: using Weblogic 6.1 and Oracle 8.1.6

Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
in the transaction branch start() failed on resource 'myXAPool' Unexpected error
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reached was 5,
which means there are enough connections in the pool available at all time.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

Hi Slava,
Sorry about that Oracle instance I am using is 8.1.7.
For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
And my Weblogic version 6.1 Sp3.
Thanks,
Sudhir.
"Slava Imeshev" <[email protected]> wrote:
Hi Sudhir,
Are you using an instance of 8.1.6 or 8.1.7? In the message header you
say
8.1.6.
Regards,
Slava Imeshev
"Sudhir Babu" <[email protected]> wrote in message
news:[email protected]..
Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured
in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reachedwas
5,
which means there are enough connections in the pool available at alltime.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

WebLogic 10.3 and JDK 1.5

Similar Messages

Maybe you are looking for