Navjeet Nehra

Greenhorn
+ Follow
since Sep 18, 2003
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Navjeet Nehra

Score 86%.

Thanks to K&B, the rachers and the mock exams from Dan C.
16 years ago
Are you sure that the last output would be "234" since the last line in the catch block is return;

I think the value of the output should be "13423"
In the above code if f() is public in PolyB then PolyC has overridden f(). Since the method to be run is decided at runtime and the ref2 object points to PolyC so the PolyC.f() will be run.
As the last line in the catch block is return. The output would include the last "4"
Hi,
The code below uses the getCharacterOutputStream() to get the writer. Hope it helps
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Clob clob = null;

// writing the message into the Clob Object.
Writer wr =
((weblogic.jdbc.vendor.oracle.OracleThinClob) clob).getCharacterOutputStream();
char[] b = message.toCharArray();
wr.write(b);
wr.flush();
String updateClobQuery = "UPDATE {Table} SET CLOB_MESSAGE = ? " +
"WHERE TIME_STAMP_LOG = ?";

preparedStatement = conn.prepareStatement(updateClobQuery);
preparedStatement.setClob(1, clob);
preparedStatement.setString(2, timeStamp);
preparedStatement.execute();
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hi,
I am having the problems running continuous 24 hrs test against Weblogic 8.1. After some time the server starts complaining about the threads stuck
<Warning> <WebLogicServer> <BEA-000337> <ExecuteThread: '7' for queue: 'weblogic.kernel.Default' has been busy for "630" seconds working on the request "weblogic.ejb20.internal.JMSMessagePoller@d64412", which is
more than the configured time (StuckThreadMaxTime) of "600" seconds.>
This happens for a number of threads and then the server goes into a continuous period of inactivity trying desperately to free memory and then eventually it start giving "java.lang.OutOfMemoryException"
My queries are
1) How to detect on what the thread is stuck on
2) In case of a stuck thread - how to roll back/stop the thread so that the rest of the processing can continue.
Thanks
Navjeet
18 years ago
Isn't CDATA section just used to tell the parser not to process the contents, but pass(print) them as it is.
18 years ago
Hi Lasse,
I tried to specify the same however it did not work. Maybe I am not doing it properly. Anyhow I have temporarily solved the problem using the following
parser.parse(this.getClass().getResourceAsStream(PARAM_FILE));
and ensuring that the file lies in a directory which is in the CLASSPATH.
However if you can elaborate on your suggestions it would be of great help.
thanks
Navjeet
Hi,
I am trying to parse a xmlfile deployed as in war file contained within an ear file
The file is parsed within a JSP. The filename is provided as an init parameter. Now I need to provide the path along with the filename in the call DocumentBuilder.parse(filename).
If the full path is hardcoded in the string "filename" there is no problem however I cannot hardcode the path of the file.
thanks in advance
Navjeet
Hi,
I have the same setup as yours and I am encountering the lock-in error when I increase the load on the system. We have however discovered that if the connections are not tested while creation , handing over to the client when
released (as provided while setting up the connection pool) we do not get the error.
Still investigating this phenomenon so cannot say for sure however it points somewhat towards the load factor.
regards
Navjeet
18 years ago
Hi,
You have not mentioned the fact which driver are you using to connect to Oracle. If you are using an XA driver and the transaction required attribute in the config file is required the Weblogic will initiate an Global transaction.
regards
Navjeet
18 years ago
Sridhar,
Assuming you are using JMS there is a JMS header property called "JMSXDeliveryCount" which contains the number of times the message has been redelivered. This contains mq "BackoutCount" which can be used to set the redelivery limit.
Also the way we have found around is when the messages rollback due to XA errors put them in a suspend queue and reprocess them later when the resources are available.
In case you want to look up Java/Mq documentation use the following - Websphere MQ using Java - csqzaw11.pdf
Hope it helps
Navjeet
18 years ago
Hi,
I am working with the WLS and MQ using the Foreign JMS Provider mapping, Haven't had any issues regarding the transaction manager. Can you elaborate on your setup and the actual problems ?
regards

Originally posted by Sridhar Sri:
Hello Friends,
Has anyone worked on bridging the Weblogic JMS Provider with MQSeries JMS provider through a WL Messagin Bridge? If yes, have you encountered any problems with the transaction manager( weblogic container) ?
I have a problem in implementing container managed transactions on an MDB in WLS because MQSeries doesnt seem to support two-phase commit. Any inputs on this issue will be highly appreciated.
Thanks
Sridhar

18 years ago