C#开发者求助：Java Web项目启动及GlassFish log4j部署错误排查

Hey there! As someone coming from C# diving into Java web apps, I totally get how this can feel overwhelming at first—let's walk through both getting your project running in the browser and fixing that GlassFish deployment error.

一、在浏览器中启动NetBeans里的Java Web项目 #

Since you've already built the project successfully, here's how to fire it up smoothly:

• Step 1: Confirm your server setup
  Right-click your project in NetBeans → Go to Properties → Navigate to the Run tab. Make sure you've selected your installed GlassFish server here (if you haven't added it yet, click Add Server to complete the setup wizard).
• Step 2: Launch the project directly
  Either right-click the project and select Run, or click the green "Run" button in the NetBeans toolbar. NetBeans will automatically deploy the project to GlassFish and usually open your browser to the default access URL—something like http://localhost:8080/YourProjectName.
• Manual access if auto-open fails
  Check the NetBeans output window for deployment logs. Look for a line like Context path: /JavaProjects—then just paste http://localhost:8080/JavaProjects into your browser to access the app directly.

二、GlassFish部署错误排查（log4j相关） #

The error you're seeing points to a missing or unresolvable log4j.properties file, plus a potential issue with the web archive not being expanded. Let's fix this step by step:

1. Verify the log4j configuration file exists #

First, check if your project's WEB-INF folder has a log4j.properties file. If it's missing:

• Create a new file named log4j.properties in WEB-INF, add basic log4j config (example below) or retrieve the correct file from your production server's source:

  log4j.rootLogger=INFO, stdout
  log4j.appender.stdout=org.apache.log4j.ConsoleAppender
  log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
  log4j.appender.stdout.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n
  

2. Ensure the file is packaged into the WAR #

After building, go to your project's dist folder, find the generated .war file, and extract it. Check if WEB-INF/log4j.properties is present inside. If not, adjust your NetBeans build settings: right-click project → Properties → Build → Packaging and make sure WEB-INF is included in the list of packaged files.

3. Fix the log4jConfigLocation path #

If the file exists but still throws the error, check your web.xml for this context parameter:

<context-param>
    <param-name>log4jConfigLocation</param-name>
    <param-value>/WEB-INF/log4j.properties</param-value>
</context-param>

Try changing the param-value to classpath:log4j.properties, then move the log4j.properties file to your project's src/main/resources folder (for Maven projects) or the src folder (for standard Java EE projects)—this ensures it's placed in the classpath where GlassFish can reliably find it.

4. Enable archive expansion in GlassFish #

The error mentions "web application archive not expanded?"—fix this by:

• When deploying via NetBeans, look for an option like Expand Archive in the deployment settings and check it.
• Or, open the GlassFish Admin Console (usually http://localhost:4848), navigate to your deployed application, set the Expand Archive property to true, then redeploy.

5. Clean up GlassFish cache #

Sometimes cached files cause unexpected deployment issues. Delete the following folders in your GlassFish installation and redeploy:

• glassfish/domains/domain1/generated
• glassfish/domains/domain1/applications/[YourProjectName]

内容的提问来源于stack exchange，提问作者user9786715