The previous time on the line. Encounter a Jndi problem, how is it a problem? It is not a problem in the test environment of the original, in the production environment, you cannot connect to the production database and then discover the problem, that is, the IBM tool generates its own active connection Jndi resource file in the test environment resources.xml, I have deleted, restarted the server, failed. Later, I thought it was definitely the cause of the was cache, so, imagine the cause of the cache, and finally, the test environment restarted was, problem solved. But later, he said it was impossible to restart the production environment was. I was old, and later the so-called leader said, he went to see the chief designer without solution, but time waits for no one. Pass 2 days or say there is no way. The way I came back in the afternoon, I thought, since you can't restart was. This is a problem with the cache, it does not change the name of the application, indeed, the Monday to work change jndi that is to overcome the name.
Copyright notice: This article Bo Master original article. Blog, not reproduced without consent.
Under the production environment was restarted do not agree, how to do?
