Hi,

I'm working on a grails 2.2.1 project running on glassfish 3.1.2.2,
using a jndi pooled datasource connected to a postgres 9.2 database.
When I deploy for the first time the application, I have no issues,
everything works fine.

But, everytime I undeploy (or redeploy) my application, my connection
pool stops working.
If I try to ping using glassfish admin console, I get this error :

Avertissement: RAR8054: Exception while creating an unpooled [test] connection for pool [ sample ], Connection could not be allocated because: No suitable driver found for jdbc:postgresql://localhost:5432/sample?loginTimeout=0&socketTimeout=0&prepareThreshold=5&unknownLength=2147483647&loglevel=0&tcpkeepalive=false
Grave: RestResponse.getResponse() donne FAILURE. endpoint = http://localhost:4848/management/domain/resources/ping-connection-pool.json ; attrs = {id=sample}'

I repeat : my connection pool works fine when I deploy (I have the
postgresql driver in "/glassfish/lib", my connection pool is correctly
configured, etc.), it's only when I undeploy that I have troubles.
This bug is highly reproductible, I even did a small grails project that
reproduces the problem, you only need to have to configure a jndi
datasource connected to a "sample" database (jndi/sample) on your
glassfish server.

Here is the github link :
https://github.com/fabier/GlassfishJDBCGrailsPostgresql
And the war :
https://www.dropbox.com/s/cb9hmgc6lfabl5x/GlassfishJDBCGrailsPostgresql-...
and the domains.xml file:
https://www.dropbox.com/s/ljealpfp0zxj2r4/domain.xml

On grails side, my connection to the pool is configured this way:

environments {
production {
dataSource {
dbCreate = "create-drop"
jndiName = "jdbc/sample"
}
}
}

I think this bug is severe, since it kills a connection pool that can be
shared amongst other webapps or ears.
For information, I did a bit of research, sensing it might be some sort
of class unloader associated with undeployment, I found log4j that could
be linked to this problem, so I tryed :
-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false
but it didn't help.
Last point : in fact, postgresql driver is fully unloaded, so that other
connection pools using postgresql driver are not usable after an undeploy.

Link to same issue in Glassfish's Jira:
http://java.net/jira/browse/GLASSFISH-20094

Link to same issue in Grails Mailing List:
http://grails.1312388.n4.nabble.com/Undeploy-on-Glassfish-causes-connect...

Please help.
Thanks.
--
Pierre FABIER
Ingénieur d'Etude
Parc technologique du canal
13, avenue de l'Europe
31520 Ramonville-Saint-Agne (France)
Tel: 09 74 77 14 21 - Fax: 09 59 64 78 74
www.camineo.com

Is it possible to have secure REST service with DIGEST and file realm?

Regards, Tomaz

Is it possible to have secure REST service with DIGEST and file realm?

Regards, Tomaz

Hi,

I am currently working with Glassfish, with a single domain. (1 application)
After few outages on my application, I started to look at installing several glassfish instances and put load balancing there (with apache and mod_jk).
I followed the oracle tutorial, and the load balancing is working well so far.

My questions, so far:
- Apache: How to avoid single point of failure ?
- Glassfish:
- Is clustering the only possibility to set-up load balancing?
- If I'm not mistaking, there is only one domain, administrating and managing the several instances, right? What happens if the node where the domain is running crashes? Everything is down? How to avoid that? Passive domains on the other nodes?
- Is there other point to consolidate?

I am quite new in the glassfish world, and totally new with high availability challenges.
Please do not hesitate to share comments with me, podcasts, documents, good practices to have a highly available architecture.

Thank you in advance !
Romain.

Hi,

How do I enable sslv3 on Glassfish 3.1.1 on aix?

When a client java program on aix is trying to connect to this glassfish
on aix I am getting the following error -

[#|2013-04-04T11:06:08.077-0700|INFO|*oracle-glassfish3.1.1*|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=12;_ThreadName=Thread-11;|admin-thread-pool-4848(2),*fatal
error: 40: Client requested protocol SSLv3 not enabled or not
supportedjavax.net.ssl.SSLHandshakeException: Client requested protocol
SSLv3 not enabled or not supported|#]*

Thanks,
Vishnu

Greetings,

I am a long time tomcat user evaluating glassfish 3.1.2.2. I imagine that
following the instructions would be an easy way to get things going,
however, the glassfish method of setup runs contrary to what I think is
normal (or even possible) in most environments. I'm sure I am missing
something simple. Here are my problems.

I understand that glassfish has a gui install. The problem is that most
places I would install glassfish are linux servers without X11. It seems
that I would therefore prefer the zip install. I did that.

I presume the setup is done through the management console. The problem is
that the management console is run at port 4848. I perform my installs
remotely over SSH. Most clients I would install for have hefty firewalls
and hefty security policies that would disallow port 4848, period. Tomcat
has its management console over the same port as the application just using
a different URL. This means I can manage tomcat at the same port as my app
by just adding "/admin" to the end of my application URL (for example).

The second problem I have is that (since I installed with a zip file)
nothing has been configured. When I try to access tha management console I
get: Configuration Error Secure Admin must be enabled to access the DAS
remotely.

I need to be able to set a password and configure the management console
through some text base config files before I even start glassfish up.

So, as you can see I am having a problem with the most basic stuff. I
looked on the net briefly and I have Heffelfinger's book but neither
answered these most basic questions.

Thanks for the help!

Blake McBride

I have been looking into this issue a few days now and I am at a loss here.
We have deployed an applications to a glassfish 3.1.2.2 (build 5) cluster, which uses jax-ws to publish a soap endpoint. Most of the traffic involves uploading files via the soap interface.
After a few weeks, all instances of the cluster crashed with

java.io.FileNotFoundException: [filename] (Too many open files)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:212)

running lsof with the glassfish pid shows a lot of entries of these two types:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 24502 user 749w FIFO 0,8 0t0 12559690 pipe
java 24502 user 750u 0000 0,9 0 1972 anon_inode

after restarting glassfish, there are about 1200 file handles open.
after a few days, this increases to about 4000. about 2000 of them are pipes. about 1000 are anon_inodes. This seems to only increase slowly, though there are a lot of request made.

ulimit -Hn shows a limit of 8192 files

I have been trying to reproduce this issue with a local installation, but haven't been able to do so. Everything was running fine - no open file handles. It looks like the open files only leak every now and then. I haven't been able to find any pattern so far.

I have been requesting heap dumps from the VM and analyzing them with VisualVM. I have noticed that there are a lot of streams, that do not have any references any more.
For instance, I have about 2000 DataOutputStreams and about 2000 java.io.File. I am wondering why these don't seem to be cleaned up by the GC. The GC log shows a full GC about every few minutes.
I have about 300 instances of FileOutputStream, however there are about 700 java.io.FileDescriptor, which seems a little high. But, a lot of them again don't have any references.

We have reviewed the code, but haven't found any critical issues. FindBug does not report any streams that are not closed as well.

Does anyone have any ideas how I could further narrow down the cause of this issue or what could be the happening here?

I have a service that uses a seperate database for each client, so we currently create a new connection pool on glassfish for each client, so I'd like to create a connection pool "on the fly" if one does not exists, keep this connection in memory for a specific time and then remove it after it times out. We have considered removing the pool all togheter and just connecting to the database for every connection, but we really like the advantages of polling connections.

I have seen (and tested) something similar on tomcat, is this possible?? any other ideas??

thanks in advance

Jose Suero

I am trying to add GlassFish 3.1 support to SignServer [DSS-306] and have some trouble getting both WS and EJB calls to work using the same classpath.

This is the setup:

• From my client application (JUnit test case) I am calling a few EJB session beans running in GlassFish and after that the JUnit tests calls my web services.
• To make the EJB calls I included the gf-client.jar on the classpath.
• To make the Web Services class the JAX-WS implementation available in the JDK should be enough, however as gf-client.jar has a lot of dependencies including the WS implementation in GlassFish there is an runtime error at the client side:

java.lang.NoSuchMethodError: javax.xml.ws.WebFault.messageName()Ljava/lang/String;
	at com.sun.xml.ws.model.RuntimeModeler.processExceptions(RuntimeModeler.java:1213)
	at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:943)
	at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:711)
	at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:472)
	at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:314)
	at com.sun.xml.ws.db.DatabindingImpl.<init>(DatabindingImpl.java:99)
	at com.sun.xml.ws.db.DatabindingProviderImpl.create(DatabindingProviderImpl.java:74)
	at com.sun.xml.ws.db.DatabindingProviderImpl.create(DatabindingProviderImpl.java:58)
	at com.sun.xml.ws.db.DatabindingFactoryImpl.createRuntime(DatabindingFactoryImpl.java:130)
	at com.sun.xml.ws.client.WSServiceDelegate.buildRuntimeModel(WSServiceDelegate.java:782)
	at com.sun.xml.ws.client.WSServiceDelegate.createSEIPortInfo(WSServiceDelegate.java:789)
	at com.sun.xml.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:765)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:386)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:363)
	at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:345)
	at javax.xml.ws.Service.getPort(Service.java:92)
	at org.signserver.protocol.ws.gen.SignServerWSService.getSignServerWSPort(SignServerWSService.java:56)
	at org.signserver.client.api.SigningAndValidationWS.<init>(SigningAndValidationWS.java:148)
	at org.signserver.client.cli.defaultimpl.WebServicesDocumentSigner.<init>(WebServicesDocumentSigner.java:51)
	at org.signserver.client.cli.defaultimpl.SignDocumentCommand.createSigner(SignDocumentCommand.java:302)
	at org.signserver.client.cli.defaultimpl.SignDocumentCommand.run(SignDocumentCommand.java:371)
	at org.signserver.client.cli.defaultimpl.SignDocumentCommand.execute(SignDocumentCommand.java:417)
	at org.signserver.client.cli.DocumentSignerTest.execute(DocumentSignerTest.java:300)
	at org.signserver.client.cli.DocumentSignerTest.test04signPDFwithPasswordOverWebservices(DocumentSignerTest.java:163)

It turns out that WebFault.class is from JAX-WS in the JDK (rt.jar) while RuntimeModeler.class is from GlassFish (webservices-osgi.jar) and they are not compatible.

If I only would do web services I just remove gf-client.jar from the classpath and the WS calls works fine but then I can not use the EJBs.

Is there a smaller sets of JARs that I can use instead of gf-client.jar which only includes what is necessary to do JNDI and EJB calls and not brings in the WS stuff?

Best regards,
Markus

Hi,

I have an existing JSF web app created with Netbeans 7.3.
Following the tutorial here (http://www.youtube.com/watch?v=qf2Jxwpbsuo) to create a REST service, I am stuck because the class ApplicationConfig.java mentioned in the tutorial is not generated. As a result I get an error msg when I type the url myapp/resource/simple in running app.

Anyone else got this issue? Any suggestion to solve it? Thx!

Clement

Is it possible to use the Eclipse Juno plugin for GlassFish 3.x with
GlassFish 4?

Alternatively, are there any preview builds of Eclipse plugins for
GlassFish 4?

Best regards,
Harald

I understand that GlassFish offers support for technologies that Tomcat
does not (EJB, I think, comes to mind). However, I am not using those
additional technologies, and that difference doesn't matter to me at this
time. Tomcat has been working well for me for several years now. The
reason I am interested in GlassFish is because, I believe, GlassFish scales
better, and perhaps easier, in large installations. So, my question is
this, is GlassFish better positioned to support large installations, such
as more than one physical computer, serving up a single URL?

Also, what other areas of GlassFish might be reason for me to switch?

Thanks.

Blake McBride

I recently installed Glassfish3. Its worked fine for a couple months. Now I can't shutdown the server. I saw some previous posts from 2005 on the same topic. Is there a "standard solution" by now? Any Suggestions?

Thanks

Hi,
I have configured https in glassfish and enabled client authentication. i have used self signed certificates (generated using keytool command).

when trying to generate webservice client, i am getting error "Problem with downloading wsdl or schema file".

Can you please let me know what needs to be done.

Thanks,
Veera.

Hi,

can I somehow limit instance or node visibility to particular user logged in?

My goal is to provide one DAS Admin Console for more people whose I don't want to see each other's nodes/instances.

Thanks.

I have repeated this now three times, yes stupid me and this is making me crazy! I have a MacBook Pro, no firewall and everything is working fine before enabling security manager.

Netbeans 3.2
Glassfish 3.1.2
Macbook Pro

Phase 1: Create JDBCRealm and save
2: Go to server-config and check Enabled Security manager
3: Choose jdbcRealm for default Realm
4: Press Save-button
5: Restart required--->Restart
6: Nothing happend and log is saying that:
[#|2013-04-09T21:48:47.296+0300|SEVERE|glassfish3.1.2|org.apache.catalina.connector.CoyoteAdapter|_ThreadID=32;_ThreadName=Thread-4;|PWC3989: An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: PermGen space
|#]
7: Boot machine
8: Start Netbeans
9 Start your app, not working. Server is not starting anymore and log says:

Exception in thread "main" java.security.AccessControlException: access denied (java.lang.RuntimePermission getenv.GlassFish_Platform)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
at java.security.AccessController.checkPermission(AccessController.java:549)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
at java.lang.System.getenv(System.java:844)
at com.sun.enterprise.glassfish.bootstrap.ASMainHelper.whichPlatform(ASMainHelper.java:105)
at com.sun.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:68)
at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:55)

10: Netbeans shows the window after 5 minutes like screenshot attached:

Starting GlassFish Server 3.1.2
Could not connect to admin listener for GlassFish Server 3.1.2.
Verify that NetBeans can make outbound connections to localhost:4848
/Users/temp/NetBeansProjects/testService2/nbproject/build-impl.xml:1034: Deployment error: Could not connect to admin listener for GlassFish Server 3.1.2.
Verify that NetBeans can make outbound connections to localhost:4848
See the server log for details.
BUILD FAILED (total time: 2 minutes 1 second)

Could somebody tell me why this is happening and how could I fix that? If I uninstall Netbeans and install it again, I will get the same problem. If I uninstall and clean everything, history data of Netbeans, cache etc and install it again, it will work again, but this takes time and is annoying.

Is this a bug? is there any possibility to start the server and get in to admin console?

Sami

Hi,

I'm trying to use the oracle.jdbc.xa.client.OracleXADataSource for my connection pool. I've set the resource type to javax.sql.XADataSource and pinged the server successfully.

However, when I perform any database operation, such as EntityManager.find, I get the following exception. Have I mis-configured my datasource or is there a problem with the driver?

Query: UpdateObjectQuery(com.calc.model.HeartbeatModel[serverId=1,hostId=GBW4TDFB4J,serverType=MASTER,timestamp=2013-04-10 13:42:35.871,availableRAM=181177984,numberOfInternalJobsRunToday=0,numberOfExternalJobsRunToday=0])
	at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
	at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:840)
	at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:906)
	at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:592)
	at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:535)
	at org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:1717)
	at org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:253)
	at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:207)
	at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193)
	at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:749)
	at org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:432)
	at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1042)
	at org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
	at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:287)
	at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
	at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:844)
	at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:743)
	at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
	at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
	at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2871)
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1516)
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1498)
	at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1449)
	at org.eclipse.persistence.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:265)
	at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:128)
	at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:3799)
	at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1415)
	at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitToDatabase(RepeatableWriteUnitOfWork.java:636)
	at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1505)
	at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:3143)
	at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.issueSQLbeforeCompletion(RepeatableWriteUnitOfWork.java:346)
	at org.eclipse.persistence.transaction.AbstractSynchronizationListener.beforeCompletion(AbstractSynchronizationListener.java:157)
	at org.eclipse.persistence.transaction.JTASynchronizationListener.beforeCompletion(JTASynchronizationListener.java:68)
	at com.sun.enterprise.transaction.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:435)
	at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.commit(JavaEETransactionManagerSimplified.java:855)
	at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:5136)
	at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:4901)
	at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:2045)
	at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1994)
	at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:213)
	at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:79)
	at $Proxy931.setModel(Unknown Source)
	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:597)
	at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie.dispatchToMethod(ReflectiveTie.java:144)
	at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:174)
	at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:528)
	at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:199)
	at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1624)
	at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1486)
	at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:990)
	at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:214)
	at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:742)
	at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.dispatch(CorbaMessageMediatorImpl.java:539)
	at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.doWork(CorbaMessageMediatorImpl.java:2324)
	at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:497)
	at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:540)
Caused by: java.sql.SQLException: Closed Statement
	at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
	at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
	at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
	at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
	at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
	at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
	at oracle.jdbc.driver.OracleStatement.ensureOpen(OracleStatement.java:3616)
	at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3369)
	at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3467)
	at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
	at com.sun.gjc.spi.base.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:125)
	at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:831)
	... 57 more

I know there has been a similar discussion every once in a while, but I couldn't find any real solution to this issue from reading previous postings.
We are currently looking for a way to limit the amount of data, that could be uploaded to our servers. The purpose is to prevent attacks where people would try to upload a big amount of very large files to our services and cause out of heap space errors. We want to abort the upload if the uploaded amount of data exceeds a certain amount. We are currently using both soap and rest endpoints via jax-rs and jax-ws.

I have come across the discussion where it has been recommended to set max-swallowing-input-bytes in the domain.xml, but we found that this didn't have any effect in glassfish 3.1.2.2.

There is also a config for the http-listener: Max Post Size, but we could still upload data via http post, that exceeded the specified size.

Any recommended way, how to solve such a problem? I hardly can believe that we are the first, who are trying to prevent such a possible attack.

Hi - We have had this issue of GF hanging after a few days and it becomes compltetely unresponsive. We don't see any memory buildup/leak and have verified the heap dumps. Fortunately,we were able to get a thread dump this time and any pointers are appreciated.

JVM version - 1.6_0.16
Platform - CentsOS, 32 Bit
GF version -
Version = Sun GlassFish Enterprise Server v2.1.1 Patch19
Command version executed successfully.

Thread dump is attached.

Thanks,
Kanwar Sangha

the problem to call with ejb renmote into a glassfish that it is behind a firewall-
read at :
http://www.java.net/forum/topic/glassfish/glassfish/ejb-remote-deployed-...

i have ubuntu 10.04
glassfsih 3.1.2.2

i have a ip public static 95.x.y.z
my glassfsih it have ip private of my lan 192.169.1.10

how i can use acc (app client for get to work the ejb appclient deployed int othe server )???

i have the problem of glassfsih behind the firewall.........

it is resolved????
glassfsih 17.151 jira .