Inactive sessions in v$session. True problem
Hi,
I am working in an Oracle 9i/Weblogic/J2EE platform. And when i look for session info in v$session view, i see that there are many sessions that have a status "Inactive". I already figured out what it means- the session is ACTIVE when it is doing an SQL query at the time and the session is INACTIVE when it is not doing an SQL query at that particular moment.
But i have questions:
1) If a client logs in to my webapplication and does a SQL query- then the sessions status is ACTIVE. After that, when the client just leaves (logs out just closes the browser) then Oracle marks that connection as 'INACTIVE'- Oracle does not KILL that session.
Ok let that be, but can another client then log in to my webapplication (from different computer) and get that same INACTIVE connection and start to use it?? If not, then these "abandoned" connection are truly useless, because they still use ORACLE resources (memory).
2)Another thing is that there are many INACTIVE sessions in v$session that have a name "plsqldev.exe" in PROGRAM column. That is a database client that i use to connect directly to my DB. But basicly i have only one PL/SQL program with one SQL query window open (this session is marked ACTIVE in v$session). So are these other 10 INACTIVE "plsqldev.exe" sessions meant for new plsql clients that may start to use the database or can only that particular user for whom the session was created at first place use that session?
And finally- sessions that are INACTIVE and have "plsqldev.exe" as a PROGRAM in v$session - is there any chance that a client logs in to webapplication and then gets that INACTIVE session?
If not, then these 10 INACTIVE plsqldev sessions (allthough the user has maybe shut down the program) are wasteless for webapplication users and they just starve the database.
Also a screenshot for illustration.
Waiting for your comments,
Thanks!
If connection pooling is in use then yes a different end-user can reuse the "inactive" session. Remember that ACTIVE and INACTIVE really only refers to if the session is executing SQL at the exact moment you query v$session.
In the case of a dedicated user connection using a product like Oracle Forms where the user spends much of the time reading and filling in screen fields the Oracle background session can show INACTIVE almost constantly because the queries being ran by the user are very fast.
Take a look at the last_call_et column. This is the time in seconds from when the last SQL statement was issued (not completed). If this value is resetting then the queries are being done.
If the time is large and the status is INACTIVE then you could have a 'dead' or 'runaway' background process which is a background process without a front-end process. Those can and should be terminated. For that matter sessions that are idle for long periods of time should probably also be killed. If nothing else runaway and idle sessions may make it appear you are using all your licensed connections even if you really are not.
Most connection pools wil automatically restart a terminated connection so if you clean-up process terminates an idle pooled connection it should not be a problem.
HTH -- Mark D Powell --
Similar Messages
-
Inactive sessions in v$session
Hi,
why there are so many apps user inactive sessions in v$session?
RegardsHi Hussein,
The process which are arctive are shown as inactive in v$session view,We cannot trust the status column of this view,By default as soon the apps is started the oracle is creating around 82 to 85 apps processes which are inactive but i think they are active.
The option referenced above is a good one to follow in this situation
A discussion of Dead Connection Detection, Resource Limits, V$SESSION, V$PROCESS and OS processes
Thanks Hussein and Anchorage
Regards -
"Restore Session" in Firefox 2.x problem
We are using custom authorization. All works fine...when user logout or close its browser, his session cannot be reused.
Problem is with FF 2.02.
If any instance of FF has been violate killed (from process explorer or PC has been rebooted), on first next start, FF is able to restore all sessions.
The problem is that in our case, it can restore session on Apex 2.2 authenticated pages also!!
Any help to ensure that this behavior cannot occur in a case of subnormal termination of Firefox browser?
Apex 2.2.0.2 , Oracle 10.2.0.2
P.S
IE 6 or 7 is working OK!
THX!Maybe you are right...but...
<br>
I tried the same test with my internet banking (cannot give you a link because it is secured with token), the same problem is somehow solved!
<br>
This mean that FF "restore session" cannot reuse previous session in any way. So it seems that this technology (it is not apex but some jsp version) can handle with this really big security issue.
<br>
Please understand that site like ours would like to secure our Internet clients who will make allocation, registratatio or even sell the stocks!
<br>
So could anyone help me to implement such a feature or point me to where to look for the solution.
<br>
THX
<br>
P.S.
<br>
Article (forum thread) is missing the point. With word you are not going to pay the bills or sell the stocks or do any manipulation with sensitive data through Internet!
<br>
<b>browser.sessionstore.resume_from_crash</b> is on client side and it is not the default option. So we cannot place that kind of security in any way.
<br>
Message was edited by:
Funky -
Same session in diffrent browser tab problem
Hello;
I am having a problem (might be browsers claim it a feature) that my application shares the same session if I use to access it from different tabs of a browser.
I have googled but could not find out any work around for it.
I want to restrict the user if he wants to access my application from another tab. Server identifies the user by session cookie generated by browser itself which kept same in all tabs. So is there any programmatic way that I be able to handle this situation. I want to catch the user at Filter level and redirect to a message page.
Your comments...
-Tahir
Edited by: tahirakram on Jul 3, 2008 10:54 AMtahirakram wrote:
Karanjit wrote:
a) While displaying login page, check if the user has already logged in. If so, redirect the page to one that gets displayed when user successfully logs on avoiding mutiple logins.
b) In login authenication process, add a logic to check whether another user has already logged in and display so in the screen.Dear Karanjit;If user want to make multiple logins by opening multiple ie browsers. Then in this case every time session id will be unique and I have no problem with this case.
My issue is to implement such logic from where I can generate seprate session id from every tab/or landing user to a message page. <session id same in all tabs of a browser window>
As I disussed above there is a solution in ASP.net aka sessionless cookies [http://msdn.microsoft.com/en-us/library/aa479314.aspx#cookieless_topic2|http://msdn.microsoft.com/en-us/library/aa479314.aspx#cookieless_topic2]
You mean cookieless sessions. Cookieless sessions are not what you are asking. You can do the same here by setting the <Context> elements cookie attribute to false, and making sure you pass all URLs through response.encodeURL(String).
This doesn't help your cause, though, because if a user presses a link on your page with the CTRL key down, a new tab opens with the same session tracking info. Or if the user copies the URL in one tab and pastes it into another tab you get the same session in multiple tabs.
>
Now the question is, How can I achieve sessionless cookies in java? And the approach will work same as ASP.net works.The approach that you point to does not address the issue at all. In fact it makes it easier to use the same session in multiple windows, not just multiple tabs.
>
thanks -
The "Pin as app tab" produces tabs that do not persist across sessions. I have this problem on two installations (PC and laptop, both running Win7), and it's really annoying (since the Permatab Mod no longer works in Ff4). Can you offer any assistance?
App tabs and Tab Groups (Panorama) are stored as part of the session data in the file sessionstore.js in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder]
* http://kb.mozillazine.org/Session_Restore
Make sure that you do not use [[Clear Recent History]] to clear the "Browsing History" -
Problem in terminating the session in a session bean
Please any one would guide me how I can kill the session in a session bean so that when the user enters through the login page(jsp) of my application its username and password should be validated each time. Presently it is just valideted just for the first time when the user enters through the login page. But if the user logs out and then re-logins through the login page he is allowed to go ahead just on the basis of the correct username.
Regards,
Shouket Ali.Try to do the following.
1. Remove the session bean as soon as you are done with it. No point let it be alive, eating resources.
2. when user logs out, put the following code in the java/jsp file which handles the logging out operation.
a. session.removeAttribute(If_any_attribute_set_for_the_user);
b. Kill the cookies if any set related to the authentication/session.
c. HttpServletRequest.getSession().invalidate();
Things will work properly. -
Not be able to obtain a transacted session within stateless session bean
I need some assistance on creating a transacted session. For some reason while within a stateless session bean, I am unable to create a transacted session even though I'm specifying to create the transacted queue session. Can anyone provide any assistance to me on this? It would be much appreciated.
Here is the code snippets involved with the problem:
Code snipet from ejb-jar.xml:
<session>
<display-name>Initial Request</display-name>
<ejb-name>InitialRequestBean</ejb-name>
<ejb-class>com.raytheon.rds.jms.InitialRequestBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
Code from stateless session bean:
static Logger logger;
private QueueConnectionFactory connectionFactory;
private SessionContext sc;
private Queue requestQueue;
public String processRequest(String msgBody)
logger.log(Level.INFO, "In processRequest(String).", msgBody);
QueueConnection con = null;
QueueSession session = null;
QueueSender sender = null;
TextMessage message = null;
String messageID = null;
QueueReceiver receiver = null;
TemporaryQueue replyQueue = null;
boolean transacted = false;
try
//Create the infrastructure (ie. The connection & the session)
logger.log(Level.FINE, "Creating connection");
con = connectionFactory.createQueueConnection();
logger.log(Level.FINE, "Creating session");
session = con.createQueueSession(true, Session.AUTO_ACKNOWLEDGE);
//Note: This line above was changed in all possible permutation and still didn't work such as using Session.SESSION_TRANSACTED
transacted = session.getTransacted();
logger.log(Level.FINE, "Is session transacted? : " + transacted);
//Note: This line above is constantly saying false
//Now first, setup the temporary reply queue and its listener
replyQueue = session.createTemporaryQueue();
logger.log(Level.FINE, "Creating receiver/consumer");
receiver = session.createReceiver(replyQueue);
con.start();
//Now create the requestor that will make the request message and put it on the request queue
logger.log(Level.FINE, "Creating Requestor/Producer");
sender = session.createSender(requestQueue);
//Now create the message and make sure that you put the "JMSReplyTo" property to the temporary response queue we just created
message = session.createTextMessage();
message.setJMSReplyTo(replyQueue);
logger.log(Level.FINE, "Created message: " + message.getJMSMessageID());
//Now add the actual info you want to send
message.setText(msgBody);
//Now send the message
logger.log(Level.INFO, "Sending message: " + message.getText());
sender.send(message);
//Now wait until we get a response
logger.log(Level.FINE, "Waiting for the response message");
Message responseMsg = receiver.receive(20000); //Toggle the "0" to specify timeout in millisectionds
//Process the message
logger.log(Level.FINE, "Processing the response message");
if(null != responseMsg)
logger.log(Level.FINE, "responseMsg is : " + responseMsg.toString());
messageID = processMessage(responseMsg);
logger.log(Level.FINE, "Response is : " + messageID);
//close the connection
logger.log(Level.FINE, "Stopping the connection");
con.stop();
catch (Throwable t)
// JMSException could be thrown
logger.log(Level.SEVERE, "Exception Thrown in sendRequest: ", t);
sc.setRollbackOnly();
finally
//Close the sender
if (sender != null)
try
logger.log(Level.FINE, "Closing the sender");
sender.close();
catch (JMSException e)
logger.log(Level.WARNING, "JMSException Thrown when trying to close the sender to the request queue: ", e);
else
logger.log(Level.FINE, "Sender is already closed.");
//Close the receiver
if (receiver != null)
try
logger.log(Level.FINE, "Closing the receiver");
receiver.close();
catch (JMSException e)
logger.log(Level.WARNING, "JMSException Thrown when trying to close the receiver to the request queue: ", e);
else
logger.log(Level.FINE, "Receiver is already closed.");
//Close the session
if (session != null)
try
logger.log(Level.FINE, "Closing the session");
session.close();
catch (JMSException e)
logger.log(Level.WARNING, "JMSException Thrown when trying to close the session to the request queue: ", e);
else
logger.log(Level.FINE, "Session is already closed.");
//Close the connection
if (con != null)
try
logger.log(Level.FINE, "Closing the connection");
con.close();
catch (JMSException e)
logger.log(Level.WARNING, "JMSException Thrown when trying to close the connection to the reply queue: ", e);
else
logger.log(Level.FINE, "Connection is already closed.");
return messageID;
}I found the answer through lots of painful searching.
http://blogs.sun.com/fkieviet/entry/request_reply_from_an_ejb
This weblog from Frank Kieviet from a sun blog explains what's happening behind the scenes.
Then I proceeded to create a Bean-Managed Transaction out of my EJB, which is using EJB 3.0. This requires the tag:
@TransactionManagement(value= TransactionManagementType.BEAN)
Note: I got this information from http://download.oracle.com/docs/cd/B31017_01/web.1013/b28221/servtran001.htm#BAJIBAFF
Then I just added the code specified in Frank's blog and everything is working now. The main portion of the code looks like this now:
//begin the user transaction
ctx.getUserTransaction().begin();
//Create the infrastructure (ie. The connection & the session)
logger.log(Level.FINE, "Creating connection");
con = connectionFactory.createQueueConnection();
//Create the session
logger.log(Level.FINE, "Creating session");
session = con.createQueueSession(false, Session.SESSION_TRANSACTED);
transacted = session.getTransacted();
logger.log(Level.FINE, "Is session transacted? : " + transacted);
//Now create the sender that will make the request message and put it on the request queue
logger.log(Level.FINE, "Creating Sender");
sender = session.createSender(requestQueue);
//Now create the message
message = session.createTextMessage();
//Now add the actual info you want to send
message.setText(msgBody);
logger.log(Level.FINE, "Created message: " + message.getJMSMessageID());
//Now first, setup the temporary reply queue and its listener
replyQueue = session.createTemporaryQueue();
if(null != replyQueue)
logger.log(Level.FINE, "Created temporary queue: " + replyQueue.getQueueName());
else
logger.log(Level.FINE, "Temporary Queue could not be created.");
//make sure that you put the "JMSReplyTo" property to the temporary response queue we just created
message.setJMSReplyTo(replyQueue);
//Now send the message
logger.log(Level.INFO, "Sending message: " + message.getText());
sender.send(message);
//Now start the connection
logger.log(Level.FINE, "Starting the connection");
con.start();
//commit the changes
ctx.getUserTransaction().commit();
ctx.getUserTransaction().begin();
//Create the receiver
logger.log(Level.FINE, "Creating Receiver");
receiver = session.createReceiver(replyQueue);
//Now wait until we get a response
logger.log(Level.FINE, "Waiting for the response message");
Message responseMsg = receiver.receive(20000); //Toggle the "0" to specify timeout in millisectionds
//Process the message
logger.log(Level.FINE, "Processing the response message");
if(null != responseMsg)
logger.log(Level.FINE, "responseMsg is : " + responseMsg.toString());
else
logger.log(Level.FINE, "No response came back.");
messageID = processMessage(responseMsg);
logger.log(Level.FINE, "Response is : " + messageID);
logger.log(Level.FINE, "Transaction is complete");
//commit the changes
ctx.getUserTransaction().commit(); -
Can anyone explain v$session and gv$session ;
Prefix G in GV$ means GLOBAL. The best way to find out the the difference between v$session and gv$session is to look in v$fixed_view_definition.
V$SESSION
select SADDR,
SID,
SERIAL#,
AUDSID,
from GV$SESSION
where inst_id = USERENV('Instance')GV$SESSION
select s.inst_id,
s.addr,
s.indx,
s.ksuseser,
s.ksuudses,
s.ksusepro,
s.ksuudlui,
s.ksuudlna,
s.ksuudoct,
s.ksusesow,
decode(s.ksusetrn, hextoraw('00'), null, s.ksusetrn),
decode(s.ksqpswat, hextoraw('00'), null, s.ksqpswat),
decode(bitand(s.ksuseidl, 11),
1,
'ACTIVE',
0,
decode(bitand(s.ksuseflg, 4096), 0, 'INACTIVE', 'CACHED'),
2,
'SNIPED',
3,
'SNIPED',
'KILLED'),
decode(s.ksspatyp, 1, 'DEDICATED', 2, 'SHARED', 3, 'PSEUDO', 'NONE'),
s.ksuudsid,
s.ksuudsna,
s.ksuseunm,
s.ksusepid,
s.ksusemnm,
s.ksusetid,
s.ksusepnm,
decode(bitand(s.ksuseflg, 19),
17,
'BACKGROUND',
1,
'USER',
2,
'RECURSIVE',
s.ksusesql,
s.ksusesqh,
s.ksusesqi,
decode(s.ksusesch, 65535, to_number(null), s.ksusesch),
s.ksusepsq,
s.ksusepha,
s.ksusepsi,
decode(s.ksusepch, 65535, to_number(null), s.ksusepch),
decode(s.ksusepeo, 0, to_number(null), s.ksusepeo),
decode(s.ksusepeo, 0, to_number(null), s.ksusepes),
decode(s.ksusepco, 0, to_number(null), s.ksusepco),
decode(s.ksusepco, 0, to_number(null), s.ksusepcs),
s.ksuseapp,
s.ksuseaph,
s.ksuseact,
s.ksuseach,
s.ksusecli,
s.ksusefix,
s.ksuseobj,
s.ksusefil,
s.ksuseblk,
s.ksuseslt,
s.ksuseltm,
s.ksusectm,
decode(bitand(s.ksusepxopt, 12), 0, 'NO', 'YES'),
decode(s.ksuseft,
2,
'SESSION',
4,
'SELECT',
8,
'TRANSACTIONAL',
'NONE'),
decode(s.ksusefm, 1, 'BASIC', 2, 'PRECONNECT', 4, 'PREPARSE', 'NONE'),
decode(s.ksusefs, 1, 'YES', 'NO'),
s.ksusegrp,
decode(bitand(s.ksusepxopt, 4),
4,
'ENABLED',
decode(bitand(s.ksusepxopt, 8), 8, 'FORCED', 'DISABLED')),
decode(bitand(s.ksusepxopt, 2),
2,
'FORCED',
decode(bitand(s.ksusepxopt, 1), 1, 'DISABLED', 'ENABLED')),
decode(bitand(s.ksusepxopt, 32),
32,
'FORCED',
decode(bitand(s.ksusepxopt, 16), 16, 'DISABLED', 'ENABLED')),
s.ksusecqd,
s.ksuseclid,
decode(s.ksuseblocker,
4294967295,
'UNKNOWN',
4294967294,
'UNKNOWN',
4294967293,
'UNKNOWN',
4294967292,
'NO HOLDER',
4294967291,
'NOT IN WAIT',
'VALID'),
decode(s.ksuseblocker,
4294967295,
to_number(null),
4294967294,
to_number(null),
4294967293,
to_number(null),
4294967292,
to_number(null),
4294967291,
to_number(null),
bitand(s.ksuseblocker, 2147418112) / 65536),
decode(s.ksuseblocker,
4294967295,
to_number(null),
4294967294,
to_number(null),
4294967293,
to_number(null),
4294967292,
to_number(null),
4294967291,
to_number(null),
bitand(s.ksuseblocker, 65535)),
s.ksuseseq,
s.ksuseopc,
e.kslednam,
e.ksledp1,
s.ksusep1,
s.ksusep1r,
e.ksledp2,
s.ksusep2,
s.ksusep2r,
e.ksledp3,
s.ksusep3,
s.ksusep3r,
e.ksledclassid,
e.ksledclass#,
e.ksledclass,
decode(s.ksusetim,
0,
0,
-1,
-1,
-2,
-2,
decode(round(s.ksusetim / 10000),
0,
-1,
round(s.ksusetim / 10000))),
s.ksusewtm,
decode(s.ksusetim,
0,
'WAITING',
-2,
'WAITED UNKNOWN TIME',
-1,
'WAITED SHORT TIME',
decode(round(s.ksusetim / 10000),
0,
'WAITED SHORT TIME',
'WAITED KNOWN TIME')),
s.ksusesvc,
decode(bitand(s.ksuseflg2, 32), 32, 'ENABLED', 'DISABLED'),
decode(bitand(s.ksuseflg2, 64), 64, 'TRUE', 'FALSE'),
decode(bitand(s.ksuseflg2, 128), 128, 'TRUE', 'FALSE')
from x$ksuse s, x$ksled e
where bitand(s.ksspaflg, 1) != 0
and bitand(s.ksuseflg, 1) != 0
and s.ksuseopc = e.indxAlexander Anokhin
http://alexanderanokhin.wordpress.com/ -
Session Replication and Session Timeout -- Urgent
WLS -4.5.1 SP 11
OS - both NT and Sol
HI All
The session does not seems to timeout when running the Weblogic servers in
clustered mode with in-memory session replication on.
This problem seems to be there in version5.1 too , as per another post , it
seems to be solved in WLS5.1 sp 8
Could anyone pls confirm in which patch in WLS 4.5.1 is the problem
addressed . I'm using patch 11 and am getting the problem.
Thanks in advance..
-Surya
Try SP13 and if the problem persists, contact [email protected]
-K
Surya B Maithani wrote:
> WLS -4.5.1 SP 11
> OS - both NT and Sol
>
> HI All
>
> The session does not seems to timeout when running the Weblogic servers in
> clustered mode with in-memory session replication on.
> This problem seems to be there in version5.1 too , as per another post , it
> seems to be solved in WLS5.1 sp 8
>
> Could anyone pls confirm in which patch in WLS 4.5.1 is the problem
> addressed . I'm using patch 11 and am getting the problem.
>
> Thanks in advance..
>
> -Surya
-
Could not create/access the TopLink Session. This session is used to connect to the datastore.
We are getting the below error in our production server & also other servers(UAT, Staging). Only option is to restart the OSB server.
Test connection is working fine and able to connect the database without any issue. We have enabled connection leak profiling and also, provided the inactive time outs , still does not work. Need your suggestion for the below error.
***endpoint***:https://extzwsdev.zurichna.com/services/RiskAnalysis-v1***
Payload<soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:ris = "http://webservices.zurich.com/zsoa/nac/underwritingmanagement/riskanalysis-v1_0" xmlns:zsoa = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/zsoa" xmlns:com = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/common" xmlns:con = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/contractandspecification" xmlns:fin = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/financialservicesagreement" xmlns:par = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/party" xmlns:act = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/activityconditionplace"> <soapenv:Header/> <soapenv:Body> <ris:calculateTargetPolicyRateChangeByProductGroup> <ris:insurancePolicySearchCriteria> <con:externalReference>1151638</con:externalReference> </ris:insurancePolicySearchCriteria> </ris:calculateTargetPolicyRateChangeByProductGroup> </soapenv:Body></soapenv:Envelope>
***RTOneService Output Response*** <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-380001: [invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
... 32 more
Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:152)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
... 1 more
Caused by: BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at oracle.tip.adapter.db.exceptions.DBResourceException.createRetriableException(DBResourceException.java:676)
at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:645)
at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:314)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:918)
at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
... 38 more
Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(Unknown Source)
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.getMetaData(Unknown Source)
at weblogic.jdbc.wrapper.Connection.getMetaData(Connection.java:479)
at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:122)
at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:92)
at oracle.tip.adapter.db.toplinkext.NameEnquoter.<init>(NameEnquoter.java:59)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:705)
at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
... 1 more
.</faultstring><detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context"><con:errorCode>BEA-380001</con:errorCode><con:reason>[invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
... 32 more
Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:152)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
... 1 more
Caused by: BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at oracle.tip.adapter.db.exceptions.DBResourceException.createRetriableException(DBResourceException.java:676)
at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:645)
at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:314)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:918)
at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
... 38 more
Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(Unknown Source)
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.getMetaData(Unknown Source)
at weblogic.jdbc.wrapper.Connection.getMetaData(Connection.java:479)
at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:122)
at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:92)
at oracle.tip.adapter.db.toplinkext.NameEnquoter.<init>(NameEnquoter.java:59)
at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:705)
at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
... 1 more
.</con:reason><con:location><con:node>RouteNode1</con:node><con:path>response-pipeline</con:path></con:location></con:fault></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
!!! Exception occurred <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-380001: [invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
... 32 more
Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkMaIts hard to say what is going on. Though the message says the error is in obtaining a TopLink session, the exception stack has nothing to do with TopLink, and the error seems to be coming from oracle.tip.adapter.db.toplinkext.NameEnquoter.init() directly calling weblogic.jdbc.wrapper.Connection.getMetaData() on what must be a stale or closed connection. This looks like a DB adapter application, so you might want to post this question there as they might be able to help configure your datasource appropriately for the application.
Best Regards,
Chris -
Clear the entry for killed/sniped session in v$session
Dear all,
In our production database(11.2.0.1.0) running on windows 2008 server many client session showing inactive from last 4-5 hour and I want to kill those session because all sessions are dedicated so for this I created a resource plan set its idle time after certain interval session status is showing killed but it is not removing entries from v$session but our client demand is it must be clear from v$session so for this i was using DOS command taskkill utility to kill particular os process so I want to know what is the smartest way to do this.This is known behavior, not an issue.
In a dedicated server environment when the session is killed and the rollback completes the process goes away so a join between v$session and v$process will fail. The v$session entry also usually goes away rather quickly, though I have seen cases where the v$session entry hung around till the instance was bounced. But normally Oracle will overlay the v$session entry with a new session using the same sid but a different serial# within seconds on a busy system.
Mark @ http://dbaspot.com/oracle-server/40419-killed-sessions.html
Metalink doc id 1023442.6 is also something confirming it.
See also below link and last reply by Mr. Braj Kishore Mahto.
http://dbaforums.org/oracle/index.php?showtopic=3039
Regards
Girish Sharma
Edited by: Girish Sharma on Nov 21, 2012 5:35 PM
So, what is best in this regard :
ALTER SYSTEM DISCONNECT SESSION
The ALTER SYSTEM DISCONNECT SESSION syntax is an alternative method for killing Oracle sessions. Unlike the KILL SESSION command which asks the session to kill itself, the DISCONNECT SESSION command kills the dedicated server process (or virtual circuit when using Shared Sever), which is equivalent to killing the server process from the operating system. The basic syntax is similar to the KILL SESSION command with the addition of the POST_TRANSACTION clause. The SID and SERIAL# values of the relevant session can be substituted into one of the following statements.
SQL> ALTER SYSTEM DISCONNECT SESSION 'sid,serial#' POST_TRANSACTION;
SQL> ALTER SYSTEM DISCONNECT SESSION 'sid,serial#' IMMEDIATE;
http://www.oracle-base.com/articles/misc/killing-oracle-sessions.php#disconnect_session -
Hi Team,
In Production IC AGENT Bussines role ,I have configured the bussines role.in DEV,and QA system it is working fine...in production ,iam getting error as below.
Worker session error in session initialization(SAM_QUEUE NOT SET )
Type = SYSTEM_ERROR,ID = ERROR_SESSOPN_INIT,description=
Could youe please help here..
Thanks
KalpanaHi Kalpana,
Please take a look at KBA 1954574 - Problems with CRM IC Functionalities related to Communication Session (alerts, greyed out ready/not ready buttons, agent dashboard) in complex system landscapes
This details a few things you need to check.
Let me know how you get on. If you have any questions or concerns.
Kind Regards,
James -
Get the current session in a Session Bean?
Hi,
I know how to get the current session from a Servlet, you use request.getSession().
However I need access to the current session from a Session Bean. As far as I know, only Servlets have a request object, so I can't use request.getSession()
Any ideas on how to access the session from a Session Bean?
Thanks!Hi,
I managed to get around the problem by using a JSP to
pass a session object to a method in my session bean.
ThanksJust be aware that the serialized Session object can be a huge stream to remotely pass to your bean...
Kexkey -
FF7.0 beta
sync on laptop and desktop
no tab history of the other devices
solution to start session with latest session of synced device?
win 7 64bitGood instinct not to shut down!
Open your current Firefox settings (AKA Firefox profile) folder using
Help > Troubleshooting Information > "Show Folder" button
Copy all sessionstore files (e.g., sessionstore.bak, sessionstore.js) to a safe location (e.g., your Documents folder). Whatever was saved before is in one or both of those files.
This problem of a window sometimes loading the correct number of tabs but the tabs not being navigated to the corresponding pages has been mentioned before, but I do not recall anyone identifying what causes it or how to solve it. If Firefox saved the URLs of those pages, they will be in one or both of those sessionstore files.
These threads have suggestions on how to "mine" the old file to extract the URLs:
* Using Firefox's Browser Console (formerly known as Error Console): https://support.mozilla.org/en-US/questions/969046#answer-471950
* Using Firefox developer tool "Scratchpad": http://forums.mozillazine.org/viewtopic.php?f=38&t=622036&start=60&p=12098147#p12098147
* Using a third party website: https://firefox-session-restore.herokuapp.com/
Can you recover them? -
Session.removeAttribute and session.invalidate
I pass a scoped object from one JSP #1 to JSP #2 in a session.
In JSP #1, I did:
<c:set var="cr" value="${articleForm.creator}" scope="session"/>In JSP #2, I did:
<bean:define id="author" name="cr" scope="session" type="java.lang.String"/>
<html:text property="receiver" value="<%=author%>" size="82" maxlength="25" tabindex="1"/>Immediately after I output the value, I want to remove the object from the session. I have two questions:
1. which one of the following should I do:
session.removeAttribute( "cr" );or
session.removerAttribute( "author" );or
session.removeAttribute( "receiver" );2. Do I have to invalidate the session; i.e. session.invalidate(); after all the objects in the session are removed?I pass a scoped object from one JSP #1 to JSP #2 in a session.
In JSP #1, I did:
<c:set var="cr" value="${articleForm.creator}" scope="session"/>In JSP #2, I did:
<bean:define id="author" name="cr" scope="session" type="java.lang.String"/> <html:text property="receiver" value="<%=author%>" size="82" maxlength="25" tabindex="1"/>Immediately after I output the value, I want to remove the object from the session. Which one of the following should I do:
session.removeAttribute( "cr" );or
session.removerAttribute( "author" );or
session.removeAttribute( "receiver" );
Maybe you are looking for
-
Thumbnail images not showing up in my Spry slideshow
Hello - Everything seems to be working in my Spry slideshow. However, my thumbnail images are not showing up in Live view or browser. The images are all in the correct folder. Here is what the script looks like: <ul id="ImageSlideShow" title="Our Pro
-
How to determine portal user in a BSP
Hi, is it possible to determine the current logged in portal user in a BSP iView? If it's possible, how? regards
-
How to set JSESSION ID as secure in Weblogic 10.3.5.0
Hi, I wanted to set my cookies secure, I am trying to make jsesion Id cookie also secure. We are using Weblogic 10.3.5.0, For all other cookies we set, cookies.setSecure(true) while creating the cookie itself as per Servlet API. But for JSession Id,
-
401-Not Authorized to view 192.168.1.1
Help! I think my wireless router is all messed up. Now I can't even view the webpage to see my router status. Where do I go or how can I get access to view my router information?
-
Hi, I was just wondering if you could help me with a question. I bought a pre-paid one year redemption card from PC World in February and have the complete bundle of all CC apps, I noticed that the Complete - for new customers is now listed as ... so