Labels

Tuesday, January 20, 2015

JBoss Application Server default ports

These are the default ports in JBoss Application Server
TCP 1090 – RMI/JRMP socket for connecting to the JMX MBeanServer
TCP 1091 – RMI server socket
TCP 1099 – JNDI Service
TCP 1098 – RMI Port for JNDI Service
TCP 4446 – JBoss Remoting Connector
TCP 4712 – JBossTS Service
TCP 4713 – JBossTS Service
TCP 5445 – HornetQ JMS Service
TCP 5455 – HornetQ Netty port
TCP 5500 – JBoss Remoting
TCP 5501 – JBoss Remoting ssl
TCP 8009 – Web server AjpConnector
TCP 8080 – Web server HTTP Connector
TCP 8083 – Web services
To change the port, we need to edit the bindings-jboss-beans.xml present at the following location.
jboss-as\server\myserver1\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml
e.g. if we want to change the JNDI port, we need to update the port property for the Naming Service

?
1
2
3
4
5
6
7
<!-- Naming Service -->
           <bean class="org.jboss.services.binding.ServiceBindingMetadata">
              <property name="serviceName">jboss:service=Naming</property>
              <property name="bindingName">Port</property>
              <property name="port">1999</property>
              <property name="description">The listening socket for the Naming service</property>
           </bean>

HOW TO CONFIGURE SSL BETWEEN APACHE and WEBLOGIC

Friday, January 9, 2015

java.sql.SQLException: Io exception: The Network Adapter could not establish the connection

Caused by: java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
 at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)
 at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:420)
 at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:165)
 at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
 at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:297)
 at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:221)
 at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:157)
 at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:94)
 at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:75)
 at com.sun.gjc.spi.CPManagedConnectionFactory.createManagedConnection(CPManagedConnectionFactory.java:133)
 ... 99 more

Monday, December 22, 2014

Create the listener for Glassfish server

netstat -an |grep -i "LISTEN"

Down load the connecter


Complie the connecter

Create the listener of the ajp 8009

he problem is from "-Dcom.sun.enterprise.web.connector.enableJK=${AJP_PORT}" seems not the right way anymore, its in Glassfish 2.1 but in Glassfish 3.1.2 you need to :
1.    From your cluster config --> Network Config --> Network Listeners (click on this)
2.    Create "New..." listener.
3.    Fill new listener info :
·         Name it like : jk-connector , port with: ${AJP_PORT} , check on "JK Listener" to enable it , forprotocol select "Use an existing protocol" then select "http-listener-1" protocol , for Thread Pool select "http-thread-pool" (not sure about this till now, but used same pool of another listeners).

Then start instances, if started successfully try check their ports is listening using "netstat -an | grep " eg: "netstat -an | grep 9090" and so.