anandraj tadkal

Ranch Hand
+ Follow
since Feb 22, 2011
anandraj likes ...
Oracle Redhat
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
6
Received in last 30 days
0
Total given
1
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by anandraj tadkal


Add an entry in the application web.xml file:

<web-app>
<session-config>
<session-timeout>15</session-timeout>
</session-config>
</web-app>



Or programmatically override the session timeout for a particular session.

HttpSession session = request.getSession();
session.setMaxInactiveInterval(10*30);



You can refer the below link:

http://weblogic-wonders.com/weblogic/2014/01/15/changing-default-session-timeout-jboss-7/

7 years ago
It might be a little late to reply on the post.

Administrators use deployment plans to easily change an application’s WebLogic Server configuration for a specific environment without modifying existing Java EE or WebLogic-specific deployment descriptors. Multiple deployment plans can be used to reconfigure a single application for deployment to multiple, differing WebLogic Server environments.

A sample demonstration of deployment plan usage with MDB is given below.

http://weblogic-wonders.com/weblogic/2009/11/29/plan-xml-usage-for-message-driven-bean/

A sample demonstration of deployment plan usage for changing the session invalidation time.

http://weblogic-wonders.com/weblogic/2009/12/16/invalidation-interval-secs/
7 years ago
You can use Jconsole, it uses the extensive instrumentation of the Java Virtual Machine (Java VM) to provide information about the performance and resource consumption of applications running on the Java platform.

Refer the below article for further details:

http://weblogic-wonders.com/weblogic/2014/01/13/jconsole-monitoring-weblogic-application-server/

You can also use Jrockit Mission Critical tool

http://weblogic-wonders.com/weblogic/2010/12/07/understanding-jrockit-runtime-analyzer-jra-recordings/
7 years ago
You can try using -XXdumpFullState argument for JRockit JVM R27.5.

With this option we will save all the process state including the heap.

http://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionXX.html

If you want to read the JRA recording please refer the below post.

http://weblogic-wonders.com/weblogic/2010/12/07/understanding-jrockit-runtime-analyzer-jra-recordings/

7 years ago
Hi Narayan,

The issue occurs if the apache is unable to proxy the request to servers or load balancer
This could be due to some disconnect between the request processing between apache and Jboss cluster. You might want to revisit the works.properties file.

Or there could be scenario where backend cluster servers are unavailable.

You can find a working sample on the below link.

http://weblogic-wonders.com/weblogic/2010/04/07/configure-apache-webserver-with-jboss-cluster/


7 years ago
I would first check the supported version for the particular JBoss version and based on that would try to use the latest in the available range.

Few parameters that need to be considered are -Xms, -Xmx, -XX:MaxPermSize.

7 years ago
You would need to enable HTTP Tunneling on the WebLogic server. By default, t3 protocol is enabled for external clients.

HTTP tunneling provides a way to simulate a stateful socket connection between WebLogic Server and a Java client when your only option is to use the HTTP protocol. It is generally used to tunnel through an HTTP port in a security firewall. HTTP is a stateless protocol, but WebLogic Server provides tunneling functionality to make the connection appear to be a regular T3Connection. However, you can expect some performance loss in comparison to a normal socket connection.

You can follow the below oracle documentation.

http://docs.oracle.com/cd/E17904_01/web.1111/e13701/web_server.htm#i1059801
7 years ago
Possible causes:
- not enough swap space left, or
- kernel parameter MAXDSIZ is very small.

Solution:
Although it appears that an OutOfMemoryError is thrown this apparent exception is reported by the HotSpot VM code when an allocation from the native heap failed and the native heap may be close to exhaustion.

The message indicates the size (in bytes) of the request that failed and also indicates what the memory is required for. In some cases the reason will be shown but in most cases the reason will be the name of a source module reporting the allocation failure.

If an OutOfMemoryError with this error is thrown it may require using utilities on the operating system to diagnose the issue further. Examples of issues that may not be related to the application are when the operating system is configured with insufficient swap space, or when there is another process on the system that is consuming all memory resources. If neither of these issues is the cause then it is possible that the application is failed due to native leak; for example, application or library code is continuously allocating memory but is not releasing it to the operating system.
For more information: http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf

The recommendation for swap space size in the Solaris is that swap should be configured about 30% of physical RAM.

The following link has suggested a workaround to add ‘-XX:+UseDefaultStackSize -Xss256K’ parameter.

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4916142

Add: -XX:CodeCacheMinimumFreeSpace=2M -XX:+ReservedCodeCacheSize=64M -XX:PermSize=128m -XX:MaxPermSize=384m (As per your other JVM settings)

http://weblogic-wonders.com/weblogic/2010/12/30/different-out-of-memory-issues/

Hope it helps you debug further.

7 years ago
Hi Raghu,

It might be a little late in the game :-) , but you can refer the below post for the steps to configure SSL on WebLogic.

http://weblogic-wonders.com/weblogic/2011/05/25/ssl-configuration-for-weblogic-server/
7 years ago
Below is description from Oracle website:

BEA-101380: More than one web fragments with the same name: "{0}".
Cause: More than one web fragments with the same name.
Action: Change one or more web fragment names to avoid the conflict.

Level: 1

Type: ERROR

Impact: HTTP

There could be a conflict in the web fragment name.

Regards,
Anandraj
7 years ago
There could be multiple scenarios where you can experience such NullPointerException.

Could you please paste the complete error stack trace here.

Few of the common SSL issues are listed below.

http://weblogic-wonders.com/weblogic/2010/01/28/troubleshooting-ssl-issues/

Regards,
Anandraj
7 years ago
The issue might occur due to conflict on the class versions.

Make sure you put the latest el-api.jar in your jre/lib/ext and give it a try.

Regards,
Anandraj
7 years ago
A singleton service is a service that can only run on a single managed server in a cluster at a time.

Weblogic Server lets you automatically monitor and migrate singleton services from one server to another.

This can be done by implementing the “weblogic.cluster.singleton.SingletonService” interface and by using activate () and deactivate () methods in a class.

Regards,
Anandraj
7 years ago