Java Application Server 9 - TCP connections

I have installed Sun Java Application Server 9 and I see that the java process that is started has a lot (more than 30) of TCP connections with a local and a remote address that are both the hostname of the machine that run JAS.
Can someone tell me what are these connections and if there is a way to decrease the amount of these connections?
Thank you

Similar Messages

The Sun Java Application Server 8.1 could not start anymore

Very incredible I was working fine from may days with Stydio Creator 2
but yesterday I run the project and it does not work anymore, please can you suggest something:
The Sun Java Application Server 8.1 could not start.
from the Output console:
C:\Sun\Creator2\SunAppServer8\bin\asadmin.bat start-domain --domaindir C:\Sun\Creator2\SunAppServer8\domains\ creator
Failed to start server localhost:4848
Deployment error: Failed to start server localhost:4848. See the server log file for details.
Exception=Deployment error: Failed to start server localhost:4848. See the server log file for details.
Deployment error: Failed to start server localhost:4848. See the server log file for details.
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:198)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:75)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:234)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:242)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125)
Caused by: Failed to start server localhost:4848
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:152)
... 10 more
and in the log file:
[#|2006-02-24T11:49:51.296+0100|WARNING|sun-appserver-pe8.1_02|
javax.enterprise.system.core|_ThreadID=25;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: [C4073]: A JMS destination limit was reached.
Too many Subscribers/Receivers for Queue :
temporary_destination://queue/192.168.0.159/3376/2 user=admin, broker=127.0.0.1:27676(2403)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onTermination(JmsProviderLifecycle.java:476)
     at com.sun.enterprise.server.ApplicationServer.onTermination(ApplicationServer.java:454)
     at com.sun.enterprise.server.Shutdown.startShutdown(Shutdown.java:42)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeShutdownEventListener(AdminEventMulticaster.java:1445)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.handleShutdownEvent(AdminEventMulticaster.java:1434)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:443)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
     at com.sun.enterprise.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:90)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
     at sun.rmi.transport.Transport$1.run(Transport.java:153)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
     at java.lang.Thread.run(Thread.java:595)
thanks

I just had the same problem this morning. I believe the app server starts and if you browser directly to your app you'd get it, but the connection between the appserver and the IDE is somehow lost. An easier solution than completely reinstalling for me was to delete the .Creator folder in my home directory (C;|Documents and Setting\<username>\.Creator) and restart Creator

Sun Java Application Server 9 Start Up Woes

Hi,
I was asked to install the netbeans 5.5 IDE (which comes with Java Application Server 9 bundled with it) and basically learn how to develop using JMS. After installing everything and following the JavaEE tutorial, I began to set everything up. I get hung during the Sun Java Application Server 9 start up.
It attempts to bind to my host name. After a week of research as to the cause, i discovered that the problem is that the server gets my host name from DNS and uses that as its bind location. The software running at my place of business prevents me from making connections such as these with anything but localhost connections.
I descovered this when I read on here from another topic that i should try and start the server after disabling my network card. This method works in that the server starts up, no longer using my host name as the host but rather using localhost. Now this in no way fixes my problem.
I was wondering if there were any workarounds that would force the application server or netbeans or whatever to use localhost isntead of doing a host name lookup?
The error I got was a NoRouteToHostException, and when I disabled my network card that error went away, the error changed to UnknownHostException, but the server started up and I was then able to go to the admin page and deploy applications (but not run)
P.S. I was going to post the output of the server start ups, but the size is crazy long, if you have a way for me to remove the stack trace I would be glad to give it a try.
-SonOfThor
Message was edited by:
SonOfThor
Linux Fedora Core, by the way.

I switched to ActiveMQ and it works perfectly.
The issue had to do with Netbeans, no matter how many config files i changed, always used my computername.host.com:8686 instead of localhost:8686.
ActiveMQ starts and runs beautifully because it binds to localhost:8686.
I dont know what the problem was, Ive read lots of solutions saying its firewall or a firewall like process. I'm running bare bones Linux Fedora Core with no extra programs. I insured my firewall was turned off before even posting this. I spoke with my IT guys and they said that the firewall thats set up here at work does not block port binds.
My conclusion: IDEs are more of a pain then they want you to believe, im going back to terminal commands.

Oracle 9.0.1 and Sun Java Application Server problem

Hello
I am gonna configure Oracle's (9.0.1) thin JDBC driver (only for JDK 1.3) on Sun Java Application Server 8
I copied the class12.zip to domain1/lib/ext. I add the usr name and passwd in domain1/config/domain.xml.
it looks like
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="oracle.jdbc.pool.OracleDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="OraclePool" pool-resize-quantity="2" res-type="javax.sql.DataSource" steady-pool-size="8">
<property name="url" value="jdbc:oracle:thin:@localhost:1521:ora9i"/>
<property name="Password" value="tiger"/>
<property name="User" value="scott"/>
It doesn't work though. Anybody know the problem?
Thanks a lot

You should use the oracle 9.0.3 ojdbc14.jar or a later version, not classes12.zip.
The config looks like for me:
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="oracle.jdbc.pool.OracleDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" max-pool-size="32" max-wait-time-in-millis="60000" name="my-oracle-pool" pool-resize-quantity="2" res-type="javax.sql.DataSource" steady-pool-size="16">
<property name="URL" value="jdbc:oracle:thin:@localhost:1521:mydb"/>
<property name="user" value="user"/>
<property name="password" value="mypass"/>
</jdbc-connection-pool>
You will also need to boot the server after adding the jar files to lib/ext

Steps to execute servlets on Sun Java Application Server

Hi
Could u tell me how to deploy servlets files and how to execute
In specs. the ask us to start cloudscape database server
In my Sun Java Application Server installations, i am not find even a single name as cloudscape
Please anyone guide me get the servelts to execute
thank u

What specs do you refer to?
Sun Java System Application Server does not include Cloudscape, nor is it required. SJSAS does include a development copy of Pointbase DB Server.
To deploy your servlet application you will need to package them into a WAR file (Web Archive). Then you can either use asadmin CLI or the admin gui to deploy the WAR. The steps are included here: http://docs.sun.com/source/816-7150-10/dwdeploy.html
Now I'm going to assume you application uses Cloudscape. To get that piece running you will need to download and install Cloudscape. You will also need the JDBC drivers for Cloudscape. Copy the JDBC driver jar file to either the <serverinstancedir>/lib directory or modify the JVM settings to include that jar file. Restart the Application Server. You will also need to add a JDBC Resource & Connection Pool. In the admin, create a new connection pool (probably called Cloudscape). Use the appropriate settings for classname and add any additional properties that are necessary (Usually URL, User, Password). Now create a JDBC Resource using that Connection Pool. Make sure the JNDI name matches what your application expects.
Now just access the URL for the application
-Jeff

How to check if a user session is active in Java application server

Hi Experts,
We have a online scenario with a third party system by which a portal user will launch the third party application in a new window from portal. The SSO will work at the third party web application with the dynamic key that is generated by calling a webservice for that user. Now, as the user works on the launched screen, they will have to check whether the user (logged in portal) session is still active. ie., they will be periodically calling a service hosted by SAP java application server to find out whether the corresponding user who launched the session is still logged in or logged out.
So, my question is, how can i find out programatically whether a user/user's session is still logged in/active in SAP Netweaver Java AS? We are in version 7.3.
Kindly help me in this regard.
Regards
Vijay.K

Hi Vijay,
Could you check below links
Tracing Single User Sessions - Administration - SAP Library
Display and Manage User Sessions (SAP Library - Tools for Monitoring the System)
Hope this helps.
Regards,
Deepak Kori

How to run ear file in java application server

i want how to run .ear file in java application server
1. i m created ear file
2. i m created jar file (bean,home,remote)
3.i m created war file(in the form of jsp)
but till now i couldnt run ear file
how to run
please hel me

You must create :
1.Jar file
2.War file
And then put them into an ear file
Exemple : myapp.ear contains
myappEJB.jar
myappWEB.war
META-INF/application.xml
and application.xml looks like this :
<application xmlns="http://java.sun.com/xml/ns/j2ee" version="1.4"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com /xml/ns/j2ee
                        http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
    <display-name>myapp</display-name>
    <description>Demo application</description>
    <module>
        <ejb>myappEJB.jar</ejb>
    </module>
    <module>
      <web>
         <web-uri>myappWAR.war</web-uri>
         <context-root>/myapp</context-root>
      </web>
    </module>
</application>Good luck

Issue with Java Application with ECC - Connection Issue

Hi
We have developed one java application to connect to SAP to extract some data. We are using java API (sapjco) to connect to the SAP. Now we are facing one issue u2013 for the ECC while connecting through the java application we are getting u201CUserid or Password incorrect erroru201D, but with the same userid and password we are able to log through the SAP GUI. If we changed the password with all CAPS (Capital Letters) and without numeric values, its working fine in java application (Means its connecting to ECC)
We are facing this issue only in ECC; the same application is running successfully in SAP 4.7 etc. without changing password.
Please Help!

I would draw the conclusion that you have to provide the paaword in upper case. There is a standar java method there that does this for you. Just do it before sending the password.
Regards,
Benny

Java - SQL Server 2000 Connectivity

hi all. i m looking for help in Java - SQL Server 2000 Connectivity.i worked on Java- Oracle & Java - MS Access format.now i m looking to work on Java - SQL Server 2000. I m using JBuilder 2005. can any1 help me how to make any change(configuration) in my SQL Server.thanx in advance.

http://www.jguru.com/forums/JBuilder is hopeless. ihvn;t get good replies from them.i downloaded the JDBC driver from microsoft and added the JAR files (3 files) and tried the following code:
import java.sql.*;
* Microsoft SQL Server JDBC test program
public class Test {
public Test() throws Exception {
// Get connection
DriverManager.registerDriver(new com.microsoft.jdbc.sqlserver.SQLServerDriver());
//Connection connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://<Host>:1433",<"UID>","<PWD>");
// Connection connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://GMC01:1433;DatabaseName=MoonDB");
Connection connection = DriverManager.getConnection("jdbc:microsoft:sqlserver://Moon:1433;DatabaseName=MoonDB");
if (connection != null) {
System.out.println();
System.out.println("Successfully connected");
System.out.println();
// Meta data
DatabaseMetaData meta = connection.getMetaData();
System.out.println("\nDriver Information");
System.out.println("Driver Name: "
+ meta.getDriverName());
System.out.println("Driver Version: "
+ meta.getDriverVersion());
System.out.println("\nDatabase Information ");
System.out.println("Database Name: "
+ meta.getDatabaseProductName());
System.out.println("Database Version: "+
meta.getDatabaseProductVersion());
} // Test
public static void main (String args[]) throws Exception {
Test test = new Test();
it run without any error and then showed fatal exception as below:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
     at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
     at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:193)
     at Test.<init>(Test.java:11)
     at Test.main(Test.java:31)
Exception in thread "main"
where's the problem?can any1 try to solve this plz.

Sun Java Application Server - Domain and Node agent stop automatically

Hi,
We have installed Sun Java Application server 8.1 in a local zone on Solaris 10. The installation was successful.
A default domain (domain1) was created. We have deployed a sample application too.
The problem is that the domain and node-agent stop automatically. And need to be restarted from asadmin start-domain command.
Not sure why this problem is occurring. One solution given in Sun Java System AS 8.1 EE Troubleshooting Guide was to add these 2 lines in the /etc/inittab file to restart the domain and node-agent whenever the system re-boots.
das:3:respawn:/opt/SUNWappserver/bin/asadmin start-domain user admin passwordfile /opt/SUNWappserver/password.txt domain1
das:3:respawn:/opt/SUNWappserver/bin/asadmin start-node-agent user admin passwordfile /opt/SUNWappserver/password.txt node-agent-name
Pls help me if I can change this inittab file from the local zone and if changing this file has any implications on the other zones on Solaris 10.
Else is there any other way to resolve this problem?
Any help would be highly appreciated.
Thankyou.

One thing not clear from the post was,
* when it is going down automatically.
* Are you facing the same problem even after starting through the asadmin
* If so, Post the server.log from "domains/logs" during the starup.
If you want to bring it up with system reboot, You need to have a startup script for that in init.d and have the links to rc2/3.d.

Sun Java Application Server 8.1 Upgrade Solaris 9 to Solaris 10

I have Sun Java Application Server 8.1 (version 8.1_02 (build b06-fcs) ) and HA which are currently installed on Solaris 9 box (Sparc).
Now, I plan to upgrade Solaris 9 to Solaris 10. What should I need to do before and after migration?
Thanks.

Before I start, disclaimer -- I have no knowledge of Hibernate and the following comments are based on the stack trace you have included.
I think your permissions might be set all right but you might have an error in the hibernate query. It looks like hibernate uses antlr to parse the queries. While parsing the query, antlr is encountering an exceptional condition and is trying to exit the VM (by calling System.exit()). Obviously, the hibernate code does not have that permission and therefore the exception is logged.
My guess is if you fix the query such that hibernate/antlr can parse it, you will not run into this error.
Hope this helps,

User Role problems in Sun Java Application Server Platform Edition 8

I am having two problems setting up user roles in Sun Java Application Server Platform Edition 8. At first, I thought that it was a problem with the higher level features that I was using, so I created a very simple example using the simplest authentication I can use, but the problem still occurs. I am using the file realm and configuring the users in the App Server Admin Console. I create 2 users in different roles. One user should have access, the other should not.
1) The first problem is that both users can access the page
2) The second problem is that the isUserInRole() method returns false for both users with the role that it should be authenticating against.
Here is a sample of my code:
Users Configured in Console:
username password roles
user1 ********** admin
user2 ********** noaccess
web.xml
     <security-role>
          <role-name>admin</role-name>
     </security-role>
     <security-constraint>
          <web-resource-collection>
               <web-resource-name>My Protected Area</web-resource-name>
               <url-pattern>/*</url-pattern>
          </web-resource-collection>
          <auth-constraint>
               <role-name>admin</role-name>
          </auth-constraint>
          <user-data-constraint>
               <transport-guarantee>NONE</transport-guarantee>
          </user-data-constraint>
     </security-constraint>
     <login-config>
          <auth-method>BASIC</auth-method>
          <realm-name>file</realm-name>
     </login-config>
     <servlet>
          <servlet-name>
               TestServlet
          </servlet-name>
          <servlet-class>
               mypackage.TestServlet
          </servlet-class>
          <security-role-ref>
               <role-name>admin</role-name>
               <role-link>admin</role-link>
          </security-role-ref>
     </servlet>
     <servlet-mapping>
          <servlet-name>
               TestServlet
          </servlet-name>
          <url-pattern>
               /TestServlet
          </url-pattern>
     </servlet-mapping>
TestServlet.java:
          out.println("admin role: " + request.isUserInRole("admin") + "<BR/>");
Thanks before hand for any responses.
- Brian

Hi Jeanfrancois,
Your suggestion has lead me to find my problem. There were actually three problems.
1) First, you suggestion to reorder my xml file did not cause any errors to occur. I got suspicious that my web.xml file was wrong. I looked at some sample web-xml files and found that I was missing the header as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' 'http://java.sun.com/dtd/web-app_2_3.dtd'>
2) When I added this information, the deploy feature failed stating the my web.xml file was out of order. I fixed the ordering. It now deployed, but the security still wasn't working.
3) I then added the sun-web.xml file. This file was missing before hand as I thought it was unnessary. However, this file added the essential mapping from a role to a group. After adding this, it now started to work.
Thanks so much for you time and effort. You really did help me.
- Brian Blank

Deployment failed. Building failed using sun java application server

Hi
am using netbean 6 ,glassfish v2 and sun java application server 9
When am try to run my jsp file am getting Deployment error report with further error given below.
Deployment error:
The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
See the server log for details.
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:163)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor256.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
Caused by: org.netbeans.modules.j2ee.deployment.impl.ServerException: The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance._start(ServerInstance.java:1270)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.startTarget(ServerInstance.java:1224)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.startTarget(ServerInstance.java:1035)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.start(ServerInstance.java:912)
at org.netbeans.modules.j2ee.deployment.impl.TargetServer.startTargets(TargetServer.java:417)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:140)
... 16 more
BUILD FAILED (total time: 44 seconds)

Hi,
I've found that if you remove the j2ee-application element related to the enterprise app you are trying to deploy from Sun\AppServer\domains\domain1\config\domain.xml, and also remove your enterprise j2ee-app directory from Sun\AppServer\domains\domain1\applications\j2ee-apps\, it works.
This is not a permanent solution. I get the same error again, when I try to redeploy the application for the third time. Hope someone can help soon!
Thanks.

Work Manager API in Sun Java Application Server 8.1

I am trying to build a parallel application using Work Manager api (javax.resource.spi.work.WorkManager;)
I studied the Websphere implementation of WorkManager there you need to make JNDI lookup for work manager and then use it to submit the work.
My question is if i make class which will implement the javax.resource.spi.work.WorkManager; interface and use that class to submit the work and execute it in parallel then will that class will handle the resource management and all j2ee services
Do we have separate implementation of work manager API for Sun Java Application Server 8.1 (any jar like asynch.jar in IBM websphere) so that we will just create a work manager using admin console and make JNDI lookup and use it
Please guide me

Before I start, disclaimer -- I have no knowledge of Hibernate and the following comments are based on the stack trace you have included.
I think your permissions might be set all right but you might have an error in the hibernate query. It looks like hibernate uses antlr to parse the queries. While parsing the query, antlr is encountering an exceptional condition and is trying to exit the VM (by calling System.exit()). Obviously, the hibernate code does not have that permission and therefore the exception is logged.
My guess is if you fix the query such that hibernate/antlr can parse it, you will not run into this error.
Hope this helps,

Java Application Server 8.1 and HTTP TRACE

I need to disable the HTTP TRACE method on our servers with Sun Java Application Server 8.1 UR2. The following URL specifies how to disable on previous versions, but does not seem relavent to newer versions.
http://sunsolve.sun.com/search/document.do?assetkey=1-26-576 70-1
Any ideas?

Please post Application Server-specific questions to the App Server forum at:
http://swforum.sun.com/jive/forum.jspa?forumID=114
Thanks,
Chris

Java Application Server 9 - TCP connections

Similar Messages

Maybe you are looking for