Closed AlphaJuliettOmega closed 7 years ago
Does this warning mean I have to change any specific settings and is it possibly related to my issue?
[2016-11-28T09:38:00.864+0200] [Payara 4.1] [WARNING] [NCLS-JMX-00020] [javax.enterprise.system.jmx] [tid: _ThreadID=51 _ThreadName=Thread-14] [timeMillis: 1480318680864] [levelValue: 900] [[
All SSL cipher suites disabled for network-listener(s). Using SSL implementation specific defaults]]
Oh I have found a little more information but I don't know what it means, in Chrome when I first load the page, in Inspector I get this error in the console:
(index):136 GET https://guardian.adept.za.net:4848/testifbackendisready.html 500 (Internal Server Error)
displayCount @ (index):136
(anonymous function) @ VM312:1
thrown in the Javascript function
<script type="text/javascript">
if (document.getElementById('layout-doc') != null) {
window.location = 'https://guardian.adept.za.net:4848/login.jsf';
}
var feedbackZoneId = 'feedbackZone';
function start() {
displayCount(1,feedbackZoneId);
}
loaded(feedbackZoneId,start);
var pageLoaded = 0;
window.onload = function() {
pageLoaded = 1;
}
function loaded(i,f) {
if (document.getElementById && document.getElementById(i) != null) {
f();
}
else
if (!pageLoaded)
setTimeout('loaded(\''+i+'\','+f+')',100);
}
String.prototype.startsWith = function(s) {
if( this.indexOf(s) == 0 )
return true;
return false;
}
function displayCount(countdn,cd)
{
if (window.XMLHttpRequest)
{// code for IE7+, Firefox, Chrome, Opera, Safari
xmlhttp=new XMLHttpRequest();
}
else
{// code for IE6, IE5
xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");
}
xmlhttp.onreadystatechange=function()
{
if (xmlhttp.readyState==4 && ((xmlhttp.status==200)||(xmlhttp.status==202)))
{
var response = ""+xmlhttp.responseText;
if (response.startsWith(":::")){
fileLines=response.split("\n");
document.getElementById("STATUS").innerHTML= fileLines[0].substring(3,fileLines[0].length);
document.getElementById("WELCOME").innerHTML= "<b>"+ fileLines[1]+"</b>";
/// document.getElementById(cd).innerHTML = countdn+' times ';
setTimeout('displayCount('+(countdn+1)+',\''+cd+'\');',999);
}else {
location.reload(true);
}
}
}
xmlhttp.open("GET","/testifbackendisready.html",true);
xmlhttp.send();
}
</script>
Reloading the page then switches the page from displaying the 'loading Admin page screen'
Welcome to Payara Server 4.1.1.163 #badassfish (build 215).
Status indicator image. Status: The Admin Console is starting. Please wait.
If the browser does not refresh the page automatically please reload the page.
To:
the Error 500 page, with this message in the console:
GET https://guardian.adept.za.net:4848/favicon.ico 500 (Internal Server Error)
Once I have reloaded the page once, the Javascript/Loading Payara page doesn't display and only the Error 500 page is displayed with the Favicon error - The Ico Mimetype is set correctly in the default-web.xml file.
Hilarious, If you set this in Domain.xml:
<web-container>
<session-config>
<session-manager>
<store-properties></store-properties>
<manager-properties></manager-properties>
</session-manager>
<session-properties **session-timeout="0"**></session-properties>
</session-config>
</web-container>
The Admin Gui is completely inaccessible, a message should be thrown in log saying something like 'Session timed out' or 'Warning, Session timeout is too low' In some other version of Glassfish setting this to 0 makes the sessions indefinite, in Payara, it breaks it.
I just tried this with a completely fresh domain and couldn't reproduce the problem. Setting session-timeout="0"
works in both Firefox and Chrome.
Hmm, I'll check if there's any settings specific to the domain that I had the issue on, I will report back in the next 48 hours
Here is a diff between the domain that is working again and a fresh domain created with the Asadmin Create-domain command, the diff was done with the linux diff command: < Signifies the offending domain's Domain.xml > Signifies the fresh domain's Domain.xml
< <login-module-config module-class="com.sun.enterprise.admin.util.AdminLoginModule" control-flag="sufficient" name="adminSpecialLM">
---
> <login-module-config control-flag="sufficient" module-class="com.sun.enterprise.admin.util.AdminLoginModule" name="adminSpecialLM">
< <login-module-config module-class="com.sun.enterprise.security.auth.login.FileLoginModule" control-flag="sufficient" name="adminFileLM">
---
> <login-module-config control-flag="sufficient" module-class="com.sun.enterprise.security.auth.login.FileLoginModule" name="adminFileLM">
< <application context-root="" object-type="system-admin" name="__admingui" directory-deployed="true" location="${com.sun.aas.installRootURI}/lib/install/applications/__admingui">
---
> <application context-root="" object-type="system-admin" directory-deployed="true" name="__admingui" location="${com.sun.aas.installRootURI}/lib/install/applications/__admingui">
> <jdbc-resource pool-name="DerbyPool" object-type="system-all" jndi-name="jdbc/__default"></jdbc-resource>
< <connector-connection-pool resource-adapter-name="jmsra" max-pool-size="250" steady-pool-size="1" name="jms/__defaultConnectionFactory-Connection-Pool" connection-definition-name="javax.jms.ConnectionFactory" transaction-support="LocalTransaction"></connector-connection-pool>
---
> <connector-connection-pool max-pool-size="250" resource-adapter-name="jmsra" steady-pool-size="1" name="jms/__defaultConnectionFactory-Connection-Pool" connection-definition-name="javax.jms.ConnectionFactory"></connector-connection-pool>
< <jdbc-connection-pool ping="true" datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" name="guardian" res-type="javax.sql.DataSource">
---
> <jdbc-connection-pool driver-classname="" datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" name="guardian" res-type="javax.sql.DataSource">
> <resource-ref ref="jdbc/__default"></resource-ref>
< <node name="localhost-domain1" install-dir="${com.sun.aas.productRoot}" type="CONFIG" node-host="localhost"></node>
---
> <node name="localhost-guardian" install-dir="${com.sun.aas.productRoot}" type="CONFIG" node-host="localhost"></node>
< <asadmin-recorder-configuration enabled="true"></asadmin-recorder-configuration>
---
> <asadmin-recorder-configuration></asadmin-recorder-configuration>
< <jms-host port="${JMS_PROVIDER_PORT}" name="default_JMS_host" host="localhost"></jms-host>
---
> <jms-host port="${JMS_PROVIDER_PORT}" host="localhost" name="default_JMS_host"></jms-host>
< <jvm-options>-Declipselink.logging.level=FINE</jvm-options>
< <thread-pool name="admin-thread-pool" min-thread-pool-size="1" max-queue-size="256" max-thread-pool-size="15"></thread-pool>
---
> <thread-pool name="admin-thread-pool" min-thread-pool-size="1" max-thread-pool-size="15" max-queue-size="256"></thread-pool>
< <jms-host port="${JMS_PROVIDER_PORT}" host="localhost" name="default_JMS_host"></jms-host>
---
> <jms-host port="${JMS_PROVIDER_PORT}" name="default_JMS_host" host="localhost"></jms-host>
< <thread-pool name="admin-thread-pool" min-thread-pool-size="1" max-queue-size="256" max-thread-pool-size="15"></thread-pool>
---
> <thread-pool name="admin-thread-pool" min-thread-pool-size="1" max-thread-pool-size="15" max-queue-size="256"></thread-pool>
< <property name="administrative.domain.name" value="domain1"></property>
< <secure-admin special-admin-indicator="2ce9132b-ee96-4a2e-a37a-0ab5caee5fed" enabled="true">
< <secure-admin-principal dn="CN=localhost,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US"></secure-admin-principal>
< <secure-admin-principal dn="CN=localhost-instance,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US"></secure-admin-principal>
---
> <property name="administrative.domain.name" value="guardian"></property>
> <secure-admin special-admin-indicator="093375b4-6d78-4531-b9d5-20b41d49e445" enabled="true">
> <secure-admin-principal dn="CN=xxx.xx.net,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US"></secure-admin-principal>
> <secure-admin-principal dn="CN=xxx.xx.net-instance,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US"></secure-admin-principal>
< <property name="org.glassfish.ejb.container.application_unique_id" value="97014689824768000"></property>
---
> <property name="org.glassfish.ejb.container.application_unique_id" value="97014510860959744"></property>
I have not attempted to reproduce it again yet as it's a project i'm developing that needs to have a few features done by the end of the week, still i'll try get back on it asap.
The session timeout=0 command doesn't show in this diff as I have removed that parameter to get the domain up again.
Possible culprits:
Asadmin Recording
possibly a Secure Admin + 'timeout = 0' combo caused this?
Aside from some differences in JDBC configuration which would not be related, I can't see much difference between the two.
I already tried with and without secure admin enabled and tried again just now with the asadmin recorder enabled and disabled and can't get a failure.
It would be interesting to see whether you can consistently reproduce this or not. If you can, then I may need to try to more closely match your setup (OS, Java version etc).
Hi @AlphaJuliettOmega have you found that this is reliably reproducible?
I do apologize most sincerely but i've not been able to reproduce the issue, I believe it must have been a mis-deploy with a corrupt war or something to that effect, something I did to it maybe? Since I removed the session-timeout=0 and re-deployed, i've only changed the admin password and adjusted one JDBC Resource.
I added session-timeout=0 in again and could access the Payara front-end perfectly fine, i'm sorry I couldn't get more debug information when it happened. At least if it is really a bug, hopefully someone will come across this thread.
Specs of VM
Ubuntu 16.04.1 LTS
Jdk 1.8_102
Payara Server 4.1.1.163 #badassfish (build 215)
Hmmm, If I directly edit the domain.xml file and add session-timeout="0" now, then it gets removed when I redeploy, is there another place I should set it from properly to propagate to the domain.xml file? Is this normal behaviour? I tried editing the file, redeploying and opening it twice and the timeout gets removed each time.
Yes, if you go to the admin console, open up the correct config in the Tree on the left (server-config
is the one for the DAS) there is an entry called Web Container
which has session properties:
Hi @AlphaJuliettOmega if this is still not reproducible, shall we close this issue for now?
yes, close it - I do apologize for the delay
Description
I restarted my VM, without changing any Payara settings. The deployed application was running as expected before the restart, now subsequent reboots or start-domain/stop-domain calls have no effect.
When I try to access the Admin interface at localhost:4848 Only this line gets printed to the Server.log file:
and in the browser it displays:
at port 8181 I can still access the Payara 'welcome page' trying to access port 8080 the browser just indefinitely loads, to no effect.
When I try access the Admin page at 4848, that Warning about Context path gets printed, but only once. Subsequent refreshes/reloads of the page does not output any more to the log file.
Expected Outcome
I want to be able to access the Admin page again.
Current Outcome
Here is the full stack-trace including the command I ran to try start the domain.
Steps to reproduce
(simply for clarification of the issue)
1 -** Start the domain
2 -** Try to access admin page by accessing from browser
https://xxx.xxx.xxx.xxx:4848/ results in a non-descriptive Error 500: Internal server error
3 -** Cat or tail server.log
No error, only one warning about the 'context path'
Environment
I'm thinking there's a configuration option i'm missing but i'm still new to this type of software so any advice or recommendations are appreciated.
If any additional information is required, i'll supply it.
Thank you devs for the great Glassfish alternative!
edit: Would someone mind explaining how I would manually completely remove the .War I have deployed without having access to the Admin web-gui? I have full ssh access/ a terminal and can delete files but I don't want a malformed deployment.