Class name is wrong or classpath is not set for : com.mysql.jdbc.jdbc2.optional.MysqlDataSource

http://stackoverflow.com/questions/17651423/unable-to-connect-to-jdbc-connection-pool-from-glassfish

https://code.google.com/p/groland3/downloads/detail?name=mysql-connector-java-5.0.5-bin.jar&can=2&q=

Hay que poner el driver aca
 mysql-connector-java-5.x.x-bin.jar copy to E:\Projects\glassfish3.1.1\glassfish\lib

TCP and UDP Ports for the vSphere Client

ESXi hosts and other network components are accessed using predetermined TCP and UDP ports. If you manage network components from outside a firewall, you might be required to reconfigure the firewall to allow access on the appropriate ports.

The table lists TCP and UDP ports, and the purpose and the type of each. Ports that are open by default at installation time are indicated by (Default).

TCP and UDP Ports

Port	Purpose	Traffic Type
443 (Default)	HTTPS access vSphere Client access to vCenter Server vSphere Client access to ESXi hosts vSphere Client access to vSphere Update Manager	Incoming TCP
902 (Default)	vSphere Client access to virtual machine consoles	Incoming and outgoing TCP, outgoing UDP
903	Remote console traffic generated by user access to virtual machines on a specific host. vSphere Client access to virtual machine consoles MKS transactions (xinetd/vmware-authd-mks)	Incoming TCP

Comando MTR

Mtr (My Trace Route) [MTR98] es una herramienta de diagnóstico de red utilizada en sistemas GNU/Linux, que combina las funcionalidades básicas de las aplicaciones traceroute y ping.Puede ejecutarse tanto desde un terminal o a través de una interfaz gráfica. 

Las opciones más comunes de ejecución de mtr son las siguientes:

• -c count: envía un número determinado de pings especificados por la variable count.

• -g: lanza mtr a través de una interfaz gráfica de usuario basada en GTK+.

• -i seconds: número de segundos transcurridos entre el intervalo de envío de dos pings consecutivos a un mismo salto. El número de segundos se define mediante la variable seconds.

• -n: no resuelve los nombre de dominio.

• -r: muestra por pantalla un informe de la traza realizada después del envío de 10 pings seguidos a cada uno de los nodos intermedios existentes entre el origen y el destino. El número de pings enviados se puede modificar utilizando para ellos la opción -c count.

• HOSTNAME: máquina destino de la traza.

Ejemplo:

mtr 192.168.1.2

Persistence.xml y servidor mysql

Once GlassFish is installed, make sure it can access MySQL Connector/J. To do this, copy the MySQL Connector/J jar file to the domain-dir/lib directory. For example, copy mysql-connector-java-5.1.30-bin.jar toC:\glassfish-install-path\domains\domain-name\lib. Restart the GlassFish Application Server. For more information, see “Integrating the JDBC Driver” in GlassFish Server Open Source Edition Administration Guide, available at GlassFish Server Documentation.

You are now ready to create JDBC Connection Pools and JDBC Resources.

Creating a Connection Pool

1. In the GlassFish Administration Console, using the navigation tree navigate to Resources, JDBC, Connection Pools.
2. In the JDBC Connection Pools frame click New. You will enter a two step wizard.
3. In the Name field under General Settings enter the name for the connection pool, for example enter MySQLConnPool.
4. In the Resource Type field, select javax.sql.DataSource from the drop-down listbox.
5. In the Database Vendor field, select MySQL from the drop-down listbox. Click Next to go to the next page of the wizard.
6. You can accept the default settings for General Settings, Pool Settings and Transactions for this example. Scroll down to Additional Properties.
7. In Additional Properties you will need to ensure the following properties are set:
   • ServerName - The server to connect to. For local testing this will be localhost.
   • User - The user name with which to connect to MySQL.
   • Password - The corresponding password for the user.
   • DatabaseName - The database to connect to, for example the sample MySQL database World.
8. Click Finish to exit the wizard. You will be taken to the JDBC Connection Pools page where all current connection pools, including the one you just created, will be displayed.
9. In the JDBC Connection Pools frame click on the connection pool you just created. Here, you can review and edit information about the connection pool. Because Connector/J does not support optimized validation queries, go to the Advanced tab, and under Connection Validation, configure the following settings:
   • Connection Validation - select Required.
   • Validation Method - select table from the drop-down menu.
   • Table Name - enter DUAL.
10. To test your connection pool click the Ping button at the top of the frame. A message will be displayed confirming correct operation or otherwise. If an error message is received recheck the previous steps, and ensure that MySQL Connector/J has been correctly copied into the previously specified location.

Now that you have created a connection pool you will also need to create a JDBC Resource (data source) for use by your application.

Creating a JDBC Resource

Your Java application will usually reference a data source object to establish a connection with the database. This needs to be created first using the following procedure.

• Using the navigation tree in the GlassFish Administration Console, navigate to Resources, JDBC, JDBC Resources. A list of resources will be displayed in the JDBC Resources frame.
• Click New. The New JDBC Resource frame will be displayed.
• In the JNDI Name field, enter the JNDI name that will be used to access this resource, for example enter jdbc/MySQLDataSource.
• In the Pool Name field, select a connection pool you want this resource to use from the drop-down listbox.
• Optionally, you can enter a description into the Description field.
• Additional properties can be added if required.
• Click OK to create the new JDBC resource. The JDBC Resources frame will list all available JDBC Resources.