This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 112689 - web application not working
Summary: web application not working
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All Linux
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-13 18:21 UTC by luismolina
Modified: 2007-09-21 06:23 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description luismolina 2007-08-13 18:21:04 UTC
in an application with jpa toplink and mysql i got this error:

deployment finished : 100%
Deploying application in domain completed successfully
Trying to create reference for application in target server  completed successfully
Trying to start application in target server  completed successfully
Error occurred during application loading phase. The application will not run properly. Please fix your application and
redeploy.
WARNING: Operation 'createResourceAndResourceReference' failed in 'resources' Config Mbean.
Target exception message: Could not add Resource Type: jdbc-connection-pool. Error Message: Operation 'setProperty'
failed in 'jdbc-connection-pool' Config Mbean.
Target exception message: Property portNumber can not be removed.
com.sun.enterprise.deployment.backend.IASDeploymentException: java.lang.RuntimeException:
javax.naming.NameNotFoundException: fa not found
connect-debugger:
Comment 1 Nitya Doraisamy 2007-08-15 19:14:58 UTC
Please attach the project or the sun-resources.xml and persistence.xml from the project.
Comment 2 Vince Kraemer 2007-08-15 22:16:52 UTC
Are you really seeing this issue in NetBeans 5.0?
  if you really are using NB 5.0, please attach the project

Can you upgrade a recent build of NetBeans 6.0?

Comment 3 luismolina 2007-08-16 07:50:44 UTC
i think the problem its with the jdbc pooling, i will try and tell you....
Comment 4 Nitya Doraisamy 2007-08-16 08:00:52 UTC
The exception seems to indicate an error in the JDBC Connection Pool resource.Could you attach the sun-resources.xml
(under the setup folder of the project). That will be useful in identifying the cause.
Comment 5 luismolina 2007-08-16 08:08:04 UTC
version changed to 6.0, error of mine.
Comment 6 luismolina 2007-08-16 13:48:36 UTC
the problem was that when you use the wizard for a new persistence unit (new entity classes from database) and say 
create new datasource, the jdbc pool its created but not the jdbc resource (in the app server), so you have to make it 
at hand..., and if you say existing datasource, the jdbc resource (in the app server) the same...
Comment 7 luismolina 2007-08-17 08:19:24 UTC
about my last comment, i think this problem could be for the app server being stoped, i mean when the wizard shows the
connections if the server its stoped, we cant know the connection pools availables.
Comment 8 Nitya Doraisamy 2007-08-17 18:25:36 UTC
The plugin can obtain list of connection pools/jdbc resources even if the server is not running. 
I cannot debug this issue unless I have the sun-resources.xml or project that is having problems. 
From the original description,  
"Operation 'createResourceAndResourceReference' failed in 'resources' Config Mbean.
Target exception message: Could not add Resource Type: jdbc-connection-pool. Error Message: Operation 'setProperty'"

It shows the connection pool reference creation is failing. The information for this connection pool in the
sun-resources.xml seems to be incomplete or has errors. 

Unable to reproduce error while creating webapp with JPA. Please attach the sun-resources.xml of the project with deploy
failure. You can find it in <project location>/setup folder.
Comment 9 Nitya Doraisamy 2007-09-21 06:23:00 UTC
Unable to reproduce and cannot isolate without requested information. Closing.
Please reopen is you continue to see this error.