robin patel

Greenhorn
+ Follow
since Jan 03, 2011
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by robin patel

Hi,

Please try to add the <Principal Name>UserName</Principal Name> inside your weblogic.xml
Also double check on that user's identity and it association to the respective group.
Mapping seems to be issue as of now, Try to enable the securityAtz on WLS and observe as to why Authorization is failing.


Regards
Rob
9 years ago
Hi Francis,

Can you try the below approach? As I can see there seems to be a issue with the Trusted certificate validation

1) Please try to access the resource(/secureWebAuth) directly on HTTPS port without Apache.
2) In the browser, you will find a paddle lock, double click on it and then save the file in a base 64 bit encoded format and save as .pem extension
3) FTP that .pem file to the box where Apache is running and do the necessary changes in the HTTPD.conf such that it reflects the new pem file.
4) Restart Apache
5) See the behavior
6) Update the results

Regards,
Rob




9 years ago
Hi,

Can you check the port number and the listen address which you are using to access the console/app from the browser?

Are you using HTTP port or HTTPS ?

If HTTP, then can you check whether the HTTP port is actually enabled or not in Weblogic ?

The best part to confirm this is to check the out file of the server and see on which port/ listen address the server is listening too and use this information you should be able to access the console and you application.


Regards,
Robin
9 years ago
Please delete your application from the WLS container

Once done, please deploy your application using the java weblogic.Deployer and observe the behavior

More details: http://download.oracle.com/docs/cd/E13222_01/wls/docs90/deployment/wldeployer.html

Also, is this your custom application or is coming to you from your vendor? If coming from Vendor, have they tested it internally that this application works??

Multiple Thread dumps taken during the state as "Activate Initializing" will tell you the exact issue.

Regards,
Rob
9 years ago
Where is this JDK usually defined?

Please go your WLS installation, search and open the file named "setDomainEnv.cmd/sh" depending upon your platform.

Normally located @ Domain_home>>bin>>setDomainEnv.cmd

Search for the string "JAVA_HOME" and look where does it points to. This will give you the location of your JDK.

Also, try keeping up the below settings
-Xms1280m -Xmx1280m -XX:PermSize=512m -XX:MaxPermSize=512m

Do let me know if you can being your instance up after this.

Regards,
Rob
9 years ago
Can you try keeping you JARS inside Domain/lib folder?
WebLogic follows dictionary level implementation when it comes to picking up the JARS.

Regards,
Rob
9 years ago
in addition to that,

can you also test this suggestion of increasing the "Thread Count"

To modify the default execute queue thread count using the Administration Console:
Start the Administration Server if it is not already running.
Access the Administration Console for the domain.
Expand the Servers node in the left pane to display the servers configured in your domain.
Right-click the name of the server instance that contains the execute queue you want to configure, and then select View Execute Queues on the pop-up menu to display a table of execute queues that can be modified.
Note: You can only modify the default execute queue for the server or a user-defined execute queue.
In the Name column, click directly on the default execute queue name to display the Configuration tab for modifying execute queues.
Locate the Thread Count value and increase or decrease it, as appropriate.
Click Apply to save your changes.
Reboot the selected server to enable the new execute queue settings.


The value of the ThreadCount attribute depends very much on the type of work your application does. For example, if your client application is thin and does a lot of its work through remote invocation, that client application will spend more time connected — and thus will require a higher thread count — than a client application that does a lot of client-side processing.
If you do not need to use more than 15 threads (the development default) or 25 threads (the production default) for your work, do not change the value of this attribute. As a general rule, if your application makes database calls that take a long time to return, you will need more execute threads than an application that makes calls that are short and turn over very rapidly. For the latter case, using a smaller number of execute threads could improve performance.

For more information visit

http://download.oracle.com/docs/cd/E13222_01/wls/docs81/perform/WLSTuning.html

Let me know if this helps

regards,
Rob
10 years ago
Hi Bhanu,

Can you help me with your environment a bit?

Is there any Webserver in front of weblogic?

How is the request flow for your application?


regards,
Rob


10 years ago
Hi Albert,

You will have to do the required settings inside the console application.

You can find the console application at the below location


D:\WLS1032\wlserver_10.3\server\lib\consoleapp\webapp\WEB-INF

You will find a weblogic.xml

Look for a session descriptor tag


<session-descriptor>
<timeout-secs>3600</timeout-secs>
<invalidation-interval-secs>60</invalidation-interval-secs>
<cookie-name>ADMINCONSOLESESSION</cookie-name>
<cookie-max-age-secs>-1</cookie-max-age-secs>
<cookie-http-only>false</cookie-http-only>
<url-rewriting-enabled>false</url-rewriting-enabled>
</session-descriptor>

change the timeout and the invalidation-interval-secs as per your choice and restart the weblogic server

Wait for the configured time and you will see that the user's session has been timedout and you will be forced to login again

Hope this helps


Regards,
Rob


10 years ago
Hi,

Were you able to configure SAML in WLS 10.3?

Do you need assistance on this ?


regards,
Rob
10 years ago
Hi Javian,

Please take a back up of your current m_properties.properties file

Once done, please enter your credentials in plain text

username=<WLS Username>
password=<WLS Password>

restart Node Manager in order for the changes to take effect.

You will see that the credential will be encrypted. There are no security issues in this.

Let me know if this works for you or not.

If not, kindly upload the NodeManger.properties file and the config.xml


Regards,
Rob
10 years ago
Hi,

I do not think that this is a Bug

can you try the below suggestion and let me know?

#invoke WLST
C:\>java weblogic.WLST
#connect WLST to an Administration Server
wls:/offline> connect('username','password')
#navigate to the ServerRuntime MBean hierarchy
wls:/mydomain/serverConfig> serverRuntime()
wls:/mydomain/serverRuntime>ls()
#navigate to the server LogRuntimeMBean
wls:/mydomain/serverRuntime> cd('LogRuntime/myserver')
wls:/mydomain/serverRuntime/LogRuntime/myserver> ls()
-r-- Name myserver
-r-- Type LogRuntime
-r-x forceLogRotation java.lang.Void :
#force the immediate rotation of the server log file
wls:/mydomain/serverRuntime/LogRuntime/myserver> cmo.forceLogRotation()
wls:/mydomain/serverRuntime/LogRuntime/myserver>
The server immediately rotates the file and prints the following message:
<Mar 2, 2005 3:23:01 PM EST> <Info> <Log Management> <BEA-170017> <The log file C:\diablodomain\servers\myserver\logs\myserver.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Mar 2, 2005 3:23:01 PM EST> <Info> <Log Management> <BEA-170018> <The log file has been rotated to C:\diablodomain\servers\myserver\logs\myserver.log00001. Log messages will continue to be logged in C:\diablodomain\servers\myserver\logs\myserver.log.>


Also, this link will help you a lot

http://download.oracle.com/docs/cd/E13222_01/wls/docs91/logging/config_logs.html#1001654


Regards,
Rob

10 years ago
Hi,

In order to make it working you need to specifically add the below parameters in your start up scripts of the WLS server


-Dweblogic.webservice.client.ssl.trustedcertfile=Give the location and the fully qualified name of the WLS Trust
-Dweblogic.webservice.client.ssl.strictcertchecking=false
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.SSL.enforceConstraints=off

Let me know if you are able to use the WL trust keystore.


Regards,
Rob
10 years ago
Hi ,

Can you please check whether "nm_password.properties" file contains the correct username and password?

If you edit nm_password.properties manually, you must restart Node Manager in order for the changes to take effect.

Below link will help:
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13740/nodemgr_config.htm#i1100227

Also try one more suggestion

Did you check if you have a boot.properties file in this location:
/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain/servers/AdminServer/data/nodemanager folder ?

If not create a plain text file called boot.properties with contents:

username=<WLS Username>
password=<WLS Password>

Check if this resolves your issue


I think you need a valid boot.properties under
/u0/app/oracle/product/middleware/user_projects/domains/ClassicDomain/servers/AdminServer/data/nodemanager

Node manager should be able to detect boot.properties under any of these folders.


Regards,
Rob
10 years ago