Preparedstatement usage
Hi Everybody,
Is preparedStatement better than statement only in case of executeBatch method???
Kindly shed some light on this.
Regards
Ashwin
WorkForFood,
>
Gosh, your post seems a bit harsh towards me, you
must feel very strongly about this issue. I read
your post, and we seem to agree on most points, does
that make you nonsensical too? I know that in an
open forum, I wouldn't use that term to describe you
(or in a closed one either). I have seen your
comments in other posts, and I would suggest that you
are both knowledgable and helpful to others. Perhaps
I failed to communicate my points well and perhaps I
interpreted your response to personally.
No. In retrospect the fault is mine. I get tired of some of the same questions and misconeptions (as raised by the OP) raised time and time again.
More than that I took your response too personally and for that I am sorry. Please accept my sincere apologies.
The singular salient point that we appear to disagree
on, is this one.
To be clear, I only use Satement when
PreparedStatement will not provide adequate
performance, which is also what I would recommendto
others.
This is a very dangerous recommendation.
You as a developer cannot and should not rely onthe
database never changing. If that were the casethen
what is the point of having JDBC at all? The point
ultimatley is that you can write code that worksnow
AND in the future.
If you adopt bad practices (and sacrificing
portability and maintainability for nanoseconds of
performance is a bad practice) then you havedefeated
this point and your application may well sufferfor
it.You make excellent points here, I cannot find fault
in them when applied to new development efforts, most
often focused on transactional processing. However,
being a DBA and only a part time Java programmer, I
have run into many circumstances where the ability to
alter the design of the application stretched beyond
what was practical, and "Statements", or looking at
this more generically, "dynamic SQL", was used to
resolve a performance issues caused by weaknesses in
the database optimizer. In my case, we are talking
about the difference between useable and unusable
applications, with the difference being hours, not
simply shaving nanoseconds from performance.
It is certainly possible that my many years in
database and development have culminated to nothing
more then nonsense, but I sure hope not. I'm sorry
if I offended you with what you describe as a
nonsense post, I was only attempting to share my
experiences with the OP, and let the OP know that
perhaps "PreparedStatement is always better then
Statement" should be considered as a guide, not an
unbreakable rule. And on that point, I can only
assume that we will continue to disagree.
Thank you for sharing your thoughts on this.To be frank I agree with you in theory, however, I disagree with giving this advice on this forum.
To me people who ask these kinds of questions have not grasped enough of the issues at stake to make a qualified determination of what they should be doing and when. I truly believe that 99.99% of those who are asking questions in this forum should almost always be using PreparedStatements and thus I believe the use of PreparedStatements should always be encouraged. If as a result of experience and knowledge one comes to the conclusion that the use of Statement would be more appropriate than so be it.
The real issue I have is that I know that if someone doesn't say use PreparedStatements alot the unexperienced may assume that they should only use PreparedStatements under some circumstances and that their only benefit is for performance and only sometimes for that.
It is the same reason why most posts to do with memory size of objects as asked in the New to Java Programming forum are best answered by saying "dont do that" and "premature optimization is evil". Are there some cases in which knowing such a thing would be useful. Yes. But each one of the relative neophytes wrongly assumes that theirs is the right case and the fact is that almost always it isn't.
Similar Messages
-
Clustering of SQL query execution times
In doing some query execution experiments I have noted a curious (to me, anyhow) clustering of execution times around two distinct points. Across about 100 tests each running 1000 queries using (pseudo-)randomly generated IDs the following pattern emerges. The queries were run from Java using all combinations of pooled/non-pooled and thin/oci driver combinations:
100 *
90 *
R 80 *
u 70 *
n 60 *
s 50 *
40 * *
30 * *
20 * * * *
10 * * * * * *
0 100 200 300 400 500 600 700 800 900 1000 1100 1200
Time(ms)Where about half of the total execution times cluster strongly about a given (short) time value with a smaller but broader clustering at a significantly slower mark, with zero intermediate values. The last point is the one I find most curious.
What I would have expected is something like this:
100
90
R 80
u 70
n 60
s 50
40 *
30 * * *
20 * * * * * *
10 * * * * * * * * * *
0 100 200 300 400 500 600 700 800 900 1000 1100 1200
Time(ms)The variables I have tentatively discounted thus far:
-query differences (single query used)
-connection differences (using single pooled connection)
-garbage collection (collection spikes independent of query execution times)
-amount of data returned in bytes (single varchar2 returned and size is independent of execution time)
-driver differences (thin and oci compared, overall times differ but pattern of clustering remains)
-differences between Statement and PreparedStatement usage (both show same pattern)
I know this is a rather open-ended question, but does the described pattern seem faniliar or spark any thoughts?
DB-side file I/O?
Thread time-slicing variations (client or DB-side)?
FWIW, the DB is 9.2.0.3 DB and the clients are running on WinXP with Java 5.0 and 9i drivers.
Thanks and regards,
MFurther context:
Are your queries only SELECT queries ?
Yes, the same SELECT query is used for all tests. The only variable is the bind variable used to identify the primary key of the selection set (i.e. SELECT a.* from a, b, c where a.x = b.x and b.y = c.y and c.pk = ?) where all PKs and FKs are indexed.Do the queries always use the same tables, the same where clauses ?
Yes, the same tables are always invoked. The where clauses invoked are identical with the excepton of the single bind variable as described above.Do your queries always use bind variables ?
A single bind variable is used in all invocations as described above.Are your queries also running in single user mode or multi user mode (do you use SELECT FOR UPDATE ?) ?
We are not using SELECT FOR UPDATEDid something else run on the database/on the server hosting the database on the same time ?
I have not eliminated the idea, but the test has been repeated roughly 100 times over the course of a week and at different times of day with the same pattern emerging. I suppose it is not out of the question that a resource-hogging process is running consistently and constantly on the DB-side box.Thanks for the input,
M -
It is indicated in most documents that can be found online that it is a better practice to use PreparedStatements everywhere instead of statements for many reasons I won't state here again.
Although, since PreparedStatements are pre-compiled on the side of the DB and kept over there, I am guessing there must be a specific amount of simultaneous PreparedStatements that can be kept within a session with the DB, or that there is some kind of longevity associated with such pre-compiled statements.
Which would it be? One of them, both, neither?
Thanks in advance
-DalzhimA PS stays open until you close() it (or close() the associated connection).
Some databases place explicit restrictions on the number of PS's. E.g. the default on Oracle is something like 128; it is configurable. Or a DB might just allow as many open PS's as you want, until the db server runs out of memory (= very bad).
In practice, you should usually close your PS's after using them. Preparing a statement should take the order of a millisecond. Although that will vary - very very complex and long statements can take longer (those you should make into stored procedures anyway.) If you really care, time your db server. If the forum search thingie actually worked you could find a ready-made timing program of mine in this very forum...
In extreme circumstances, you could keep a small handful of PSs open permanently. These would be PSs that profiling shows are used several times a second all the time.
It makes little sense to keep open a PS that is used, say, a few times per minute. Remember: you save only a fractional millisecond, and PS's cost memory in the server. -
How to retrieve a SQL query (in String format) from a PreparedStatement
Hello all,
I am in the process of unit testing an application accessing a Oracle 9i 9.2 RDBMS server with JDBC.
My query is:
As I have access to PreparedStatement and CallableStatement Java objets but not to the source queries which help create those objects?
Is thtere a simple way by using an API, to retrieve the SQL command (with possible ? as placeholders for parameters).
I have already looked at the API documentation for those two objets (and for the Statement and ResultSetmetaData objects too) but to no avail.
Thank you for any help on this issue,
Best regards,
BenoîtSorry for having wasted your time... and for not understanding what you meant in your first reply.
But the codlet was only to show the main idea:
Here is the code which compiles OK for this approach to reach its intended goal:
main class (file TestSuiteClass.java):
import java.sql.*;
import static java.lang.Class.*;
* Created by IntelliJ IDEA.
* User: bgilon
* Date: 15/03/12
* Time: 10:05
* To change this template use File | Settings | File Templates.
public class TestSuiteClass {
public static void main(final String[] args) throws Exception {
// Class.forName("oracle.jdbc.OracleDriver");
final Connection mconn= new mConnection(
DriverManager.getConnection("jdbc:oracle:thin:scott/tiger@host:port:service"));
* final Statement lstmt= TestedClass.TestedMethod(mconn, ...);
* final String SqlSrc= mconn.getSqlSrc(lstmt).toUpperCase(), SqlTypedReq= mconn.getTypReq(lstmt);
* assertEquals("test 1", "UPDATE IZ_PD SET FIELD1= ? WHERE FIELDPK= ?", SqlSrc);
Proxy class (file mConnector.java):
import java.sql.*;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
import java.util.Properties;
* Created by IntelliJ IDEA.
* User: bgilon
* Date: 15/03/12
* Time: 10:05
* To change this template use File | Settings | File Templates.
* This file should be compiled with JDK 1.6, but can be used with previous JDK versions.
* See OKwith1pN booleans usage for not throwing Exceptions as Unknown methods by the conn object...
public final class mConnection implements Connection {
private final Connection conn;
private final List<Statement> Stmts= new ArrayList<Statement>();
private final List<String> SqlSrcs= new ArrayList<String>();
private final List<Integer> TypSrcs= new ArrayList<Integer>();
private final static String jvmv= System.getProperty("java.specification.version");
private static final boolean OKwith1p2;
private static final boolean OKwith1p4; /* OKwith1p5, */
private static final boolean OKwith1p6;
static {
/* jvmv= System.getProperty("java.version");
System.out.println("jvmv = " + jvmv);
jvmv= System.getProperty("java.vm.version");
System.out.println("jvmv = " + jvmv); */
System.out.println("jvmv = " + jvmv);
OKwith1p2= (jvmv.compareTo("1.2") >= 0);
OKwith1p4= (jvmv.compareTo("1.4") >= 0);
// OKwith1p5= (jvmv.compareTo("1.5") >= 0);
OKwith1p6= (jvmv.compareTo("1.6") >= 0);
public String getSqlSrc(final Statement pstmt) {
int ix= 0;
for(Statement stmt : this.Stmts) {
if(stmt == pstmt) return SqlSrcs.get(ix);
ix+= 1;
return null;
static private final String[] TypeNames= new String[] { "Statement", "PreparedStatement", "CallableStatement" };
public String getTypReq(final Statement pstmt) {
int ix= 0;
for(Statement stmt : this.Stmts) {
if(stmt == pstmt) return TypeNames[TypSrcs.get(ix)];
ix+= 1;
return null;
private void storedStatement(
final Statement stmt,
final String sqlSrc,
final Integer typReq
Stmts.add(stmt);
SqlSrcs.add(sqlSrc);
TypSrcs.add(typReq);
public Connection getDecoratedConn() {
return conn;
mConnection(final Connection pconn) {
this.conn= pconn;
public boolean isClosed() throws SQLException {
return conn.isClosed();
public void rollback(Savepoint savepoint) throws SQLException {
if(OKwith1p4) conn.rollback(savepoint);
public boolean isReadOnly() throws SQLException {
return conn.isReadOnly();
public int getTransactionIsolation() throws SQLException {
return conn.getTransactionIsolation();
public void setTransactionIsolation(int level)throws SQLException {
conn.setTransactionIsolation(level);
public Properties getClientInfo() throws SQLException {
return OKwith1p6 ? conn.getClientInfo() : null;
public <T> T unwrap(Class<T> iface)
throws SQLException {
return conn.unwrap(iface);
public void setAutoCommit(boolean auto) throws SQLException {
conn.setAutoCommit(auto);
public boolean getAutoCommit() throws SQLException {
return conn.getAutoCommit();
public Map<String,Class<?>> getTypeMap() throws SQLException {
if(!OKwith1p2) return null;
return conn.getTypeMap();
public void setTypeMap(Map<String,Class<?>> map) throws SQLException {
if(!OKwith1p2) return;
conn.setTypeMap(map);
public void setHoldability(final int holdability) throws SQLException {
if(OKwith1p4) conn.setHoldability(holdability);
public Struct createStruct(String typeName, Object[] attributes) throws SQLException {
return conn.createStruct(typeName, attributes);
public void commit() throws SQLException {
conn.commit();
public void rollback() throws SQLException {
conn.rollback();
public boolean isValid(int timeout) throws SQLException {
return OKwith1p6 && conn.isValid(timeout);
public void clearWarnings() throws SQLException {
conn.clearWarnings();
public int getHoldability() throws SQLException {
if(!OKwith1p4) return -1;
return conn.getHoldability();
public Statement createStatement() throws SQLException {
return conn.createStatement();
public PreparedStatement prepareStatement(final String SqlSrc) throws SQLException {
if(!OKwith1p2) return null;
final PreparedStatement lstmt= conn.prepareStatement(SqlSrc);
storedStatement(lstmt, SqlSrc, 1);
return lstmt;
public PreparedStatement prepareStatement(String sql, String[] columnNames) throws SQLException {
if(!OKwith1p4) return null;
final PreparedStatement lstmt= conn.prepareStatement(sql, columnNames);
storedStatement(lstmt, sql, 1);
return lstmt;
public PreparedStatement prepareStatement(String sql, int resultSetType, int resultSetConcurrency) throws SQLException {
final PreparedStatement lstmt= conn.prepareStatement(sql, resultSetType, resultSetConcurrency);
storedStatement(lstmt, sql, 1);
return lstmt;
public PreparedStatement prepareStatement(String sql, int[] columnIndexes) throws SQLException {
final PreparedStatement lstmt= conn.prepareStatement(sql, columnIndexes);
storedStatement(lstmt, sql, 1);
return lstmt;
public void setClientInfo(String name, String value) throws SQLClientInfoException {
if(OKwith1p6)
conn.setClientInfo(name, value);
public PreparedStatement prepareStatement(final String SqlSrc,
int resultType,
int resultSetCurrency,
int resultSetHoldability) throws SQLException {
final PreparedStatement lstmt= conn.prepareStatement(SqlSrc, resultType, resultSetCurrency);
storedStatement(lstmt, SqlSrc, 1);
return lstmt;
public PreparedStatement prepareStatement(final String SqlSrc,
int autogeneratedkeys) throws SQLException {
if(!OKwith1p4) return null;
final PreparedStatement lstmt= conn.prepareStatement(SqlSrc, autogeneratedkeys);
storedStatement(lstmt, SqlSrc, 1);
return lstmt;
public CallableStatement prepareCall(final String SqlSrc) throws SQLException {
final CallableStatement lstmt= conn.prepareCall(SqlSrc);
storedStatement(lstmt, SqlSrc, 2);
return lstmt;
public CallableStatement prepareCall(final String SqlSrc,
int resultType,
int resultSetCurrency,
int resultSetHoldability) throws SQLException {
if(!OKwith1p4) return null;
final CallableStatement lstmt= conn.prepareCall(SqlSrc, resultType, resultSetCurrency, resultSetHoldability);
storedStatement(lstmt, SqlSrc, 2);
return lstmt;
public Array createArrayOf(String typeName, Object[] elements) throws SQLException {
return OKwith1p6 ? conn.createArrayOf(typeName, elements) : null;
public CallableStatement prepareCall(final String SqlSrc,
int resultType,
int resultSetCurrency) throws SQLException {
if (!OKwith1p2) return null;
final CallableStatement lstmt= conn.prepareCall(SqlSrc, resultType, resultSetCurrency);
storedStatement(lstmt, SqlSrc, 2);
return lstmt;
public SQLXML createSQLXML() throws SQLException {
return OKwith1p6 ? conn.createSQLXML() : null;
public DatabaseMetaData getMetaData() throws SQLException {
return conn.getMetaData();
public String getCatalog() throws SQLException {
return conn.getCatalog();
public void setCatalog(final String str) throws SQLException {
conn.setCatalog(str);
public void setReadOnly(final boolean readonly) throws SQLException {
conn.setReadOnly(readonly);
public Statement createStatement(int resultSetType, int resultSetConcurrency, int resultSetHoldability) throws SQLException {
return conn.createStatement(resultSetType, resultSetConcurrency, resultSetHoldability);
public Statement createStatement(int resultSetType, int resultSetConcurrency) throws SQLException {
if(!OKwith1p2) return null;
return conn.createStatement(resultSetType, resultSetConcurrency);
public String nativeSQL(final String sql) throws SQLException {
return conn.nativeSQL(sql);
public void releaseSavepoint(Savepoint savepoint) throws SQLException {
if(OKwith1p4) conn.releaseSavepoint(savepoint);
public Savepoint setSavepoint() throws SQLException {
return OKwith1p4 ? conn.setSavepoint() : null;
public Savepoint setSavepoint(final String str) throws SQLException {
return OKwith1p4 ? conn.setSavepoint(str) : null;
public boolean isWrapperFor(Class iface) throws SQLException {
return conn.isWrapperFor(iface);
public String getClientInfo(final String str) throws SQLException {
return OKwith1p6 ? conn.getClientInfo(str) : null;
public void setClientInfo(final Properties pro) throws SQLClientInfoException {
if (OKwith1p6) conn.setClientInfo(pro);
public Blob createBlob() throws SQLException {
return OKwith1p6 ? conn.createBlob() : null;
public Clob createClob() throws SQLException {
return OKwith1p6 ? conn.createClob() : null;
public NClob createNClob() throws SQLException {
return OKwith1p6 ? conn.createNClob() : null;
public SQLWarning getWarnings() throws SQLException {
return conn.getWarnings();
public void close() throws SQLException {
conn.close();
Final word:
The final word about this is: there is currently three ways to obtain source SQL queries from compiled statement objects.
a) Use a proxy class the mConnector above;
b) Use a proxy JDBC driver as Log4JDBC;
c) Use the trace facility of the driver (however, post analyzing the logs would depend upon the driver selected).
Thank you for reading,
Benoît -
PreparedStatement and open cursors
Hi,
i write an application where it is necessary to get a lot of preparedStatements in one connection. The preparedStatements are used
only once and they are closed after the usage. But it seems to me that this close
has no effect. Depending on the value in open cursors the error ORA - 01000 raises and it is not possible to get another preparedStatement without closing and opening the connection. But that increases the runtime to much and the application is a performance-critical application.
Does anyone have an idea how to solve the problem?
Thanks>
Any thoughts what could be the problem. Only time I ever got them was because the result set, statement, connection wasn't being closed or wasn't being closed in the correct order. -
AbstractMethodError while calling PreparedStatement.setBinaryStream()
I am getting AbstractMethodError while calling PreparedStatement.setBinaryStream(int, InputStream) for a BLOB column
I am using Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit
JDBC Driver ojdbc6.jar (downloaded from oracle website corresponding to 11.2.0.2 version)
JDK 6
I understand this error is due to my code calling abstract method which is not available in JDBC 3.x and it requires JDBC 4.0
But I am not able to find any traces of usage of earlier version of driver.
Debugging steps performed with results are as below
1) I enabled -verbose:class VM argument that outputs all the classes loaded along with jar from which it loads. Everywhere i see ojdbc6.jar (No reference to older or any other jdbc driver jar file)
2) Below is code segment and its output
Connection con = getConnection(); // get connection
DatabaseMetaData d= con.getMetaData();
d.getDatabaseProductName(); // output: Oracle
d.getDatabaseProductVersion(); // output: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
d.getDatabaseMajorVersion(); // output: 11
d.getDatabaseMinorVersion(); // output: 2
d.getDriverName(); // output: Oracle JDBC driver
d.getDriverVersion(); // output: 11.2.0.2.0
d.getDriverMajorVersion(); // output: 11
d.getDriverMinorVersion(); // output: 2
d.supportsGetGeneratedKeys(); // output: true
3) I updated code (its third party component, so not suppose to update :( )
Added third argument whick works fine (it means at runtime it is using older jdbc driver???)
PreparedStatement.setBinaryStream(int, InputStream, (int)length
Please let me know if i am missing anything here... how can i solve this issue?
Thanks!From my initial post
I am getting AbstractMethodError while calling PreparedStatement.setBinaryStream(int, InputStream) for a BLOB column
3) I updated code (its third party component, so not suppose to update )
Added third argument whick works fine (it means at runtime it is using older jdbc driver???)(3) will not work if correct ojdbc6.jar is used. Because third argument is int and not long. long will work with ojdbc6 but will not work with older version.
I am using third party component and they are using - PreparedStatement.setBinaryStream(int, InputStream)
It should work with JDK 6, Oracle 11g and ojdbc6.jar driver.
I am sure its simple classpath issue or some configuration mismatch - just couldn't see it right now.
I will probably create new workspace / or test on other system now
Thanks! -
PreparedStatement general questions
I've been looking high and (not too) low for a definitive answer for this. Of course, not finding what I want to hear, I assume I'm looking in the wrong place...
Is there an advantage to using PreparedStatement (vs. Statement) when there are no variables in the query?
Possibly another way of getting at the same info:
Is a PreparedStatement query in the shared pool shared by all users, or is there a shared pool for each user, each with his own set of parsed statements (I'm specifically talking about Oracle)?
The reason I ask the second question is that, since my query doesn't have variables, even as a Statement object, it will be identical each time it's executed, so Oracle won't parse it again, correct? But that's not what I'm seeing.
Thanks!
Bryanjbisotti is right. The PreparedStement statement cached ( which is the correct terminology, pooling suggesting exclusive use, whereas cache imply shared usage) per connection.
Oracle has two schemas for caching PreparedStatements
Explicit - User identifies each statement by a unique key when storing
it to cache. This key is later used to retrieve the statement
for use. Faster
Implicit - User sumply create the statement, internal functionality
takes care of the rest
Go to Oracle site to find out more. You will find code samples for both
approaches
Code snippet for Implicit approach
// Enable connection for caching
con.setStmtCacheSize(size, true);
// Get current size of cache
int size = con.getStmtCacheSize();
Note: Once the connection is closed, the caching is lost -
Reuse of preparedstatements and the connection pool
It seems useful (for performance reasons) to reuse a prepared statement in
subsequent calls to the database. In WebLogic, however, after each call we
return the Connection object to the WebLogic connection pool. A prepared
statement is created on a specific Connection object. The next time we want
to use the same query we get a Connection from the pool, which might be
another instance of the Connection class. Therefor it seems impossible or at
least dangerous to reuse the same prepared statement. Even in the case this
would work we're indirectly using the other Connection, which we already
returned to the pool and which could be retrieved from the pool by someone
else. So, can't we reuse preparedstatements ?Hi Raja,
Currently the only bullet-proof way to make sure that all statements are
cached is to set the cache size to a number of possible prepared statements
in the application.
The only consequence of increased cache size is growing amount of
memory required by a server instance.
Regards,
Slava Imeshev
"Rajiv Jauhari" <[email protected]> wrote in message
news:[email protected]...
Is there an easy way to tell whether the prepared statement cache size one
has set is
appropriate? Some way to monitor cache hit rate or usage count (i.e., the
actual number of statements cached) while running a load test? I'm using
Weblogic 6.1sp3 and Oracle 8.1.7.4.
Another way to think of this question is: is there a negative impact ifthe
cache size is set too large?
In the case of Oracle I believe one might run out of cursors, but is there
any other negative consequence that you know of?
Thanks,
Rajiv
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
Vyas wrote:
If multiples (of the same statement) can be cached would it not result
in too many
prepared statements of the same type in the cache ?
This could happen
1. When a load test is done when all the threads start doing exactly
the
same work.
Because of contention everybody gets their own statement copy(theoritically, even
if in practice it may not exactly happen like that). In such a case
you
are going
to create load on the database in terms of open cursors.Each thread will get it's own connection, and the statement cache isper-connection.
Cursors, in Oracle's case, do need to be configured to support acache-full of
retained statements. Alternately, the cache should be set to a smallenough size to
require only as many cursors as the DBMS will allow per connection.
Another issue is what happens when the cache limit is hit ?
In the above example let's say cache limit is 50 and I am doing 50
user
load test.
because of load test let's say the cache gets filled with 50 of the
same
statement.
When load test moves to the next sequence of action requiring a
diffrent
statement
what happens to the cache ?
thanks
VyasThe only way a given connection's statement cache will get a duplicatestatement
is if some single JDBC thread required multiple copies of the samestatement. A
multi-user test will usually just ensure that each pooled connectioncaches the
same selection of different statements that the test user used. If thetest user
just repeatedly makes and uses one statement, the first time they do it,the
statement will be cached, and every subsequent repeat of the user codewill get
the same cached statement. The cache will still have 49 empty slotswaiting for
different statements. Currently the cache is simple-minded. It is a
fixed
(configurable)
size per connection, and the first N prepared/callable statements getcached for the
life of the pooled connection that created them. All other subsequentstatements will
be made and closed on a per-connection-use basis. Therefore, it can bethat a startup
or stress load that runs before standard runtime service, and which usessignificantly
different a statement profile could populate the cache with rarely-usedwasted statements.
If I were a customer in this circumstance, I would either prime thecaches, by determining
which statements I wanted cached, and then running a startup class thatreserved all the
pool connections, and made these statements on each before closing them.Alternately,
after startup/stress I would reset the pool, and allow the runtime load
to
fill the cache of
the regenerated pool.
Joe Weinstein at B.E.A.
thanks
Vyas
Joseph Weinstein <[email protected]> wrote:
JS wrote:
It seems useful (for performance reasons) to reuse a prepared
statement
in
subsequent calls to the database. In WebLogic, however, after each
call
we
return the Connection object to the WebLogic connection pool. A
prepared
statement is created on a specific Connection object. The next timewe
want
to use the same query we get a Connection from the pool, which
might
be
another instance of the Connection class. Therefor it seemsimpossible
or at
least dangerous to reuse the same prepared statement. Even in the
case
this
would work we're indirectly using the other Connection, which we
already
returned to the pool and which could be retrieved from the pool bysomeone
else. So, can't we reuse preparedstatements ?We already have you covered! Weblogic caches PreparedStatements along
with the pooled connection they came from. Every time you obtain a
pool
connection and run a prepareStatement() or prepareCall(), we willtransparently
give you a previously made statement, if the SQL exactly matches, andno
other place in the current thread stack is using that statement(multiples
can
be cached)
You are correct, of course, that statements you have should only
be
useable
to you while you have the connection from which they came. We have
you
covered
there too. If you were to try to use any prepared statement that
you'd
gotten
from
a pool connection after you'd put the connection back into the pool,those
statements
would throw an exception saying that they had been made inoperable atthe
time
you'd closed the connection.
Joe Weinstein at B.E.A. -
Here is my code, and errfile. The code is very simple. It can run on the windows2000. The errors are reported when it is running on the linux. It has confused me two weeks. My God
If you know the answer, please email me. [email protected]
import java.sql.*;
import java.util.*;
public class InsertDatabase{
String url;
Connection con ;
public static void main(String args[])throws Exception{
InsertDatabase j=new InsertDatabase();
if(args.length < 2){
System.out.println("\n"+"Usage java InsertDatabase -i no name"+"\n");
return;
if(args[0].equals("-i")) j.start(Integer.parseInt(args[1]), args[2]);
}//main
public void start(int empno, String ename)throws Exception{
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
url = "jdbc:oracle:oci8:@";
con = DriverManager.getConnection (url, "scott", "tiger");
PreparedStatement pstmt = con.prepareStatement("insert into emp (empno) values (?)");
//// Add LESLIE as employee number 1500
pstmt.setInt (1, empno); // The first ? is for EMPNO
//// Do the insertion
pstmt.execute ();
pstmt.close();
con.close();
}///~
The following is errors reported by the compiler:
java.lang.ExceptionInInitializerError: [exception was kaffe.util.SupportDisabled: GNU gmp was not found by Kaffe configure script]
at oracle.jdbc.dbaccess.DBConversion.IntToNumberBytes(DBConversion.java:line unknown, pc 0x82c206e)
at oracle.jdbc.driver.OraclePreparedStatement.setInt(OraclePreparedStatement.java:line unknown, pc 0x8361d64)
at InsertDatabase.start(InsertDatabase.java:33)
at InsertDatabase.main(InsertDatabase.java:20)
kaffe.util.SupportDisabled: GNU gmp was not found by Kaffe configure script
at java.lang.Throwable.fillInStackTrace(Throwable.java:native)
at java.lang.Throwable.<init>(Throwable.java:38)
at java.lang.Error.<init>(Error.java:21)
at kaffe.util.SupportDisabled.<init>(SupportDisabled.java:22)
at java.math.BigInteger.initialize0(BigInteger.java:native)
at java.math.BigInteger.<clinit>(BigInteger.java:30)
at java.math.BigDecimal.<init>(BigDecimal.java:36)
at oracle.jdbc.dbaccess.DBConversion.IntToNumberBytes(DBConversion.java:line unknown, pc 0x82c206e)
at oracle.jdbc.driver.OraclePreparedStatement.setInt(OraclePreparedStatement.java:line unknown, pc 0x8361d64)
at InsertDatabase.start(InsertDatabase.java:33)
at InsertDatabase.main(InsertDatabase.java:20)I think you will have to use the thin driver. I don't think there is an oci8 driver in the linux Oracle release ...at least that was the conclusion I came to.
-
Updating and reading same column with PreparedStatement
sqlStr = "UPDATE user_mstr SET userid=?, username=?, duration=?, location=?, expiry_date=?, remainder_days=? WHERE userid=?";
stmt = DBConnection.getPreparedStatement(conn,sqlStr);
stmt.setString(1,strUserid);
stmt.setString(2,strUsername);
stmt.setString(3,strDuration);
stmt.setString(4,strLocation);
stmt.setDate(5,sqlDate);
stmt.setString(6,strRemainderDays);
stmt.setString(7,strUserid);
int rowcount = stmt.executeUpdate();This is the problem i'm facing right now: A numberformatexception is always thrown, meaning that the statement did not execute properly.
There is nothing wrong with the SQL, because i've used the query analyzer, and the record was updated fine.
There is also nothing wrong with the date field because when i took the code for updating the date column out, the update was fine too.
So what could be wrong here? Is it because double usage of userid in the preparedstatement? I think that is the problem, because when i did not update the userid, the update is fine. Is it that, i cannot update a field that is currently being used when using a prepared statement?
Is there a way to go around this besides adding another recordid column?
Thanks all.
Edited by: tsek1125 on Nov 13, 2007 8:58 PMif(rowcount > 0){
response.sendRedirect("updated.jsp");
}else {
throw new NumberFormatException("");
}Sorry BalusC, I forgot to post this portion: the NFE occurs only because the statement did not execute properly.. This portion is right after the first code chunk that i've posted.
Using the Netbeans debugger, i found out that all the fields are 'correct'. And that the NFE is thrown by: int rowcount = stmt.executeUpdate() Which leaves me to wonder what the problem is.
The userid is actually a string and not a real 'id', duration and remainder days are integers.
To clarify, now i've narrow the problem to: when i choose to update the userid column, it does not work. (and i think this is due to the part of the sql statement "WHERE userid = ?")
Why is a possible reason and solution? Thanks for your help :)
*/ -
I'm having a heck of a time trying to figure out how to make prepared statements work with JDBC. We've got an IBM DB2 (V5.2) database running on a Solaris 7 box.
We use a unique id in many of our tables that was defined like:
create table phone(
tech_id char(13) for bit data not null unique,
Currently our programs do not use PreparedStatements, and work like this:
Statement stmt = con.createStatement();
ResultSet rs = stmt.executeQuery("SELECT TECH_ID FROM PHONE WHERE "
+ "AREA_CODE = '701'");
while(rs.next())
String tech_id = rs.getString("tech_id");
The above code will place something like: 19991229000416205209000000 in the variable tech_id. To use this tech_id in another query, I use code like:
ResultSet rs = stmt.executeQuery("SELECT PREFIX,NUMBER FROM PHONE WHERE "
+ "TECH_ID = x'" + tech_id + "'");
if(rs.next())
System.out.println(rs.getString("prefix") + rs.getString("number"));
Now, how would I go about doing the same thing using prepared statements?
I would have expected:
PreparedStatement ps = con.prepareStatement("SELECT PREFIX FROM PHONE "
+ "WHERE TECH_ID = ?");
ps.setString(1, tech_id);
ResultSet rs = ps.executeQuery();
if(rs.next())
System.out.println(rs.getString("prefix"));
But, this code doesn't work. I throw and exception on the executeQuery(). Basically, I need assistance or direction for using this funky char(13) bit data data type in my jdbc programs.
If anyone could offer pointers to URLs that contain this type of information, or maybe even post some examples, I would definately appreciate the help.
Thanks a lot.Perhaps you should include the entire exception error thrown when you try to execute this PreparedStatement object. Usually, we can tell what was happening to the SQL query or what the JDBC connection was trying to get that caused the exception to be thrown.
Your source code looks okay and there is no syntaxes or usage errors.
So in summary, I think the members of this forum can help you further if you can include the error messages thrown by the VM.
Allen Lai
Sun Microsystems -
High CPU usage on idle server.
Hi
I have a problem with a weblogic server 5.1 SP#6 running with JDK1.2.2 on a Solaris Sparc server.
The server starts using about 80-90 % of the cpu after about 2 hours (even if it is idle). After two
days the server hungs completely and needs to be restarted.
During this time the server gets longer and longer response time.
At the bottom of this post, i added a thread dump when the server had about 85% CPU usage and low
usage.
Gratefull for any help.
Regards Ståle
A SIGQUIT has been received. Do you want to:
[ 0 ] continue program
[ 1 ] check & print one deadlock
[ 2 ] check & print all deadlocks
[ 3 ] dump thread stacks
[ 4 ] dump lock registry
[ 5 ] heap inspection
[ 6 ] terminate program
Type number corresponding to selected action: Found 0 deadlock
Full thread dump:
"Keep-Alive-Timer:lille.hvor.no" (TID:0x2c792f8, sys_thread_t:0x2c79230, state:CW, thread_t: t@1180,
threadID:0xe7731dc8, stack_bottom:0xe7732000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Keep-Alive-Timer:www.movieseer.com" (TID:0x27b5140, sys_thread_t:0x27b5078, state:CW, thread_t:
t@1109, threadID:0xe7791dc8, stack_bottom:0xe7792000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Keep-Alive-Timer:wap.politiet.net" (TID:0x331f790, sys_thread_t:0x331f6c8, state:CW, thread_t:
t@1100, threadID:0xe78f1dc8, stack_bottom:0xe78f2000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Keep-Alive-Timer:stars927.com" (TID:0x2e6d530, sys_thread_t:0x2e6d468, state:CW, thread_t: t@919,
threadID:0xe78c1dc8, stack_bottom:0xe78c2000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Keep-Alive-Timer:wap.eurosport.com" (TID:0x32a8d88, sys_thread_t:0x32a8cc0, state:CW, thread_t:
t@802, threadID:0xe7ac1dc8, stack_bottom:0xe7ac2000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Keep-Alive-Timer:wap.caplex.net" (TID:0x320bed8, sys_thread_t:0x320be10, state:CW, thread_t: t@622,
threadID:0xe7af1dc8, stack_bottom:0xe7af2000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Thread-138" (TID:0x2540a10, sys_thread_t:0x2540948, state:CW, thread_t: t@303, threadID:0xe7da1dc8,
stack_bottom:0xe7da2000, stack_size:0x20000) prio=1
[1] java.lang.Thread.sleep(Native Method)
[2] com.telenor.wamp.framework.cache.CacheHolder.run(CacheHolder.java:243)
[3] java.lang.Thread.run(Thread.java:478)
"HighPriority TimeEventGenerator" (TID:0x1a34788, sys_thread_t:0x1a346c0, state:CW, thread_t: t@104,
threadID:0xe7f11dc8, stack_bottom:0xe7f12000, stack_size:0x20000) prio=9
[1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
[2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
[3] java.lang.Thread.run(Thread.java:479)
"ListenThread" (TID:0x1969ea0, sys_thread_t:0x1969dd8, state:R, thread_t: t@103,
threadID:0xe7f91dc8, stack_bottom:0xe7f92000, stack_size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
[4] java.net.ServerSocket.accept(ServerSocket.java:223)
[5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
"Thread-1" (TID:0x19681d0, sys_thread_t:0x1968108, state:CW, thread_t: t@102, threadID:0xe7fc1dc8,
stack_bottom:0xe7fc2000, stack_size:0x20000) prio=1
[1] java.lang.Thread.sleep(Native Method)
[2] no.infohwy.djuice.common.CacheHolder.run(CacheHolder.java:215)
[3] java.lang.Thread.run(Thread.java:479)
"SessionMessageProcessor $SESSION$ " (TID:0x1957158, sys_thread_t:0x1957090, state:CW, thread_t:
t@101, threadID:0xe8021dc8, stack_bottom:0xe8022000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor $SESSION$ " (TID:0x195adc0, sys_thread_t:0x195acf8, state:CW, thread_t:
t@100, threadID:0xe8051dc8, stack_bottom:0xe8052000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"JMS Session Delivery Thread" (TID:0x195fe58, sys_thread_t:0x195fd90, state:CW, thread_t: t@99,
threadID:0xe8081dc8, stack_bottom:0xe8082000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.jclient.Session.Rv_(Session.java:1398)
[3] progress.message.jclient.QueueSession.run(QueueSession.java:579)
[4] progress.message.jclient.uj.run(Session$SessionThread.java:1206)
"SessionMessageProcessor $QR$ " (TID:0x195ec50, sys_thread_t:0x195eb88, state:CW, thread_t: t@98,
threadID:0xe80e1dc8, stack_bottom:0xe80e2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor $QR$ " (TID:0x195ea30, sys_thread_t:0x195e968, state:CW, thread_t: t@97,
threadID:0xe8111dc8, stack_bottom:0xe8112000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor $SESSION$ " (TID:0x194c4e0, sys_thread_t:0x194c418, state:CW, thread_t:
t@96, threadID:0xe8141dc8, stack_bottom:0xe8142000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor $SESSION$ " (TID:0x1939ad0, sys_thread_t:0x1939a08, state:CW, thread_t:
t@95, threadID:0xe8171dc8, stack_bottom:0xe8172000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"ClientListener MIP Djuice2" (TID:0x18c3db0, sys_thread_t:0x18c3ce8, state:R, thread_t: t@94,
threadID:0xe81c1dc8, stack_bottom:0xe81c2000, stack_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] java.io.BufferedInputStream.fill(BufferedInputStream.java:171)
[4] java.io.BufferedInputStream.read1(BufferedInputStream.java:221)
[5] java.io.BufferedInputStream.read(BufferedInputStream.java:278)
[6] progress.message.zclient.MgramBuffer.read(MgramBuffer.java:91)
[7] progress.message.zclient.Mgram.<init>(Mgram.java:551)
[8] progress.message.zclient.ClientListener.qI_(ClientListener.java:482)
[9] progress.message.zclient.ClientListener.threadMain(ClientListener.java:267)
[10] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"ClientSender MIP Djuice2" (TID:0x18c7a98, sys_thread_t:0x18c79d0, state:CW, thread_t: t@93,
threadID:0xe8201dc8, stack_bottom:0xe8202000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.ClientSender.threadMain(ClientSender.java:460)
[3] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor MIP " (TID:0x1849970, sys_thread_t:0x18498a8, state:CW, thread_t: t@92,
threadID:0xe8241dc8, stack_bottom:0xe8242000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor MIP " (TID:0x183c008, sys_thread_t:0x183bf40, state:CW, thread_t: t@91,
threadID:0xe8271dc8, stack_bottom:0xe8272000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"NBExecuteThread-1" (TID:0x5b4cf8, sys_thread_t:0x5b4c30, state:CW, thread_t: t@87,
threadID:0xe8ca1dc8, stack_bottom:0xe8ca2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"NBExecuteThread-0" (TID:0x5afcf8, sys_thread_t:0x5afc30, state:CW, thread_t: t@86,
threadID:0xe8cf1dc8, stack_bottom:0xe8cf2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-74" (TID:0x5b50f8, sys_thread_t:0x5b5030, state:R, thread_t: t@85,
threadID:0xe8d21dc8, stack_bottom:0xe8d22000, stack_size:0x20000) prio=5
[1] java.net.PlainDatagramSocketImpl.peek(Native Method)
[2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
[3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
[4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
[5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-73" (TID:0x5b54f8, sys_thread_t:0x5b5430, state:R, thread_t: t@84,
threadID:0xe8d71dc8, stack_bottom:0xe8d72000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
[2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-72" (TID:0x5c50f8, sys_thread_t:0x5c5030, state:MW, thread_t: t@83,
threadID:0xe8da1dc8, stack_bottom:0xe8da2000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-71" (TID:0x5c60f8, sys_thread_t:0x5c6030, state:MW, thread_t: t@82,
threadID:0xe8df1dc8, stack_bottom:0xe8df2000, stack_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-70" (TID:0x5c64f8, sys_thread_t:0x5c6430, state:R, thread_t: t@81,
threadID:0xe8e21dc8, stack_bottom:0xe8e22000, stack_size:0x20000) prio=5
[1] java.net.SocketOutputStream.socketWrite(Native Method)
[2] java.net.SocketOutputStream.write(SocketOutputStream.java:87)
[3] weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:84)
[4] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:99)
[5] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:94)
[6] weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamImpl.java:195)
[7] weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:134)
[8] jsp_servlet._projects._djuice._prod._mcommerce._mainProducts._jspService(_mainProducts.java:87)
[9] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[10] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[11] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[12] no.infohwy.djuice.command.CCommandServlet.doGet(CCommandServlet.java:156)
[13] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[14] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[15] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[16] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[17] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[18] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
[19] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[21] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-69" (TID:0x7c7950, sys_thread_t:0x7c7888, state:CW, thread_t: t@80,
threadID:0xe8e71dc8, stack_bottom:0xe8e72000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-68" (TID:0x601cf8, sys_thread_t:0x601c30, state:R, thread_t: t@79,
threadID:0xe8ea1dc8, stack_bottom:0xe8ea2000, stack_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
[4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
[5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
[6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
[7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
[8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-67" (TID:0x60b0f8, sys_thread_t:0x60b030, state:R, thread_t: t@78,
threadID:0xe8ef1dc8, stack_bottom:0xe8ef2000, stack_size:0x20000) prio=5
[1] java.net.SocketOutputStream.socketWrite(Native Method)
[2] java.net.SocketOutputStream.write(SocketOutputStream.java:87)
[3] weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:84)
[4] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:99)
[5] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:94)
[6] weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamImpl.java:195)
[7] weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:134)
[8] jsp_servlet._projects._djuice._prod._mcommerce._mainProducts._jspService(_mainProducts.java:87)
[9] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[10] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[11] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[12] no.infohwy.djuice.command.CCommandServlet.doGet(CCommandServlet.java:156)
[13] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[14] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[15] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[16] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[17] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[18] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
[19] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[21] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-66" (TID:0x6034f8, sys_thread_t:0x603430, state:CW, thread_t: t@77,
threadID:0xe8f21dc8, stack_bottom:0xe8f22000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-65" (TID:0x5c70f8, sys_thread_t:0x5c7030, state:CW, thread_t: t@76,
threadID:0xe8f71dc8, stack_bottom:0xe8f72000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-64" (TID:0x616cf8, sys_thread_t:0x616c30, state:CW, thread_t: t@75,
threadID:0xe8fa1dc8, stack_bottom:0xe8fa2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-63" (TID:0x6384f8, sys_thread_t:0x638430, state:CW, thread_t: t@74,
threadID:0xe8ff1dc8, stack_bottom:0xe8ff2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-62" (TID:0x6374f8, sys_thread_t:0x637430, state:CW, thread_t: t@73,
threadID:0xe9021dc8, stack_bottom:0xe9022000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-61" (TID:0x644cf8, sys_thread_t:0x644c30, state:CW, thread_t: t@72,
threadID:0xe9071dc8, stack_bottom:0xe9072000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-60" (TID:0x648cf8, sys_thread_t:0x648c30, state:CW, thread_t: t@71,
threadID:0xe90a1dc8, stack_bottom:0xe90a2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-59" (TID:0x64dcf8, sys_thread_t:0x64dc30, state:CW, thread_t: t@70,
threadID:0xe90f1dc8, stack_bottom:0xe90f2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-58" (TID:0x64d0f8, sys_thread_t:0x64d030, state:CW, thread_t: t@69,
threadID:0xe9121dc8, stack_bottom:0xe9122000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-57" (TID:0x6528f8, sys_thread_t:0x652830, state:R, thread_t: t@68,
threadID:0xe9171dc8, stack_bottom:0xe9172000, stack_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
[4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
[5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
[6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
[7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
[8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-56" (TID:0x6834f8, sys_thread_t:0x683430, state:CW, thread_t: t@67,
threadID:0xe91a1dc8, stack_bottom:0xe91a2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-55" (TID:0x525cf8, sys_thread_t:0x525c30, state:CW, thread_t: t@66,
threadID:0xe91f1dc8, stack_bottom:0xe91f2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-54" (TID:0x5260f8, sys_thread_t:0x526030, state:CW, thread_t: t@65,
threadID:0xe9221dc8, stack_bottom:0xe9222000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-53" (TID:0x6aacf8, sys_thread_t:0x6aac30, state:CW, thread_t: t@64,
threadID:0xe9271dc8, stack_bottom:0xe9272000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-52" (TID:0x6ab0f8, sys_thread_t:0x6ab030, state:R, thread_t: t@63,
threadID:0xe92a1dc8, stack_bottom:0xe92a2000, stack_size:0x20000) prio=5
[1] java.net.SocketOutputStream.socketWrite(Native Method)
[2] java.net.SocketOutputStream.write(SocketOutputStream.java:87)
[3] weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:84)
[4] weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:99)
[5] weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:439)
[6] weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:463)
[7] weblogic.servlet.FileServlet.sendFile(FileServlet.java:220)
[8] weblogic.servlet.FileServlet.service(FileServlet.java:48)
[9] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[10] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[11] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[12] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[13] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
[14] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[15] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[16] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-51" (TID:0x70e4f8, sys_thread_t:0x70e430, state:CW, thread_t: t@62,
threadID:0xe92f1dc8, stack_bottom:0xe92f2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-50" (TID:0x7174f8, sys_thread_t:0x717430, state:CW, thread_t: t@61,
threadID:0xe9321dc8, stack_bottom:0xe9322000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-49" (TID:0x71d0f8, sys_thread_t:0x71d030, state:CW, thread_t: t@60,
threadID:0xe9371dc8, stack_bottom:0xe9372000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-48" (TID:0x733a60, sys_thread_t:0x733998, state:R, thread_t: t@59,
threadID:0xe93a1dc8, stack_bottom:0xe93a2000, stack_size:0x20000) prio=5
[1] java.io.BufferedInputStream.read(BufferedInputStream.java:207)
[2] jsp_servlet._projects._djuice._prod._wapalizer._index._jspService(_index.java:79)
[3] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[4] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[5] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[6] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[7] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
[8] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[9] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[10] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-47" (TID:0x73acf8, sys_thread_t:0x73ac30, state:CW, thread_t: t@58,
threadID:0xe93f1dc8, stack_bottom:0xe93f2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-46" (TID:0x77a0f8, sys_thread_t:0x77a030, state:CW, thread_t: t@57,
threadID:0xe9421dc8, stack_bottom:0xe9422000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-45" (TID:0x785530, sys_thread_t:0x785468, state:CW, thread_t: t@56,
threadID:0xe9471dc8, stack_bottom:0xe9472000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-44" (TID:0x7834f8, sys_thread_t:0x783430, state:CW, thread_t: t@55,
threadID:0xe94a1dc8, stack_bottom:0xe94a2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-43" (TID:0x78b0f8, sys_thread_t:0x78b030, state:CW, thread_t: t@54,
threadID:0xe94f1dc8, stack_bottom:0xe94f2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-42" (TID:0x78ecf8, sys_thread_t:0x78ec30, state:CW, thread_t: t@53,
threadID:0xe9521dc8, stack_bottom:0xe9522000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-41" (TID:0x79b4f8, sys_thread_t:0x79b430, state:CW, thread_t: t@52,
threadID:0xe9571dc8, stack_bottom:0xe9572000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-40" (TID:0x7a18f8, sys_thread_t:0x7a1830, state:CW, thread_t: t@51,
threadID:0xe95a1dc8, stack_bottom:0xe95a2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-39" (TID:0x7c9cf8, sys_thread_t:0x7c9c30, state:CW, thread_t: t@50,
threadID:0xe95f1dc8, stack_bottom:0xe95f2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-38" (TID:0x7ca0f8, sys_thread_t:0x7ca030, state:R, thread_t: t@49,
threadID:0xe9621dc8, stack_bottom:0xe9622000, stack_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
[4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
[5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
[6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
[7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
[8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-37" (TID:0x7dfcf8, sys_thread_t:0x7dfc30, state:CW, thread_t: t@48,
threadID:0xe9671dc8, stack_bottom:0xe9672000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-36" (TID:0x7fa0f8, sys_thread_t:0x7fa030, statAnother Thread dump when the server have more load.
Still running with about 90 % of the CPU
-regards Ståle
SIGQUIT
A SIGQUIT has been received. Do you want to:
[ 0 ] continue program
[ 1 ] check & print one deadlock
[ 2 ] check & print all deadlocks
[ 3 ] dump thread stacks
[ 4 ] dump lock registry
[ 5 ] heap inspection
[ 6 ] terminate program
Type number corresponding to selected action: Found 0 deadlock
Full thread dump:
"Keep-Alive-Timer:wap.mobitel.si" (TID:0x3062ee0, sys_thread_t:0x3062e18, state:CW, thread_t:
t@4879, threadID:0xe7a41dc8, stack_bot
tom:0xe7a42000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Keep-Alive-Timer:wap.thai2hand.com" (TID:0x2734098, sys_thread_t:0x2733fd0, state:CW, thread_t:
t@4812, threadID:0xe7bd1dc8, stack_
bottom:0xe7bd2000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Keep-Alive-Timer:lille.hvor.no" (TID:0x2738ba0, sys_thread_t:0x2738ad8, state:CW, thread_t: t@4756,
threadID:0xe7a71dc8, stack_bott
om:0xe7a72000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Keep-Alive-Timer:stars927.com" (TID:0x3c7fbd8, sys_thread_t:0x3c7fb10, state:CW, thread_t: t@4415,
threadID:0xe7cd1dc8, stack_botto
m:0xe7cd2000, stack_size:0x20000) prio=8
[1] java.lang.Thread.sleep(Native Method)
[2] sun.net.www.http.ClientVector.run(KeepAliveCache.java:220)
[3] java.lang.Thread.run(Thread.java:478)
"Thread-113" (TID:0x2089788, sys_thread_t:0x20896c0, state:CW, thread_t: t@266, threadID:0xe7e11dc8,
stack_bottom:0xe7e12000, stack_
size:0x20000) prio=1
[1] java.lang.Thread.sleep(Native Method)
[2] com.telenor.wamp.framework.cache.CacheHolder.run(CacheHolder.java:243)
[3] java.lang.Thread.run(Thread.java:478)
"HighPriority TimeEventGenerator" (TID:0x1bd29f0, sys_thread_t:0x1bd2928, state:CW, thread_t: t@107,
threadID:0xe7e41dc8, stack_bott
om:0xe7e42000, stack_size:0x20000) prio=9
[1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
[2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
[3] java.lang.Thread.run(Thread.java:479)
"ListenThread" (TID:0x17825c8, sys_thread_t:0x1782500, state:R, thread_t: t@103,
threadID:0xe7f91dc8, stack_bottom:0xe7f92000, stack
_size:0x20000) prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
[4] java.net.ServerSocket.accept(ServerSocket.java:223)
[5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
"Thread-1" (TID:0x195e9d0, sys_thread_t:0x195e908, state:CW, thread_t: t@102, threadID:0xe7fc1dc8,
stack_bottom:0xe7fc2000, stack_si
ze:0x20000) prio=1
[1] java.lang.Thread.sleep(Native Method)
[2] no.infohwy.djuice.common.CacheHolder.run(CacheHolder.java:215)
[3] java.lang.Thread.run(Thread.java:479)
"SessionMessageProcessor $SESSION$ " (TID:0x19505b0, sys_thread_t:0x19504e8, state:CW, thread_t:
t@101, threadID:0xe8021dc8, stack_b
ottom:0xe8022000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor $SESSION$ " (TID:0x18bf198, sys_thread_t:0x18bf0d0, state:CW, thread_t:
t@100, threadID:0xe8051dc8, stack_b
ottom:0xe8052000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"JMS Session Delivery Thread" (TID:0x1958158, sys_thread_t:0x1958090, state:CW, thread_t: t@99,
threadID:0xe8081dc8, stack_bottom:0x
e8082000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.jclient.Session.Rv_(Session.java:1398)
[3] progress.message.jclient.QueueSession.run(QueueSession.java:579)
[4] progress.message.jclient.uj.run(Session$SessionThread.java:1206)
"SessionMessageProcessor $QR$ " (TID:0x194b820, sys_thread_t:0x194b758, state:CW, thread_t: t@98,
threadID:0xe80e1dc8, stack_bottom:
0xe80e2000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor $QR$ " (TID:0x194b600, sys_thread_t:0x194b538, state:CW, thread_t: t@97,
threadID:0xe8111dc8, stack_bottom:
0xe8112000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor $SESSION$ " (TID:0x19428e0, sys_thread_t:0x1942818, state:CW, thread_t:
t@96, threadID:0xe8141dc8, stack_bo
ttom:0xe8142000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor $SESSION$ " (TID:0x192de58, sys_thread_t:0x192dd90, state:CW, thread_t:
t@95, threadID:0xe8171dc8, stack_bo
ttom:0xe8172000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"ClientListener MIP Djuice2" (TID:0x18c4338, sys_thread_t:0x18c4270, state:R, thread_t: t@94,
threadID:0xe81c1dc8, stack_bottom:0xe8
1c2000, stack_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] java.io.BufferedInputStream.fill(BufferedInputStream.java:171)
[4] java.io.BufferedInputStream.read1(BufferedInputStream.java:221)
[5] java.io.BufferedInputStream.read(BufferedInputStream.java:278)
[6] progress.message.zclient.MgramBuffer.read(MgramBuffer.java:91)
[7] progress.message.zclient.Mgram.<init>(Mgram.java:551)
[8] progress.message.zclient.ClientListener.qI_(ClientListener.java:482)
[9] progress.message.zclient.ClientListener.threadMain(ClientListener.java:267)
[10] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"ClientSender MIP Djuice2" (TID:0x18b9688, sys_thread_t:0x18b95c0, state:CW, thread_t: t@93,
threadID:0xe8201dc8, stack_bottom:0xe82
02000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.ClientSender.threadMain(ClientSender.java:460)
[3] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessionMessageProcessor MIP " (TID:0x18ba280, sys_thread_t:0x18ba1b8, state:CW, thread_t: t@92,
threadID:0xe8241dc8, stack_bottom:0
xe8242000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"SessiOnMessageProcessor MIP " (TID:0x184ee78, sys_thread_t:0x184edb0, state:CW, thread_t: t@91,
threadID:0xe8271dc8, stack_bottom:0
xe8272000, stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] progress.message.zclient.xb.HE_(MessageHandlerQueue.java:66)
[3] progress.message.zclient.xf.threadMain(SessionMessageProcessor.java:63)
[4] progress.message.zclient.DebugThread.run(DebugThread.java:54)
"NBExecuteThread-1" (TID:0x7678f0, sys_thread_t:0x767828, state:CW, thread_t: t@87,
threadID:0xe8ca1dc8, stack_bottom:0xe8ca2000, st
ack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"NBExecuteThread-0" (TID:0x812d28, sys_thread_t:0x812c60, state:CW, thread_t: t@86,
threadID:0xe8cf1dc8, stack_bottom:0xe8cf2000, st
ack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-74" (TID:0x4fccf8, sys_thread_t:0x4fcc30, state:R, thread_t: t@85,
threadID:0xe8d21dc8, stack_bottom:0xe8d22000, stac
k_size:0x20000) prio=5
[1] java.net.PlainDatagramSocketImpl.peek(Native Method)
[2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
[3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
[4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
[5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-73" (TID:0x5500f8, sys_thread_t:0x550030, state:MW, thread_t: t@84,
threadID:0xe8d71dc8, stack_bottom:0xe8d72000, sta
ck_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-72" (TID:0x5628f8, sys_thread_t:0x562830, state:MW, thread_t: t@83,
threadID:0xe8da1dc8, stack_bottom:0xe8da2000, sta
ck_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-71" (TID:0x5db0f8, sys_thread_t:0x5db030, state:R, thread_t: t@82,
threadID:0xe8df1dc8, stack_bottom:0xe8df2000, stac
k_size:0x20000) prio=5
[1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
[2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
[3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-70" (TID:0x5db4f8, sys_thread_t:0x5db430, state:R, thread_t: t@81,
threadID:0xe8e21dc8, stack_bottom:0xe8e22000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] com.sybase.timedio.RawDbio.reallyRead(RawDbio.java)
[4] com.sybase.timedio.Dbio.doRead(Dbio.java)
[5] com.sybase.timedio.InStreamMgr.readIfOwner(InStreamMgr.java)
[6] com.sybase.timedio.InStreamMgr.doRead(InStreamMgr.java)
[7] com.sybase.tds.TdsProtocolContext.getChunk(TdsProtocolContext.java)
[8] com.sybase.tds.PduInputFormatter.readPacket(PduInputFormatter.java)
[9] com.sybase.tds.PduInputFormatter.read(PduInputFormatter.java)
[10] com.sybase.tds.TdsInputStream.read(TdsInputStream.java)
[11] com.sybase.tds.TdsInputStream.readUnsignedByte(TdsInputStream.java)
[12] com.sybase.tds.Tds.nextResult(Tds.java)
[13] com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
[14] com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
[15] com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
[16] com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
[17] com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
[18] weblogic.jdbc.pool.PreparedStatement.executeUpdate(PreparedStatement.java:63)
[19]
com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.update(ProfileDeviceEntityPSWebLogic_CMP_R
DBMS.java:302)
[20]
com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.store(ProfileDeviceEntityPSWebLogic_CMP_RD
BMS.java:287)
[21] weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:170)
[22] weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.java:224)
[23] weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.java:295)
[24] weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:697)
[25]
com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.setDateLastLogon(ProfileDeviceEntityBeanEOImpl.java:
188)
[26] com.djuice.ci.ejb.ProfileManagerBean.chooseProfile(ProfileManagerBean.java:1221)
[27] com.djuice.ci.ejb.ProfileManagerBean.getProfile(ProfileManagerBean.java:221)
[28] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.getProfile(ProfileManagerBeanEOImpl.java:769)
[29] no.infohwy.djuice.ejb.CFacadeBean.getProfile(CFacadeBean.java:170)
[30] no.infohwy.djuice.ejb.CFacadeBeanEOImpl.getProfile(CFacadeBeanEOImpl.java:2146)
[31]
no.infohwy.djuice.ejb.CFacadeBeanEOImpl_ServiceStub.getProfile(CFacadeBeanEOImpl_ServiceStub.java:71
8)
.... remainder of stack truncated ...
"ExecuteThread-69" (TID:0x7a21c0, sys_thread_t:0x7a20f8, state:R, thread_t: t@80,
threadID:0xe8e71dc8, stack_bottom:0xe8e72000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] com.sybase.timedio.RawDbio.reallyRead(RawDbio.java)
[4] com.sybase.timedio.Dbio.doRead(Dbio.java)
[5] com.sybase.timedio.InStreamMgr.readIfOwner(InStreamMgr.java)
[6] com.sybase.timedio.InStreamMgr.doRead(InStreamMgr.java)
[7] com.sybase.tds.TdsProtocolContext.getChunk(TdsProtocolContext.java)
[8] com.sybase.tds.PduInputFormatter.readPacket(PduInputFormatter.java)
[9] com.sybase.tds.PduInputFormatter.read(PduInputFormatter.java)
[10] com.sybase.tds.TdsInputStream.read(TdsInputStream.java)
[11] com.sybase.tds.TdsInputStream.readUnsignedByte(TdsInputStream.java)
[12] com.sybase.tds.Tds.nextResult(Tds.java)
[13] com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
[14] com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
[15] com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
[16] com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
[17] com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
[18] weblogic.jdbc.pool.PreparedStatement.executeUpdate(PreparedStatement.java:63)
[19]
com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.update(ProfileDeviceEntityPSWebLogic_CMP_R
DBMS.java:302)
[20]
com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.store(ProfileDeviceEntityPSWebLogic_CMP_RD
BMS.java:287)
[21] weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:170)
[22] weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.java:224)
[23] weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.java:295)
[24] weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:697)
[25]
com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.setDateLastLogon(ProfileDeviceEntityBeanEOImpl.java:
188)
[26] com.djuice.ci.ejb.ProfileManagerBean.chooseProfile(ProfileManagerBean.java:1221)
[27] com.djuice.ci.ejb.ProfileManagerBean.getCurrentProfile(ProfileManagerBean.java:3136)
[28] com.djuice.ci.ejb.ProfileManagerBean.login(ProfileManagerBean.java:146)
[29] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.login(ProfileManagerBeanEOImpl.java:80)
[30] no.infohwy.djuice.ejb.CFacadeBean.login(CFacadeBean.java:122)
[31] no.infohwy.djuice.ejb.CFacadeBeanEOImpl.login(CFacadeBeanEOImpl.java:1200)
.... remainder of stack truncated ...
"ExecuteThread-68" (TID:0x5af0f8, sys_thread_t:0x5af030, state:R, thread_t: t@79,
threadID:0xe8ea1dc8, stack_bottom:0xe8ea2000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
[4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
[5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
[6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
[7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
[8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-67" (TID:0x5dbcf8, sys_thread_t:0x5dbc30, state:R, thread_t: t@78,
threadID:0xe8ef1dc8, stack_bottom:0xe8ef2000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
[4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
[5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
[6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
[7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
[8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-66" (TID:0x5b30f8, sys_thread_t:0x5b3030, state:R, thread_t: t@77,
threadID:0xe8f21dc8, stack_bottom:0xe8f22000, stac
k_size:0x20000) prio=5
[1] java.io.BufferedInputStream.fill(BufferedInputStream.java:171)
[2] java.io.BufferedInputStream.read(BufferedInputStream.java:207)
[3] jsp_servlet._projects._djuice._prod._wapalizer._index._jspService(_index.java:79)
[4] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[5] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[6] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[7] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[8] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
[9] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[10] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[11] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-65" (TID:0x5c28f8, sys_thread_t:0x5c2830, state:R, thread_t: t@76,
threadID:0xe8f71dc8, stack_bottom:0xe8f72000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
[4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
[5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
[6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
[7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
[8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-64" (TID:0x5c5cf8, sys_thread_t:0x5c5c30, state:R, thread_t: t@75,
threadID:0xe8fa1dc8, stack_bottom:0xe8fa2000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] com.sybase.timedio.RawDbio.reallyRead(RawDbio.java)
[4] com.sybase.timedio.Dbio.doRead(Dbio.java)
[5] com.sybase.timedio.InStreamMgr.readIfOwner(InStreamMgr.java)
[6] com.sybase.timedio.InStreamMgr.doRead(InStreamMgr.java)
[7] com.sybase.tds.TdsProtocolContext.getChunk(TdsProtocolContext.java)
[8] com.sybase.tds.PduInputFormatter.readPacket(PduInputFormatter.java)
[9] com.sybase.tds.PduInputFormatter.read(PduInputFormatter.java)
[10] com.sybase.tds.TdsInputStream.read(TdsInputStream.java)
[11] com.sybase.tds.TdsInputStream.readUnsignedByte(TdsInputStream.java)
[12] com.sybase.tds.Tds.nextResult(Tds.java)
[13] com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
[14] com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
[15] com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
[16] com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
[17] com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
[18] weblogic.jdbc.pool.PreparedStatement.executeUpdate(PreparedStatement.java:63)
[19]
com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.update(ProfileDeviceEntityPSWebLogic_CMP_R
DBMS.java:302)
[20]
com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.store(ProfileDeviceEntityPSWebLogic_CMP_RD
BMS.java:287)
[21] weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:170)
[22] weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.java:224)
[23] weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.java:295)
[24] weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:697)
[25]
com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.getDeviceType(ProfileDeviceEntityBeanEOImpl.java:442
[26] com.djuice.ci.ejb.ProfileManagerBean.createProfileBean(ProfileManagerBean.java:2598)
[27] com.djuice.ci.ejb.ProfileManagerBean.getProfileBean(ProfileManagerBean.java:318)
[28] com.djuice.ci.ejb.ProfileManagerBean.getProfilesForDevice(ProfileManagerBean.java:411)
[29] com.djuice.ci.ejb.ProfileManagerBean.getCurrentProfile(ProfileManagerBean.java:3136)
[30] com.djuice.ci.ejb.ProfileManagerBean.login(ProfileManagerBean.java:146)
[31] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.login(ProfileManagerBeanEOImpl.java:80)
.... remainder of stack truncated ...
"ExecuteThread-63" (TID:0x5e18f8, sys_thread_t:0x5e1830, state:R, thread_t: t@74,
threadID:0xe8ff1dc8, stack_bottom:0xe8ff2000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
[4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
[5] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:99)
[6] weblogic.socket.JVMSocketManager.accept(JVMSocketManager.java:377)
[7] weblogic.t3.srvr.ListenThread$RJVMListenRequest.execute(ListenThread.java:505)
[8] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-62" (TID:0x60b4f8, sys_thread_t:0x60b430, state:R, thread_t: t@73,
threadID:0xe9021dc8, stack_bottom:0xe9022000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] com.sybase.timedio.RawDbio.reallyRead(RawDbio.java)
[4] com.sybase.timedio.Dbio.doRead(Dbio.java)
[5] com.sybase.timedio.InStreamMgr.readIfOwner(InStreamMgr.java)
[6] com.sybase.timedio.InStreamMgr.doRead(InStreamMgr.java)
[7] com.sybase.tds.TdsProtocolContext.getChunk(TdsProtocolContext.java)
[8] com.sybase.tds.PduInputFormatter.readPacket(PduInputFormatter.java)
[9] com.sybase.tds.PduInputFormatter.read(PduInputFormatter.java)
[10] com.sybase.tds.TdsInputStream.read(TdsInputStream.java)
[11] com.sybase.tds.TdsInputStream.readUnsignedByte(TdsInputStream.java)
[12] com.sybase.tds.Tds.nextResult(Tds.java)
[13] com.sybase.jdbc.ResultGetter.nextResult(ResultGetter.java)
[14] com.sybase.jdbc.SybStatement.nextResult(SybStatement.java)
[15] com.sybase.jdbc.SybStatement.updateLoop(SybStatement.java)
[16] com.sybase.jdbc.SybStatement.executeUpdate(SybStatement.java)
[17] com.sybase.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java)
[18] weblogic.jdbc.pool.PreparedStatement.executeUpdate(PreparedStatement.java:63)
[19]
com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.update(ProfileDeviceEntityPSWebLogic_CMP_R
DBMS.java:302)
[20]
com.djuice.ci.ejb.ProfileDeviceEntityPSWebLogic_CMP_RDBMS.store(ProfileDeviceEntityPSWebLogic_CMP_RD
BMS.java:287)
[21] weblogic.ejb.internal.EntityEJBContext.store(EntityEJBContext.java:170)
[22] weblogic.ejb.internal.EntityEJBContext.beforeCompletion(EntityEJBContext.java:224)
[23] weblogic.ejb.internal.StatefulEJBObject.postInvokeNoTx(StatefulEJBObject.java:295)
[24] weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:697)
[25]
com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.getDeviceType(ProfileDeviceEntityBeanEOImpl.java:442
[26] com.djuice.ci.ejb.ProfileManagerBean.createProfileBean(ProfileManagerBean.java:2598)
[27] com.djuice.ci.ejb.ProfileManagerBean.getProfileBean(ProfileManagerBean.java:318)
[28] com.djuice.ci.ejb.ProfileManagerBean.getProfilesForDevice(ProfileManagerBean.java:411)
[29] com.djuice.ci.ejb.ProfileManagerBean.getCurrentProfile(ProfileManagerBean.java:3136)
[30] com.djuice.ci.ejb.ProfileManagerBean.login(ProfileManagerBean.java:146)
[31] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.login(ProfileManagerBeanEOImpl.java:80)
.... remainder of stack truncated ...
"ExecuteThread-61" (TID:0x607cf8, sys_thread_t:0x607c30, state:CW, thread_t: t@72,
threadID:0xe9071dc8, stack_bottom:0xe9072000, sta
ck_size:0x20000) prio=5
[1] weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:262)
[2] weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:35)
[3] weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:98)
[4] weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
[5] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:427)
[6] weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:92)
[7] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:454)
[8]
com.djuice.ci.ejb.ProfileDeviceEntityBeanEOImpl.setDateLastLogon(ProfileDeviceEntityBeanEOImpl.java:
188)
[9] com.djuice.ci.ejb.ProfileManagerBean.chooseProfile(ProfileManagerBean.java:1221)
[10] com.djuice.ci.ejb.ProfileManagerBean.getCurrentProfile(ProfileManagerBean.java:3136)
[11] com.djuice.ci.ejb.ProfileManagerBean.login(ProfileManagerBean.java:146)
[12] com.djuice.ci.ejb.ProfileManagerBeanEOImpl.login(ProfileManagerBeanEOImpl.java:80)
[13] no.infohwy.djuice.ejb.CFacadeBean.login(CFacadeBean.java:122)
[14] no.infohwy.djuice.ejb.CFacadeBeanEOImpl.login(CFacadeBeanEOImpl.java:1200)
[15]
no.infohwy.djuice.ejb.CFacadeBeanEOImpl_ServiceStub.login(CFacadeBeanEOImpl_ServiceStub.java:760)
[16] no.infohwy.djuice.command.wap.CWapLogIn.execute(CWapLogIn.java:118)
[17] no.infohwy.djuice.command.CCommandServletWapPda.doGet(CCommandServletWapPda.java:123)
[18] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[19] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[20] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[21] weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:96)
[22] no.infohwy.djuice.common.LogonWapPda.doGet(LogonWapPda.java:65)
[23] javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
[24] javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
[25] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[26] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[27] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[28] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
[29] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[30] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[31] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
.... remainder of stack truncated ...
"ExecuteThread-60" (TID:0x6124f8, sys_thread_t:0x612430, state:R, thread_t: t@71,
threadID:0xe90a1dc8, stack_bottom:0xe90a2000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] java.io.BufferedInputStream.fill(BufferedInputStream.java:171)
[4] java.io.BufferedInputStream.read1(BufferedInputStream.java:221)
[5] java.io.BufferedInputStream.read(BufferedInputStream.java:278)
[6] java.io.FilterInputStream.read(FilterInputStream.java:118)
[7] java.io.PushbackInputStream.read(PushbackInputStream.java:147)
[8] sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:504)
[9] sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:440)
[10] java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:141)
[11] jsp_servlet._projects._djuice._prod._wapalizer._index._jspService(_index.java:79)
[12] weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
[13] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:114)
[14] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:723)
[15] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
[16] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:76)
[17] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:344)
[18] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:244)
[19] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
"ExecuteThread-59" (TID:0x6378f8, sys_thread_t:0x637830, state:R, thread_t: t@70,
threadID:0xe90f1dc8, stack_bottom:0xe90f2000, stac
k_size:0x20000) prio=5
[1] java.net.SocketInputStream.socketRead(Native Method)
[2] java.net.SocketInputStream.read(SocketInputStream.java:85)
[3] weblogic.socket.ResettableSocket.getPrefix(ResettableSocket.java:53)
[4] weblogic.socket.JVMSocketT3.claimSocket(JVMSocketT3.java:109)
[5] weblogic.socket.JVMSocketT3.claimSocket( -
Problem with Firefox and very heavy memory usage
For several releases now, Firefox has been particularly heavy on memory usage. With its most recent version, with a single browser instance and only one tab, Firefox consumes more memory that any other application running on my Windows PC. The memory footprint grows significantly as I open additional tabs, getting to almost 1GB when there are 7 or 8 tabs open. This is as true with no extensions or pluggins, and with the usual set, (firebug, fire cookie, fireshot, XMarks). Right now, with 2 tabs, the memory is at 217,128K and climbing, CPU is between 0.2 and 1.5%.
I have read dozens of threads providing "helpful" suggestions, and tried any that seem reasonable. But like most others who experience Firebug's memory problems, none address the issue.
Firefox is an excellent tool for web developers, and I rely on it heavily, but have now resorted to using Chrome as the default and only open Firefox when I must, in order to test or debug a page.
Is there no hope of resolving this problem? So far, from responses to other similar threads, the response has been to deny any responsibility and blame extensions and/or pluggins. This is not helpful and not accurate. Will Firefox accept ownership for this problem and try to address it properly, or must we continue to suffer for your failings?55%, it's still 1.6Gb....there shouldn't be a problem scanning something that it says will take up 300Mb, then actually only takes up 70Mb.
And not wrong, it obviously isn't releasing the memory when other applications need it because it doesn't, I have to close PS before it will release it. Yes, it probably is supposed to release it, but it isn't.
Thank you for your answer (even if it did appear to me to be a bit rude/shouty, perhaps something more polite than "Wrong!" next time) but I'm sitting at my computer, and I can see what is using how much memory and when, you can't. -
Problem with scanning and memory usage
I'm running PS CS3 on Vista Home Premium, 1.86Ghz Intel core 2 processor, and 4GB RAM.
I realise Vista only sees 3.3GB of this RAM, and I know Vista uses about 1GB all the time.
Question:
While running PS, and only PS, with no files open, I have 2GB of RAM, why will PS not let me scan a file that it says will take up 300Mb?
200Mb is about the limit that it will let me scan, but even then, the actual end product ends up being less than 100Mb. (around 70mb in most cases)I'm using a Dell AIO A920, latest drivers etc, and PS is set to use all avaliable RAM.
Not only will it not let me scan, once a file I've opened has used up "x" amount of RAM, even if I then close that file, "x" amount of RAM will STILL be unavaliable. This means if I scan something, I have to save it, close PS, then open it again before I can scan anything else.
Surely this isn't normal. Or am I being stupid and missing something obvious?
I've also monitored the memory usage during scanning using task manager and various other things, it hardly goes up at all, then shoots up to 70-80% once the 70ishMb file is loaded. Something is up because if that were true, I'd actually only have 1Gb of RAM, and running Vista would be nearly impossible.
It's not a Vista thing either as I had this problem when I had XP. In fact it was worse then, I could hardly scan anything, had to be very low resolution.
Thanks in advance for any help55%, it's still 1.6Gb....there shouldn't be a problem scanning something that it says will take up 300Mb, then actually only takes up 70Mb.
And not wrong, it obviously isn't releasing the memory when other applications need it because it doesn't, I have to close PS before it will release it. Yes, it probably is supposed to release it, but it isn't.
Thank you for your answer (even if it did appear to me to be a bit rude/shouty, perhaps something more polite than "Wrong!" next time) but I'm sitting at my computer, and I can see what is using how much memory and when, you can't. -
Problem with JTree and memory usage
I have problem with the JTree when memory usage is over the phisical memory( I have 512MB).
I use JTree to display very large data about structure organization of big company. It is working fine until memory usage is over the phisical memory - then some of nodes are not visible.
I hope somebody has an idea about this problem.55%, it's still 1.6Gb....there shouldn't be a problem scanning something that it says will take up 300Mb, then actually only takes up 70Mb.
And not wrong, it obviously isn't releasing the memory when other applications need it because it doesn't, I have to close PS before it will release it. Yes, it probably is supposed to release it, but it isn't.
Thank you for your answer (even if it did appear to me to be a bit rude/shouty, perhaps something more polite than "Wrong!" next time) but I'm sitting at my computer, and I can see what is using how much memory and when, you can't.
Maybe you are looking for
-
EP6.0 SP20 on IE 7 on Windows Vista
Hi! We currently have Enterprise Portals 6.0 SP 20 on Windows Server 2003. When we tried to edit locallly ppt files stored on Content Magament we got an error. Also we got errors when downloading Office files (also stored in CM) through Internet E
-
Hi, Everyone, I am new to pl/sql and when i am writing a if else statment in a procedure i get errors. could anyone please help me how to write this one procedure: create or replace PROCEDURE call_all_test ( b_bmonth IN NUMBER, b_TE
-
I can't hear Cortana or speak to her
Hi, I've been having an issue with Cortana. She's never been able to speak, even when she's supposed to practice saying my name. Also I noticed in Settings\System\Speech when I try to preview the voice for text to speech that won't work as well. The
-
First of all, just let me say I have read everything there is available on layout managers and how pack() and validate() work. My problem is simply that my JDialog appears far longer than its components, and I can't see why. I've created screenshots
-
Hi, I recently installed Lightroom 1.1 on a windows XP systems that is already running Photoshop CS3. Unfortunately, lightroom does not think Photoshop is installed, so control-E doesn't work. I was able to get access to photoshop with control-shift-