You mean the JSP or tomcat, the java server stuff? What about after "server is connected" ... if it needs lots of separate sessions, and they're all trying to connect at the exact same moment it just might take several moments for them all to get established.while the server is connecting
Define "several". Is it 20? 50? All within 1 second? 10 seconds?makes several connections to Oracle 10g express on startup
andORA-12154: TNS:could not resolve the connect identifier
Hmmm maybe another Oracle client is in the way, something installed later might preempt the XE ORACLE_HOME and the tnsnames.ora in use might not be the one you think.XE is defined in tnsnames.ora.
Interesting. sqlnet.ora is for the client configuration, IMHO its not good to put a dependency on the network for a configuration file.getting SQLNET.ORA from a network path
If you figure that out, try adjusting the connect string to <host>:<port>/<servicename> in place of <port>:<sid> that should let the connection go via shared serverwhere the JDBC URL gets set
Fairly sure all those adjustments can be made without stopping/starting the listener or database. If that SERVICE= name gets changed, might cause some glitches for Apex, if you're using that at all. Changing the SERVICE= will require at least an 'alter system register;' to push an instance registration through the listener.
alter system set dispatchers = '(PROTOCOL=TCP)(dispatchers=5)(SERVICE=XEXDB)' scope=both; alter system set max_dispatchers = 20 scope=both; alter system set max_shared_servers = 20 scope=both; alter system set shared_servers = 5 scope=both;