Hello,
we try to run JBoss 4.0.3 on Solaris 9, on a 24 CPU Fujitsu/Siemens.
It works perfectly using Java 1.4, but with Java 1.5/1.6 the JBoss process consumes up to 35% CPU time (8 CPUs of the 24 available!) during startup.
(We then kill the process(after 2/3 minutes), it would finally make the machine totally unavailable)
We have no problems running the same installation on a 2-CPU Solaris 9 machine aswell as on the WinXP computers we use for development.
I guess Java 1.6 may not be supported by version 4.0.3 but 1.5 should work without any problems, right?
Any help/ideas greatly appreciated
thanks in advance
Karl
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069492#4069492
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069492
"shane.bryzak(a)jboss.com" wrote : "samdoyle" wrote : It is being deployed in GlassFish V2 build 56
|
| Ah I missed this bit before. It is possible that this has something to do with remoting not working, however go ahead and send me your test case and I can at least try it with JBossAS. If it works there, then I may be able to get someone else to try it out with Glassfish (I've never used it before).
I doubt it would have anything to do with GlassFish. The other areas of Seam appear to work fine.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069483#4069483
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069483
I used SoapUI to issue the following request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://com.twocoast.tcsc.web.service">
| <soapenv:Header/>
| <soapenv:Body>
| <com:isConfigurationChangePending>
| <serverName>QUATTRO</serverName>
| </com:isConfigurationChangePending>
| </soapenv:Body>
| </soapenv:Envelope>
and got the following response (no conversation Id):
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
| <env:Header/>
| <env:Body>
| <ns2:isConfigurationChangePendingResponse xmlns:ns2="http://com.twocoast.tcsc.web.service">
| <return>true</return>
| </ns2:isConfigurationChangePendingResponse>
| </env:Body>
| </env:Envelope>
If I annotate the isConfigurationChangePending with @Begin in the seam component (which is called by the SLSB annotated with @WebService) I get the following response:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
| <env:Header/>
| <env:Body>
| <env:Fault>
| <faultcode>env:Server</faultcode>
| <faultstring>java.lang.IllegalStateException: Do not start long-running conversations in direct calls to EJBs</faultstring>
| </env:Fault>
| </env:Body>
| </env:Envelope>
I'm also seeing the following error show up in the log whenever a web request is processed (regardless of whether the method is annotated):
22:15:29,460 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@949f87
FYI- I'm using seam libraries built from CVS today.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069482#4069482
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069482