Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fuseki WAR file fails to start #2448

Closed
afs opened this issue May 5, 2024 · 1 comment · Fixed by #2449
Closed

Fuseki WAR file fails to start #2448

afs opened this issue May 5, 2024 · 1 comment · Fixed by #2449
Labels

Comments

@afs
Copy link
Member

afs commented May 5, 2024

Version

5.0.0

What happened?

The Fuseki webapp fails to start.

In the application/localhost log:
"There is already a Shiro environment associated with the current ServletContext. "

05-May-2024 16:37:20.159 INFO [main] org.apache.catalina.core.ApplicationContext.log Initializing Shiro environment
05-May-2024 16:37:20.386 SEVERE [main] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [org.apache.shiro.ee.listeners.EnvironmentLoaderListener]
	java.lang.IllegalStateException: There is already a Shiro environment associated with the current ServletContext.  Check if you have multiple EnvironmentLoader* definitions in your web.xml!
		at org.apache.shiro.web.env.EnvironmentLoader.initEnvironment(EnvironmentLoader.java:132)

and in the catalina log:

05-May-2024 16:37:20.386 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
05-May-2024 16:37:20.387 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/fuseki] startup failed due to previous errors

Relevant output and stacktrace

No response

Are you interested in making a pull request?

Yes

@afs afs added the bug label May 5, 2024
@afs
Copy link
Member Author

afs commented May 5, 2024

It seems that automatic initialization now (5.0.0) causes the error. Fuseki web.xml has an explicitly configured Shiro listener to find the shiro.ini file from the FUSEKI_BASE area.

Workaround:

Add to web.xml:

  <context-param>
    <param-name>org.apache.shiro.ee.disabled</param-name>
    <param-value>true</param-value>
  </context-param>

@afs afs changed the title Fuseki WAR file Fuseki WAR packing fails to start May 5, 2024
@afs afs changed the title Fuseki WAR packing fails to start Fuseki WAR file fails to start May 5, 2024
afs added a commit to afs/jena that referenced this issue May 5, 2024
@afs afs closed this as completed in #2449 May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant