[JCA/JBoss] - Re: JBoss Connection Socket usage in error scenarios
by dkilley
Hi Vickyk,
I've enabled said debugging and will provide the actual log entries below, unfortunatly it did not reveal any meaningful exception/data, imho.
What I did notice with the information you gave me, browsing the Web Source Code, that perhaps I noticed something based ony our suggestion...
> BaseWrapperManagedConnection.java
if (mcf.getNewConnectionSQL() != null)
| {
| Statement s = con.createStatement();
| try
| {
| s.execute(mcf.getNewConnectionSQL());
| }
| finally
| {
| s.close();
| }
| }
In this case the statement is closed, but nothing is done to the connection object, up in HALocalManagedConnectionFactory we have the following
try
| {
| Driver d = getDriver(url);
| Connection con = d.connect(url, copy);
| if(con == null)
| {
| log.warn("Wrong driver class for this connection URL: " + url);
| urlSelector.failedUrl(url);
| }
| else
| {
| return new LocalManagedConnection(this, con, props, transactionIsolation, preparedStatementCacheSize);
| }
| }
| catch(Exception e)
| {
| log.warn("Failed to create connection for " + url + ": " + e.getMessage());
| urlSelector.failedUrl(url);
| }
In this case, where new LocalManagedConnection throws an exception, no call to con.close() is called, and it would only be called on the destroy.
What I am suggesting is either a new try/finally around the New LocalManagedConnection which closes the connection if it fails, or perhaps a finally added to the existing try, which may try to con.close when connections were not successful, thus a new try inside is better?
I am not a coder so I am way out of my depth on the specific suggestions for fixing, I am just providing some suggestions ;)
Thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148981#4148981
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148981
18 years, 1 month
[JBoss Tools (users)] - Re: Do the JBoss Tools for SEAM work?
by JeffCybulski
I've completely removed JBoss AS, SEAM, JBoss Tools, etc.. etc.. and performed a clean install. Whatever was causing that issue disappeared.
I've new configured Ajax, XDocs, and Seam (2.0.1.GA) home. I create a new new project using the wizard, selecting "Seam 2.0 technology preview". When I publish I get:
"ERROR [MainDeployer] Could not initialise deployment: file:/Developer/Java/jboss-4.2.2.GA/server/default/deploy/HelloWorld-ear.ear/
org.jboss.deployment.DeploymentException: url file:/Developer/Java/jboss-4.2.2.GA/server/default/deploy/HelloWorld-ear.ear/jboss-seam.jar"
After manually copying the required JARs to the deployment directory (which is a problem?) I get:
"ERROR [[/HelloWorld]] Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
java.lang.ExceptionInInitializerError"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148977#4148977
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148977
18 years, 1 month
[JBoss Tools (users)] - Re: Do the JBoss Tools for SEAM work?
by JeffCybulski
I'm using the JBoss adapter, as specified in the document. 'JBoss, a division of RedHat'/'JBoss AS 4.2'.
When I do a 'Publish' or 'Clean..' under 'JBoss Server View', 2 things occur:
1) 'default,all,minimal,other - type your own here' directory, at the same level as /server in the AS, is created. It has contains an empty 'deploy' subdirectory.
2) 15:38:38,772 ERROR [MainDeployer] Could not initialise deployment: file:/Developer/Java/jboss-4.2.2.GA/server/default/deploy/HelloWorld-ear.ear/
org.jboss.deployment.DeploymentException: url file:/Developer/Java/jboss-4.2.2.GA/server/default/deploy/HelloWorld-ear.ear/jboss-seam.jar could not be opened, does it exist?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148957#4148957
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148957
18 years, 1 month