Help Connecting Weblogic to Oracle.

Hello,
We are encountering some error to connect weblogic at start up to
oracle 8i on a Solaris box. I have attached an error log file for the
same. The Error is something to do with ORA-24327.
The Fact is I am able to connect to oracle from NT Weblogic server,
NT SQL, SVRMGRL . But when I try to connect to oracle from Solaris
WebLogic I get this Error.
Thanks in advance for the help.
[weblogic.log]

According to our jdbc engineer:
ORA-24327 ("need explicit attach before authenticating a user")
First, this is not one of our error codes. Its one of OCI's many ways of telling you it
could not connect for some unknown reason. Unfortunately, this generally doesn't help
solve the problem. Currently, I'm aware of
two things that might cause this problem:
1. Oracle client DLL/SO is not compatable with Oracle server or Oracle client
installation. The former is a limitation of oracle that we can't do anything about.
The latter often implies an installation problem or conflict with some other installed
software. For example, some Oracle applications will install the OCI DLL in your path
(most
often in the windows system directory), thinking that its being helpful.
Unfortunately, if your ORACLE_HOME is pointing to a different version of oracle, this
will screw you. So if you get this error, one thing to check whether you have an old
version of OCI (OCI.DLL and/or OCIW32.dll) somewhere in your path.
2. More recently, I've learned that this error can also occur if your tnsnames.ora
does not have a reference to the service you are trying to access.
Hope this helps
--Kumar
Sheshadri Yagati wrote:
Hello,
We are encountering some error to connect weblogic at start up to
oracle 8i on a Solaris box. I have attached an error log file for the
same. The Error is something to do with ORA-24327.
The Fact is I am able to connect to oracle from NT Weblogic server,
NT SQL, SVRMGRL . But when I try to connect to oracle from Solaris
WebLogic I get this Error.
Thanks in advance for the help.
Name: weblogic.log
weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
Encoding: base64

Similar Messages

Help: Connecting to Personal Oracle 9i

I'm developing a web site that is going to use an Oracle database.
For that purpose I installed Microsoft Personal Web Server, and Personal Oracle 9i on a Windows 98.
I created a database using SQLPlus, but I can't connect to the database. I can't even create an ODBC connection.
The error message I get is ORA-12541. (no listener).
I am under the impression that the Personal Oracle doesn't work with a listener, is that right? What can I do in order to access the database from my client application?
Thanks ahead,
Fernando Cachicas.

The database listener usually runs as a service, but you can manually start it. Go to the bin directory of the DB and type:
"lsnrctl start"

Connecting to aa Oracle Server Using Power Query

Hi
Just got started with Power Query,
I want to get connected to the remote Oracle Server, which is used as DB by our Internal Ticketing system.
Can Any one let me know how can I get connected to Oracle Server. I had gone through some documentation from below link
http://office.microsoft.com/en-us/excel-help/connect-to-an-oracle-database-HA104019815.aspx?CTT=5&origin=HA104003952
and downloaded the "instantclient-basic-windows.x64-12.1.0.1.0" from Oracle Site too.
Can some one guide me on how to proceed further.
Regards
Surya

Any ideas for Surya?
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Needed help on connecting weblogic 8.1 SP5 with oracle 10g and mysql 5.0

Hi !!
Hope you are doing well...
Can anyone tell me how to connect weblogic 8.1 SP5 with an oracle 10g DB on windows..
also, how to connect weblogic 8.1 SP5 with mysql 5.0 on windows..
Please step by step... very urgent..
Thanks!! Jhonson

Shouldn't this be posted in BEA forums?
Try getting help there and if you encounter any Oracle related exception, you can post here.

Help in creating the connection pool for Oracle 8i using Jdriver

Hi
Iam pretty new to Weblogic and would be greatfull if some one can help me
out in finding the parameters to be specified in Weblogic console for creating
a Connection pool for Oracle 8i database running on solaris. I have installed
necessary client libraries in weblogic machine.
The details for my database are as follows
database name : mydb
database server : 173.24.24.1
database port : 1521
username : myuser
I would appreciate if you can provide me the following details to be entered in
weblogic console for creating the connection pool
URL
DRIVER CLASS NAME
PROPERTIES
ACL NAME
PASSWORD
Thanks,
S Hari

Hari
Jdbc Connection Pool Configuration
URL= jdbc:weblogic:oracle
DRIVER CLASS NAME=weblogic.jdbc.oci.Driver
PROPERTIES
user=myuser
password=<password in mydb>
server=mydb
After configuring Connection Pool Select Targets tab. Select Server from Available
to Chosen.
Deepak
Hari wrote:
Hi
Iam pretty new to Weblogic and would be greatfull if some one can help me
out in finding the parameters to be specified in Weblogic console for creating
a Connection pool for Oracle 8i database running on solaris. I have installed
necessary client libraries in weblogic machine.
The details for my database are as follows
database name : mydb
database server : 173.24.24.1
database port : 1521
username : myuser
I would appreciate if you can provide me the following details to be entered in
weblogic console for creating the connection pool
URL
DRIVER CLASS NAME
PROPERTIES
ACL NAME
PASSWORD
Thanks,
S Hari

Help connection to oracle db using jdbc

Hi
I am trying to connect to a oracle database. I am using Oracle 9 and jsdk 1.4.2. but i keep getting the following error and i dont know what iam doing wrong.
I have put in my classpath where the orcle drivers are. I have also tried puting the drivers in j2sdk/jre/lib folder (files copied nls_charset12.zip,classes12.zip,ojdbc14.jar). My code compiles and runs but the error i get is
"java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver"
SAMPLE of my code:
Class.forName("oracle.jdbc.driver.OracleDriver");
String dataSource = "jdbc:oracle:thin:@devflgdb";
Connection con = DriverManager.getConnection(dataSource,"babu_s2","babu_s2");

I am working on the same; here is my servlet code, hope it helps
private static void loadJDBCDriver ()
System.out.println ("Loading Database driver...");
try {
DriverManager.registerDriver ( new oracle.jdbc.driver.OracleDriver());
catch (Exception e) {}
try {
DriverManager.registerDriver ( new sun.jdbc.odbc.JdbcOdbcDriver() );
catch (Exception e2) {
System.err.println ("loadJDBCDriver: " + e2.toString());
return;
System.out.println ("Database driver loaded...");
private static Connection getConnected () {
System.out.println ("Establishing database connection...");
String jdbc_url;
Connection conn;
try {
jdbc_url = "jdbc:oracle:thin:@localhost:1521:oracle";
conn = DriverManager.getConnection (jdbc_url, "scott", "tiger");
catch (Exception e) {
try {
jdbc_url = "jdbc:odbc:BookNook";
conn = DriverManager.getConnection (jdbc_url);
catch (SQLException e2) {
System.err.println ("getConnected: " + e2.toString() );
return null;
System.out.println ("Database connection established ...");
return conn;

Help connecting to Oracle via ADODB in MS Access 2003

I'm attempting to use vb within Microsoft Access to return a recordset.
I can connect, but I when I execute my select statement, I get the following message:
Run-time error '-2147217865 (80040e37)':
[Microsoft][ODBC driver for Oracle][Oracle]ORA-00942: table or view does not exist.
I've doublechecked the tablename in the select statement, and it is good. I've run the select statement directly from Access - using a linked table within Oracle, and it runs fine.
I'm using Oracle Net Manager 10.2.0.0.0, and my ODBC driver is "Oracle in OraClient10g_home1" My OS is XP SP2
Here is the connection (details obscured) info I'm using: Note. I don't get the error until I open the recordset.
strConnect = "Driver={Microsoft ODBC for Oracle};Server=myoradb;Uid=userid;Pwd=pass;"
sql = "select * from TABLE where SOMETEXTFIELD='sometextvalue'"
Set conn = CreateObject("ADODB.Connection")
Set rsSizing = CreateObject("ADODB.Recordset")
conn.open strConnect
rsSizing.open sql, conn, 3, 1
Any help would be much appreciated,
Joe

962228 wrote:
At our College, we have a server with Oracle installed and 33 clients connecting to the Oracle database on the server. This semester, for whatever reason, we're having an issue linking from MS Access 2013 (32-bit) to the Oracle database. We create the link and it seems to work fine after entering username and password (we are using the 32 bit ODBC drivers). However, when we connect, the window that shows the available tables to link to shows no tables. Its' completely blank. We can see the tables through the database side, and the drivers *seem* to be ok . . . has anyone seen this before? We're new to Oracle and are not sure what the problem could be. Any help is greatly appreciated. Thank you!
I know this probably isn't much help, but many years ago I was faced with an issue that sounded somewhat similar. User department had an Access application. The .mdb file was on a file server, so everyone in the department was using the same file .. not indivdual copies that could have diverged. Desktop PC configuration was tightly controlled by IT, so assumed the same for each. Even though all seemed to connect to the Oracle db, some saw data and other saw "????". Connection to the Oracle db was via ODBC. In the end, the only solution we came up with was to configure some users with the Oracle ODBC driver and others with the MS ODBC for Oracle.

JDBC connect to remote Oracle, IOException,Help!

I am trying to connect to remote Oracle 8.1.6 resides on IBM AIX server, the oracle SID is correct, and ping host address is also successful. also, downloaded JDBC driver classes12.zip from oracle...but i still encounter the IOException: Network adapter cannot establish connection!...could anyone tell me how to test whether the oracle's listener works...?
i also tried to run the following piece of code on that IBM server, changed the host address to 'localhost', but still, the IOExcetpion:Network adapter cannot establish connection!...why? cos i am running the code on the server where Oracle resides.....
great appreciation for anyone replies me.....the code is here:
import java.io.*;
import java.sql.*;
import java.text.*;
import oracle.jdbc.driver.*;
public class viewtable
Connection con;
Statement st;
public viewtable (String args[]) throws ClassNotFoundException,FileNotFoundException,IOException,SQLException
url="jdbc:oracle:thin:system/manager@IP:1521:SID";
Class.forName ("oracle.jdbc.driver.OracleDriver");
try
con=DriverManager.getConnection(url);
st = con.createStatement ();
doexample ();
st.close ();
con.close ();
}catch(SQLException e)
System.err.println(e.getMessage());
public void doexample () throws SQLException
ResultSet rs = st.executeQuery("select * from sales");
if(rs!=null) {
while(rs.next())
int a = rs.getInt("no"); System.out.println("NO = "+a);
rs.close();
public static void main (String args[])
System.out.println ("Oracle Exercise 1 \n");
try
viewtable test = new viewtable(args);
} catch (Exception ex)
System.err.println ("Exception caught.\n"+ex);
ex.printStackTrace ();

with an RS/6000, don't you have a db admin ? he/she should know how to set up the listener properly.
if you have to do it on your own, try the following things:
- www.orafaq.com is often very helpful
- search the web for "oracle listener" etc. A first goolg search gave me the following link: http://www.ibiblio.org/mdw/HOWTO/Oracle-7-HOWTO.html
- check the files listener.ora and tnsnames.ora. They should be located somewhere in your oracle home direcotry on the server
good luck
PS: to start a listenter, type "startup" in the lsnrctl tool, maybe you can already see something.

Need help connecting to Oracle 8i db

I'm trying to build a very simple jsp page that connects to a Oracle 8i schema I already have.
Here's the entry in the data-sources.xml for the project:
<native-data-source name="jdev-connection-native-VacationTest" jndi-name="jdbc/VacationTestCoreDS" url="jdbc:oracle:thin:@xxxxxx:1521:ORCL" user="xxxxx" password="xxxx" data-source-class="oracle.jdbc.pool.OracleDataSource"/>
In the Index.jsp page I have:
<sql:query var="adminQuery" dataSource="jdbc/VacationTestCoreDS"
sql="select * from persons where type=\'Admin\'"/>
I have this defined in my web.xml file:
<resource-ref>
<res-ref-name>jdbc/VacationTestCoreDS</res-ref-name>
<res-type>oracle.jdbc.driver.OracleDriver</res-type>
<res-auth>Container</res-auth>
</resource-ref>
When I run the application, I get the error below which I have not been able to resolve. I have also tried the jdev-connection-managed source but the application couldn't find the jndi definition. Any ideas on what could be causing this problem?
thanks
Ash
500 Internal Server Error
java.lang.NullPointerException
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.connector.ApplicationConnectionManager.getOracleConnectionManager(ApplicationConnectionManager.java:304)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.administration.ApplicationResourceFinder.getJCAConnectionResource(ApplicationResourceFinder.java:455)
     at com.oracle.naming.J2EEContext.addResourceEntries(J2EEContext.java:743)
     at com.oracle.naming.J2EEContext.create(J2EEContext.java:81)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.getEnvironmentContext(HttpApplication.java:6797)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.ApplicationContext.getEnvironmentContext(ApplicationContext.java:365)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.ApplicationContext.lookupInJavaContext(ApplicationContext.java:318)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:234)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.ApplicationContext.lookup(ApplicationContext.java:199)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at org.apache.taglibs.standard.tag.common.sql.DataSourceUtil.getDataSource(DataSourceUtil.java:72)
     at org.apache.taglibs.standard.tag.common.sql.SetDataSourceTagSupport.doStartTag(SetDataSourceTagSupport.java:91)
     at index.jspService(_index.java:50)
     [index.jsp]

I still haven't solved this; but I understand that I need to use the managed pool connection (jdbc/VacationTestDS) and this is defined in the workspace-data-source.xml file
However, when I run the application, I now get this error:
WARNING J2EE JNDI0002 Resource reference jdbc/VacationTestDS not found. Allowing J2EEContext creation to continue anyway.
Is there nobody who has seen this problem before?

Please help, probleme de connection to database oracle and java

Ihave a problem to make connection to database Oracle when I use a simple code of java
======================
import java.sql.*;
public class Exemple1 {
public static void main (String args[]) {
Statement stmt = null;
Connection con=null;
try {
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
con = DriverManager.getConnection ("jdbc:oracle:thin:@localhost:1521:GB","scott","tiger");
catch (Exception e) { System.out.println(e); }
=================
I have :
* Linux (Fedora core3).
* Oracle 10g
My var. environ.:
* ORACLE_HOME=/u01/app/oracle/product/10.1.0/Db_1
* PATH=$ORACLE_HOME/bin
* CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc14.jar
the error is:
Exception in thread "main" java.lang.NoClassDefFoundError: while resolving class: oracle.sql.CharacterSet
at java.lang.VMClassLoader.resolveClass(java.lang.Class) (/usr/lib/libgcj.so.5.0.0)
at java.lang.Class.initializeClass() (/usr/lib/libgcj.so.5.0.0)
at JvResolvePoolEntry(java.lang.Class, int) (/usr/lib/libgcj.so.5.0.0)
at oracle.jdbc.driver.DBConversion.DBConversion(short, short, short) (Unknown Source)
at oracle.jdbc.driver.T4CConnection.connect(java.lang.String, java.util.Properties) (Unknown Source)
at oracle.jdbc.driver.T4CConnection.logon() (Unknown Source)
I don't know what's heppen exactly?

If
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
is replaced
with
Class.forName("oracle.jdbc.driver.OracleDriver");does the java.lang.NoClassDefFoundError: while resolving class: oracle.sql.CharacterSet get generated?

Help - Could not load 'oracle.jdbc.driver.OracleDriver ...

I'm using oci8 to connect to the Oracle database.
URL: jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(PORT=1527)(HOST=testhost)))(CONNECT_DATA=(SID=fnoe2pa)))
When I tried to start the weblogic server, I got the following errors:
Can you suggest what I should do next (step-wise)??? Thanks, Bobby
<Sleeping in createResource()>
####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001060> <Cannot startup connection pool
"pool/test_myapp" weblogic.common.ResourceException:
Could not load 'oracle.jdbc.driver.OracleDriver
If this is a type-4 JDBC driver, it could occur if the JDBC
driver is not in the system CLASSPATH.
If this is a type-2 JDBC driver, it may also indicate that
the Driver native layers(DBMS client lib or driver DLL)
have not been installed properly on your system
or in your PATH environment variable.
This is most likely caused by one of the following:
1. The native layer SO, SL, or DLL could not be found.
2. The file permissions on the native layer SO, SL, or DLL
have not been set properly.
3. The native layer SO, SL, or DLL exists, but is either
invalid or corrupted.
For more information, read the installation documentation
for your JDBC Driver, available from:
http://e-docs.bea.com
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:212)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
     at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:705)
     at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
     at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:650)
     at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy31.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy42.start(Unknown Source)
     at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
     at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
     at weblogic.management.Admin.finish(Admin.java:644)
     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
     at weblogic.Server.main(Server.java:35)
>
####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001082> <Creating Data Source named
jdbc/test_myapp for pool pool/test_myapp>
####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001070> <Checking existence of connection pool
pool/test_myapp requested by user system>
####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001059> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbc/test_myapp) can't
be created with non-existent Pool (connection or multi)
(pool/test_myapp)>
####<15/08/2002 14:09:50> <Info> <EJB> <qawebmethods> <myserver>
<main> <system> <> <010008> <EJB Deploying file: myapp-ejb.jar>
####<15/08/2002 14:09:50> <Warning> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160007> <You are running WebLogic Server with J2EE
1.3 features enabled. The implementation of specific J2EE 1.3 features
(EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
in BEA WebLogic Server 6.1 is of a non-final version of the
appropriate specification. It is subject to change in future releases
once the specification becomes finalized. This may cause application
code developed for BEA WebLogic Server 6.1 that uses the new features
of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
future releases of BEA WebLogic Server.>
####<15/08/2002 14:09:59> <Error> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160001> <Error deploying application myapp-ejb:
Unable to deploy EJB: Counter from myapp-ejb.jar:
The DataSource with the JNDI name: jdbc/test_myapp could not be
located. Please ensure that the DataSource has been deployed
successfully and that the JNDI name in your EJB Deployment descriptor
is correct.
>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101053> <[HTTP myserver] Loading web app: myapp>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101059> <[myserver] Loading myapp from WAR file:
C:\bea\wlserver6.1\.\config\mydomain\applications\.wlnotdelete\wlap31483\myapp.war>
####<15/08/2002 14:09:59> <Warning> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160007> <You are running WebLogic Server with J2EE
1.3 features enabled. The implementation of specific J2EE 1.3 features
(EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
in BEA WebLogic Server 6.1 is of a non-final version of the
appropriate specification. It is subject to change in future releases
once the specification becomes finalized. This may cause application
code developed for BEA WebLogic Server 6.1 that uses the new features
of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
future releases of BEA WebLogic Server.>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101031>
<[WebAppServletContext(1412030,myapp,/myapp)] extracting classfiles to
C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp:>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101032>
<[WebAppServletContext(1412030,myapp,/myapp)] extracted classfiles
successfully...>
####<15/08/2002 14:10:04> <Info> <HTTP Session> <qawebmethods>
<myserver> <main> <system> <> <100037> <Creating SessionContext of
type: memory for webapp: /myapp>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering classpath
servlet with initArgs 'null'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering getior
servlet with initArgs 'null'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering tunneling
servlets with initArgs 'wl-dispatch-policy=direct'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering JSPServlet
with initArgs '[JspConfig:
verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp,pageCheckSeconds=1,superclass=null,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
####<15/08/2002 14:10:04> <Debug> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101097> <Registering ServletContext:
"myapp:/myapp">
####<15/08/2002 14:10:04> <Info> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160003> <Deployed : myapp>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101133> <Initializing WEB server myserver>
####<15/08/2002 14:10:04> <Notice> <Management> <qawebmethods>
<myserver> <main> <system> <> <141052> <Application Poller started for
development server.>
####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <ListenThread> <system> <> <000202> <ListenThread listening
on port 7001>
####<15/08/2002 14:10:04> <Info> <NT Performance Pack> <qawebmethods>
<myserver> <ListenThread> <system> <> <000000> <NATIVE: NTSocketMuxer
was built on Nov 1 2001 16:39:28
>
####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <SSLListenThread> <system> <> <000202> <SSLListenThread
listening on port 7002>
####<15/08/2002 14:10:05> <Notice> <Management> <qawebmethods>
<myserver> <main> <system> <> <141030> <Starting discovery of Managed
Server... This feature is on by default, you may turn this off by
passing -Dweblogic.management.discover=false>
####<15/08/2002 14:10:05> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <main> <system> <> <000331> <Started WebLogic Admin Server
"myserver" for domain "mydomain" running in Development Mode>
####<15/08/2002 14:10:11> <Info> <NT Performance Pack> <qawebmethods>
<myserver> <ExecuteThread: '14' for queue: 'default'> <> <> <000000>
<Allocating: '2' NT reader threads>
####<15/08/2002 14:10:13> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)] actions:
init>
####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)]
FileServlet: init>
####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)]
FileServlet: Using standard I/O>

"thorick" <[email protected]> wrote in message news:<[email protected]>...
Most likely, the OCI libraries could not be loaded.
Before continuing down this path, is there any reason
why you want to use an OCI based Driver as opposed to the
all Java Oracle thin driver ?There is indeed a valid reason for my choice.
I am currently connecting to the Oracle "Rdb" 7.0 database (located on
VMS) - not Oracle Oracle.
The SQL Service software we're currently using is version 7.1. This
version works well with the OCI8 driver (when connecting to the
database from Windows NT). This version of SQL Service however does
NOT work for the THIN driver (unless we upgrade the SQL Service to
version 7.1.5.5 - which we're not prepared to do so because it is not
stable enough from our previous test/trials). SQLSRV Version 7.1.5.5
works for THIN driver but it will result in uncommitted
transactions/unresolved connection/stopping of listener issues and
there is a need to restart the service from time to time. Oracle has
since confirmed that this is a bug that they have yet to resolve...
So we have to stick to OCI8 (THICK) for the time being. I would really
appreciate it very much if you can tell me the various OCI libraries
that I need to load (in terms of WebLogic Server config file settings
etc..).
By the way I have already installed the Oracle 8 client software on
the NT server (where WebLogic Server is) and I have also set up the
relevant SID (using the Net8 Assistant) that points to the Oracle Rdb
database on the VMS. I have also tried using SQL*Plus to connect to
the database and I can connect properly to the database. But WebLogic
simply doesn't seem to load the software.
Help...
Regards,
Bobby Brown, writing from Australia.

Unable create Connection pool for Oracle apps Adapter.

Hi All,
We are trying to create a connection pool for Oracle Apps adapter in 11G SOA suite.
However during the process getting the following error:
An error occurred during activation of changes, please see the log for details.
A <jndi-name> is specified for the resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is specified in ra.xml
Can any one help us on this.
Thanks
Parker.

Please refer section "Configuring Connection Information" at below link -
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10537/T430238T430340.htm#T464886
Regards,
Anuj

How to connect weblogic 8.1 to IBM MQ Series from remote machines?

Hi,
          I am trying to connect WebLogic 8.1 to IBM MQ Series 6.0 both are running in a seperate machines.Can we do using JNDI services? Can anyone help me to fix this issue?

I'm cutting/pasting my notes on the topic, including MQ specific notes. Start with the Integrating Remote JMS Providers FAQ (link below). You can also search this newsgroup for answers.
          Tom
          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 and http://e-docs.bea.com/wls/docs81/faq/interop.html
          Integration with 8.1 Details
          To start, first read the "Integrating Remote JMS Providers FAQ" (released in Dec 2004) at:
          http://e-docs.bea.com/wls/docs81/faq/interop.html
          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 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, but you may want to refer to the "Using Foreign JMS Providers With WLS" white-paper mentioned below, which is 7.0 specific but contains specific examples of configuring non-WebLogic JMS vendors. See also notes on "MQ" 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 and supported on more platforms, WL supports access via the standard IIOP protocol. 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 the client. These operation 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 are 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 (older version)
          http://xa-compliant-oracleaq.projects.dev2dev.bea.com (newer version)
          Caveats:
          It may be that 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".
          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

Wls:/offline connect('weblogic','welcome1','t3://applfs3:7001')

Hi All,
When I am connecting from WLST then i am getting below error
connect('weblogic','welcome1','t3://applfs3:7001')
jar;D:\PRODUC~1\Oracle\WLS\WLSERV~1.3\common\derby\lib\derbynet.jar;D:\PRODUC~1\Oracle\WLS\WLSERV~1.3\common\derby\lib\derbyclient.jar;D:\PRODUC~1\Oracle\WLS\WLSERV~
1.3\common\derby\lib\derbytools.jar;;
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> connect('weblogic','welcome1','t3://applfs3:7001')
Connecting to t3://applfs3:7001 with userid weblogic ...
Traceback (innermost last):
File "", line 1, in ?
File "", line 22, in connect
File "", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://applfs3:7001
Use dumpStack() to view the full stacktrace
wls:/offline> connect('weblogic','welcome1','t3://10.100.4.16:7001')
Connecting to t3://10.100.4.16:7001 with userid weblogic ...
Traceback (innermost last):
File "", line 1, in ?
File "", line 22, in connect
File "", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://10.100.4.16:7001
Use dumpStack() to view the full stacktrace
wls:/offline> connect('weblogic','welcome1','t3://applfs3:7001')
Connecting to t3://applfs3:7001 with userid weblogic ...
Traceback (innermost last):
File "", line 1, in ?
File "", line 22, in connect
File "", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://applfs3:7001
Use dumpStack() to view the full stacktrace
wls:/offline> dumpStack()
This Exception occurred at Tue Jun 25 16:27:13 AST 2013.
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://applfs3:7001: Destination unreachable; nested exception is:
        java.net.ConnectException: Connection refused: connect; No available router to destination]
        at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
        at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
        at weblogic.jndi.Environment.getContext(Environment.java:315)
        at weblogic.jndi.Environment.getContext(Environment.java:285)
        at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
        at javax.naming.InitialContext.init(InitialContext.java:223)
        at javax.naming.InitialContext.(InitialContext.java:197)
        at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:520)
        at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:573)
        at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:313)
        at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
        at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
        at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.python.core.PyReflectedFunction.__call__(Unknown Source)
        at org.python.core.PyMethod.__call__(Unknown Source)
        at org.python.core.PyObject.__call__(Unknown Source)
        at org.python.core.PyObject.invoke(Unknown Source)
        at org.python.pycode._pyx66.connect$1(:16)
        at org.python.pycode._pyx66.call_function()
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyFunction.__call__(Unknown Source)
        at org.python.pycode._pyx71.f$0(:1)
        at org.python.pycode._pyx71.call_function()
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyCode.call(Unknown Source)
        at org.python.core.Py.runCode(Unknown Source)
        at org.python.core.Py.exec(Unknown Source)
        at org.python.util.PythonInterpreter.exec(Unknown Source)
        at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
        at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
        at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
        at weblogic.management.scripting.WLST.main(WLST.java:173)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at weblogic.WLST.main(WLST.java:29)
Caused by: java.net.ConnectException: t3://applfs3:7001: Destination unreachable; nested exception is:
        java.net.ConnectException: Connection refused: connect; No available router to destination
        at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
        at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
        at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
        at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
        ... 43 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
        java.net.ConnectException: Connection refused: connect; No available router to destination
        at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
        at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
        at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
        at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
        at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
        at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
        at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
        at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
        at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
        at weblogic.jndi.Environment.getContext(Environment.java:315)
        at weblogic.jndi.Environment.getContext(Environment.java:285)
        at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
        at javax.naming.InitialContext.init(InitialContext.java:223)
        at javax.naming.InitialContext.(InitialContext.java:198)
        at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:520)
        at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:573)
        at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:315)
        at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
        at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:62)
        at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:148)
        ... 30 more
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://applfs3:7001: Destination unreachable; nested exception is:
        java.net.ConnectException: Connection refused: connect; No available router to destination]
wls:/offline>wls:/offline>
Thanks and Regards
Maroof

Hi Maroof,
"There is no server running at t3://applfs3:7001"
This error comes when you try to connect to a server which is not running or down.
Please ensure that your Admin server is up and running for applfs3:7001 and then try to connect using WLST.
Thanks,
Vivek Vishal

Error connecting weblogic server 10.3.6.0 64bits

Hello
I installed weblogic server 10.3.6.0 64bits on windows server 2008 R2 64bits.
I have jdeveloper 11.1.1.7.0 installed on client machines which are xp pro 32bits and win 7 32bits.
When I try to connect weblogic server from jdeveloper it is giving me network error as below: Test failed: IO Error: The Network Adapter could not establish the connection
Although I can see this 64bits server from this machine and share server's hard disk too.
Need help in this regard.
Regards,
Masood
Edited by: Masood on Jun 3, 2013 3:40 AM

Hii,
No resources currently available in pool ePayBatchDS to allocate to applications.
This exception cleaarly shows the connection are not available to allocate to ePayBatchDS datasource.
As you said there are altogether 7 data source out which six are working and one is not.
In general if you are creating a datasource and providing a connection pool size we should consider the number of connection available or allowed at the database side as well.
Please cross check at the DB side the number of connection available and based on that try to tune the connection pool size in your data sources.
Regards,
Abdul

Help Connecting Weblogic to Oracle.

Similar Messages

Maybe you are looking for