FAQs - Revision history

G.dimaio at 14:53, 14 April 2017

2017-04-14T14:53:31Z

D.barra at 16:32, 22 May 2014

2014-05-22T16:32:09Z

Anonymous at 09:04, 11 February 2012

2012-02-11T09:04:06Z

Anonymous at 08:53, 11 February 2012

2012-02-11T08:53:10Z

N.decarlo at 19:53, 9 February 2012

2012-02-09T19:53:52Z

N.decarlo at 19:04, 9 February 2012

2012-02-09T19:04:51Z

G.iannello at 10:07, 31 January 2012

2012-01-31T10:07:28Z

Anonymous at 09:40, 26 January 2012

2012-01-26T09:40:41Z

Anonymous at 09:39, 26 January 2012

2012-01-26T09:39:58Z

C.ortenzi at 19:13, 24 January 2012

2012-01-24T19:13:25Z

@@ Line 3: / Line 3: @@
 {{GVESB}} is 100% compatible with the ''Java Virtual Machine'' provided by Oracle.
 We recommend to use the JDK 1.6 version provided by Oracle, although we are aware of {{GVESB}} users that have found no malfunctionings with OpenJDK.
 '''I'm unable to start {{GVESB}} because there are some ports already in use on the server. What can I do?'''
@@ Line 22: / Line 23: @@
 '''I can't access the administration console. What can I do?'''
-Check, in the log file ''server.log'', the correct ''deployment'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''<nowiki>http://SERVER-HOSTNAME:8080/web-console/</nowiki>'' in the J2EE Domains if the file ''gvconsole-3.2.0.war'' is present.
+Check, in the log file ''server.log'', the correct ''deployment'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''<nowiki>http://SERVER-HOSTNAME:8080/web-console/</nowiki>'' in the J2EE Domains if the file ''gvconsole.war'' is present.

@@ Line 1: / Line 1: @@
-'''May I use the open source version of JDK, OpenJDK, instead of the one provided by Sun?'''
+'''May I use the open source version of JDK, OpenJDK, instead of the one provided by Oracle?'''
-{{GVESB}} is 100% compatible with the ''Java Virtual Machine'' of Sun Microsystems.
+{{GVESB}} is 100% compatible with the ''Java Virtual Machine'' provided by Oracle.
-We recommend to use the JDK 1.6 version provided by Sun Microsystems, although we are aware of {{GVESB}} users that have found no malfunctionings with OpenJDK.
+We recommend to use the JDK 1.6 version provided by Oracle, although we are aware of {{GVESB}} users that have found no malfunctionings with OpenJDK.
 '''I'm unable to start {{GVESB}} because there are some ports already in use on the server. What can I do?'''
-The startup script contains the parameter "-Djboss.service.binding.set=ports-default" defined in JB_OPTS variable.<br/>
+The startup script contains the parameter "-Djboss.service.binding.set=ports-default" defined in the variable JB_OPTS.<br/>
 You can modify "ports-default" choosing another portset with one in the following list:
@@ Line 22: / Line 22: @@
 '''I can't access the administration console. What can I do?'''
-Check, in the log file ''server.log'', the correct ''deploy'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''<nowiki>http://SERVER-HOSTNAME:8080/web-console/</nowiki>'' in J2EE Domains if file ''gvconsole-3.2.0.war'' is present.
+Check, in the log file ''server.log'', the correct ''deployment'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''<nowiki>http://SERVER-HOSTNAME:8080/web-console/</nowiki>'' in the J2EE Domains if the file ''gvconsole-3.2.0.war'' is present.
@@ Line 39: / Line 39: @@
-User can eventually attach the log files presents in the directories ''$GV_HOME/log'' and ''$GV_SERVER/log''. See also the forum available at http://www.greenvulcano.com/forum/ where it is possible to find any information of a technical nature as well as requesting help from the ''community'' creating a ''thread/post'' with the problem description.
+Users are encouraged to attach the log files present in the directories ''$GV_HOME/log'' and ''$GV_SERVER/log''. See also the forum available at http://www.greenvulcano.com/forum/ where it is possible to find any information of a technical nature as well as requesting help from the ''community'' creating a ''thread/post'' with the problem description.

← Older revision		Revision as of 09:04, 11 February 2012
Line 40:		Line 40:

	User can eventually attach the log files presents in the directories ''$GV_HOME/log'' and ''$GV_SERVER/log''. See also the forum available at http://www.greenvulcano.com/forum/ where it is possible to find any information of a technical nature as well as requesting help from the ''community'' creating a ''thread/post'' with the problem description.		User can eventually attach the log files presents in the directories ''$GV_HOME/log'' and ''$GV_SERVER/log''. See also the forum available at http://www.greenvulcano.com/forum/ where it is possible to find any information of a technical nature as well as requesting help from the ''community'' creating a ''thread/post'' with the problem description.
−	~~[[To do]]~~

← Older revision		Revision as of 08:53, 11 February 2012
Line 40:		Line 40:

	User can eventually attach the log files presents in the directories ''$GV_HOME/log'' and ''$GV_SERVER/log''. See also the forum available at http://www.greenvulcano.com/forum/ where it is possible to find any information of a technical nature as well as requesting help from the ''community'' creating a ''thread/post'' with the problem description.		User can eventually attach the log files presents in the directories ''$GV_HOME/log'' and ''$GV_SERVER/log''. See also the forum available at http://www.greenvulcano.com/forum/ where it is possible to find any information of a technical nature as well as requesting help from the ''community'' creating a ''thread/post'' with the problem description.
		+	[[To do]]

← Older revision		Revision as of 19:53, 9 February 2012
Line 4:		Line 4:
	We recommend to use the JDK 1.6 version provided by Sun Microsystems, although we are aware of {{GVESB}} users that have found no malfunctionings with OpenJDK.		We recommend to use the JDK 1.6 version provided by Sun Microsystems, although we are aware of {{GVESB}} users that have found no malfunctionings with OpenJDK.

		+	'''I'm unable to start {{GVESB}} because there are some ports already in use on the server. What can I do?'''
		+
		+	The startup script contains the parameter "-Djboss.service.binding.set=ports-default" defined in JB_OPTS variable.<br/>
		+	You can modify "ports-default" choosing another portset with one in the following list:
		+
		+	* ports-01; The ports-01 bindings are obtained by taking the base bindings and adding 100 to each port value
		+	* ports-02; The ports-02 bindings are obtained by taking the base bindings and adding 200 to each port value
		+	* ports-03; The ports-03 bindings are obtained by taking the base bindings and adding 300 to each port value
		+	<br/>
		+	Eg. -Djboss.service.binding.set=ports-01

	'''How can I access the {{GVESB}} administration console?'''		'''How can I access the {{GVESB}} administration console?'''

← Older revision		Revision as of 19:04, 9 February 2012
Line 12:		Line 12:
	'''I can't access the administration console. What can I do?'''		'''I can't access the administration console. What can I do?'''

−	Check, in the log file ''server.log'', the correct ''deploy'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''<nowiki>http://SERVER-HOSTNAME:8080/web-console/</nowiki>'' in J2EE Domains if file ''gvconsole-3.1.0.war'' is present.	+	Check, in the log file ''server.log'', the correct ''deploy'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''<nowiki>http://SERVER-HOSTNAME:8080/web-console/</nowiki>'' in J2EE Domains if file ''gvconsole-3.2.0.war'' is present.

← Older revision		Revision as of 10:07, 31 January 2012
Line 2:		Line 2:

	{{GVESB}} is 100% compatible with the ''Java Virtual Machine'' of Sun Microsystems.		{{GVESB}} is 100% compatible with the ''Java Virtual Machine'' of Sun Microsystems.
−	~~It is advisable~~ to use the JDK 1.6 version provided by Sun Microsystems, although we are aware of {{GVESB}} users that have found no ~~malfunction~~ with OpenJDK.	+	We recommend to use the JDK 1.6 version provided by Sun Microsystems, although we are aware of {{GVESB}} users that have found no malfunctionings with OpenJDK.

@@ Line 27: / Line 27: @@
 * Operating System
 * Short description of the hardware architecture
 User can eventually attach the log files presents in the directories ''$GV_HOME/log'' and ''$GV_SERVER/log''. See also the forum available at http://www.greenvulcano.com/forum/ where it is possible to find any information of a technical nature as well as requesting help from the ''community'' creating a ''thread/post'' with the problem description.

@@ Line 7: / Line 7: @@
 '''How can I access the {{GVESB}} administration console?'''
-The console is available at ''http://SERVER-HOSTNAME:8080/gvconsole'', where "SERVER-HOSTNAME" should be replaced by the address of the server where {{GVESB}} was installed.
+The console is available at ''<nowiki>http://SERVER-HOSTNAME:8080/gvconsole</nowiki>'', where "SERVER-HOSTNAME" should be replaced by the address of the server where {{GVESB}} was installed.
 '''I can't access the administration console. What can I do?'''
-Check, in the log file ''server.log'', the correct ''deploy'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''http://SERVER-HOSTNAME:8080/web-console/'' in J2EE Domains if file ''gvconsole-3.1.0.war'' is present.
+Check, in the log file ''server.log'', the correct ''deploy'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''<nowiki>http://SERVER-HOSTNAME:8080/web-console/</nowiki>'' in J2EE Domains if file ''gvconsole-3.1.0.war'' is present.