There is an error running weblogic

First of all, this error translation is really bad, and I almost don't know what the error is when I look at Chinese.

Second, as you said, the service does force to shutdown when it starts (startweblogic) because the user authentication fails.

Finally, when you create a domain, you create an administrator user, the file must first write username and password in plaintext, assuming that the username and password are all weblogic, the format is as follows:

username=weblogic

password=weblogic

As the error message you posted, you need to use this boot when startweblogic, and weblogic will help you encrypt the contents of this file after starting it for the first time, so don't worry about password leakage.

This file weblogic92 is placed in the root directory of the user domain, and weblogic10 is placed in the servers adminserver security directory under the user domain.

All you need to do is initialize a file in the specified directory and good luck.

Delete all the contents under the servers, create a new one in the domain, enter username and password, save and restart admin

1. $* is a special variable in the shell that displays all parameters passed to the script as a single string.

For example, if you do this:

sh aaa bbb ccc

Then: $*='aaa bbb ccc'

2. If you want to start multiple managed services, you need to start them separately, and you can't add multiple service names to the end.

Brother, I also encountered this situation, it is not a simple increase in the number of connection pools can be solved, everyone thinks that the use of connection pools can make the connection better control, so simply configure the connection pool, as long as you can connect to the database, you feel that everything is OK.

In fact, if you don't configure the connection pool correctly, it will outweigh the losses. The reason is that the connection pool does reduce the overhead of the system each time you connect to the database, because there will be some available connections in the connection pool, and the program can just come here to pick it up when you use it, and the connections in the connection pool will generally not be closed, which is the problem.

This number of connections that are not closed will directly consume the number of connections that the Bumper database can provide.

This has the same effect as using the app to connect and forgetting to close it. It is even more serious (because the connections in the connection pool will be sent to SQL to test without becoming stale, and the connections in the program will time out).

Therefore, when using connection pools in the future, you must remember to configure the timeout option, rather than simply configuring the maximum and minimum numbers. Most connection pools have an option to configure the timeout initiator connection in the pool, such as MaxWait for DPCP, maximum-connection-lifetime for Proxool, and IdleTimeOutMinutes for JBoss built-in connection pools, but they are all 0-1L by default.

That is, by default, connections in the connection pool do not time out. This is important: the connection to the database is always the envy of the connection in the pool.

When these connections are consumed, if there are other external connections that want to use the database, there are no more connections available to the database.