Steve Nelligan

Greenhorn
+ Follow
since Nov 09, 2010
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Steve Nelligan


I'm in the process of updating our portal from Tomcat 7 to Tomcat 8.0 and Java 7 to Java 8 (amazon-corretto-8.242.08.1-windows-x64-jdk)

I am having a problem on startup of our portal application (Jetspeed 2).

It is throwing an error in localHost on statup:

05-Sep-2020 10:40:28.531 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.loadOnStartup Servlet [DiagnosticsServlet] in web application [/fsportal] threw load() exception
org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:55)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:277)
at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:75)
at org.apache.jasper.compiler.TagLibraryInfoImpl.generateTldResourcePath(TagLibraryInfoImpl.java:250)
at org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:125)
at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:421)
at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:479)
at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1435)
at org.apache.jasper.compiler.Parser.parse(Parser.java:139)
at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:227)
at org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:201)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:358)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:338)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:325)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:580)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:363)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)
at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:138)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1188)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1132)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1021)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5085)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5397)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:755)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:731)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:620)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1832)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

I've already removed the "standard-1.1.2.jar" from the lib folder....
I've updated the jstl-1.1.2.jar with the latest version of it (just in case).

Still getting the above errors...

Not sure if this is a java 8 issue or a Tomcat 8.0 issue.


Any Ideas?


3 weeks ago
1. Speed up startup
2. remove extra entries in log file
1 month ago
The information contained in the documents all refer to .jar files.
The problem is where Tomcat is scanning Resource paths which do not contain jar files; rather portal page configuration files.
1 month ago


I am cleaning up the TLD messages:

FINE [localhost-startStop-1] org.apache.jasper.servlet.TldScanner$TldScannerCallback.scan No TLD files were found in [file:???...jar]. Consider adding the JAR to the tomcat.util.scan.StandardJarScanFilter.jarsToSkip property in CATALINA_BASE/conf/catalina.properties file.



I am also getting the messages:

FINE [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanResourcePaths No TLD files were found in resource path [/WEB-INF/pages/reports/].



How do I stop the scanning of resources?


1 month ago


We are currently running Tomcat 7 and Java 7.

We are updating to Java 8 with Tomcat 8.

When starting an application in Tomcat 8 with Java 8, I get the following errorsin the Catalina log:
24-Jul-2020 11:45:17.868 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log ContextListener: contextInitialized()
24-Jul-2020 11:45:17.868 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log SessionListener: contextInitialized()
24-Jul-2020 11:45:17.868 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log ContextListener: attributeAdded('StockTicker', 'async.Stockticker@771243ed')
24-Jul-2020 14:19:21.990 SEVERE [localhost-startStop-9] org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener of class org.springframework.web.context.ContextLoaderListener
java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderListener
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1352)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1180)
at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:544)
at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:525)
at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4822)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5363)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:755)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:731)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:973)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1850)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

24-Jul-2020 14:19:21.990 SEVERE [localhost-startStop-9] org.apache.catalina.core.StandardContext.listenerStart Skipped installing application listeners due to previous error(s)


Any help would be appreciated.


2 months ago
When a webapp is deployed to tomcat, the x.war file is exploded and a folder with name "x" is created in the webapps folder.
At the same time, a folder is created in the TEMP directory with a name #-x. Where # is a sequential number.

This has always been the case since I took over working with Tomcat.  Is this an unusual occurrence?


10 months ago
Note: the temp directory is empty.
Adding the jars to the do not scan list did speed up the startup; but when I shut down tomcat
I get the following errors:




INFO: Stopping service Catalina
Nov 13, 2019 8:04:25 AM org.apache.catalina.loader.WebappClassLoaderBase openJARs
WARNING: Failed to open JAR [null]
java.io.FileNotFoundException: G:\Tomcat7\temp\8-unauthorized\WEB-INF\lib\commons-lang-2.6.jar (The system cannot find the path specified)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:215)
at java.util.zip.ZipFile.<init>(ZipFile.java:145)
at java.util.jar.JarFile.<init>(JarFile.java:153)
at java.util.jar.JarFile.<init>(JarFile.java:117)
at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:315)
at org.apache.catalina.loader.WebappClassLoaderBase.openJARs(WebappClassLoaderBase.java:3131)
at org.apache.catalina.loader.WebappClassLoaderBase.findResourceInternal(WebappClassLoaderBase.java:3443)
at org.apache.catalina.loader.WebappClassLoaderBase.findResource(WebappClassLoaderBase.java:1505)
at org.apache.catalina.loader.WebappClassLoaderBase.getResourceAsStream(WebappClassLoaderBase.java:1749)
at org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc(WebappClassLoaderBase.java:2345)
at org.apache.catalina.loader.WebappClassLoaderBase.clearReferences(WebappClassLoaderBase.java:2286)
at org.apache.catalina.loader.WebappClassLoaderBase.stop(WebappClassLoaderBase.java:2186)
at org.apache.catalina.loader.WebappLoader.stopInternal(WebappLoader.java:684)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5978)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1723)
at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1712)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Nov 13, 2019 8:04:25 AM org.apache.catalina.loader.WebappClassLoaderBase openJARs
WARNING: Failed to open JAR [null]
java.io.FileNotFoundException: G:\Tomcat7\temp\8-unauthorized\WEB-INF\lib\commons-lang-2.6.jar (The system cannot find the path specified)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:215)
at java.util.zip.ZipFile.<init>(ZipFile.java:145)
...

10 months ago
The startup of siteminder.war takes 64071ms or 1.07 minutes.


The environment on the server is the same, we were running tomcat 7.0.34 and it took approx 4 minutes
We installed 7.0.96 on the server in it's own folder and configured it same as previous verion and now it takes 23 minutes.

We do have a large number of jar files in our system.

What changed between 7.0.34 and 7.0.96 to cause this startup problem?

-Steve Nelligan

10 months ago
Below is the catalina-Tomcat log for 7.0.96

Nov 12, 2019 11:28:40 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Nov 12, 2019 11:28:40 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8443"]
Nov 12, 2019 11:28:40 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Nov 12, 2019 11:28:40 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1411 ms
Nov 12, 2019 11:28:40 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Nov 12, 2019 11:28:40 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.96
Nov 12, 2019 11:28:40 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor G:\tomcat7\conf\Catalina\localhost\fsportal.xml
Nov 12, 2019 11:28:40 AM org.apache.catalina.realm.JAASRealm setUseContextClassLoader
INFO: Setting useContextClassLoader = true
Nov 12, 2019 11:29:56 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 12, 2019 11:30:08 AM org.apache.jasper.compiler.TldLocationsCache tldScanJar
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 12, 2019 11:30:09 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deployment of configuration descriptor G:\tomcat7\conf\Catalina\localhost\fsportal.xml has finished in 89,389 ms
Nov 12, 2019 11:30:09 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive G:\tomcat7\webapps\accountrequest.war
Nov 12, 2019 11:31:16 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 12, 2019 11:31:16 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive G:\tomcat7\webapps\accountrequest.war has finished in 66,909 ms
Nov 12, 2019 11:31:16 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive G:\tomcat7\webapps\aimibuy.war
Nov 12, 2019 11:32:24 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 12, 2019 11:32:24 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive G:\tomcat7\webapps\aimibuy.war has finished in 67,362 ms
Nov 12, 2019 11:32:24 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive G:\tomcat7\webapps\externalcharges.war
Nov 12, 2019 11:33:30 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 12, 2019 11:33:30 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive G:\tomcat7\webapps\externalcharges.war has finished in 66,347 ms
Nov 12, 2019 11:33:30 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive G:\tomcat7\webapps\hrportlet.war
Nov 12, 2019 11:34:35 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/portlet is already defined
Nov 12, 2019 11:34:35 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 12, 2019 11:34:35 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive G:\tomcat7\webapps\hrportlet.war has finished in 65,021 ms
Nov 12, 2019 11:34:35 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive G:\tomcat7\webapps\ibuystartpage.war
Nov 12, 2019 11:35:39 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 12, 2019 11:35:39 AM org.apache.catalina.startup.HostConfig deployWAR
...
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Nov 12, 2019 11:52:55 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory G:\tomcat7\webapps\sitemindertest has finished in 64,071 ms
Nov 12, 2019 11:52:55 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Nov 12, 2019 11:52:55 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8443"]
Nov 12, 2019 11:52:55 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Nov 12, 2019 11:52:55 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1454863 ms
10 months ago

Because of an error being generated in 7.0.34
"Unable to process Jar entry [module-info.class] from Jar.../] for annotations"
We upgraded the tomcat to 7.0.96.
It appears that the newer version of tomcat scans all the jar files and reports errors that the TLD is not found.

It is taking a large amount of time to start up tomcat.
Version7.0.34  took 765,583ms to startup with all the apps deployed.
Version 7.0.96  took 1,953,913ms to startup with only a couple of the apps deployed.

I have tried making the following change in catalina.properties "org.apache.catalina.startup.ContextConfig.jarsToSkip=*.jar"
But this does not appear to work...

Does any one know how to speed up the startup of tomcat 7.0.96.
Because of our Apps, we are stuck with Java 7 and Tomcat 7.  Plans are in the works to correct this, but it is not a easy change.

Thanks in advance,
Steve Nelligan
University of Illinois
snelliga@illinois.edu




10 months ago



I am trying to learn JavA EE and purchased a course "Java EE: EJB 3.0 and Java Persistence" from Learn NowJava.com.

I'm doing fine until the end of module 5, where I start getting an error when starting JBOSS:

10:52:03,113 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
10:52:03,902 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/EJB_EAR_Project.ear/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying Simple_EJB_Project.jar: Container jboss.j2ee:ear=EJB_EAR_Project.ear,jar=Simple_EJB_Project.jar,name=Teller,service=EJB3 failed to resolve persistence unit BankAccountJPA
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:201)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:103)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalArgumentException: Container jboss.j2ee:ear=EJB_EAR_Project.ear,jar=Simple_EJB_Project.jar,name=Teller,service=EJB3 failed to resolve persistence unit BankAccountJPA
at org.jboss.injection.PersistenceUnitHandler.addPUDependency(PersistenceUnitHandler.java:135)
at org.jboss.injection.PersistenceContextHandler.loadXml(PersistenceContextHandler.java:76)
at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:588)
at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:415)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:523)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:194)
... 23 more
Caused by: java.lang.IllegalArgumentException: Can't find a persistence unit named 'BankAccountJPA' in AbstractVFSDeploymentContext@1649490869{vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/EJB_EAR_Project.ear/Simple_EJB_Project.jar/}
at org.jboss.jpa.resolvers.BasePersistenceUnitDependencyResolver.resolvePersistenceUnitSupplier(BasePersistenceUnitDependencyResolver.java:107)
at org.jboss.ejb3.Ejb3Deployment.resolvePersistenceUnitSupplier(Ejb3Deployment.java:720)
at org.jboss.ejb3.EJBContainer.resolvePersistenceUnitSupplier(EJBContainer.java:1428)
at org.jboss.injection.PersistenceUnitHandler.addPUDependency(PersistenceUnitHandler.java:130)
... 28 more
10:52:03,921 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS IN ERROR:
Deployment "vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/EJB_EAR_Project.ear/" is in error due to the following reason(s): java.lang.IllegalArgumentException: Can't find a persistence unit named 'BankAccountJPA' in AbstractVFSDeploymentContext@1649490869{vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/EJB_EAR_Project.ear/Simple_EJB_Project.jar/}

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I am using Eclipse Indigo Service Release 2 Build id: 20120216-1857; which appears to be slightly different from the one in the course.
I have been able to translate the minor differences.

I believe that this is my problem:
Course:
Properties for Simple_EJB_Project
---> Java EE Module Dependencies
Click on "BankAccountJPA"
Shows only 1 warning on bottom of screen (no detail show in video)

My IDE:
Properties for simple_EJB_Project
(THERE IS NO "Java EE Module Dependencies")
---> Java Build Path
"Projects" Tab
Added "BankAccountJPA"


The Class "BankAccount" can now be imported in the source "Teller.java"

Shows 4 warning on bottom of screen

Description Resource Path Location Type
Classpath entry /BankAccountJPA will not be exported or published. Runtime ClassNotFoundExceptions may result. Simple_EJB_Project P/Simple_EJB_Project Classpath Dependency Validator Message
Classpath entry /Simple_EJB_ProjectClient will not be exported or published. Runtime ClassNotFoundExceptions may result. SimpleWebClient P/SimpleWebClient Classpath Dependency Validator Message
Classpath entry /Simple_EJB_ProjectClient will not be exported or published. Runtime ClassNotFoundExceptions may result. Simple_EJB_Project P/Simple_EJB_Project Classpath Dependency Validator Message
No connection specified for project. No database-specific validation will be performed. BankAccountJPA JPA Problem



I believe the problem is related to the warning messages above.

How to I correct the project so that the above warning are fixed and hopefully the starting of JBOSS?

Any direction would be appreciated.




I finally got it working.

Turns out that in the resource name tag the type had a space within the quotes. Once I fixed this, everything fell into place.
javascript:emoticon('');
9 years ago


I am trying to setup Tomcat to use JNDI for dataConnections.

I have Oracle working, but can not get SQL working. What I was looking for was differences between the Oracle and SQL connections.

I can't figure out why Oracle would work, but not SQL.

This is the error I am getting on the screen when trying to connect to a SQL Server:


Error Log:



When I list the environment Object the following is the list of objects I get.

I believe that all of them should be org.apache.tomcat.dbcp.dbcp.BasicDataSource

Each was declared the same except the fsSql uses a Microsoft Driver and jTDS using a jtds driver for MS-SQL.

I added "factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory" to the context file, but this did not help.

Any ideas why the SQL connections are being created differently?



Thanks in advance.


Long term, I want to use Birt, but since I had problems getting it to work, I started with a JSP Page to use the JDNI, When I get this working, I would then start fighting with Birt.

the JSP Page: