Cursor Parse Exception With OCI Drivers

I am getting the following Error if I call an Oracle Function with two
Params. Based on the values of parameters the where clause is changed but
returns the same Resultset. If I already have called the fucntion once and
then pass different values to the parameters I get the following erros.
I am closing the Connection, Resultset, and Callable statement at the end of
my call to the Function.
I am using OCI Drivers
I am using Bind Variables in Oracle Function.
Here is the Error
Label Code is SMOCONTESTS
java.sql.SQLException: ORA-01475: must reparse cursor to change bind
variable da
tatype
at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:238)
at weblogic.jdbcbase.oci.Statement.executeUpdate(Statement.java:869)
at weblogic.jdbcbase.oci.Statement.execute(Statement.java:1364)
at
weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:4
5)
at
weblogic.jdbc.rmi.internal.PreparedStatementImpl.execute(PreparedStat
ementImpl.java:289)
at
weblogic.jdbc.rmi.SerialPreparedStatement.execute(SerialPreparedState
ment.java:398)

Make sure ORACLE_HOME is properly set in your environment.
Also WLS is not able to find the library in PATH env variable.
Otherwise do this
java -Djava.library.path=$WL_HOME/bin/oci815_8 etc. etc.. weblogic.Server
where WL_HOME is your weblogic installation directory and i assume you want to
use oci815 or load the
appropriate dll.
Hope this helps
Let us know if you still see problems.
Kumar
Lee Mei Wah wrote:
Hi
I've the problem of creating the oracle connection pool wtih error
message:
java.sql.SQLException: System.loadLibrary threw
java.lang.UnsatisfiedLinkError with the
message 'no weblogicoci36 in java.library.path'.
I'm running Weblogic 5.1 and oracle8.0.5 on NT.
Has anyone got a solution for that?
Lee
"Jennifer Yang" <[email protected]> wrote in message
news:3998a1d1$[email protected]..
I was running batch update example, and I ran into the same problem, buton
NT.
What do I need to do?
We are using WebLogic 5.1
Jennifer
"Kelvin Yip" <[email protected]> wrote in message
news:3994602b$[email protected]..
I think you may have followed their documentation and it is wrong. You
may
have set your LD_LIBRARY_PATH to
oci80x_x but you should look for ...weblogic/lib/soloris/oci80x_xinstead.
You are picking up the NT dll not the soloris so.
"Sudharsan Srinivasan" <[email protected]> wrote in message
news:39919e36$[email protected]..
Hi I'm using the WebLogic's driver. It is giving the following error
when
I try to start the connection pool.
"<JDBC Pool> Failed to create connection pool "oraclePool"
<JDBC Pool> weblogic.common.ResourceException:
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary threwjava.lang.UnsatisfiedLinkError
with the message 'no weblogicoci34 in java.library.path'."
I'm running WebLogic 4.5.2 and I have setup the LD_LIBRARY_PATH.
Thanks in advance.
-Sudharsan.

Similar Messages

Parse Exception with JAXP....

Hi.....
When I use JAXP to parse the next xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Login SYSTEM "login.dtd">
<Login>
<username>tony</username>
<password>abc123</password>
</Login>
It will throw SAXParseException: 'No such related URI "login.dtd"'
/* code */
Document doc = null;
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
InputSource src = new InputSource(new BufferedReader(new FileReader(new File("classes/xml/file/login.xml"))));
doc = db.parse(src);
But If I change the InputSource into File it will run well:
/* code */
File docFile = new File("classes/xml/file/login.xml");
Document doc = null;
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
doc = db.parse(docFile );
If I need to parse xml messages from remote server, it means the message can't be changed and it don't exist in any file. How to parse the message with 'InputSource' or other? How to ignore "<!DOCTYPE Login SYSTEM "login.dtd">" in the message when parsing?

I tried use EntityResolver but it didn't work.
I just want the message to be parsed. And the message is got from remote server, so I don't need to read the dtd file.
How to prevent DTD from being accessed?
I use MyResolver class to setEntityResolver, but it didn't work .....
class MyResolver implements EntityResolver {
public InputSource resolveEntity(String publicId, String systemId) {
StringReader strReader = new StringReader("This is a custom entity");
if (systemId.equals("login.dtd") {
System.out.println("Resolving entity: " + systemId);
return new InputSource(new ByteArrayInputStream("<?xml version='1.0' encoding='UTF-8'?>".getBytes()));
} else {
return null;
Please help!!!!!

Problems with OCI Drivers

Hi I'm using the WebLogic's driver. It is giving the following error when I try to start the connection pool.
"<JDBC Pool> Failed to create connection pool "oraclePool"
<JDBC Pool> weblogic.common.ResourceException:
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary threw java.lang.UnsatisfiedLinkError
with the message 'no weblogicoci34 in java.library.path'."
I'm running WebLogic 4.5.2 and I have setup the LD_LIBRARY_PATH.
Thanks in advance.
-Sudharsan.

Make sure ORACLE_HOME is properly set in your environment.
Also WLS is not able to find the library in PATH env variable.
Otherwise do this
java -Djava.library.path=$WL_HOME/bin/oci815_8 etc. etc.. weblogic.Server
where WL_HOME is your weblogic installation directory and i assume you want to
use oci815 or load the
appropriate dll.
Hope this helps
Let us know if you still see problems.
Kumar
Lee Mei Wah wrote:
Hi
I've the problem of creating the oracle connection pool wtih error
message:
java.sql.SQLException: System.loadLibrary threw
java.lang.UnsatisfiedLinkError with the
message 'no weblogicoci36 in java.library.path'.
I'm running Weblogic 5.1 and oracle8.0.5 on NT.
Has anyone got a solution for that?
Lee
"Jennifer Yang" <[email protected]> wrote in message
news:3998a1d1$[email protected]..
I was running batch update example, and I ran into the same problem, buton
NT.
What do I need to do?
We are using WebLogic 5.1
Jennifer
"Kelvin Yip" <[email protected]> wrote in message
news:3994602b$[email protected]..
I think you may have followed their documentation and it is wrong. You
may
have set your LD_LIBRARY_PATH to
oci80x_x but you should look for ...weblogic/lib/soloris/oci80x_xinstead.
You are picking up the NT dll not the soloris so.
"Sudharsan Srinivasan" <[email protected]> wrote in message
news:39919e36$[email protected]..
Hi I'm using the WebLogic's driver. It is giving the following error
when
I try to start the connection pool.
"<JDBC Pool> Failed to create connection pool "oraclePool"
<JDBC Pool> weblogic.common.ResourceException:
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary threwjava.lang.UnsatisfiedLinkError
with the message 'no weblogicoci34 in java.library.path'."
I'm running WebLogic 4.5.2 and I have setup the LD_LIBRARY_PATH.
Thanks in advance.
-Sudharsan.

Parse exception with french characters

My parsing program throws a SaxParseException upon the parse of some french characters; in particular a "�" character. These characters are enclosed in a CDATA tag, so I'm not sure why its being parsed. My file is encoded in UTF-8. How can resolve this problem? Thanks
org.xml.sax.SAXParseException: Invalid byte 2 of 3-byte UTF-8 sequence.
     at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
     at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)

Your file is not encoded in UTF-8, although the XML
prolog claims it is.Meaning the sender/creator of the file is at fault?
If not UTF-8, then probably ISO-8859-1, correct?Most likely the creator of the file is at fault. But it's possible that it has been through some transformation between them and you that rewrote it in a new charset.
Sure, the real encoding could be ISO-8859-1. Or it could be windows-1252. Other encodings are possible but unlikely, I suppose.

I can access a function in a package using OCI drivers but not PDO drivers

Hello all, i am a newbie to Oracle and its drivers for PHP. I would like to use PDO, and I have my database activity in packages, which have procedures and functions. My package has overloaded functions and that has been giving me a tough time with these drivers. So one signature of my function get_data contains a four arguments and all four are numbers, while another signature of get_data has the first two as numbers and the next two as varchar2. So when I try to access this function which is part of a package, I am able to retrieve data, and the driver I am using is OCI8, but when I try to do the same with PDO, it does not work. It gives me this error,
*General error: 6553 OCIStmtExecute: ORA-06553: PLS-307: too many declarations of 'GET_DATA' match this call (/var/www/php-5.3.3/ext/pdo_oci/oci_statement.c:146)' in /var/www/pdo_check.php:251 Stack trace: #0 /var/www/pdo_check.php(251): PDOStatement->execute() #1 /var/www/pdo_check.php(345): dbPDO->execPackage2() #2 {main} thrown in /var/www/pdo_check.php on line 251 *
I got this error earlier with OCI drivers, then I added the datatype while binding the values.
Has anybody had this headache earlier??
##Works
*$qu = oci_parse($connect, 'select pack.get_data(:p1,:p2,:p3,:p4)as rc from dual');
$p1 = (int)121;
$p2 = (int)222;
$p3 = (int)324;
$p4 = (int)001;
oci_bind_by_name($qu,":p1",$p1,10,OCI_B_INT);
oci_bind_by_name($qu,":p2",$p2,10,OCI_B_INT);
oci_bind_by_name($qu,":p3",$p3,10,OCI_B_INT);
oci_bind_by_name($qu,":p4",$p4,10,OCI_B_INT);
oci_execute($qu) or die("did not execute");
$r = oci_fetch_array($qu);*
##Does not work
*$sql = 'select pack.get_data(:p1,:p2,:p3,:p4) from dual';
$result = $this->dbConnect->prepare($sql);
$p1 = (int)2;
$p2 = (int)2;
$p3 = (int)2;
$p4 = (int)6;
$result->bindParam(':p1', $p1, PDO::PARAM_INT);
$result->bindParam(':p2', $p2, PDO::PARAM_INT);
$result->bindParam(':p3', $p3, PDO::PARAM_INT);
$result->bindParam(':p4', $p4, PDO::PARAM_INT);
$result->execute();*
I am still perplexed why is PDO giving me an error, when I have virtually mentioned everything is asks for?

I think the only person who can really answer this question is Chris Jones. For my money I tend to steer clear of PDO as it is a bit quirky ( at least in my experience ) and it does not support reference cursors.

Installing 8.1.6 OCI drivers with 8.1.5 RDBMS

Hi,
I developpe an application in java 1.2.2 which have to connect to an
Oracle 8.1.5 Database.
Or 8.1.5 OCI or thin Driver don't support java 1.2.x so I try to use
8.1.6 OCI with 8.1.5 Database as it is said in JDBC FAQ :
"JDBC 8.1.6 drivers can talk to RDBMS 8.1.6, 8.1.6sdk, 8.1.5, 8.0.6,
8.0.5, 8.0.4 and 7.3.4."
"8.1.6 OCI and THIN Driver - JDK 1.1.x and JDK 1.2.x"
I would prefer to use OCI Driver due to performance so I would like to
know how can I install 8.1.6 OCI Driver? Should I install a 8.1.6 Client
to connect to an 8.1.5 Database?
Thanks,

all jdbc oci drivers require the matching client install on the same platform.
(i.e. The 817 JDBC oci driver requires the RDBMS 817 client install, etc.)

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

OCI Drivers in JDBC receiver

Hi All,
Brief Scenario: Insert data to CLOB field (source field may be more than 4000kb). Requirement to use OCI drivers in JDBC receiver adapter.
When calling Stored Procedure to insert CLOB data field, exception thrown by AE or Oracle server:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SP_ORDERS' (structure 'STATEMENT'): java.sql.SQLException: ORA-00932: inconsistent datatypes: expected %s got %s
I want to confirm whether SAP support OCI drivers using Stored Procedure?.
Thanks,
Rajesh Yallabandi

Not solved... work around alternate solution.
Edited by: sappi71 on Jun 20, 2011 10:38 PM

Exceptions with JEditorPane setPage() method (Catching not possible)

hi all
if anyone can help me...please help
I got serious exceptions with the JEditorPane()'s setPage() method
I have written the try & catch still i could not catch the exception..(those exceptions are not displaying any of my program lines)..setPage() mehod was executed properly and the page was displyed on the editorpane..and then exceptions r coming..
--------my code--------
java.net.URL fileurl =LongTask.class.getResource(modifiedfilename);
editorpane.setPage(fileurl);
---------------------exceptions
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:393)
at javax.swing.text.SimpleAttributeSet.addAttribute(SimpleAttributeSet.java:176)
at javax.swing.text.html.CSS.translateHTMLToCSS(CSS.java:687)
at javax.swing.text.html.StyleSheet.translateHTMLToCSS(StyleSheet.java:491)
at javax.swing.text.html.StyleSheet$ViewAttributeSet.<init>(StyleSheet.java:2476)
at javax.swing.text.html.StyleSheet.getViewAttributes(StyleSheet.java:312)
at javax.swing.text.html.BlockView.getAttributes(BlockView.java:275)
at javax.swing.text.html.StyleSheet$ViewAttributeSet.getResolveParent(StyleSheet.java:2609)
at javax.swing.text.html.StyleSheet$ViewAttributeSet.doGetAttribute(StyleSheet.java:2589)
at javax.swing.text.html.StyleSheet$ViewAttributeSet.getAttribute(StyleSheet.java:2569)
at javax.swing.text.ParagraphView.setPropertiesFromAttributes(ParagraphView.java:105)
at javax.swing.text.html.ParagraphView.setPropertiesFromAttributes(ParagraphView.java:87)
at javax.swing.text.html.ParagraphView.setParent(ParagraphView.java:60)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.html.BlockView.setParent(BlockView.java:55)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.html.TableView$RowView.replace(TableView.java:1414)
at javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.html.TableView.replace(TableView.java:864)
at javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
at javax.swing.text.CompositeView.setParent(CompositeView.java:122)
at javax.swing.text.html.TableView.setParent(TableView.java:768)
at javax.swing.text.CompositeView.replace(CompositeView.java:200)
at javax.swing.text.BoxView.replace(BoxView.java:164)
at javax.swing.text.View.updateChildren(View.java:1126)
at javax.swing.text.View.insertUpdate(View.java:710)
at javax.swing.text.View.forwardUpdateToView(View.java:1217)
at javax.swing.text.View.forwardUpdate(View.java:1192)
at javax.swing.text.BoxView.forwardUpdate(BoxView.java:222)
at javax.swing.text.View.insertUpdate(View.java:716)
at javax.swing.plaf.basic.BasicTextUI$RootView.insertUpdate(BasicTextUI.java:1487)
at javax.swing.plaf.basic.BasicTextUI$UpdateHandler.insertUpdate(BasicTextUI.java:1726)
at javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:184)
at javax.swing.text.DefaultStyledDocument.insert(DefaultStyledDocument.java:201)
at javax.swing.text.html.HTMLDocument.insert(HTMLDocument.java:232)
at javax.swing.text.html.HTMLDocument$HTMLReader.flushBuffer(HTMLDocument.java:3254)
at javax.swing.text.html.HTMLDocument$HTMLReader.addContent(HTMLDocument.java:3196)
at javax.swing.text.html.HTMLDocument$HTMLReader.blockClose(HTMLDocument.java:3128)
at javax.swing.text.html.HTMLDocument$HTMLReader$BlockAction.end(HTMLDocument.java:2334)
at javax.swing.text.html.HTMLDocument$HTMLReader.handleEndTag(HTMLDocument.java:2233)
at javax.swing.text.html.parser.DocumentParser.handleEndTag(DocumentParser.java:217)
at javax.swing.text.html.parser.Parser.parse(Parser.java:2072)
at javax.swing.text.html.parser.DocumentParser.parse(DocumentParser.java:106)
at javax.swing.text.html.parser.ParserDelegator.parse(ParserDelegator.java:78)
at javax.swing.text.html.HTMLEditorKit.read(HTMLEditorKit.java:230)
at javax.swing.JEditorPane.read(JEditorPane.java:504)
at javax.swing.JEditorPane$PageLoader.run(JEditorPane.java:551)
please share ideas to solve this problem

But how can I cause GUI thread to run in my thread
group? As I suppose GUI thread is started by JVM and
is something separate from my code - I can get a
reference to GUI thread but don't know how to
manipulate or replace it...One alternative is to completely separate the GUI code from your code.
Your code, which is wrapped in appropriate try/catch blocks, runs on its own thread and does its own processing. When it's done with that processing, it queues the results on the event thread for display. If an exception occurs during your processing, then you queue something that notifies the GUI.
The simplest way to implement this is to spawn a new thread for each operation. The Runnable that you give to that thread looks like the following:
public MyOperationClass implements Runnable
    public void run()
        try
            // do your exception-generating code here
            SwingUtilities.invokeLater( new MyGUIUpdateClass(param1, param2));
        catch (Exception e)
            SwingUtilities.invokeLater(new MyExceptionReporter(e));
}This is only a bare-bones solution (and hasn't been compiled). Since it separates the GUI from actual processing, you'll probably want to display a wait cursor while the processing thread is doing its thing. You'll probably end up implementing a class that implements this pattern. You may also want to create a producer-consumer thread, so that the user won't invoke, say, a dozen different operations at once.
However, this sort of code is absolutely essential to Swing programming. Most apps do extensive non-GUI processing, such as database queries. If you run such queries in the GUI thread, your GUI will freeze.
Sun has named this pattern "SwingWorker", although I don't think they've fleshed it out very fully: http://java.sun.com/products/jfc/tsc/articles/threads/threads2.html

Invalid Cursor state Exception - Help required

Hi,
I'm having a web page(JSP), which is making use of 3 ResultSet objects. Using the first two, i'll populate two different Drop down list, with values from database(Access) while loading the page for first time.
Now if the user select any value from any (or both) of drop down list and clicks submit, i need to display all values in database, meeting the criteria from first & second drop down list. For this selection, i'm using the third ResultSet variable. While executing the query, i'm sure that 3rd ResultSet is returning some value. But when i try to retrieve the value to a string variable, i'm getting the Invalid cursor state exception.
Throughout the page, i haven't closed any of the ResultSet. When i closed the first and second ResultSets in the third function(where 3rd ResultSet is used), i'm not getting any value. Its returning like ResultSet closed.
Please help me to get this solved. It's very urgent because without this, i cannot proceed further. Please share your ideas.
Thanks in advace for your valuable help

If you open a new resultset within the same statement, all previously opened will be closed.
Read the API docs, luke.

Problem to create data source with OCI type of driver

Hi Experts
We are creating an XA datasource with OCI type of driver using an enterprise application with data-sources.xml, the xml is like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE data-sources SYSTEM "data-sources.dtd" >
<data-sources>
     <data-source>
          <data-source-name>OCI_DS_XA</data-source-name>
          <driver-name>ORACLE_DRIVER</driver-name>
          <init-connections>1</init-connections>
          <max-connections>25</max-connections>
          <max-time-to-wait-connection>120</max-time-to-wait-connection>
          <expiration-control>
               <connection-lifetime>60</connection-lifetime>
               <run-cleanup-thread>300</run-cleanup-thread>
          </expiration-control>
          <sql-engine>Vendor_SQL</sql-engine>
          <jdbc-2.0>
               <xads-class-name>
                    oracle.jdbc.xa.client.OracleXADataSource
               </xads-class-name>
               <object-factory>
                    oracle.jdbc.pool.OracleDataSourceFactory
               </object-factory>
               <properties>
                    <property>
                         <property-name>serverName</property-name>
                         <property-value><SERVER_NAME></property-value>
                    </property>
                    <property>
                         <property-name>serverPort</property-name>
                         <property-value>1521</property-value>
                    </property>
                    <property>
                         <property-name>databaseName</property-name>
                         <property-value>ORCL</property-value>
                    </property>
                    <property>
                         <property-name>driverType</property-name>
                         <property-value>oci</property-value>
                    </property>
                    <property>
                         <property-name>user</property-name>
                         <property-value>username</property-value>
                    </property>
                    <property>
                         <property-name>password</property-name>
                         <property-value>password</property-value>
                    </property>
               </properties>
          </jdbc-2.0>
          </data-source>
</data-sources>
We have installed oracle client in server M/C and configured all the environment variables. While we are deploying the application from CE developer studio IDE to the CE 7.1 AS, we are getting the following error:
Description:
          1. Exception has been returned while the 'sap.com/DS_TEST_EAR' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7653550:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "OCI_DS_XA".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1467)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:468)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:248)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3387)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3373)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3276)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3249)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.frame.core.database.DatabaseException: Exception of type java.sql.SQLException occurred: Closed Connection.
     at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:49)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1400)
     ... 33 more
Caused by: java.sql.SQLException: Closed Connection
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
     at oracle.jdbc.driver.GetCharSetError.processError(T2CConnection.java:3082)
     at oracle.jdbc.driver.T2CConnection.getCharSetIds(T2CConnection.java:2811)
     at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:300)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:344)
     at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:136)
     at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:79)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:545)
     at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:194)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:121)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:333)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:84)
     at com.sap.sql.connect.factory.XADSPooledConnectionFactory.getPooledConnection(XADSPooledConnectionFactory.java:27)
     at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
     at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.initConnections(DBDataSourcePoolImpl.java:1099)
     at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.<init>(DBDataSourcePoolImpl.java:49)
     at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:507)
     at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:136)
     at com.sap.sql.manager.OpenSQLManager.createDataSource(OpenSQLManager.java:141)
     at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:42)
     ... 34 more
But when we are creating the datasource with thin type of driver, it is working fine. We have already created a driver with name ORACLE_DRIVER in server using the ojdbc14.jar using Netweaver administrator consol.
Same this is happening when we are creating the OCI type of datasource by using Netweaver administrator consol by specifying all the parameter as above and also the initial connection pool size is more than zero.
Same thing is happening for normal (JDBC 1x) datasource creation with OCI type driver.

Hello,
I ran a search on SDN, related to your error code, i found the following:
UnsupportedClassVersionError in NWDS CE
DeploymentWarning-WebService-Collection
Maybe its useful to you
Regards,
Siddhesh

XML Parser Exception in Install of AIA 11.1.1.5 on SOA 11.1.1.5

I am attempting to install AIA Foundation Pack on a SOA domain and continually encounter an XML parsing exception error as the installer is attempting to install WSM security policies. Here are the key details:
AIA version = 11.1.1.5
SOA Suite = 11.1.1.5
WebLogic = 10.3.5
Operating System = Fedora14 (a home lab machine but I don't think this is an OS issue)
The error is encountered about 17 minutes into the lengthy process. Just before the error appears in the installation log, the following message appears indicating roughly what step is being performed:
[zip] Building zip: /opt/oraclemw/aia11115/aia_instances/dev1/tmp/aia_security_policies.zip
The core error messages are:
[exec] SEVERE: WSM-01605 XML parser exception
[exec] oracle.xml.parser.v2.XMLParseException: Expected 'EOF'.
[exec] at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
The python modules being executed by the WLST scripting tool at the time of the failure are:
[exec] Problem invoking WLST - Traceback (innermost last):
[exec] File "/opt/oraclemw/aia11115/Infrastructure/Install/AID/lib/py/importpolicy.py", line 29, in ?
[exec] File "/opt/oraclemw/oracle_common/common/wlst/wsmManage.py", line 719, in importRepository
[exec] File "/opt/oraclemw/oracle_common/common/wlst/lib/ora_util.py", line 51, in raiseScriptingException
[exec] OracleScriptingException: None
Finally, the outer XML files being used as input for the deployer that seems to be running at the time are:
/opt/oraclemw/aia11115/Infrastructure/Install/AID/AIAExecuteDriver.xml
with references to lines 221 and 64.
The problem occurs whether I try to use Java JDK 16.0.20 or JRockit R28.2.0 as the JRE when running the AIA installer. (The WebLogic domain is configured to use JRockit).
Any suggestions? Is there a library conflict being picked up between different releases of XercesImpl? I would hope there isn't actually a bad XML file in the AIA artifacts or WSM (Web Service Management) policies being deployed.

HI
How this issue was resolved? Please explain in detail. I am facing the same issue.
Regards
Arun

Parse Exception : java.text.ParseException: Unparseable date

I have inherited a UDF in some mapping that on the whole, works okay...
but it throws an error after mapping a few dates:
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
the first few map okay... then i get the exception.
the UDF is as follows:
public String convertDateTimeToUTC(String strDate, Container container) throws StreamTransformationException{
AbstractTrace trace = container.getTrace();
Date date=null;
SimpleDateFormat sdfSource = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ssZ");
try{
String dt = strDate;
date = sdfSource.parse(dt);
trace.addInfo("Local Date:"+date);
SimpleDateFormat sdfDestination = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss");
strDate = sdfDestination.format(date);
catch(ParseException pe){
trace.addInfo("Parse Exception : " + pe);
return strDate;
can anyone see why this fails after successfully mapping a few fields???

the first mapping works correctly...
then we reuse the same fields to map to the additional segments.
the context is correct as it is trying to pull the same fields in... it just throw the error with the same data in the same UDF/Function Library but for different segments! :o(
http://img199.imageshack.us/img199/3104/dateconversion.jpg
as you can see from the screenshot above, the mapping works in the first instance, then fails on subsequent nodes.

JmsAdapter DOM Parsing Exception handling

Hi,
I'm currently facing a problem with the behaviour of the Jms Adapter.
Whenever a JMS message is put in the queue and that message is not XML valid, the Jms Adapter (consumer) throw the exception "DOM Parsing Exception in translator Exception".
That's fine, I understand that the message was not well formed. But what is not fine is that the underlying BPEL is not instanciated : meaning I can't handle the exception properly.
Is there a way to force the Jms Adapter not to crash on the DOM Parsing for the BPEL to be instanciated (and then being able to handle the exception there) ?
Or is there a way to handle the error thrown by the Jms Adapter itself ? How ?
I think I do have a workaround to this if there is no better option (if both above questions cannot be answered) but I would rather not implement it since it will involve some extra steps / complexity.
> It would be to check the "native format opaque schema" option and then use a java embedded to decode the base64 into a string for eventually parsing it.
regards,
mathieu

Hi Mathieu,
The messages that error out before being posted to the service infrastructure are referred to as rejected messages. For example, the Oracle File Adapter selects a file having data in CSV format and tries to translate it to XML format (using NXSD). If there is any error in the translation, this message is rejected and are not be posted to the target composite.
You can create rejection handlers to handle message errors. Message errors include those that occur during translation, correlation ID mismatch and XML parsing after message reception.
Docs on how to do that are here...
http://docs.oracle.com/cd/E28280_01/integration.1111/e10231/life_cycle.htm#CIAIICJJ
Cheers,
Vlad

Getting DOM Parsing Exception in translator while Dequeuing the message from JMS topic

Hi All,
Hope you all doing good.
I have an issue.
I am running on 11.1.1.5 SOA suite version on Linux.
In my aplication I have 4 projects which are connected by with topic/queue.
But in one of the communication, the JMS topic throws me the below error in the log, but dequeue happend perfectly fine and the application runs smoothly.
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project1>
JmsConsumer_sendInboundMessage:[des
tination = <TOPIC NAME> subscriber = <Consumer project name>
Error (DOM Parsing Exception in translator.[[
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
) while preparing to send XMLRecord JmsXMLRecord
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project name>
java.lang.Exception: DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
        at oracle.tip.adapter.jms.inbound.JmsConsumer.translateFromNative(JmsConsumer.java:603)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:403)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:1161)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:1048)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
But when I try putting the archived data on this topic, it throws me the same error but even dequeuing doesnt happen.
I have extracted the payload and validated against the xsd, it looks fine and even the validator doesnt throw me any error.
But I guess I am missing something, which I am immediately not getting.
Please let me know, if I am soemthing here which is causing this erro.
Thanks,
Chandru

I searched about this error, but no luck.
First time when the message dequeues, the consumer can consume the message but throws the error in the log.
But when I put the message back into queue from archive directory, the consumer doesnt consume message and throws me the same error.
Does anyone faced this sort of issue.
I checked my xsd throughly, and validated it externally. but didnt fine any error.
if anyone knows, suggest me how to resolve this issue.
thanks & regards
Chandru

Cursor Parse Exception With OCI Drivers

Similar Messages

Maybe you are looking for