Oracle SOA on Weblogic
You will get to see this kind of exception, when you run Oracle BPELPM on weblogic server.
If you get "java.lang.OutOfMemoryError:" when you try to launch the BPEL Console page from OracleBPELServer domain.
You can find the fix below.
If you get this exception from your log file (oracleBPELServer.out) under your domain. Then do the following to fix this issue.
1. Navigate to the Weblogic Admin console.
2. Click on the server tab on your left side.
3. Click on your instance - domain
4. Click on the Server start, you can see this tab when the Configuration link is selected.
5. Please set values for those empty fields.
a. Java_home:
b. Java Vendor:
c. Bea Home:
d. Root Directory: root directory of the bpel domain.
6. Then in the "Arguments:" field you have to add the following. prefix the entry with the below value and add a space after adding the string.
-Xms128m -Xmx256m -XX:MaxPermSize=512m
7. Then restart the oracleBPELServer using the admin console.
8. Then you can launch your BPEL Console. It should come up.
NOTE: The arguments that you include in the console is specific to the domain and if you try modifying the arguments in the setEnv.cmd file,
it will be for the Admin Server. Keep this point in mind.
If my entry is wrong, please put your comment.
Tuesday, November 11, 2008
"Authentication denied: Boot identity not valid; "
This post is for WEBLOGIC Server Issue.
If you hit with this exception while launching your weblogic server the below are the fix you can try.
1. Launch the Admin console.
2. Click on the domain.
3. Click on the general tab.
4. Click on the Server start
5. In the Arguments property serach for the proxy entries and keep the values for those proxy entries as empty values.
Because the server is trying with the proxy and if there is some problem with the proxy it throws the Boot Identity not valid error.
Remove the proxy information from the arguments. Make the -Dhttp.proxySet=false as false. by default it will be "true".
Then restart the domain.
Hope your domain will come up.
If you still have problem, plz detail your exception.
If you hit with this exception while launching your weblogic server the below are the fix you can try.
1. Launch the Admin console.
2. Click on the domain.
3. Click on the general tab.
4. Click on the Server start
5. In the Arguments property serach for the proxy entries and keep the values for those proxy entries as empty values.
Because the server is trying with the proxy and if there is some problem with the proxy it throws the Boot Identity not valid error.
Remove the proxy information from the arguments. Make the -Dhttp.proxySet=false as false. by default it will be "true".
Then restart the domain.
Hope your domain will come up.
If you still have problem, plz detail your exception.
Subscribe to:
Posts (Atom)