DBMS exception

Hi,
Running Jdev 11.1.1.5 in WinXP, I do have this exception when running the app
Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:276)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1249)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1166)
     at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:249)
     at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1154)
     Truncated. see log file for complete stacktrace
while I have checked that
1)     I do verify the connection within Model\Project property\Business components is fine
2)     no other specific connection made within the Java files
What can be the reason of the exception? How to find out any other connection there?

Hua,
have you started the integrated server (e.g. menu 'run'-'Start server instance')?
If the server is not running you can't connect.
Next you need to check that the port your integrated server is listening to is '7101'. For this you loog at the server log, the first line you see when you start the server should read
*** Using HTTP port 7101 ***If you see a different port number you should use this when you try to access the wls (http://127.0.0.1:port_you_see/console).
Or you go to the 'Application Server Navigator', open the 'Application Servers' node , select the 'IntegratedWebLogicServer', right click on it and select 'Launch Administrative Console'.
Timo

Similar Messages

ORA-24327 with OCI driver

Hi,
We noticed that when we use the OCI driver for Oracle 8.1.7, we cannot have
an initial connection pool size greater than 249. On the 250th one, there is
a DBMS exception (ORA-24327) and weblogic says that it cannot create the
connection.
If we move to the Thin driver, there is no longer this restriction and we've
tried it with success with more than 550 connections.
Anyone know any limitation about the OCI driver and if there is any
parameter on the OCI driver side or on the DB side to tune so that we can
have more than 249 connections in our pool ?
FI, we have the following configuration (in config.xml) :
<JDBCConnectionPool CapacityIncrement="5"
Name="imJDBCConnectionPool" Targets="imadmin"
DriverName="weblogic.jdbc.oci.Driver" URL="jdbc:weblogic:oracle"
InitialCapacity="270" MaxCapacity="270"
TestTableName="dual" RefreshMinutes="40"
ShrinkingEnabled="false" ShrinkPeriodMinutes="15"
Properties="user=im;password=im;server=im09"/>
and we have the following TNSNAMES.ORA :
IM09.IM =
(DESCRIPTION =
(failover = on)
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domaina-1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domainb-1)(PORT = 1521))
(CONNECT_DATA = (SERVICE_NAME = IM09.im)(SERVER = shared))
and SQLNET.ORA (to resolve the IM domain name) :
NAMES.DEFAULT_DOMAIN=IM
Thanks
-Vincent

Vincent Massol wrote:
>
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Vincent,
Just for curiosity sake, what are you doing with 250 connections?
It's not in the Cactus area, is it? :-)
grin ;-)
No, I'm currently working for a customer, doing some lab performance tests.
We wanted to use the OCI driver for the TAF feature of OPS (transparent
application failover) but found that the Thin driver is performing so much
better that we have switched to using it along with the multipool feature of
WebLogic. Hi. Beware of 'TAF'. Note that all cursors will be defunct on failover,
so any JDBC statement or ResultSet in progress at the time of failover will
be lost. (IE: not at all transparent).
Joe
We haven't done any failover test yet so we don't know yet how the
multipool (with a 'load-balancing' strategy) perform upon failover of one
instance. If it's ok we'll keep using the thin driver. If not, we'll switch
back to OCI drivers and try the TAF feature.
Also, I don't think we really need that big number of connections. It seems
we had some other performance issue which the DB which was making us use
lots of connections on the WL side. With the thin driver we're only using
about 39-100 connections maximum with a thread count of 40 (that's because a
given message does up to 3 SQL statements per transaction (and a connection
is only effectively released in the pool after the commit)).
I've introduced Cactus on the project, of course, but only for the unit
tests (I'm also using Mock Objects) ... :-)
Regards,
-Vincent
Regards,
Slava Imeshev
"Vincent Massol" <[email protected]> wrote in message
news:[email protected]...
Hi,
We noticed that when we use the OCI driver for Oracle 8.1.7, we cannothave
an initial connection pool size greater than 249. On the 250th one,
there
is
a DBMS exception (ORA-24327) and weblogic says that it cannot create the
connection.
If we move to the Thin driver, there is no longer this restriction andwe've
tried it with success with more than 550 connections.
Anyone know any limitation about the OCI driver and if there is any
parameter on the OCI driver side or on the DB side to tune so that we
can
have more than 249 connections in our pool ?
FI, we have the following configuration (in config.xml) :
<JDBCConnectionPool CapacityIncrement="5"
Name="imJDBCConnectionPool" Targets="imadmin"
DriverName="weblogic.jdbc.oci.Driver" URL="jdbc:weblogic:oracle"
InitialCapacity="270" MaxCapacity="270"
TestTableName="dual" RefreshMinutes="40"
ShrinkingEnabled="false" ShrinkPeriodMinutes="15"
Properties="user=im;password=im;server=im09"/>
and we have the following TNSNAMES.ORA :
IM09.IM =
(DESCRIPTION =
(failover = on)
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domaina-1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domainb-1)(PORT = 1521))
(CONNECT_DATA = (SERVICE_NAME = IM09.im)(SERVER = shared))
and SQLNET.ORA (to resolve the IM domain name) :
NAMES.DEFAULT_DOMAIN=IM
Thanks
-Vincent
B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
SENIOR WEB DEVELOPER San Jose, CA
SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
SR. PRODUCT MANAGER Bellevue, WA
SR. WEB DESIGNER San Jose, CA
Channel Marketing Manager - EMEA Region London, GBR
DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
QUALITY ASSURANCE ENGINEER Redmond, WA
Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
E-Marketing Programs Specialist EMEA London, GBR
BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
MANAGER, E-SALES Plano, TX

EJB- Db failover question

Can anyone help explain what are my options for database failover? I am
          using WLAS 5.1. I have seen a lot of information on servlets replication,
          web proxying, and EJB clustering, but what about Db failure and rollover to
          a secondary Db? Is this something better handled at the Db level or is there
          anything at the application for managing this? I was intending to delve into
          Db replication and have a complete backup Db system, but am fuzzy on how to
          implement the EJB-JDBC connection / connection pools.
          Thanks
          - Ben Embree


          Ben wrote:
          >
          > Can anyone help explain what are my options for database failover? I am
          > using WLAS 5.1. I have seen a lot of information on servlets replication,
          > web proxying, and EJB clustering, but what about Db failure and rollover to
          > a secondary Db? Is this something better handled at the Db level or is there
          > anything at the application for managing this? I was intending to delve into
          > Db replication and have a complete backup Db system, but am fuzzy on how to
          > implement the EJB-JDBC connection / connection pools.
          >
          > Thanks
          > - Ben Embree
          Hi Ben. Database failover is best handled by the DBMS offering some sort of
          transparent failover to a hot-standby DBMS instance, using dual-ported disks
          so the user's transactional state is retained. Oracle purports to offer such
          for OCI clients, and if so, our JDBC driver for Oracle would fully, passively
          benefit. The driver and application would never know the connection had been
          switched.
          However, the fundamental issue is that relational DBMSes currently enforce
          a tight bond between a transaction and a single unbroken socket connection
          to a single client OS process. Whenever this socket connection is broken,
          whether by the client dying, a firewall closing it for idleness, etc, the DBMS
          will roll back the tx. No other connection to that database can ever contribute
          to, adopt, or resurrect the lost tx. Therefore, at any higher level than the DBMS,
          the only viable response to a connection failure is to assume a total tx rollback,
          and to reconnect to the DBMS, and restart the transaction from the very beginning.
          We are shortly going to offer 'multipools', which will look like a basic pool
          to clients, but will consist of an ordered list of basic pools, and when a connection
          request comes in, if the DBMS for the first pool in the list is down, we will try
          to return a connection from the next pool, presumably to another DBMS. This is a
          failover pool. This can only work during connection attempts, so any DBMS failure
          except at connect time will still require a manual re-connection as a part of redoing
          the whole tx. With respect to clustering, as soon as any JDBC is started for a given tx,
          it must be pursued to completion through the given cluster instance. No other cluster
          instance can contribute to JDBC within the tx to that DBMS except by making a
          type-3 JDBC connection to the other cluster instance to pass to the one real DBMS
          connection.
          I hope this helps,
          Joe Weinstein
          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 Application Server
          Crossroads A-List Award: Rapid Application Development Tools for Java
          Intelligent Enterprise RealWare: Best Application Using a Component Architecture
          http://www.bea.com/press/awards_weblogic.html

Could not create pool connection. The DBMS driver exception was:java.sql.SQLException: ORA-01017: invalid username/password

Could not create pool connection.The DBMS driver exception was:java.sql.SQLException:
ORA-01017: invalid username/password
Even though I could able to connect to Oracle database using correct userid,password
and HostString using OracleClient, I couldnt able to do with connectionpool. Here
is the error message..
<Jan 21, 2003 2:27:50 AM PST> <Notice> <WebLogicServer> <Starting WebLogic Admin
Server "examplesServer" for domain "examples">
Starting Loading jDriver/Oracle .....
---------- LOGIN ERROR CODE: 1017
---------- LOGIN ERROR CODE: 1017
<Jan 21, 2003 2:28:06 AM PST> <Error> <JDBC> <Cannot startup connection pool "or
aclePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: ORA-01017: invalid username/password; logon denied - (Obj
ectel/********@ora8i)
at weblogic.db.oci.OciConnection.getLDAException(OciConnection.java:164)
at weblogic.jdbc.oci.Driver.connect(Driver.java:112)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Jan 21, 2003 2:28:14 AM PST> <Notice> <Management> <Application Poller started
for development server.>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <SSLListenThread listeni
ng on port 7002>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <Management> <Starting discovery of Manag
ed Server... This feature is on by default, you may turn this off by passing -Dw
eblogic.management.discover=false>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogic Admin
Server "examplesServer" for domain "examples" running in Development Mode>

URL=jdbc:weblogic:oracle:oracle8i(server)
Driver Classname=weblogic.jdbc.oci.Driver
AClname=weblogic.jdbc.connectionPool.oraclePool
intialcapacity=1
MaximumCapacity=10
Capacity Increment=2
Login Delay Seconds=1sec
Refresh Period=15 Minutes
Supports Local Transaction=No
Allow Shrinking=No
Shrink Period=15
Prepared Statement Cache Size=10
TargetServer=ExamplesServer
Properties
user=Objectel
password=superman
Test table=yes
Test Reserved Connections=yes
Test Released Connections=Yes
I could able to connect to oracledataBase if I use
user=scott
password=tiger
with any other database user Iam getting the following error
Could not create pool connection. The DBMS driver exception was:java.sql.SQLException:
ORA-01017: invalid username/password
"Neo Gigs" <[email protected]> wrote:
By end of the error you shown:
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogicAdmin
Server "examplesServer" for domain "examples" running in DevelopmentMode>
You are running the Examples application shipped with WLS, which I guest
the
correct DB to connect with is Cloudscape yet to Oracle, unless you make
changes to the original ConnectionPool in the examples. Anyhow, please
show
us your configuration of the ConnectionPool used when this error pops.
"Raj" <[email protected]> wrote in message
news:[email protected]...
Could not create pool connection.The DBMS driver exceptionwas:java.sql.SQLException:
ORA-01017: invalid username/password
Even though I could able to connect to Oracle database using correctuserid,password
and HostString using OracleClient, I couldnt able to do withconnectionpool. Here
is the error message..
<Jan 21, 2003 2:27:50 AM PST> <Notice> <WebLogicServer> <Starting WebLogicAdmin
Server "examplesServer" for domain "examples">
Starting Loading jDriver/Oracle .....
---------- LOGIN ERROR CODE: 1017
---------- LOGIN ERROR CODE: 1017
<Jan 21, 2003 2:28:06 AM PST> <Error> <JDBC> <Cannot startup connectionpool "or
aclePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: ORA-01017: invalid username/password; logondenied - (Obj
ectel/********@ora8i)
atweblogic.db.oci.OciConnection.getLDAException(OciConnection.java:164)
at weblogic.jdbc.oci.Driver.connect(Driver.java:112)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:193)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub
start(ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:209)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub
start(ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Jan 21, 2003 2:28:14 AM PST> <Notice> <Management> <Application Pollerstarted
for development server.>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <ListenThreadlistening
on port 7001>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <SSLListenThreadlisteni
ng on port 7002>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <Management> <Starting discoveryof
Manag
ed Server... This feature is on by default, you may turn this off bypassing -Dw
eblogic.management.discover=false>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogicAdmin
Server "examplesServer" for domain "examples" running in DevelopmentMode>

Could not create pool connection. the dbms driver exception was : null

Hi,
I am creating Data source to connect to my DB2 database
Details of the connections are as follows
1) URL : jdbc:as400://hostname;translate binary=true
2) Driver class : com.ibm.as400.access.AS400JDBCDriver
am getting following error when I am trying to deploy the data source to server
An error occurred during activation of changes, please see the log for details.
weblogic.application.ModuleException:
weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: null
Connection is successful using test configuration.
Weblogic Version am using is 10.3.
Please help.
Thanks,
Arun

Hi. That means the JDBC driver you specified threw a NullPointerException
when we tried to make a connection with it...
Can you show the XML file for the DataSource? It's in the domain's
config/jdbc directory.

The DBMS driver exception was: 166

Hi, I have a problem with the creation of a pool using 'thin'. My weblogic is configured with option:
-Doracle.net.tns_admin
In tnsname i has configurate the conection and if i has a sqlplus coneccion is right, and driver for jdbc isin CLASSPATH.
when i trie to make Pool in weblogic (weblogic 8 with SP6) this is message i obtain:
<26-ene-2011 10H13' CET> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "NuevoPool": 166>
<26-ene-2011 10H13' CET> <Error> <JDBC> <BEA-001150> <Connection Pool "NuevoPool" deployment failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: 166.>
someone has idea where is the problem or some actions to find problem
Thanks so much.

Can you show us what happens when you try to connect using the driver directly to the DBMS,
using the same properties, URL, and classpath as WebLogic, with a simple program like:
------------------------------------------------------------------------- thin.java ---------------------------------
import java.util.*;
import java.sql.*;
public class thin
public static void main(String argv[]) throws Exception
Connection c = null;
try
Driver dr = new oracle.jdbc.OracleDriver();
Properties props = new Properties();
props.put("user", "scott");
props.put("password", "tiger");
String URL = "jdbc:oracle:thin:@MyDBMSBox:1531:MYSID";
c = dr.connect(URL, props);
System.out.println("The driver is " + c.getMetaData().getDriverVersion() );
System.out.println("The DBMS is " + c.getMetaData().getDatabaseProductVersion() );
catch (Exception e)
e.printStackTrace();
finally { try {c.close();} catch (Exception ign){} }
}

Should I be able to update a Blob via a ResultSet? (11g driver exception)

This code fails at the last line:
stmt = conn.createStatement();
String tableName = "TBL_esun01_PPP";
stmt.execute("drop table TBL_esun01_PPP");
stmt.execute("create table TBL_esun01_PPP (sid int not null primary key, blob_col blob)");
stmt.close();
//insert test data
String blobContent = "WLS JDBC4 test for blob.";
String blobContentUpdate = "WLS JDBC4 test for UpdateBlob. [Updated]";
ByteArrayInputStream inputStream = new ByteArrayInputStream(blobContent.getBytes());
ByteArrayInputStream inputStreamUpdate = new ByteArrayInputStream(blobContentUpdate.getByte
s());
String insertSql = "INSERT INTO " + tableName + " VALUES (?, ?)";
PreparedStatement pstmt = conn.prepareStatement(insertSql);
int key = 1;
pstmt.setInt(1, key);
pstmt.setBlob(2, inputStream);
pstmt.execute();
pstmt.close();
inputStream.close();
//update data
String querySql1 = "SELECT sid FROM " + tableName;
String querySql2 = "SELECT sid, blob_col FROM " + tableName;
Statement stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_UPDATABLE);
// we can get updatable resultset in the same way without lob object.
// following updating can succeed.
System.out.println("Get updatable resultset using: "+querySql1);
ResultSet rs = stmt.executeQuery(querySql1);
rs.next();
rs.updateInt(1, 2);
rs.updateRow();
rs.close();
inputStreamUpdate.close();
System.out.println("Get updatable resultset using: "+querySql2);
try {// failed to get updatable resultset
rs = stmt.executeQuery(querySql2);
rs.next();
rs.updateBlob(2, inputStreamUpdate); // Fails here...
The driver is 11.1.0.6.0-Production
The DBMS is Oracle Database 11g Release 11.1.0.0.0 - Production
Get updatable resultset using: SELECT sid FROM TBL_esun01_PPP
Get updatable resultset using: SELECT sid, blob_col FROM TBL_esun01_PPP
We can not get updatable Resultset. Exception message:
java.sql.SQLException: Invalid operation for read only resultset: updateBlob
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:229)
at oracle.jdbc.driver.BaseResultSet.updateBlob(BaseResultSet.java:506)
at TestUpdatableRS.test(TestUpdatableRS.java:84)
at TestUpdatableRS.main(TestUpdatableRS.java:112)
thanks,
Joe

Joe,
a) I could not find updateBlob(int, java.io.InputStream). It is updateBlob(int, java.sql.Blob).
b) I tried the below test and it worked fine, I am using the latest drivers.
CREATE TABLE BLOB_TABLE (C1 NUMBER, C2 BLOB);
INSERT INTO BLOB_TABLE VALUES(55, '101011');
public static void test2(Connection conn) throws SQLException {
System.out.println("test -");
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
String query = "select c1, c2 FROM blob_table";
pstmt = conn.prepareStatement(query, ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_UPDATABLE);
rs = pstmt.executeQuery();
SQLWarning x = pstmt.getWarnings();
if (x != null)
System.out.println(x.getMessage());
x = rs.getWarnings();
if (x != null)
System.out.println(x.getMessage());
BLOB blob = BLOB.createTemporary(conn, true, BLOB.DURATION_SESSION);
byte[] b = new byte[50];
java.util.Arrays.fill(b, (byte) 53);
blob.putBytes(1L, b);
if (rs.next()) {
rs.updateInt(1, 88);
rs.updateBlob(2, blob);
rs.updateRow();
x = rs.getWarnings();
if (x != null) {
System.out.println(x.getMessage());
} catch (SQLException ea) {
System.out.println(ea);
} finally {
if (rs != null) {
rs.close();
if (pstmt != null) {
pstmt.close();
System.out.println("test - done");
} // end of test2(Connection);
==
Ashok

DBMS scheduler jobs running twice

Hi,
I have 4 DBMS scheduler jobs , which checks for a specific job status in DB and sends an email , when i started the schedule for the first week the jobs executed fine from next week I am getting two emails from each job , when i check the logs USER_SCHEDULER_JOB_RUN_DETAILS I see only one run , which seems weird to me so i disabled one job and left the three jobs in schedule , next time i got two emails from 3 jobs and one from disabled job . After checking logs i see that there is no entry of the disabled job execution . I am not sure where is the problem i can't find any log from where the disabled job executing. Please help me
Job schedule is to run every Saturday
Interval setup :
start_date => trunc(SYSDATE)+ 8.5/24,
repeat_interval => 'TRUNC(LEAST(NEXT_DAY(SYSDATE,''SATURDAY'') )) + 8.5/24'
Suresh

Hi,
I tried to schedule the same jobs using DBMS_JOB but i still get the same problem , I created the procedure with all code in and scheduled it using dbms job , first day it run once second day it run twice ( sending two emails) Inow i am not sure if issue is with my code or scheduler
Procedure
Declare
v_count number;
v_Recipient VARCHAR2(400) := '[email protected]';
v_Subject VARCHAR2(80) := 'TEST_Email';
v_Mail_Host VARCHAR2(30) := 'localhost';
v_Mail_Conn utl_smtp.Connection;
crlf VARCHAR2(2) := chr(13)||chr(10);
BEGIN
select count(*) into v_count from TEC_CODERETURN@RPRD where interface like 'FOR002B' and trunc(rundate) =trunc(sysdate);
if v_count = 0
then
v_Mail_Conn := utl_smtp.Open_Connection(v_Mail_Host, 25);
utl_smtp.Rcpt(v_Mail_Conn, '[email protected]');
UTL_SMTP.OPEN_DATA(v_Mail_Conn);
utl_smtp.WRITE_RAW_DATA(v_Mail_Conn, UTL_RAW.CAST_TO_RAW(
'Date: ' || to_char(sysdate, 'Dy, DD Mon YYYY hh24:mi:ss') || UTL_TCP.CRLF ||
'From: ' || '[email protected]' || UTL_TCP.CRLF ||
'Subject: '|| v_Subject || UTL_TCP.CRLF ||
'To: ' || v_Recipient || UTL_TCP.CRLF ||
'This is a test Alert'|| UTL_TCP.CRLF
UTL_SMTP.CLOSE_DATA(v_mail_conn);
utl_smtp.Quit(v_mail_conn);
end if;
EXCEPTION
WHEN utl_smtp.Transient_Error OR utl_smtp.Permanent_Error then
raise_application_error(-20000, 'Unable to send mail: '||sqlerrm);
END;
DBMS job creation
DECLARE
jobno NUMBER;
BEGIN
DBMS_JOB.submit
(job => jobno,
what => 'TEST_ALERT;',
next_date => trunc(sysdate)+0.1/24,
interval => 'SYSDATE + 1',
no_parse => TRUE );
DBMS_OUTPUT.put_line ('Created Job - the job number is:' || TO_CHAR (jobno));
COMMIT;
END;
Suresh

Unexpected exception while enlisting XAConnection

Hi. I am getting the following error when executing getHibernateTemplate().findByNamedParam(...):
          org.springframework.jdbc.UncategorizedSQLException : Hibernate operation: Cannot open connection; uncategorized SQLException for SQL [???]; SQL state [null]; error code [0]; Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 33 seconds
          BEA1-000114394FEB
          at weblogic.jdbc.jta.DataSource.enlist(DataSource.jav a:1420)
          at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlis t(DataSource.java:1332)
          at weblogic.jdbc.jta.DataSource.getConnection(DataSou rce.java:440)
          at weblogic.jdbc.jta.DataSource.connect(DataSource.ja va:396)
          at weblogic.jdbc.common.internal.RmiDataSource.getCon nection(RmiDataSource.java:359)
          at org.springframework.orm.hibernate3.LocalDataSource ConnectionProvider.getConnection(LocalDataSourceCo nnectionProvider.java:81)
          at org.hibernate.jdbc.ConnectionManager.openConnectio n(ConnectionManager.java:423)
          at org.hibernate.jdbc.ConnectionManager.getConnection (ConnectionManager.java:144)
          at org.hibernate.jdbc.AbstractBatcher.prepareQuerySta tement(AbstractBatcher.java:139)
          at org.hibernate.loader.Loader.prepareQueryStatement( Loader.java:1547)
          at org.hibernate.loader.Loader.doQuery(Loader.java:67 3)
          at org.hibernate.loader.Loader.doQueryAndInitializeNo nLazyCollections(Loader.java:236)
          at org.hibernate.loader.Loader.doList(Loader.java:222 0)
          at org.hibernate.loader.Loader.listIgnoreQueryCache(L oader.java:2104)
          at org.hibernate.loader.Loader.list(Loader.java:2099)
          at org.hibernate.loader.hql.QueryLoader.list(QueryLoa der.java:378)
          at org.hibernate.hql.ast.QueryTranslatorImpl.list(Que ryTranslatorImpl.java:338)
          at org.hibernate.engine.query.HQLQueryPlan.performLis t(HQLQueryPlan.java:172)
          at org.hibernate.impl.SessionImpl.list(SessionImpl.ja va:1121)
          at org.hibernate.impl.QueryImpl.list(QueryImpl.java:7 9)
          at org.springframework.orm.hibernate3.HibernateTempla te$30.doInHibernate(HibernateTemplate.java:875)
          at org.springframework.orm.hibernate3.HibernateTempla te.execute(HibernateTemplate.java:372)
          at org.springframework.orm.hibernate3.HibernateTempla te.findByNamedParam(HibernateTemplate.java:866)
          at uk.xxx.xxx.xxx.Impl.getRereference(Impl.java:208)

It means what it says, that whatever this user invoke is
          doing, it took longer than the transaction timeout limit
          before getting to this point, so the transaction was marked
          for rollback already, and the application code is being
          denied their request for a DBMS connection.
          Joe

Please, If you can help me in XML-DBMS

I just want to convert a big xml file to mysql database. every thing is customized well in xml-DBMS technique in JBuilder 2005.
this erorr mesage had came when I started to transfere into the database.
Transfer to DBMS Failure -
de.tudarmstadt.ito.xmldbms.KeyException: Can't call commit when autocommit=true
in mysql environment, I have wrote in my.ini file under [mysqld]
init_connect='SET AUTOCOMMIT=0'
I don't know if this error is related to the mysql or to java (/jbuilder). and what is the solution?
I would be gratefull to you for any help.

this is the class, the packages have already defined
import com.borland.jbuilder.xml.database.template.*;
import com.borland.jbuilder.xml.database.xmldbms.*;
import com.mysql.jdbc.Driver;
public class trans {
XMLDBMSTable xMLDBMSTable1 = new XMLDBMSTable();
public trans(){
try {
jbInit();
} catch (Exception ex) {
ex.printStackTrace();
public static void main (String arg[])
{trans t = new trans();
private void jbInit() throws Exception {
xMLDBMSTable1.setDriver("com.mysql.jdbc.Driver");
xMLDBMSTable1.setMapFileName("F:/textxml/files/uniprot.map");
xMLDBMSTable1.setMode(XMLDBMSData.XML_TO_DB);
xMLDBMSTable1.setPassword("bazallh");
xMLDBMSTable1.setUrl("jdbc:mysql://localhost/jbuilder");
xMLDBMSTable1.setUserName("root");
xMLDBMSTable1.setXmlFileName( "F:/JavaProject/files/xmlfiles/uniprot_sprot.xml");
xMLDBMSTable1.transfer();
}

Java exception appear during file adapter to handle large xml

Hi,Guys,
I am using file adapter to poll one folder of my local.one get input.xml,then do something,then write out output.xml.
input.xml format is :
<mes:DataRequestIns xmlns:mes="http://xml.netbeans.org/schema/MessageDefined">

     <mes:DataIns>
          <mes:address>Ang Mo Kio 5,63 street</mes:address>
          <mes:birthday>14/12/1970</mes:birthday>
          <mes:firstName>Sing1</mes:firstName>
          <mes:gender>0</mes:gender>
          <mes:ID>1001</mes:ID>
          <mes:lastName>NorthMan</mes:lastName>
          <mes:postcode>2002</mes:postcode>
          <mes:telephone>6665222</mes:telephone>
          <mes:surname>Sur</mes:surname>
          <mes:status>single</mes:status>
          <mes:location>sgp</mes:location>
          <mes:HP1>11111</mes:HP1>
          <mes:HP2>22222</mes:HP2>
          <mes:passport>123456878</mes:passport>
          <mes:company>ST</mes:company>
          <mes:department>TO</mes:department>
          <mes:occupation>engineer</mes:occupation>
          <mes:experience>10</mes:experience>
          <mes:level>2</mes:level>
          <mes:certificate>high</mes:certificate>
          <mes:specialisation>computer</mes:specialisation>
          <mes:staffNumber>1020</mes:staffNumber>
          <mes:fax>00200</mes:fax>
          <mes:email>[email protected]</mes:email>
          <mes:national1>sgp</mes:national1>
          <mes:national2>sgp</mes:national2>
          <mes:interestingField>bpel</mes:interestingField>
          <mes:national>earth</mes:national>
          <mes:oversea>yes</mes:oversea>
     </mes:DataIns>
<mes:DataIns>
</mes:DataIns>
</mes:DataRequestIns>
if my input.xml contain less than 1000 records,then it's working,once greater than 1000,then appear exception.for normal case ,must have more than 10000 records need to handle,and file size is 11.2MB.
so,Does any other way or how to use file adapter to handle it ?
thank you
exception :
SEVERE: An error occured while scanning for the next trigger to fire.
org.quartz.JobPersistenceException: Failed to obtain DB connection from data sou
rce 'soaNonManagedDS': java.sql.SQLException: Could not retrieve datasource via
JNDI url 'jdbc/SOALocalTxDataSource' weblogic.jdbc.extensions.ConnectionDeadSQLE
xception: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.
ResourceException: Could not create pool connection. The DBMS driver exception w
*as: Socket read timed out [See nested exception: java.sql.SQLException: Could no*
*t retrieve datasource via JNDI url 'jdbc/SOALocalTxDataSource' weblogic.jdbc.ext*
*ensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadExc*
*eption: 0:weblogic.common.ResourceException: Could not create pool connection. T*
*he DBMS driver exception was: Socket read timed out]*
at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(Jo
bStoreCMT.java:167)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLoc
k(JobStoreSupport.java:3652)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobSt
oreSupport.java:2654)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:
*235)*
Caused by: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jd
bc/SOALocalTxDataSource' weblogic.jdbc.extensions.ConnectionDeadSQLException: we
blogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceExce
ption: Could not create pool connection. The DBMS driver exception was: Socket r
ead timed out
another exception:
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.
message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Ro
lledback.: weblogic.transaction.internal.TimedOutException: Transaction timed ou
t after 302 seconds
BEA1-3468FC5E3C698D2A82F7
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTran
sactionImpl.java:1742)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTim
edOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(Transacti
onManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(Ser
verTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
*; nested exception is: weblogic.transaction.internal.TimedOutException: Transact*
ion timed out after 302 seconds
BEA1-3468FC5E3C698D2A82F7
This error contained an exception thrown by the message handler.
Edited by: aris yu on Dec 27, 2009 11:55 PM

Hi,
we have to explicitly mention batch while configuaring file adapter.
i.e. in step 5 : Check file contains multiple messages and mention how many messages u want to process in a batch.
i.e. if you have 10000 msgs in ur file mention the size as 500. Then it will read 10000 records in 20 batches.
Now while writing to a file use Append=true property.
U have to add this property to fileadapter.wsdl (in jca:operation tag) which will be created when u complete the configuaration of file adapter with write operation.
Regards
PavanKumar.M

Can I modify WLI system Bean's transaction attribute --turn on archiver resulting endless exception in log file

hi,erveryone,
one difficult question need help.
Environment: WLS8.1sp2 + WLI8.1sp2 + ORACLE9i + solaris9
when I started archiver manually,just for a while, wli system generated about 40,000 JMS messages in
wli.internal.worklist.timer.queue,and consume the great mass of system resource of Database server,I had to stop these
archive processes immediately to keep other applicaitons which using the same database running normal. I did so by
following steps:
(1) in WLI console, delete wli.internal.worklist.timer.queue;
(2) in WLI console, reconstruct wli.internal.worklist.timer.queue;
(3) restart wli server.
after server was restarted, wli server output endless and repeatly exception to log file ,the typical exception was:
####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '54' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B26B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
java.sql.SQLException: Transaction rolled back: Unknown reason.
java.sql.SQLException: Transaction rolled back: Unknown reason
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1299)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
DBMS.java:1055)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
Logic_CMP_RDBMS.java:596)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
Logic_CMP_RDBMS.java:584)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
ava:2423)
     at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
     at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
     at
com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
     at
com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
1c_EOImpl.java:698)
     at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
     at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '96' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B96B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found..
javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
DBMS.java:1165)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
Logic_CMP_RDBMS.java:596)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
Logic_CMP_RDBMS.java:584)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
ava:2423)
     at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
     at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
     at
com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
     at
com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
     at
com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
1c_EOImpl.java:698)
     at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
     at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
The wli server generated log file very quickly ,:it can output 1M bytes log file per second,all logged information
is similar to the <BEA-010049> excetpion metioned above. BEA support engineer suggested me to totally stop the
archive ,I did so,but the server was still ouput the log file like crazy as before and the normal log information are
completely override by <BEA-010049> excetpion.
I checked the EntityEJBs in WLI console :Mywlidomain> Applications> WLI System EJBs> WLI Worklist Persistence$)A#,and
found that in statistics table :
ListenerBean : Pool miss ratio = 99.67%, transaction rollback ration = 99.90%,Destory Bean Ratio = 99.48%(see
attachment)
WorklistTimerMDB: transaction rollback ratio = 99.97%
It seems ListenerBean worked incorrectly.I searched in support.bea.com and found one example which also about server
output endless log file,the author solved this problem by changing Bean's transaction-attribute from 'Required'
to 'RequiresNew' thought he didn't know why it works. I try this method by changing ListenerBean's
transaction-attribute from 'Required' to 'RequiresNew'.
$weblogic_home/integration/lib/wli-ejbs.ear/ejb-jar-generic.xml:
<ejb-name>CommentBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>ListenerBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>RequiresNew</trans-attribute> -----------the default value is Required,I modified it to
RequiresNew.
</container-transaction>
<container-transaction>
really it works, the log file output resume normal. But there are still some problems:
(1) this exception is still exist:
javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
(2) is this method safe ?(Does "Modify ListenBean's transaction-attribute" impat other parts of wli system?)
(3) after changed the transaction attribute, if turn on archive again, the server output endless exception:
####<Jun 1, 2005 5:14:58 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '63' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-2F43890B86B0A8856F80> <BEA-010036> <Exception from ejbStore:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
branch
oracle.jdbc.xa.OracleXAException
     at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
     at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
     at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
6)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
     at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
     at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
     at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
     at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
     at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
branch
oracle.jdbc.xa.OracleXAException
     at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
     at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
     at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
6)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
     at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
     at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
     at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
     at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
     at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1292)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
6)
     at
com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
     at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
     at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
     at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
     at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
     at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
How can I solve these problem ? any suggestion is warm welcome.
Thanks in advance.
Great Lou

Back up all data to at least two different storage devices, if you haven't already done so. The backups can be made with Time Machine or with a mirroring tool such as Carbon Copy Cloner. Preferably both.
Boot into Recovery (command-R at startup), launch Disk Utility, and erase the startup volume with the default options.This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For details of how this works, see here:
Using Setup Assistant
Transfer only "Users" and "Settings" – not "Applications" or "Other files." Don't transfer the Guest account, if it was enabled on the old system. Test. If the problem is still there, you have a hardware fault. Take the machine to an Apple Store for diagnosis.
If the problem is resolved, reinstall your third-party software cautiously. Self-contained applications that install into the Applications folder by drag-and-drop or download from the App Store are safe. Anything that comes packaged as an installer or that prompts for an administrator password is suspect, and you must test thoroughly after reinstalling each such item to make sure you haven't restored the problem.
Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

Exceptions in stored procedure

Hello,
Consider a situation where a java class is executing a PL/SQL stored procedure. What happens if an error occurs in a stored procedure. Its obvious that the error is converted into SQLException in Java, and this is taken care of JDBC drivers.
Is there a case where any kind of exception is not converted into SQLException or is ignored by the JDBC driver? and..
Is it a good practice to handle Exceptions both in PL/SQL stored procedures and in Java?
or
Is it enough to handle just in Java?
Thanks
-Rao

Thanks damorgan,
I understand how exceptions work, but my question is specifially about how exception has to be defined when there are 2 "begins" in the procedure and the exception is caught in the internal begin. to elaborate of What I am tring to say, consider this
procedure finderror is
BEGIN
no_emp_found EXCEPTION;
begin
(SOME SELECT STATEMENT)
WHEN NO_DATA_FOUND THEN
RAISE no_emp_found
end;
EXCEPTION
WHEN no_emp_found
dbms.putline ('CAUGHT IT')
end finderror;
will the above code work, I mean conceptually (ignore the syntax). Or do I have to define the following part inside the internal (begin...end)
EXCEPTION
WHEN no_emp_found
dbms.putline ('CAUGHT IT')
Thanks

"No more data to read from socket" exception when testing connections

Hi,
I will appriciate your help with the following problem.
We have the follwoing errors in the weblogic.log (We are using weblogic 8.1.0.2 and Oracle 9.2.0.3)
####<Dec 20, 2006 10:47:49 AM EET> <Info> <JDBC> <ep> <mfserver> <Thread-14> <<WLS Kernel>> <> <BEA-001128> <Connection for pool "oraclePool" closed.>
####<Dec 20, 2006 10:47:49 AM EET> <Info> <JDBC> <ep > <mfserver> <Thread-14> <<WLS Kernel>> <> <BEA-001067> <Connection for pool "oraclePool" refreshed.>
####<Dec 20, 2006 10:47:51 AM EET> <Error> <JDBC> <ep > <mfserver> <Thread-14> <<WLS Kernel>> <> <BEA-001112> <Test "select count(*) from DUAL" set up for pool "oraclePool" failed with exception: "java.sql.SQLException: No more data to read from socket".>
####<Dec 20, 2006 10:47:51 AM EET> <Error> <JDBC> <ep > <mfserver> <Thread-14> <<WLS Kernel>> <> <BEA-001131> <Received an exception when closing a cached statement for the pool "oraclePool": java.sql.SQLException: Io exception: Broken pipe.>
These exception occures every hour after the connection pool is being closed and refreshed.
Also there are a lot of the follwoing warnning in the log :
<BEA-001074><A JDBC pool connection leak was detected.
Does these two problems connected? What can we do in order to solve it?
Thanks
Edited by RF123 at 01/28/2007 3:41 AM

R F wrote:
Hi,
I will appriciate your help with the following problem.
We have the follwoing errors in the weblogic.log (We are using weblogic 8.1.0.2 and Oracle 9.2.0.3)
####<Dec 20, 2006 10:47:49 AM EET> <Info> <JDBC> <ep> <mfserver> <Thread-14> <<WLS Kernel>
<> <BEA-001128> <Connection for pool "oraclePool" closed.>
####<Dec 20, 2006 10:47:49 AM EET> <Info> <JDBC> <ep > <mfserver> <Thread-14> <<WLS Kernel>
<> <BEA-001067> <Connection for pool "oraclePool" refreshed.>
####<Dec 20, 2006 10:47:51 AM EET> <Error> <JDBC> <ep > <mfserver> <Thread-14> <<WLS Kernel>
<> <BEA-001112> <Test "select count(*) from DUAL" set up for pool "oraclePool" failed with exception:
"java.sql.SQLException: No more data to read from socket".>
####<Dec 20, 2006 10:47:51 AM EET> <Error> <JDBC> <ep > <mfserver> <Thread-14> <<WLS Kernel>
<> <BEA-001131> <Received an exception when closing a cached statement for the pool "oraclePool":
java.sql.SQLException: Io exception: Broken pipe.>
These exception occures every hour after the connection pool is being closed and refreshed.
Also there are a lot of the follwoing warnning in the log :
<BEA-001074><A JDBC pool connection leak was detected.
Does these two problems connected? What can we do in order to solve it?Hi. The problems are not directly related, but may have the same cause.
Something is killing your DBMS connections out from under the driver.
Do you have a firewall between WLS and the DBMS, or a flakey network?
Contact BEA support to get the 8.1sp2 patch for getting meaningful
connection leak traces (CR209251_81sp2.jar). When that patch is installed
the leak messages should show a full stack trace of the application code
where the connection was obtained. It is that application code that
somehow failed to close the pool connection, causing a pool leak. I
suspect that the application code got an unexpected exception, such as
when/if the DBMS/network/firewall killed a connection. In this case I
believe the application went through an exception-handling path that
forgot to close the connection.
Joe

Exceptions in a stored procedure

Hi
I am writing a stored procedure and I am running a select statement. On NO_DATA_FOUND exception, I want to raise another exception called NO_EMP_FOUND. Question is where in the stored procedure I have to define this. Remember that the select statement is within a BEGIN and END
begin
no_emp_found exception;
Begin
select a,b INTO d,c
FROM BLABLA
WHERE BLA = BLA;
EXCEPTION
WHEN NO_DATA_FOUND
RAISE NO_EMP_FOUND;
END;
<<is this where I can define the NO_EMP_FOUND, or it has to be within the internal begin and end??>>
END;
Thanks

Thanks damorgan,
I understand how exceptions work, but my question is specifially about how exception has to be defined when there are 2 "begins" in the procedure and the exception is caught in the internal begin. to elaborate of What I am tring to say, consider this
procedure finderror is
BEGIN
no_emp_found EXCEPTION;
begin
(SOME SELECT STATEMENT)
WHEN NO_DATA_FOUND THEN
RAISE no_emp_found
end;
EXCEPTION
WHEN no_emp_found
dbms.putline ('CAUGHT IT')
end finderror;
will the above code work, I mean conceptually (ignore the syntax). Or do I have to define the following part inside the internal (begin...end)
EXCEPTION
WHEN no_emp_found
dbms.putline ('CAUGHT IT')
Thanks

DBMS exception

Similar Messages

Maybe you are looking for