July 25, 2008 09:38am pdt

1. girionis 14,000
2. ramazany... 11,050
3. J4M3S_... 8,450
4. PascalHer... 3,500
5. Nellios 3,250
6. melchkish... 2,500
7. Ajay-Singh 2,250
8. CEHJ 2,100
9. DaveyEss 2,000
9. Meritor 2,000
9. successc... 2,000
9. mukundha... 2,000
9. MicheleM... 2,000
9. zrgiu 2,000
15. TimYates 1,500
15. HonorGod 1,500
15. cedlinx 1,500

1. ramazany... 17,050
2. girionis 14,000
3. J4M3S_... 8,450
4. CEHJ 7,720
5. rama_kri... 7,000
6. mayankea... 5,500
7. Ajay-Singh 4,250
8. objects 3,780
9. PascalHer... 3,500
10. Nellios 3,250
11. contactka... 3,000
12. melchkish... 2,500
13. giltjr 2,400
14. DaveyEss 2,200
15. schwertner 2,000
15. MicheleM... 2,000
15. mhunts 2,000
15. Meritor 2,000
15. gibu_geo... 2,000
15. mukundha... 2,000
15. zrgiu 2,000
15. karanw 2,000
15. CSecurity 2,000
15. Kuldeepc... 2,000
15. successc... 2,000

04.04.2008 at 03:56AM PDT, ID: 23295583

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.7

Problem in JBoss Connection Pooling

Zones: Jboss Application Server, MySQL

Tags: JBoss,MySQL

Dear Experts,

Our application is based on struts,mysql as database,JBoss as server.we are using connection pooling mechanism in our application..we are using a seperate Database.java file to get the connection.I have sent some code snippets for your clarification...

when ever we are in need of connection,we are getting the connection by using the File(Database.java) and after using the connection we are closing the connection.But when we are checking the jmx-console for the number of active connections,it is displaying all the connections that has been requested from starting of the application.It seems that it is not closing the connections.like this when it has reached the
max number of connections the application is throwing an error.

Is it the proper way of implementing the connection pooling mechanism?If i had missed out anything in my coding,please advice how to implement in a correct way.For your reference i have sent the code snippets for you.

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:

           
           
             Database.java(to get database connections)
 
public static Connection con;
	public static String Databasename;
	private static Database db=new Database();
	private Database(){}
	public static Database getDatabase()  throws Exception   
	{
			
		try
		{			
			InitialContext ctx = new InitialContext();
	               DataSource ds =(DataSource)ctx.lookup("java:/MySQLDB");
	             con = ds.getConnection();
		}
		finally
		{
		}
		return db;
	}
 
DAO class.
 
public class LoginBeanDAO 
{
	Database db=null;
       public LoginBeanDAO(HttpServletRequest request)throws Exception
	{
		db=Database.getDatabase();
		UserDetails=new ArrayList();
		loginmaildetails=new ArrayList();
		session=request.getSession(true);
		LOGIN_STATUS=false;
		unreadmailscount=0;
	}

           
         

Start your free trial to view this solution

Question Stats

Zone: Networking

Question Asked By: CIPL-Senthil

Solution Provided By: cedlinx

Participating Experts: 1

Solution Grade: B

Translate:

Loading Advertisement...

20080236-EE-VQP-29 / EE_QW_2_20070628