[JBossWS] - Re: Help! Call Web service error!
by lixun
Thank you Peter!
Follow your instruction, I add -verbose:class to JAVA_OPTS to run.bat, when jboss starts, I get a long class load list,
In this list, I find these classes either loaded from jboss_home or java_home, and not know whick one is the stray JAR file.
With no solution, I copy the whole jboss directory to other windows platform, On new windows platform, I call web service successfully!
But On first windows platform, exception still occurs.
My two windows platform have similar Enviroment Setting, and I still in doubt what's the root cause of the exception.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231535#4231535
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231535
16 years, 11 months
[EJB/JBoss] - Suggestion for transaction configuration on stateful session
by vettori
Hi,
I'm using jboss 4.2.3. I use a stateful session bean to perform a long and complex operation on the entities that can require a lot of database accesses and other operations for each entity.
The stateful session bean has a few methods to setup the operation: one is to select the set of entities to process, one is to set the number of "batches" and one to set the "batch" size.
Then there's a method that when called performs the operation on a subset of the specified size of the selected entities. This method uses flush and clear method of the entity manager to flush changes to disk. This method is called from the client once for each "batch".
This bean is called from a java app, a sort of batch app that runs once a week. It simply select the number of batches and their size and then it calls the main method of the bean with a for loop.
The entire job on my actual data set runs for about 40 minutes.
At the end of the process I get an exception, a transaction timeout.
Now I suspect that using the standard transaction configuration, the transaction starts when the batch app calls the first bean method and it ends when the app destroy the bean. Since the actual jboss tx timeout is set to 600 seconds this makes the session bean timeout.
What's the best transaction configuration for the bean ? Should I set all "setup" methods to Never and the main method of the bean to requires new ? Or should I set all to Never ? Any other hint ?
Thank you for your help.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231521#4231521
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231521
16 years, 11 months
[EJB 3.0] - Re: Stateful bean keep-alive
by xmedeko
Hello Peter,
thanks for your reply.
"PeterJ" wrote : Don't set removalTimeoutSeconds, use idleTimeoutSeconds instead. ...
unfortunately, our session bean cannot be serialized from various reasons. I am moving an existing, a little bit larger, application into JBoss. It would be not easy to make it serializable. (Maybe in the future I will have to do it anyway.)
"PeterJ" wrote : Creating a new client thread might work, but you have to be careful. First, the thread must not lookup the EJB itself - you will end up with a new EJB, not with the one that you want to keep alive. Therefore, you must pass the bean's proxy to the thread. Second, I recommend creating a separate method on the EJB that does nothing - the primary purpose of this method is for the extra thread to occasionally call it. This should guarantee that the state of the bean does not change inadvertently.
Yes, that what I have already done :-)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231519#4231519
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231519
16 years, 11 months
[JBoss Tools (users)] - Not running in Debug Mode
by pmsudha
Hi
without debug mode my application running but with debug mode my application not running.
in this same system my application ran with debug mode. but i don't know what is the reason for not running.
Im using JBoss Developer Studio 2.0.0.CR2
21:11:36,000 INFO [SeamFilter] Initializing filter: org.jboss.seam.web.redirectFilter
21:11:36,078 INFO [SeamFilter] Initializing filter: org.jboss.seam.web.exceptionFilter
21:11:36,093 INFO [SeamFilter] Initializing filter: org.jboss.seam.web.multipartFilter
21:11:36,109 INFO [SeamFilter] Initializing filter: org.jboss.seam.web.identityFilter
21:12:38,296 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
21:12:43,203 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
21:12:45,515 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812042120)] Started in 6m:31s:47ms
21:13:37,578 INFO [Contexts] starting up: org.jboss.seam.security.ruleBasedPermissionResolver
21:14:39,125 INFO [RuleBase] parsing rules: /security.drl
21:15:10,984 INFO [Contexts] starting up: org.jboss.seam.security.identity
21:15:11,109 INFO [Contexts] starting up: org.jboss.seam.web.session
up to this line printing in the console but here after no response.. what is the problem?
--Sudha Perumal.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231514#4231514
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231514
16 years, 11 months