Issues with weblogic 7.0 and Java 1.2, Please Respond ASAP

Hi Everyone,

I have servlet program running on weblogic 7.0. The code works fine in development (same config as Production).

But I have problems with the code in production/Test domain. The code runs successfully only for the first time. Subsequent execution of the code results into infinite loop.

Has anyone came across this issue. If so please help

Thanks in advance

[402 byte] By [nilona] at [2007-11-26 14:54:09]
# 1

weblogic 7? jdk 1.2?

we're up to weblogic 9.2 now. time to upgrade, dude.

"I have servlet program running on weblogic 7.0. The code works fine in development (same config as Production). "

Fine.

"But I have problems with the code in production/Test domain"

Confusing. Is this production or test? You said production was the same as dev.

If the code is the same, then the environments are not.

Servlet? Infinite loop? Not likely. Do you mean subsequent HTTP requests?

Can't help with so little information. Sounds like an unstructured mess.

Logs, monitors. If it were me, I'd attach IntelliJ to the instance that was hanging up and walk through it with the debugger to see what was going on.

%

duffymoa at 2007-7-8 8:42:35 > top of Java-index,Java Essentials,Java Programming...
# 2

> weblogic 7? jdk 1.2?

>

> we're up to weblogic 9.2 now. time to upgrade,

> dude.

>

Sometimes you can't.

We're stuck with WL 6.1 and Java 1.3 because that's what a major customer is using who won't upgrade and WL 6 can't talk to anything except another WL 6 and requires 1.3 and nothing else.

Another customer uses WL 7 (but doesn't need to talk to our appservers directly, luckily) and supporting them is a pain.

It does some rather weird things with our webservices...

jwentinga at 2007-7-8 8:42:35 > top of Java-index,Java Essentials,Java Programming...
# 3

Hi Everyone,

Sorry for the insufficient infomation.

Here is the details :

I have servlet program running on weblogic 7.0. The code works fine in development (same config as Production). So not able to use debugger in Dev.

But I have problems with the code in production domain. The code runs successfully only for the first time and displays the result in the screen. (its using the if condition checking the boolean value returned from another methods is true or false.) Next time, when i run with the same input, it returns the value from another method and returns the value to the caller and starts executing from begining of the caller methods (instead of displaying result in the screen) and it goes in to the loop.

Has anyone came across this issue. If so please help

Thanks in advance

nilona at 2007-7-8 8:42:35 > top of Java-index,Java Essentials,Java Programming...
# 4

> Hi Everyone,

> The code works fine in development (same config as

> Production).

>

> But I have problems with the code in production

> domain.

This tells me that the first statement is false - development is NOT the same as production. You need to stop telling yourself that they're the same and figure out what's different.

> The code runs successfully only for the first

> time and displays the result in the screen. (its

> using the if condition checking the boolean value

> returned from another methods is true or false.)

> Next time, when i run with the same input, it

> returns the value from another method and returns

> the value to the caller and starts executing from

> begining of the caller methods (instead of

> displaying result in the screen) and it goes in to

> the loop.

Could be anything - threading issues, etc. Who knows? You've really provided no details at all. I'm not sure I'd want to see them, either, because this will be a very difficult problem to solve on a forum. You really ought to be talking to your WebLogic support.

%

duffymoa at 2007-7-8 8:42:35 > top of Java-index,Java Essentials,Java Programming...
# 5
Start by posting the servlet code. Put in code tags, please.%
duffymoa at 2007-7-8 8:42:35 > top of Java-index,Java Essentials,Java Programming...
# 6

well, from what I can glean from the incoherent ramblings it sounds like he's using a static boolean in a servlet to determine if something should be done.

In a test environment where he's the only one using the application (and it's thus effectively running singlethreaded) that's fine.

In a production environment with multiple users it's going to fail almost instantly.

Nothing to do with WL, nothing to do with Java 1.2 (which isn't supported by WL 7, so he must mean some other 1.2 spec), everything to do with OP not understanding how servlets work.

jwentinga at 2007-7-8 8:42:35 > top of Java-index,Java Essentials,Java Programming...
# 7
Hi All,Thanks for you replyI would like to add one more information here ....When i redeploy the application its working for the first time. Then it goes in to loop ... Thanks in advance
nilona at 2007-7-8 8:42:35 > top of Java-index,Java Essentials,Java Programming...