Mila Shanoy

Greenhorn
+ Follow
since Aug 21, 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 Mila Shanoy

I am getting a weird error when trying to startup a managed server (Linux, WL6.1)
I am starting it with the command line:
startManagedWebLogic.sh managedapp http://adminapp:7001

Here is the error:
starting wls managed server...
Starting WebLogic Server ....
Connecting to http://adminapp:7001...
<Sep 3, 2003 2:55:56 PM EDT> <Emergency> <Configuration Management> <Errors detected attempting to connect to admin server at http://adminapp:7001 during initialization of managed server ( null:7001 ). The reported error was: < null > This condition generally results when the managed and admin servers are using the same listen address and port.>
<Sep 3, 2003 2:55:56 PM EDT> <Emergency> <Server> <Unable to initialize the server: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException - with nested exception:
[java.lang.NoSuchMethodError]
java.lang.NoSuchMethodError
at weblogic.rjvm.ConnectionManager.createIdentifyMsg(ConnectionManager.java:1138)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1035)...............

What does it mean ".. managed and admin servers are using the same listen address and port"? I appreciate any ideas you might have.
18 years ago
You are right. I went to the console of the admin server and configured the new managed server, which added it to confog.xml of the admin server. That fixed the problem. Thank you.
18 years ago
I am installing WL6.1 on Linux, as a Managed Server, and getting the following error. I would appreciate any insights/guesses you have about the cause of the exception:
starting wls managed server...
Starting WebLogic Server ....
Connecting to http://adminapp1:7001...
*******************************************
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: manapp1 not found
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
at weblogic.management.Admin.initialize(Admin.java:340)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
*******************************************
Thank you.
18 years ago
Thank you. You confirmed my suspicions.
I am cleaning up/debugging the following code:
stmt = conn.createStatement();
stmt.execute(some_select_query1);
rs = stmt.getResultSet();
// ..... some code that uses rs ....
stmt.execute(some_select_query2);
rs = stmt.getResultSet();
// ..... some code that uses rs ....

My question is: does the code leave hanging resultset objects? Does it need rs.close() before each 'rs = stmt.getResultSet();'
What is your opinion/experience on that?
Thank you.