How to enable HOT deployment scanner in JBoss ?

Steps :

• Open the file $JBOSS_HOME/server/[Instance Name]/conf/jboss-service.xml
• Search for "ScanEnabled"
• The enable to the Hot deployment scanner as below
  true
  
• You can set the Automatic scan period for Hot deployment,
  5000
• Restart the service once you made the changes.

Siebel Mobile Client Debugging (Using Environment Variable)

We often come across errors and problems in Siebel application whose source cannot be easily identified. The standard spooling (/s method in the Target of the siebel exe) of queries is helpful many times.
But many other times there is need of more detailed logging than the one produced by simple spool.
I am listing an already existing very simple method of detailed logging here. Many of you might already be aware and using this method. I have always found this method gives me the exact source of the problem.
Ok so say you are getting an error, which cannot be linked to any configuration or any change you have done.

The steps to increase the logging detail are:
1. Right-Click My Computer select Properties.
2. Goto Advanced tab in the system properties.
3. Click on the environment variables
4. In the environment variables window, create a new system variable by clicking the New button
5. Add variable name as SIEBEL_LOG_EVENTS, the variable value can be 4 or 5. I would recommend using value 4 to start, if that is not helpful increase it to 5.
6. Restart the system after making this change.
7. Start the Siebel application, reproduce the problem which needs debugging.
8. Goto the Log folder in the Webclient directory, open the Siebel.log file (it will be large in size) present there.
9. Search for error in this log file.

IMPORTANT: Remember to remove this System Variable after you are done with your debugging, otherwise the size of the file will go on increasing and eat up you system memory. And yes you will again need to restart your system for the removal to take effect.

The size of the log file generated by using this method is quite large. It might become a bit difficult to handle these files if you are not used to handling very large files. You can use the wordpad to open these files which will be a little bit faster than usual notepad. I use a different method involving a file splitting tool. I will handle that in my next post.

Have a successful debugging!!!

JBOSS Default Ports Configuration

Below listed are Default ports which can see after starting the default JBOSS instance…….
——————————————————————————————————————
8009 Apache java portocol connector
8080 HTTP 1.1 Connector
1099 Naming Bootstrap
1098 Naming Remote Method invocation
4444 EJB Invoker
4445 Alernative Pooled EJB Invoker
8083 Class Loading Service
8093 Messaging UIL2
———————–
Clustering
———————–
1100 Clustered Naming Service
1102 Naming Discovery

Log Levels on JBOSS Application server

There are 6 different log levels that can be configured in JBOSS Application server
A)FATAL
B)ERROR
C)WARN
D)INFO
E)DEBUG
F)TRACE

Excel API — POI.jar

Jakarta POI is an excellent api for manipulating excel operations using Java.

Neve use wrap text and autosize column methods on sheet class.

Use HSSFPalette class for better User Interface.

Connection Dead Exception in Sybase : Memory Leakage issue in Weblogic Server

If you are facing some Memory Leakage Problems in Web Applications and if it is a J2EE Struts based Web Application deployed in Weblogic Server 8.1. The memory in the server gets dumped in about 3-4 days and recycling needs to be done in the nodes to free up the memory. And also if the application does not have any EJB Transaction Management. Then follow the below resolutions and try it.

1)The memory issue could be the result of repeated ‘connection closed exception’ and its stack trace.
2)The checking, whether the connection is closed or not is wrong ‘DBUtil. closeQueryObjects’ method. Refer the following code

if(con != null){
try{con.close();
}
catch(Exception e){
m_logger.error("Exception when closing connection", e);
}

3)The right way to check whether a connection is closed or not id connection.isClosed()

JBoss is loosing its charm ?

Jboss is certainly facing an evolution competitive front, and basically has not reponded to it.
The competitive fronts are two-fold, and will be recognizable by even the most passing of observers in the middleware market.

1. Seam is losing month-by-month to Spring
2. Jboss is losing month-by-month to Glassfish

Here are some of the proof-points, first the JCP page for Web Beans, the standardization process of Seam:
http://jcp.org/en/jsr/detail?id=299

It shows a slower growth, while Spring rolls out S2AP and myriad other complementary technologies to seize the develper's attention. Seam is dying on the vine, and its own complexity does not bode well for a major roll-out of improvements any time soon

Just look at jboss.org, it is a mind -numbing array of ongoing and outstanding projects with SSO, ESB, and Rules among others seemingly having no delivery date in sight, that translates to project stability. This makes us to think whether JBoss products and projects is under-resourced?