-
Notifications
You must be signed in to change notification settings - Fork 304
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
Allow disabling of iiop-service when MDBs present #164
Comments
Created internal issue |
smillidge
added a commit
to smillidge/Payara
that referenced
this issue
Mar 14, 2017
smillidge
added a commit
that referenced
this issue
Mar 18, 2017
lprimak
pushed a commit
to flowlogix/Payara
that referenced
this issue
Jul 5, 2017
lprimak
pushed a commit
to flowlogix/Payara
that referenced
this issue
Dec 15, 2017
…ivationConfigProperty-is-not-substituted-fs (pull request payara#164) PAYARA-2221 Fix recognition of resourceAdapter environment variables (payara#2189)
Pandrex247
added a commit
to Pandrex247/Payara
that referenced
this issue
Sep 10, 2020
FISH-396 _JAVA_OPTIONS prevents Payara Server determining Java version for JVM options
Cousjava
pushed a commit
to Cousjava/Payara
that referenced
this issue
Nov 2, 2020
FISH-396 _JAVA_OPTIONS prevents Payara Server determining Java version for JVM options
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Essentially the MessageBeanContainer fails to start unless iiop-service is configured. This seems like an undesirable dependency. We typically disable all uneeded elements when going to production but have found we can not disable iiop-service if we use MDBs.
This was initially reported in
https://java.net/jira/browse/GLASSFISH-21156
The text was updated successfully, but these errors were encountered: