This error occurs when we double click the installable exe and your MaAfee antivirus agent is active. So either disabling theagents or by ununstalling the McAfee agent will resolve the issue.
2. If the startWeblogicServer command starts command prompts and closes
Then start the installation in a command prompt and write the log out put to a file by adding ">> mylog.log " at the end of the command lin.
3. "Test Console" service is not running. Contact administrator to start this service.
This error comes because the address is not binded properly. This can be bind properly to one address. This is can be done in the Weblogic Administration Console at a. Home >Summary of Servers >[Your Server]->General->Listen Address
Setting the "Listen Address" explicitly to 127.0.0.1
4. Server is not starting properly and the error log shows like below
javax.transaction.SystemException:weblogic.transaction.loggingresource.LoggingResourceException:java.sql.SQLException: JDBC LLR, table verify failed for table 'WL_LLR_ADMINSERVER', row'JDBC LLR Domain//Server' record had unexpected value 'my_domain2//AdminServer' expected'my_domain//AdminServer'*** ONLY the original domain and server that creates an LLR table may access it ***
This is because we are not using the Derby database for our examples. If we are not working on the examples then we don't need the Derby Database server. So, to resolve this issue, the solution is if you are using the Derby then open config .xml and delete
Now you may get error like [ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.But the server starts promptly.
{OR}
Alternatively , Execute the following sql statement from SOA_INFRA schema user.
select RECORDSTR from WL_LLR_ADMINSERVER where XIDSTR = 'JDBC LLR Domain//Server';
UPDATE WL_LLR_ADMINSERVER set RECORDSTR = '
{Note:
COMMIT;
5. OEPE (Eclipse) insists server failed to start (But the Server started well).
This issue is because the OEPE is not properly binded with the server host name. Similar issue like system binding as shown above. The solution is commenting the entry for localhost in the host file with (#) letter as shown below
#127.0.0.1 localhost
{OR}
Alternatively you can check if the Server binding is properly mentioned or not as in the issue No.3
6. If you are not able to shutdown the server from the default configured start up menu item and getting the flowing error
Connecting to t3://KSHAIK-LPT:7001 with userid weblogic ...
This Exception occurred at Fri Dec 10 19:01:26 IST 2010.
javax.naming.CommunicationException [Root exception is java.net.ConnectException
: t3://KSHAIK-LPT:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available rou
ter to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:366)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:117)
Solution, is change the stopWeblogicServer.cmd script
By pointing to set AdminServer host as localhost, If its localhost then try to change it to port 127.0.0.1 or write the mechine name.
7. When we create the OSB and SOA in one domain both in one jvm (one server) then the important thing to remember is After this selection you should see a screen with two servers One managed server for OSB and one managed for SOA.
Since we would like to have both the servers in one managed server (one JVM) we will have to do one important step here. We have to delete either of the servers and rename the other server with deleted server name.eg delete osb_server1 and rename the soa_server1 to osb_server1 or we can also delete soa_server1 and rename the osb_server1 to soa_server1
8. ESB Proxy
The solution is to Make sure that the in OSB Console, all the sessions are activated, no partially activated status. Also, if you are configuring the domain only for OSB along with admin server in single server mode then update the LISTENER HOST with 127.0.0.1. Or if you are installing the admin server and OSB in a managed server along with SOA or without SOA then keep the LISTENER HOST empty for both the admin server and the managed server.
9. [JCATransport:381987]An error occured while validating JCA transport endpoint. JNDI lookup with URL: jca://eis/DB/esrdDatabase failed. Missing JNDI configuration such as undeployed or misconfigured JCA Adapter RAR or connection factory
The actual solution is available in the follow two other blogs, which helped me to resolve the issue
http://guidoschmutz.wordpress.com/2010/08/08/oracle-service-bus-11g-and-db-adapter-a-different-more-integrated-approach/ and
http://tech-learnings.blogspot.com/2009/08/creating-connection-factory-for.html
10. Caused By: java.lang.NoSuchMethodError:
org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar([Lorg/apache/xerces/xni/pa
rser/XMLInputSource;)V
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(Unknown Source)
at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:594)
at com.sun.faces.config.DbfFactory.initSchema(DbfFactory.java:151)
at com.sun.faces.config.DbfFactory.
at com.sun.faces.config.ConfigManager$ParseTask.
Truncated. see log file for complete stacktrace
The resolution is , Giving the security permission for Everyone on the Oracle_SOA1 folder and wlserver_10.3 and then Restarted the server. Then it started working well.
11. If the managed server startup command is closing immediately without starting the server then the issue might be passing the user id weblogic and its password in the same command line like below
startManagedWebLogic.cmd osb_server1 http://localhost:7001/ weblogic password
2 comments:
very usefull, thanks!
very good troubleshoot :). Thank you so much
Post a Comment