At startup: "Unable to resolve weblogic.jdbc.connectionPool"

WLS 6.0 SP1 on Solaris 8
Oracle 8.1.7 using JDBC Thin driver from Oracle.
At startup of WebLogic, just after WLS creates the pool, I get a JNDI
NameNotFoundException, as shown below.
However, this does not seem to cause any problems for us.
####<Jun 20, 2001 10:16:17 AM GMT+10:00> <Info> <JDBC Pool ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool: 'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 20, 2001 10:16:20 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:21 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:22 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:23 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <Adapter> <pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[-4918694186591914732S:192.168.0.52:[7001,7001,7002,7002,7001,7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@1fea8a>
javax.naming.NameNotFoundException: Unable to resolve
weblogic.jdbc.connectionPool Resolved: 'weblogic' Unresolved:'jdbc' ;
remaining name 'connectionPool'
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
at
weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNamingNode_WLSkel.java:230)

Just installed SP2 on top of WebLogic Server 6.0 SP1.
I still get the same message in weblogic.log while it was starting up:
####<Jun 28, 2001 12:53:00 PM GMT+10:00> <Info> <WebLogicServer>
<pssydsun01> <myserver> <main> <> <> <000000> <IIOP subsystem enabled.>
####<Jun 28, 2001 12:53:10 PM GMT+10:00> <Info> <WebLogicServer>
<pssydsun01> <myserver> <main> <system> <> <000214> <WebLogic Server (6.0
Service Pack 2 05/24/2001 11:55:28 #117037) "myserver"
(c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000 BEA Systems, Inc.>
####<Jun 28, 2001 12:53:23 PM GMT+10:00> <Info> <JDBC Pool ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool: 'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 28, 2001 12:53:26 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:27 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:28 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:29 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:30 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:30 PM GMT+10:00> <Info> <Adapter> <pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[7126974831161186990S:192.168.0.52:[7001,7001,7002,7002,7001,7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@504ec1>
javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved: ''
Unresolved:'jdbc' ; remaining name ''
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
Daniel Hoppe wrote:
Hi,
it's a problem in SP1, doesn't seem to cause any harm. Afaik it's fixed
in RP1 and in SP2
Daniel
-----Urspr?ngliche Nachricht-----
Von: Jesus M. Salvo Jr. [mailto:[email protected]]
Bereitgestellt: Mittwoch, 20. Juni 2001 02:17
Bereitgestellt in: jndi
Unterhaltung: At startup: "Unable to resolve
weblogic.jdbc.connectionPool"
Betreff: At startup: "Unable to resolve weblogic.jdbc.connectionPool"
WLS 6.0 SP1 on Solaris 8
Oracle 8.1.7 using JDBC Thin driver from Oracle.
At startup of WebLogic, just after WLS creates the pool, I get a JNDI
NameNotFoundException, as shown below.
However, this does not seem to cause any problems for us.
####<Jun 20, 2001 10:16:17 AM GMT+10:00> <Info> <JDBC Pool
ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool:
'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 20, 2001 10:16:20 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:21 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:22 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:23 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <Adapter>
<pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[-4918694186591914732S:192.168.0.52:[7001,7001,7002,7002,7001,
7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@1fea8a>
javax.naming.NameNotFoundException: Unable to resolve
weblogic.jdbc.connectionPool Resolved: 'weblogic' Unresolved:'jdbc' ;
remaining name 'connectionPool'
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundExceptio
n(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingN
ode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamin
gNode.java:129)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
at
weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNaming
Node_WLSkel.java:230)

Similar Messages

JMS Unable to resolve 'weblogic.jms.TempDestinationFactory' error!

          We are running an application within the Weblogic 7.x EJB Framework. While trying
          to connect to the application from our GUI I get the following error. **... Unable
          to resolve 'weblogic.jms.TempDestinationFactory' Resolved: 'weblogic.jms' Unresolved:'TempDestinationFactory'
          ; We have configured our JMS server with two topics - one of which is used for
          persistent storage (i.e has the 'store' configuration attribute set to TRUE).
          Also we have configured NO stores but a JDBC Tx DataSource.
          I would appreciate any suggestions.
          **see attached picture**
          [confui2.jpg]


In order to use WLS JMS temporary destinations, you have to have a temporary destination template configured for
          the JMS server.
          Dongbo
          Puneet Bhatia wrote:
          > We are running an application within the Weblogic 7.x EJB Framework. While trying
          > to connect to the application from our GUI I get the following error. **... Unable
          > to resolve 'weblogic.jms.TempDestinationFactory' Resolved: 'weblogic.jms' Unresolved:'TempDestinationFactory'
          > ; We have configured our JMS server with two topics - one of which is used for
          > persistent storage (i.e has the 'store' configuration attribute set to TRUE).
          > Also we have configured NO stores but a JDBC Tx DataSource.
          > I would appreciate any suggestions.
          >
          > **see attached picture**
          >
          > ------------------------------------------------------------------------
          > Name: confui2.jpg
          > confui2.jpg Type: JPEG Image (image/pjpeg)
          > Encoding: base64

Unable to resolve 'weblogic.messaging.dispatcher.S:null'

We have a WLS 10.3 cluster with 1 admin server and 2 managed servers. Each managed server hosts JMS queues so we have a distributed queue environment. Applications periodically report an issue that prevents messages from being dropped onto the queues. The frequency of the issue is weekly and sometimes multiple times during the week. We have found that un-targeting and re-targeting the JMS Servers seems to resolve the problem (at least in the short term). The message producer applications are using the weblogic.jar and an xa connection factory. I've included the stack trace below. I'm hoping that someone can help uncover the root cause of the issue.
Stack Trace:
Caused by: weblogic.jms.common.JMSException: No failover destination.
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1275)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:783)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:597)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:574)
at org.springframework.jms.core.JmsTemplate$4.doInJms(JmsTemplate.java:551)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:471)
... 8 more
Caused by: weblogic.jms.common.JMSException: No failover destination.
at weblogic.jms.frontend.FEProducer.pickNextDestination(FEProducer.java:750)
at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1092)
at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server null
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
at weblogic.jms.frontend.FEProducer.findDispatcher(FEProducer.java:825)
at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:995)
... 9 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:null'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:null'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
... 14 more

Hi,
I would suggest you to go through these 2 links which you give all the details about UDD
Topic:Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
http://middlewaremagic.com/weblogic/?p=3747
Topic:JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
http://middlewaremagic.com/weblogic/?page_id=1976
Tips to solve UDQ issues
- Make sure the Server Affinity Enabled parameter should be un-checked (disable) which under the [ Connection factory –> Configuration (tab) –> Load Balance (sub-tab)]
- Disable the Server Affinity Enabled parameter for the connection factory whish is been used by your UDQ.
- All the managed servers are in the same cluster.
- If the managed serves are in different boxes make sure the listing address is given correctly which is under [ Machine –> Configuration (tab) –> Node Manager (sub-tab) ]
- Test if you are able to PING the servers on different boxes and make sure that there is no network issues and you are able to communicate with the servers.
Hope this helps you.
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…

JNDI naming exception...unable to resolve 'weblogic.management.adminhome'

I'm able to start admin server and access admin console (web). When I try to connect to admin server from managed server using WLST, I'm getting the error "compatibility mbean server is not initialized properly....". I tried to ping admin server from managed server using WLST ping command (java weblogic.Admin -url xxxxx -username xxxx-password xxxx PING), I'm getting error "JNDI naming exception....unable to resolve 'weblogic.management.adminhome'".

In order to run it remotely, I need to manually export the EAR file from Eclipse, ftp to the remote server and deploy it to the managed server.
It seems that I missed some jar files in the managed server classpath. But, I don't know which.

Major performance problem in weblogic jdbc

I ran a test which selected ~1000 rows from an oracle database table. The
code ran in 4 seconds when I used the Oracle driver directly:
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection connection = DriverManager.getConnection(URL, "XXX", "XXX");
When I changed the code to get the connection from weblogic, it took 128
SECONDS!!!!
weblogic.jdbc.connectionPool.pointclick=\
url=jdbc:oracle:thin:@XXX:dev,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=1,\
maxCapacity=2,\
capacityIncrement=1,\
props=user=XXX;password=XXX
weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.pointclick=pointclick
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
Context context = new InitialContext(properties);
try
DataSource dataSource = (DataSource)context.lookup(NAME);
Connection connection = dataSource.getConnection();
// if(!autoCommit)
// connection.setAutoCommit(false);
return connection;
finally
context.close();
The strangest thing is that when I used the weblogic pool, if I executed
"select column from table" it took 128 seconds, but "select * from table"
only took 32 seconds. Why would it take longer to process less data?
And more importantly, why does the weblogic connection take so damn long?
Thanks for your help.
Sean Rohead

Hey, I finally managed to get JDBC logging up and running! Had to do with
permission setting, adding the following entry to weblogic.policy:
permission java.sql.SQLPermission "setLog";
Boy are you right; JDBC logging is slow as mud! Good thing we use BMP
entity beans, so I guess I can log JDBC calls myself in the
ejbCreate/Load/Store/Remove hooks!
Gene Chuang
Teach the world. Join Kiko!
http://www.kiko.com/profile/join.jsp?refcode=TAF-gchuang
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
>
>
Gene Chuang wrote:
Hey, I've tried setting weblogic.jdbc.enableLogFile=true before and
can't
even get the server to start up! Since JDBC logging is not only slow,but
buggy,JDBC logging is slow for the reasons described, but not buggy as such.
is there a possibility Weblogic can implement a JDBC log for a future
release?
Seems like Weblogic can catch SQL calls much easier than we can,
especially for CMP!It is conceivable that our pool drivers (pool,jts,rmi etc) couldindependently
log SQL for debugging purposes, but we need to retain the semantics ofturning
on jdbc logging, which in any case will continue to emanate from any JDBCdriver.
In any case, we wouldn't do anything differently that DriverManager doesfor
simply writing to a file, which would be serialized by the stream anyway.
Joe
Gene Chuang
Teach the world. Join Kiko!
http://www.kiko.com/profile/join.jsp?refcode=TAF-gchuang
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
Sean Rohead wrote:
OK, disregard everything I said in my last post. The REAL reason
for
the
slowdown is that I had "weblogic.jdbc.enableLogFile=true" in my
weblogic.properties. So, there is nothing wrong with the JNDIDataSource
object. Sorry if I misled anyone.
Still, it does seem rather excessive for logging to cause a 30Xslowdown.
Someone at BEA ought to take a closer look at that...Known issue, not ours.
JDBC logging collect anything logged by any JDBC driver or by anySQLException.
These all call DriverManager.println() which is class synchronized in
the
JVM,
so this will serialize most JDBC threads, and slow the server down a
lot,
independently of the disk I/O needed to grow the file.
Joe
Sean Rohead
"Sean Rohead" <[email protected]> wrote in message
news:[email protected]...
Nice work, Charlie!
When I just connected to the pool directly, it ran fine. I am
guessing
that
the DataSource returns a connection that connects first to the
server
via
RMI and then to the database. I am trying to obtain a JDBC
connection
for
use in EJB and servlets, so this is clearly overkill. The
question I
now
have is what is the best way to obtain a transactional
connection
without
the overhead described above? Can I somehow create a
transactional
DataSource that doesn't go over RMI? Or, should I just use thejts
driver
directly? I tried the following code, but got an error:
Driver driver = new weblogic.jdbc.jts.Driver();
Properties properties = new Properties();
properties.put("connectionPoolID", "pointclick");
Connection connection = driver.connect("jdbc:weblogic:jts",properties);
The error was:
java.sql.SQLException: The url cannot be null
atjava.sql.DriverManager.getConnection(DriverManager.java:434)
atjava.sql.DriverManager.getConnection(DriverManager.java:106)
at weblogic.jdbcbase.jts.Driver.connect(Driver.java:213)
at
pointclick.jdbc.ConnectionFactory.getConnection(ConnectionFactory.java:24)
atpointclick.servlet.TestServlet.doGet(TestServlet.java:36)
atjavax.servlet.http.HttpServlet.service(HttpServlet.java:740)
atjavax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:124)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:744)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:692)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:251)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
atweblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>>>>>
>>>>>
I copied the code above from
http://www.weblogic.com/docs51/classdocs/jts_driver.html and there
was
no
mention of setting any other properties. If I create the
connection
this
way from an EJB, will it still participate in the transaction
started
by
the
EJB container?
Sean Rohead
"Charlie Crook" <[email protected]> wrote in message
news:[email protected]...
Your Oracle example is also using JNDI to obtain the connection;
not
just
getting a connection from a pool. So you've actually changed 2conditions
( non-pool to pool, non-JNDI to JNDI ). So both of these should
be
considered as suspects for the performance.
"Sean Rohead" <[email protected]> wrote in message
news:[email protected]...
I ran a test which selected ~1000 rows from an oracle database
table.
The
code ran in 4 seconds when I used the Oracle driver directly:
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection connection = DriverManager.getConnection(URL,
"XXX",
"XXX");
When I changed the code to get the connection from weblogic,
it
took
128
SECONDS!!!!
weblogic.jdbc.connectionPool.pointclick=\
url=jdbc:oracle:thin:@XXX:dev,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=1,\
maxCapacity=2,\
capacityIncrement=1,\
props=user=XXX;password=XXX
weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.pointclick=pointclick
>>>>>>>
>>>>>>>
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
Context context = new InitialContext(properties);
try
DataSource dataSource = (DataSource)context.lookup(NAME);
Connection connection = dataSource.getConnection();
// if(!autoCommit)
// connection.setAutoCommit(false);
return connection;
finally
context.close();
The strangest thing is that when I used the weblogic pool, ifI
executed
"select column from table" it took 128 seconds, but "select *
from
table"
only took 32 seconds. Why would it take longer to process
less
data?
And more importantly, why does the weblogic connection take sodamn
long?
Thanks for your help.
Sean Rohead
PS: Folks: BEA WebLogic is in S.F., and now has some entry-level
positions
for
people who want to work with Java and E-Commerce infrastructure
products.
Send
resumes to [email protected]
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web ApplicationServer
Crossroads A-List Award: Rapid Application Development Tools for
Java
Intelligent Enterprise RealWare: Best Application Using a ComponentArchitecture
http://www.bea.com/press/awards_weblogic.html
PS: Folks: BEA WebLogic is in S.F., and now has some entry-level positionsfor
people who want to work with Java and E-Commerce infrastructure products.Send
resumes to [email protected]
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web ApplicationServer
Crossroads A-List Award: Rapid Application Development Tools for Java
Intelligent Enterprise RealWare: Best Application Using a ComponentArchitecture
http://www.bea.com/press/awards_weblogic.html

Unable to resolve JNDI DataSource in weblogic 12c When you upgrade web application

I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
public static DataSource getJndiDataSource(String name) {
JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
Properties jndiEnvironment = new Properties();
jndiEnvironment.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
dsLookup.setJndiEnvironment(jndiEnvironment);
try {
dsLookup.setResourceRef(false);
return dsLookup.getDataSource(name);
} catch (Exception e) {
dsLookup.setResourceRef(true);
return dsLookup.getDataSource(name);
And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'

I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
public static DataSource getJndiDataSource(String name) {
JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
Properties jndiEnvironment = new Properties();
jndiEnvironment.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
dsLookup.setJndiEnvironment(jndiEnvironment);
try {
dsLookup.setResourceRef(false);
return dsLookup.getDataSource(name);
} catch (Exception e) {
dsLookup.setResourceRef(true);
return dsLookup.getDataSource(name);
And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'

Javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'   - in Weblogic on starting the server

Hi,
I am not able to resolve the JNDI name - ATGProductionDS
I have used CIM to create this and i am using ATG10.2 with MYSQL as my database and weblogic.
/atg/epub/file/ConfigFileSystem journaling file system started: vfs=file:/C:
/Stixs/ATG/ATG10.2/home/PublishingAgent/deploymentconfig/live/config/ journalDirectory=C:\Stixs\ATG\ATG10.2\home\PublishingAgent\deploymentc
onfig\data\config
**** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource     Failed to resolve ATGProduct
ionDS   javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'. Resolved ''; remaining name 'ATGProductionDS'
**** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource             at weblogic.jndi.int
ernal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
**** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource             at weblogic.jndi.int
Entries from Weblogic console -datasources
ATGBatchDS
Generic
ATGBatchDS
ATGProductionDS
Generic
ATGProductionDS
atg_production_lockserver, atg_publishing_lockserver
ATGPublishingDS
Generic
ATGPublishingDS
atg_publishing_lockserver
Please provide assistance.

Hi,
if you click the "Control" tab for the ATGProductionDS datasource in the Weblogic console does it show the State as running?
Does the "Monitoring" tab for the datasource show the State as running? If you click on the "Testing" tab can you test the datasource successfully?
If you inspect the Server using the Weblogic console there is a link "View JNDI Tree" If you click the link do you see the datasource listed in the left pane?
Do you see any errors for the ATGProductionDS in the Weblogic server log and out log files?

Error at startup Unable to find DocumentConnectionPool , Need Help urgently

Iam getting an error when iam starting up the server.
trace is :
weblogic.ejb20.WLDeploymentException: Unable to find DocumentConnectionPool 'def
ault' configuration MBeanjavax.ejb.CreateException: Unable to find DocumentConne
ctionPool 'default' configuration MBean
at com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl.ejb
Create(SPIFastDocumentManagerImpl.java:328)
at com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl_lw3
66m_Impl.ejbCreate(SPIFastDocumentManagerImpl_lw366m_Impl.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionP
ool.java:151)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManag
er.java:380)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:
1472)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:404)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer
.java:983)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:969)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:619)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:194)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManag
er.java:380)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:
1472)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:404)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer
.java:983)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:969)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:619)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
My application-config.xml has :
<DocumentConnectionPool
CapacityIncrement="1"
DriverName="com.bea.p13n.content.document.jdbc.Driver"
InitialCapacity="5"
MaxCapacity="5"
Name="default"
Properties="schemaXML=D:/myServer/dmsBase/doc-schemas;docBase=D:/myServer/dmsBase;jdbc.dataSource=weblogic.jdbc.pool.commercePool"
URL="jdbc:beasys:docmgmt:com.bea.p13n.content.document.ref.RefDocumentProvider"
/>
and my config.xml has:
<Application Deployed="true" Name="MyApp"
Path="D:\apps\MyApp"
StagedTargets="myServer" TwoPhase="true">
<ApplicationConfiguration Name="MyApp"
Targets="myServer" URI="META-INF/application-config.xml"/>
</Application>
So , it is targetted on my server and also the app-config has it defined.
Can anyone tell me where is the problem.?

For ne one who is interested,
we figured what went wrong in our configuration.
We are using oracle as backend but driver for the datasource under consideration is given is the driver for reference cloudscape database. Once driver is changed to oracle's OCI driver problem got resolved
Good luck :-)
Manohar

Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'

Hello,
I hope I am posting this in the right place, if not please forgiv and point me to the right place.
Yesterday we did a live upgrade on a system that is running WebLogic 9.2, OSM 6.3.1 and Oracle DB 10.2.0.2, those applications are on a seperate system slice, we did a complete upgrade from Solaris 10/9 (update 6) to the latest Solaris 8/11 (update 10), on SPARC. After the upgrade everything was working and applications are able to start, but weblogic server is spewing the following error message:
<Aug 1, 2012 12:03:58 PM CEST> <Error> <oms.core> <600022> <EJB Create exception thrown while creating object=EventDispatcherEJB.>
<01-Aug-2012 12:03:58,982 CEST PM> <ERROR> <poller.a> <Timer-4> <Failed to process events>
java.rmi.RemoteException: Error in ejbCreate:; nested exception is:
javax.ejb.CreateException: Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'. Resolved 'mslv.oms.oms1.internal.jms'
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:724)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
at weblogic.ejb.container.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:220)
at weblogic.ejb.container.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:64)
at com.mslv.oms.eventengine.EventDispatcher_86q3j1_EOImpl.processTimeout(EventDispatcher_86q3j1_EOImpl.java:485)
at com.mslv.oms.poller.a.handleNotification(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1652)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
we went back and activated Solaris update 8, and we still got that problem. The requests that the clients that connect via OSM frontend application that communicates with WebLogic arent being processed.
The oracle db is working and listening to port 1521, I can connect to it and can connect with the user defined in the WebLogic connection pool.
This is the first time working on this system, the application and integration was done by someone else who are not available to help us out, I hope someone here on the forum will be able to help us out with this problem.
Regards,
Omar

Often ConnectionFactory errors are caused by an inability to connect with the database hosting the OSM schema and user.
Check the database and make sure that both it and its listener are accepting connections. If that is ok you can also check the oms_pool configuration in WebLogic. Make sure the JNDI connection is valid. In my environments I see that DHCP often screws things up. If I install OSM on a host that has a DHCP assigned address (I'm guilty of being lazy when working in VMs and not statically assigning IP addresses) I often break the JNDI when I reboot the VM and get a new IP.
In WebLogic Admin Console:
Domain > Services > JDBC >Connection Pool > URL
and make sure the JDBC connection string is correct.

Unable to resolve 'TestDS3'.

I copy code from other thread and need to find a datasource named TestDS3. TestDS3 is created by me using weblogic 10.3.5 console. However, the following code has errors. If I change to
DataSource datasource = (DataSource)initialContext.lookup("CP-TestDS3");
I still get the same error.
================error=======================
"C:\Program Files\Java\jdk1.6.0_24\bin\javaw.exe" -client -classpath C:\JdevWorkspace\ANTdatasource\.adf;C:\JdevWorkspace\ANTdatasource\Project2\classes;E:\Jdeveloper_11115\wlserver_10.3\server\lib\weblogic.jar -Djavax.net.ssl.trustStore=E:\Jdeveloper_11115\wlserver_10.3\server\lib\DemoTrust.jks ant.DatasourceInfo
Exception in thread "main" javax.naming.NameNotFoundException: Unable to resolve 'TestDS3'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'TestDS3'. Resolved '']; remaining name 'TestDS3'
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
     at weblogic.jndi.internal.ServerNamingNode_1035_WLStub.lookup(Unknown Source)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at ant.DatasourceInfo.main(DatasourceInfo.java:31)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'TestDS3'. Resolved ''
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Process exited with exit code 1.
================code=======================
package ant;
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Hashtable;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.sql.DataSource;
public class DatasourceInfo {
public DatasourceInfo() {
super();
public static void main(String[] args) throws Exception {
DatasourceInfo datasourceInfo = new DatasourceInfo();
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
Context initialContext = new InitialContext(ht);
DataSource datasource = (DataSource)initialContext.lookup("TestDS3");
if (datasource != null) {
Connection Conn = datasource.getConnection();
========config.xml====================================
<jdbc-system-resource>
<name>CP-TestDS3</name>
<target>AdminServer</target>
<deployment-order>1</deployment-order>
<descriptor-file-name>jdbc/CP-TestDS3-4702-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>

Hi,
Try with JNDI name instead of data source name for lookup, JNDI name would be something like "jdbc/TestDS3"
Sireesha

Unable to resolve 'cgDataSource'

Hello,
I'm getting the following error when I try to test my web service. I will really appreciate your help.
Thanks
Godwin
=========error message=====weblogic platform 8.1=====
Error: An unexpected exception occurred while attempting to locate the
run-time information for this Web Service. Error:
javax.ejb.EJBException:nested exception is:
javax.naming.NameNotFoundException: Unable to resolve 'cgDataSource'
Resolved ; remaining name 'cgDataSource'
=======================================================
===========code========================================
public class Hello implements com.bea.jws.WebService
public Callback callback;
static final long serialVersionUID = 1L;
* @common:operation
public String hello_sync(String name)
return "Hello, " + name + "!";
* @common:operation
* @jws:conversation phase="start"
* @common:message-buffer enable="true"
public void hello_async(String name)
String greeting;
greeting = "Hello, " + name + "!";
this.callback.hello_callback(greeting);
public interface Callback extends com.bea.control.ServiceControl
* @jws:conversation phase="finish"
* @common:message-buffer enable="true"
void hello_callback(String message);
=====================================================

Hi,
without more information I would try to solve thisone like this :
1. see if the cgDataSource is configured and deployed in config.xml
2. if 1 is true, see the logs for details on why the DS does not deploy. If no the underlying connection pool fails to create connections during startup the DS will not be deployed either.
- Anders M.

Javax.naming.NameNotFoundException: Unable to resolve comp/env/CustomerBeanRef

Hi,
I used wls 6.1 sp2 and the sql2000 I wonder any one have the following problem
before.
in the weblogic-ejb-jar.xml I defined tthe <local-jndi name>customer.LocalCustomerHome</local-jndi-name>
and in the jsp page I lookup by InitialContext ic = new InitialContext(); // System.out.println("Init
context"); System.out.println(ic.toString()); Object o = ic.lookup("customer.LocalCustomerHome");
I am using global namespace(customer.LocalCustomerHome) rather than the local
java:comp/env/ejb namespace in here.
when I try to run the jsp file to create customer I got javax.naming.NameNotFoundException:
Unable to resolve comp/env/CustomerBeanRef I changed the comp/env/CustomerBeanRef
in the lookup code of the jsp to customer.LocalCustomerHome that is defined in
weblogic-ejb-jar.xml but it still refer to comp/env/CustomerBeanRef.
I stop the wlserver and deleted all __generate.class from the jsp then restart
the wlserver it still the same.
Thanks
-------part of weblogic-ejb-jar.xml -----------
<weblogic-enterprise-bean> <ejb-name>CustomerBean</ejb-name> <entity-descriptor>
<persistence> <persistence-type> <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version> <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type> <persistence-use> <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version> </persistence-use>
</persistence>
</entity-descriptor>
<local-jndi-name>customer.LocalCustomerHome</local-jndi-name> </weblogic-enterprise-bean>
-------------------end of weblogic-ejb-jar.xml ---------------
[createCustomer.jsp]

Hi,
set this under startup script at java option.
-Dweblogic.jndi.retainenvironment=true
and restart the server again.
Regards,
Kal

Javax.naming.NameNotFoundException: Unable to resolve ejb-link.

Env: JDK 1.3.1_08
Weblogic: 7.0
We are attempting to use EJB's (session) and have it all localized in a jar.
The Business and Custom Logic is all compiled to WEB-INF/classes. All the jars including the EJB jar is under WEB-INF/lib.
On Startup Weblogic throws the error message
weblogic.management.ApplicationException: activate failed for application
Module Name: application, Error: weblogic.j2ee.DeploymentException: Could not setup environment - with nested exception:
[javax.naming.NameNotFoundException: Unable to resolve ejb-link. Appejb.jar#AppServerBean is not in the context. The context includes the following link bindings: {} Make sure the link reference is relative to the URI of the referencing module.]
I have tried using the ../ notation before the Appejb.jar in the web.xml and what not, but that does not work either.
I have sucesfully deployed the EJB jar through the weblogic console.
Any Clues or suggestions will be most appreciated..
thanks
-a

Create a ear application from the ejb jar and web application war.
Copy ear application to the applications directory.
In the ejb-link element in web.xml specify the relative path to the ejb jar.
<ejb-link>../Appejb.jar</ejb-link>
thanks,
Deepak
Akshay <[email protected]> wrote:
Env: JDK 1.3.1_08
Weblogic: 7.0
We are attempting to use EJB's (session) and have it all localized in
a jar.
The Business and Custom Logic is all compiled to WEB-INF/classes. All
the jars including the EJB jar is under WEB-INF/lib.
On Startup Weblogic throws the error message
weblogic.management.ApplicationException: activate failed for application
Module Name: application, Error: weblogic.j2ee.DeploymentException: Could
not setup environment - with nested exception:
[javax.naming.NameNotFoundException: Unable to resolve ejb-link. Appejb.jar#AppServerBean
is not in the context. The context includes the following link bindings:
{} Make sure the link reference is relative to the URI of the referencing
module.]
I have tried using the ../ notation before the Appejb.jar in the web.xml
and what not, but that does not work either.
I have sucesfully deployed the EJB jar through the weblogic console.
Any Clues or suggestions will be most appreciated..
thanks
-a

Error in a page with a master-detail:Unable to resolve a Validator instance

Hi all,
I am using Jdeveloper 11.1.1.2
I have a page with a master table and a detail table.
When I try to select a row in the some tables (master or detail), I have this error:
<AbstractValidatorTag><createValidator> Unable to resolve a Validator instance using either validatorId ' or binding #{row.bindings.IdLocazione.validator}.
<RegistrationConfigurator><handleError> Server Exception during PPR, #1
javax.servlet.ServletException: Unable to resolve a Validator instance using either validatorId '' or binding '#{row.bindings.IdLocazione.validator}'.
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:270)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any suggestions?
Thanks
Andrea
Edited by: Andrea9 on 17-feb-2010 00:45

I am using ADF, I can reproduce in a testcase, but I need time.
If you want, I can cut and paste the jspx page.
However, I have a panelStretchLayout: on top facet I have the master table, while in the center facet I have the detail table.
I have a query component to filtering data of the master table.
I have this problem doing this:
1) create a new record on master table.
2) create some records on detail table (sons of the record of the master table just created).
3) clicking on "find" of the query component.
I have tried to do a master-detail with the HR connection using Departments table (master) and Employee (detail). When I try to delete a departments, it does not work, because I have to delete the employees first, while in my case I want to delete the master and the detail in cascade.
Thanks
Edited by: Andrea9 on 17-feb-2010 08:25

Sneaking Behind the JDBC ConnectionPools

Hi, this is Kinan
- This case happend with me:
- the (application2) on (server2) got a remote (weblogic.jdbc.common.internal.RmiDataSource) instance which defined in the (server1)
- When the (application2) tries to get a connection from this DataSource instance, it looks like that the WebLogic creates physical connection dirctly to the Oracle database server ignoring the ConnectionPool configuration from the (server1)
- The Question is: are their any configuration must be made to force the WebLogic to use the ConnectionPool config and not to create a dirct database connection??
- The general problem that I'm dealing with is that I want the (server2) to access the database only through the (server1)
Good Luck

kinan kinan wrote:
Hi, this is Kinan
- This case happend with me:
- the (application2) on (server2) got a remote (weblogic.jdbc.common.internal.RmiDataSource) instance which defined in the (server1)
- When the (application2) tries to get a connection from this DataSource instance, it looks like that the WebLogic creates physical connection dirctly to the Oracle database server ignoring the ConnectionPool configuration from the (server1)
- The Question is: are their any configuration must be made to force the WebLogic to use the ConnectionPool config and not to create a dirct database connection??
- The general problem that I'm dealing with is that I want the (server2) to access the database only through the (server1)
Good LuckHi. If the DataSource/pool is deployed/defined for both servers, you can't
stop the server from giving you a locally-made (but still pooled)
connection, but if you are absolutely sure the pool and datasource are only
defined for one server, then there is no way the other server will make a
direct connection. I suggest opening a support case so they can try to
duplicate this.
Joe

At startup: "Unable to resolve weblogic.jdbc.connectionPool"

Similar Messages

Maybe you are looking for