ArrayIndexOutOfBoundException when using Callable Statement in Weblogic 8.1

Hi all,
We recently ported our application from 6.1 to 8.1.
I have noticed the following exception in 8.1 (which was working fine in 6.1)
java.lang.ArrayIndexOutOfBoundsException: 7
[ERROR] nfusion.admin.UpdateBureauLogin.5 131575 2003-10-15 16:21:58,385 Exception
caught
java.lang.ArrayIndexOutOfBoundsException: 7
at oracle.jdbc.dbaccess.DBDataSetImpl._getDBItem(DBDataSetImpl.java:303)
at oracle.jdbc.dbaccess.DBDataSetImpl._createOrGetDBItem(DBDataSetImpl.java:542)
at oracle.jdbc.dbaccess.DBDataSetImpl.setBytesBindItem(DBDataSetImpl.java:1642)
at oracle.jdbc.driver.OraclePreparedStatement.setItem(OraclePreparedStatement.java:745)
at oracle.jdbc.driver.OraclePreparedStatement.setString(OraclePreparedStatement.java:1083)
at weblogic.jdbc.wrapper.PreparedStatement.setString(PreparedStatement.java:415)
at com.ecredit.nfusion.businessobject.bureau.dao.DefaultBureauLoginDao.store(DefaultBureauLoginDao.java:200)
at com.ecredit.nfusion.businessobject.bureau.BureauManagerBean.updateBureauLogins(BureauManagerBean.java:940)
at com.ecredit.nfusion.businessobject.bureau.BureauManagerBean.setDetails(BureauManagerBean.java:424)
at com.ecredit.nfusion.businessobject.bureau.BureauManagerBean_lptk9u_EOImpl.setDetails(BureauManagerBean_lptk9u_EOImpl.java:46)
at com.ecredit.nfusion.businessservice.admin.UpdateBureauLoginHandler.execute(UpdateBureauLoginHandler.java:73)
at com.ecredit.nfusion.platform.requestproxy.RequestProxyBean.execute(RequestProxyBean.java:155)
at com.ecredit.nfusion.platform.requestproxy.RequestProxyBean_vc5299_EOImpl.execute(RequestProxyBean_vc5299_EOImpl.java:46)
at com.ecredit.nfusion.platform.requestdelegate.AbstractRequestDelegate.invokeProxy(AbstractRequestDelegate.java:135)
at com.ecredit.nfusion.platform.requestdelegate.HTMLRequestDelegate.execute(HTMLRequestDelegate.java:240)
at com.ecredit.nfusion.platform.inboundadapter.HTTPInboundAdapter.service(HTTPInboundAdapter.java:184)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6291)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3575)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2573)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
I am not able to figure out why this is happening in WL 8.1 and is working fine
in 6.1.
We are using Oracle 8.1.7 database. I have downloaded the thin driver for 8.1.7
(classes12.zip) and have included it before the weblogic jar files (in the startWeblogic.sh
file).
Any help would be greatly appreciated.
Regards,
-Rajan

Rajan Desai wrote:
I already have classes12.zip for Oracle 8.1.7 in my class path (before weblogic.jar
file).
Inspite of that it is giving this error.
Any other suggestion to resolve this problem?Yes, but just to be sure, would you show us the first 20 or so lines of the server log?
It should have a line describing the actual java command that starts the server, including
the class path that the startup script assembles for this line.
Thanks,
Joe
>
>
-RD
Mitesh Patel <[email protected]> wrote:
In 8.1, default oracle thin driver is changed from 817 to 920. This might
be bug in new oracle driver.
Please put classes12.zip file from oracle 817 version, that might resolve
your problem.
Thanks,
Mitesh
Rajan Desai wrote:
Hi all,
We recently ported our application from 6.1 to 8.1.
I have noticed the following exception in 8.1 (which was working finein 6.1)
java.lang.ArrayIndexOutOfBoundsException: 7
[ERROR] nfusion.admin.UpdateBureauLogin.5 131575 2003-10-15 16:21:58,385Exception
caught
java.lang.ArrayIndexOutOfBoundsException: 7
at oracle.jdbc.dbaccess.DBDataSetImpl._getDBItem(DBDataSetImpl.java:303)
at oracle.jdbc.dbaccess.DBDataSetImpl._createOrGetDBItem(DBDataSetImpl.java:542)
at oracle.jdbc.dbaccess.DBDataSetImpl.setBytesBindItem(DBDataSetImpl.java:1642)
at oracle.jdbc.driver.OraclePreparedStatement.setItem(OraclePreparedStatement.java:745)
at oracle.jdbc.driver.OraclePreparedStatement.setString(OraclePreparedStatement.java:1083)
at weblogic.jdbc.wrapper.PreparedStatement.setString(PreparedStatement.java:415)
at com.ecredit.nfusion.businessobject.bureau.dao.DefaultBureauLoginDao.store(DefaultBureauLoginDao.java:200)
at com.ecredit.nfusion.businessobject.bureau.BureauManagerBean.updateBureauLogins(BureauManagerBean.java:940)
at com.ecredit.nfusion.businessobject.bureau.BureauManagerBean.setDetails(BureauManagerBean.java:424)
at com.ecredit.nfusion.businessobject.bureau.BureauManagerBean_lptk9u_EOImpl.setDetails(BureauManagerBean_lptk9u_EOImpl.java:46)
at com.ecredit.nfusion.businessservice.admin.UpdateBureauLoginHandler.execute(UpdateBureauLoginHandler.java:73)
at com.ecredit.nfusion.platform.requestproxy.RequestProxyBean.execute(RequestProxyBean.java:155)
at com.ecredit.nfusion.platform.requestproxy.RequestProxyBean_vc5299_EOImpl.execute(RequestProxyBean_vc5299_EOImpl.java:46)
at com.ecredit.nfusion.platform.requestdelegate.AbstractRequestDelegate.invokeProxy(AbstractRequestDelegate.java:135)
at com.ecredit.nfusion.platform.requestdelegate.HTMLRequestDelegate.execute(HTMLRequestDelegate.java:240)
at com.ecredit.nfusion.platform.inboundadapter.HTTPInboundAdapter.service(HTTPInboundAdapter.java:184)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6291)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3575)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2573)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
I am not able to figure out why this is happening in WL 8.1 and isworking fine
in 6.1.
We are using Oracle 8.1.7 database. I have downloaded the thin driverfor 8.1.7
(classes12.zip) and have included it before the weblogic jar files(in the startWeblogic.sh
file).
Any help would be greatly appreciated.
Regards,
-Rajan

Similar Messages

Statement closed when using callable statements with oracle xe

hi all, i've got this problem with oracle express edition 10g. I am using also oc4j v10.1.2.0.2. When working with a normal oracle database it was working fine (i think the code was the same, it's some time since i last tried, but you can see the code is very simple).
So i just create a callable statement like this:
CallableStatement cs = con.prepareCall(sentencia.toString(), ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE, ResultSet.HOLD_CURSORS_OVER_COMMIT);
and then when trying to access the statement to register an out parameter like this
cs.registerOutParameter(1, parámetros[0].getTipo());
it gives this error:
java.sql.SQLException: Statement was closed
It's puzzling me because, as i said before, i think the same code was working ok with a normal oracle database.
Any idea what can it be?
cheers

Ah okay, sorry I've re-read your post.
I believe you need to create a clob object that encapsulates your xml file.
I've never done this but I would image it involves creating a class that implements the clob interface and passing an instantiation of this class to the callablestatement.
Let me know how you get on.

Calling a procedure/function in CO using Callable Statement

Hi,
Please help me in understanding this:
__method1__
BEGIN
:1 := Package.Function(
param1 => :2"
,param2 => :3"
,param3 => :4"
,param4 => :5"
END;
method2
BEGIN
Package.Function(:1, :2, :3, :4, :5);"
END;
Whats the significance of using method1?
I have seen the callable statements written as in method1 but, the parameters passed are not in order and not all params are passed.
When i tried writing similar code, I got "Invalid Column Index" exception. Please let me know how to overcome this.
Thanks

Hi,
You can call a function using Callable Statement as
public String checkprimarycontact(String pri_loc_id,String org_id,String party_id)
int p_location_id = 0;
int p_org_id = 0;
int p_party_id = 0;
p_location_id = Integer.parseInt(pri_loc_id);
p_org_id = Integer.parseInt(org_id);
p_party_id = Integer.parseInt(party_id);
String priflag = "";
try
Connection conn1 = getOADBTransaction().getJdbcConnection();
CallableStatement cstmt1 = conn1.prepareCall("{? = call GET_PRIMARY_FUNCTION(?,?,?)}");
cstmt1.registerOutParameter(1,Types.VARCHAR);
cstmt1.setInt(2,p_location_id);
cstmt1.setInt(3,p_org_id);
cstmt1.setInt(4,p_party_id);
cstmt1.execute();
priflag = cstmt1.getString(1);
catch(Exception e1)
e1.printStackTrace();
return priflag;
Thanks,
Gaurav

How to avoid data repetation when using select statements with innerjoin

how to avoid data repetation when using select statements with innerjoin.
thanks in advance,
satheesh

you can use a query like this...
SELECT DISTINCT
         frg~prc_group1                  "Product Group 1
         frg~prc_group2                  "Product Group 2
         frg~prc_group3                  "Product Group 3
         frg~prc_group4                  "Product Group 4
         frg~prc_group5                  "Product Group 5
         prc~product_id                  "Product ID
         txt~short_text                  "Product Description
UP TO 10 ROWS
INTO TABLE l_i_data
FROM
Joining CRMM_PR_SALESG and
COMM_PR_FRG_ROD
crmm_pr_salesg AS frg
INNER JOIN comm_pr_frg_rod AS prd
ON frgfrg_guid = prdfragment_guid
Joining COMM_PRODUCT and
COMM_PR_FRG_ROD
INNER JOIN comm_product AS prc
ON prdproduct_guid = prcproduct_guid
Joining COMM_PRSHTEXT and
COMM_PR_FRG_ROD
INNER JOIN comm_prshtext AS txt
ON prdproduct_guid = txtproduct_guid
WHERE frg~prc_group1 IN r_zprc_group1
   AND frg~prc_group2 IN r_zprc_group2
   AND frg~prc_group3 IN r_zprc_group3
   AND frg~prc_group4 IN r_zprc_group4
   AND frg~prc_group5 IN r_zprc_group5.
reward it it helps
Edited by: Apan Kumar Motilal on Jun 24, 2008 1:57 PM

How to return Multiple ResultSets Using Callable Statement

hi everybody,
while i was working with callable statements i came across a problem of how to fetch Multiple Resultsets by means of Stored Procedures written for tables in Oracle.
If any one can help me, pls do help me with a detailed explanation, and if possible do get me a example source code too.
khumaar

I have a similar problem with oracle and jdbc:
I want to send a sql query like:
sqlQuery = "select n1, n2 from table1; select n1, n2
from table2"
I used a prepared statement, but when I call
.execute(sqlQuery)
oracle doesn't like this,
can someone help on this?Try putting a begin/end around it. Play with the syntax first in sqlplus.
You do realize that you MUST extract using the syntax for extracting multiple result sets correct? It will NOT work as one result set.

Compiler error when useing switch statements in an inner class

I have defined several constants in a class and want to use this constans also in an inner class.
All the constants are defined as private static final int.
All works fine except when useing the switch statement in the inner class. I get the compiler error ""constant expression required". If I change the definition from private static final to protected static final it works, but why?
What's the difference?
Look at an example:
public class Switchtest
   private static final int AA = 0;
   protected static final int BB = 1;
   private static int i = 0;
   public Switchtest()
      i = 0; // <- OK
      switch(i)
         case AA: break; //<- OK, funny no problem
         case BB: break; //<- OK
         default: break;
private class InnerClass
      public InnerClass()
         i = 0; // <- OK: is accessible
         if (AA == i) // <- OK: AA is seen by the inner class; i is also accessible
            i = AA + 1;
         switch(i)
            case AA: break; // <- STRANGE?! Fail: Constant expression required
            case BB: break; // <- OK
            default: break;
}Thank's a lot for an explanation.

Just a though:
Maybe some subclass of Switchtest could decalare its own variable AA that is not final, but it can not declare its own BB because it is visible from the superclass. Therefore the compiler can not know for sure that AA is final.

How to use Callable statements.

Hi.
I'm just new in using JSP. I just want to ask how to call stored procedures (ex. from SQL Server) using the Callable statements. A sample code will be very helpful......
Ex. I have these parameters for my stored proc:
name = "sentiments"; //value will always vary
add = "NJ"; //value will always vary
stored proc name is => usp_updateFile
Thank you very much for your time.

See http://developer.java.sun.com/developer/onlineTraining/Database/JDBC20Intro/JDBC20.html#JDBC2013_4

Tips to remember when using Queued State machine

I have been able to work through to convert my State Machine architecture to a QSM thereby eliminating using Local variables/property nodes to send values/data to my State machine but instead sending them through queues.
I would like some tips/advice on making use of them perfectly. Especially, "Not to do" stuff with queues and How to efficiently release a queue etc. What is the convention when using queues? Thanks!
V
I may not be perfect, but I'm all I got!
Solved!
Go to Solution.

VeeJay wrote:
Hmmm!! I jumped the gun... I would have to say, Neither... I guess it isn't really QSM or Queued message handler. My State machine is the generic one. But, data for the SM is obtained from a queue and feedback is sent back from the State machine through a queue. Does that clarify ?
BTW, good to know more variations.. Thanks!
That is a QSM.
I will defer to those that use them regularly.
I would only use such a a construct if the queue was limited to a single entry and prevented inserting multiple states at the front or back of the queue.
As long as the queue is limited to a single entry then a State Transition Diagram could be used to described all of the states.
The multiple entry version can be thought of as a method to implement a "goto" statement in LV. Very useful for those that come from a background working with stacks and pushing and popping off work and those that use them often love them.
But for me let me refer to a letter from Dijkstra quote from here
"GOTO Staements Concidered Harmful" goto statement introduces chaos
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Problem when getting resultset when using connection pooling in weblogic

Hello,
I am new to database connection pooling. I am using weblogic server, Java 1.6, MySql database. I have done connection pooling in weblogic server. The problem arise when I try to run select query I cannot fetch data in ResultSet. For insert it works fine...
import java.io.Serializable;
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.ArrayList;
import java.util.List;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.sql.DataSource;
public class DatabaseToText implements Serializable {
public DatabaseToText() {
super();
// TODO Auto-generated constructor stub
public static void main(String[] args) {
Connection conn;
Statement stmt;
ResultSet rs;
String str1, str2;
List l1 = new ArrayList();
try {
System.out.println("in try block");
Properties prop = new Properties();
prop.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
prop.put(Context.PROVIDER_URL, "t3://localhost:7001");
System.out.println("properties are set ");
Context ctx = new InitialContext(prop);
System.out.println("b4 lookup(mysqljndi)");
Object obj = ctx.lookup("mysqljndi"); // java:comp/env/CPDS
System.out.println("afta lookup(mysqljndi)");
DataSource ds = (DataSource) obj;
conn = ds.getConnection();
stmt = conn.createStatement();
String query = "select * from logindb.userregister";
System.out.println("query is = " + query);
rs = stmt.executeQuery(query);
System.out.println("size of rs is :: " + rs.getFetchSize());
if (rs != null) {
while (rs.next()) {
str1 = rs.getString(0);
str2 = rs.getString(1);
System.out.println("username is :: " + str1 + "password is : " + str2);
} else {
System.out.println("no values get fetched");
ctx.close();
} catch (Exception e) {
e.printStackTrace();
OUTPUT IN CONSOLE
in try block
properties are set
b4 lookup(mysqljndi)
afta lookup(mysqljndi)
query is = select * from logindb.userregister
size of rs is :: 0
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[java.rmi.MarshalException: error marshalling return; nested exception is:
     java.io.NotSerializableException: com.mysql.jdbc.ResultSet]
     at weblogic.jdbc.rmi.SerialResultSet.next(SerialResultSet.java:89)
     at DatabaseToText.main(DatabaseToText.java:69)
Record is getting inserted but when i use select query i cannot get the output...
Regards,

This problem is solved in JDBC section of this forum

Deadlock in TopLink when using JMS listener on WebLogic

I am experiencing a deadlock in TopLink 10.1.3 on WebLogic 9 in code that previously worked on TopLink 9.0.4 with WebLogic 8.1. As such, I'm not sure if it's due to the TopLink change, the WebLogic change or both. Anyway, we have a JMS listener (note, NOT a MessageDrivenBean) that is updating an existing TopLink cached domaing object. The JMS listener thread gets stuck when attempting to commit the transaction. The thread-dump shows that there is another thread which is blocked in the ConcurrencyManager waiting to obtain the lock on an object which is being updated by the listener thread. It appears to me that the root cause is that the Synchronization.afterCompletion() listener is running on a different thread than the one which owns the locks which were obtained beforeCompletion.
See stack traces.
First, the message listener thread which is waiting for participants in the transaction to commit:
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=9 tid=0x3a4a4728 nid=0xa48 in Object.wait() [0x3a0cf000..0x3a0cfbec]
     at java.lang.Object.wait(Native Method)
     - waiting on <0x0c7a0908> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2665)
     - locked <0x0c7a0908> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2570)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:277)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:226)
     at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:539)
     at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)
     at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
     at com.avinamart.BusinessLogic.Bean.JobService.JobService_u1ylwo_EOImpl.submitJobAndRun(JobService_u1ylwo_EOImpl.java:1388)
     at com.avinamart.Framework.Event.Task.OptimizationTaskListener._submitAsAJob(OptimizationTaskListener.java:253)
     at com.avinamart.Framework.Event.Task.OptimizationTaskListener._submitAsAJob(OptimizationTaskListener.java:217)
     at com.avinamart.Framework.Event.Task.OptimizationTaskListener.processMessage(OptimizationTaskListener.java:344)
     at com.emptoris.base.event.EPASSMessageBaseListener.onMessage(EPASSMessageBaseListener.java:722)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession.pushMessage(JMSSession.java:3253)
     at weblogic.jms.client.JMSSession.invoke(JMSSession.java:4195)
     at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:674)
     at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:262)
     at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:134)
     at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:36)
     at weblogic.messaging.dispatcher.DispatcherServerRef$1.run(DispatcherServerRef.java:105)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Next, the other thread which is participating in the transaction which is stuck:
"[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=5 tid=0x3adb80a0 nid=0xb30 in Object.wait() [0x3c7af000..0x3c7afd6c]
     at java.lang.Object.wait(Native Method)
     - waiting on <0x0c7a0000> (a oracle.toplink.internal.helper.ConcurrencyManager)
     at java.lang.Object.wait(Object.java:474)
     at oracle.toplink.internal.helper.ConcurrencyManager.acquire(ConcurrencyManager.java:76)
     - locked <0x0c7a0000> (a oracle.toplink.internal.helper.ConcurrencyManager)
     at oracle.toplink.internal.identitymaps.CacheKey.acquire(CacheKey.java:80)
     at oracle.toplink.internal.identitymaps.FullIdentityMap.remove(FullIdentityMap.java:164)
     at oracle.toplink.internal.identitymaps.HardCacheWeakIdentityMap.remove(HardCacheWeakIdentityMap.java:82)
     at oracle.toplink.internal.helper.WriteLockManager.releaseAllAcquiredLocks(WriteLockManager.java:363)
     at oracle.toplink.publicinterface.UnitOfWork.afterTransaction(UnitOfWork.java:2123)
     at oracle.toplink.transaction.AbstractSynchronizationListener.afterCompletion(AbstractSynchronizationListener.java:135)
     at oracle.toplink.transaction.JTASynchronizationListener.afterCompletion(JTASynchronizationListener.java:66)
     at weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(ServerSCInfo.java:862)
     at weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(ServerTransactionImpl.java:2913)
     at weblogic.transaction.internal.ServerTransactionImpl.afterCommittedStateHousekeeping(ServerTransactionImpl.java:2806)
     at weblogic.transaction.internal.ServerTransactionImpl.setCommittedUnsync(ServerTransactionImpl.java:2857)
     at weblogic.transaction.internal.ServerTransactionImpl.ackCommit(ServerTransactionImpl.java:1097)
     - locked <0x0c7a0908> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.CoordinatorImpl.ackCommit(CoordinatorImpl.java:211)
     at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
     at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
     at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Is this the same concurrency bug which was fixed in 10.1.3.1??? As I am writing this, I am attempting to build the application with the updated TopLink jar to test for myself. Has anyone else seen this scenario with WebLogic? I should also point out that the problem only occurs when the listener is running on a separate server than the one hosting the JMS queue it reads from. It may be that when the listener runs on the same server, it does not use multiple threads in the transaction.
Any ideas are greatly appreciated.
- Bruno

We've got the same kind of issue with toplink 10.1.3.0.0 and bea weblogic 8.1 SP5.
I 've not tried with 10.1.3.1.0, did you?
Do you have a new status for this issue.
Chris

How to get a "blank" answer when using "if" statements in a table

I'm using a table for an invoice where an item is ordered, but more may be shipped than ordered. I have the formcalc expression figured out where I can get a 0 in the "backordered" column if the amount shipped is more than the item ordered, but I can't get rid of the 0 in the rest of the backordered column when there isn't any information in the "ordered" and "shipped" columns. Trying to get that column to be blank if there is no shipping or ordering information.
So far this is working for the math part. Not sure how to write a "blank" into the calculation
Sum(ordered-shipped)
if (Sum(ordered-shipped)>0)
then backordered=Sum(ordered-shipped)
elseif (Sum(ordered-shipped)<0)
then backordered=0
endif
Any advice will be greatly appreciated. Thanks!

I'm still getting a 0 in all the backordered columns when I'd like them to be empty. The form has more rows than I will be using, so when there is no information in the shipped and ordered row, I'd like the backordered row to be empty/blank. I've tried writing this at the end of my formula
elseif ordered=null and shipped=null
then backordered=null(but I really want it to be blank)
or elseif Table1.Row1.ordered=null and Table1.Row1.shipped=null
then Table1.Row1.backordered=null
And yes, backordered is a numeric field.
Any more advice? Thanks!

How to call stored procedure in SYBASE using callable statement

Hi all,
Im using jdbc code to execute a stored procedure in sybase but while running the code i get an error saying
java.sql.SQLException: JZ0R2: No result set for this query.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:506)
at com.sybase.jdbc2.jdbc.SybStatement.queryLoop(SybStatement.java:1552)
at com.sybase.jdbc2.jdbc.SybStatement.executeQuery(SybStatement.java:1522)
at com.sybase.jdbc2.jdbc.SybCallableStatement.executeQuery(SybCallableStatement.java:76)
but when i execute the same procedure in sybase it returns some result but i know its not in resultset format .I want to know is anyone experienced same problem in their side.
My question is how to obtain the result which is not in the format result set obtained by executing the stored procedure.
Thanks n advance
work machine

Check this post out:
http://forum.java.sun.com/thread.jspa?threadID=638768&messageID=3785982
But I think you should be getting results right? What do you mean you want it in a format other than resultset?

Issue in Calling PL/SQL packages using callable statement

Hi ,
I have the requirement of calling two pl/sql packages , After call of first package is successful , i need to pass the output of that first package as input to second package.
Since i have called both the packages in same method of AM, first package gets executed successfully but second package doesnt get the input values required from first package and results in error.
Looks like since commit is happening in the single session second package is passed with NULL values.
Need suggestion for proper way of calling pl/sql packages when second package is dependant on first one:
Code used inside AM Method:
if("PENDING_XXX".equals(regVORow.getRegStatus()))
regVORow.setRegStatus("VENDOR_CREATED");
getOADBTransaction().commit();
OracleCallableStatement cStmt = null;
OADBTransaction dbTxn = getOADBTransaction();
NUMBER vendor_id = new NUMBER(-1);
NUMBER vendor_site_id = new NUMBER(-1);
int vendor_id_value = -2000;
String vendor_number = null;
try
cStmt = (OracleCallableStatement)dbTxn.createCallableStatement("begin *XXB_POS_PVT.create_vendo*r( p_vendor_name => :1, p_supplier_reg_id => :2, p_vendor_id=>:3); end;", 1);
cStmt.setString(1, regVORow.getSupplierName());
cStmt.setNUMBER(2, new Number(Integer.parseInt(supplierId)));
cStmt.registerOutParameter(3, 4);
cStmt.execute();
vendor_id = cStmt.getNUMBER(3);
vendor_id_value = vendor_id.intValue();
catch(SQLException e)
throw new OAException(e.getMessage());
Number vendorId = new Number(vendor_id_value);
regVORow.setVendorId(vendorId);
if(vendorId != null)
vendor_number = getSupplierVendorNumber(vendorId);
getOADBTransaction().commit();
AsiPosSupplierOpCosVOImpl regOpCosVO = (AsiPosSupplierOpCosVOImpl)this.getAsiPosSupplierOpCosVO1();
AsiPosSupplierOpCosVORowImpl row = null;
int fetchedRowCount = regOpCosVO.getFetchedRowCount();
RowSetIterator createIter1 = regOpCosVO.createRowSetIterator("createIter1");
if(fetchedRowCount > 0)
createIter1.setRangeStart(0);
createIter1.setRangeSize(fetchedRowCount);
for(int i = 0; i < fetchedRowCount; i++)
row = (AsiPosSupplierOpCosVORowImpl)createIter1.getRowAtRangeIndex(i);
if(row.getApprovalStatus().equalsIgnoreCase("HEAD_APPROVED"))
try
oadbtransactionimpl.writeDiagnostics(this,"Creating Site - " + vendor_id_value+" "+row.getSupplierOpcoCode()+" "+supplierId,1);
cStmt = (OracleCallableStatement)dbTxn.createCallableStatement("begin *XXB_POS_PVT.create_vendor_sites*(p_supplier_reg_id => :1, p_vendor_id=>:2, p_opco_code=>:3, p_vendor_site_id=>:4); end;", 1);
cStmt.setNUMBER(1, new Number(Integer.parseInt(supplierId)));
cStmt.setNUMBER(2, new Number(vendor_id_value));
cStmt.setString(3,row.getSupplierOpcoCode());
cStmt.registerOutParameter(4, 4);
cStmt.execute();
vendor_site_id = cStmt.getNUMBER(4);
getOADBTransaction().commit();
catch(SQLException e)
throw new OAException(e.getMessage());
createIter1.closeRowSetIterator();

Hi ,
There are some validation that can be performed from Entity level ( EO ) , you can go through them in Jdev guide .
It depends on the business requirement , not all validation can be performed from Entity level .
Let us know your business requirement , will try to clear your doubt .
--Keerthi

Got error when use case statement in oracle stored procedure

Hi,
I have a query like:
select merchant_id,
case
when product_type='K' then 'Production'
when product_carrier='UC' THEN 'Shipping'
end the_type
from product_tbl
where merchant_id=10114
It works fine. But as soon as I put it into a stored procedure, I got error like:
Encountered the symbol "CASE" when expecting one of the following:
( - + mod null <an identifier>
Please help!

Oracle 8i doesn't support CASE into PL/SQL, so as Kamal said, create a view with the CASE, and use this view into your PL/SQL.
Nicolas.
And an example here :
Re: Execute Immediate doesnot work in 8i (8.1.7) and Ref Cursor not exec qu
Sorry Kamal.
Message was edited by:
N. Gasparotto

Account Password Changed When Using OCI Drivers With WebLogic 6.0

Hello all,
Could be I am losing my mind but I saw some strange bahavior and I was wondering if anyone could offer an explination. We're running BEA WL6.0sp2 on an HPUX box with both an 8.1.7 client and server installation for development. We noticed that when we try to use the OCI driver to connect to our database, the password for our account is being changed on connection. This is definitely repeatable as we demonstrated it for the DBAs while they yelled at us. I highly doubt there is anything in WL that would cause the problem and everything works fine with the Thin drivers, with the JDrivers provided by BEA and with the credentials from SQL+.
Our problem is we need the Layer 2 OCI support. Is there something in the OCI client installation that would cause this behavior?

Hello all,
Could be I am losing my mind but I saw some strange bahavior and I was wondering if anyone could offer an explination. We're running BEA WL6.0sp2 on an HPUX box with both an 8.1.7 client and server installation for development. We noticed that when we try to use the OCI driver to connect to our database, the password for our account is being changed on connection. This is definitely repeatable as we demonstrated it for the DBAs while they yelled at us. I highly doubt there is anything in WL that would cause the problem and everything works fine with the Thin drivers, with the JDrivers provided by BEA and with the credentials from SQL+.
Our problem is we need the Layer 2 OCI support. Is there something in the OCI client installation that would cause this behavior?

ArrayIndexOutOfBoundException when using Callable Statement in Weblogic 8.1

Similar Messages

Maybe you are looking for