[JBoss Cache: Core Edition] - Resource cleanup upon eviction -- change in behaviour in 1.4
by cowan
Hi all,
We have recently upgraded JBoss Cache from 1.3 to 1.4 (yes, yes! I know!), and have encountered a behaviour change which has us stumped. We want to perform (non-critical but useful) resource cleanup and lifecycle measurements/logging for the objects in one region of the cache when they're evicted. Previously, in 1.3, we had our own class which extended LRUPolicy, and effectively did the following:
| public void evict(Fqn fqn) {
| ...
| try {
| OurClass obj = cache.peek(fqn, KEY);
| obj.cleanUp();
| } finally {
| super.evict(fqn);
| }
| }
|
which seemed to work fine. What we're finding in 1.4, though, is that this behaviour doesn't actually evict the node correctly. I've written a small test case for this and it seems that the call to cache.peek returns the correct object, we close it OK, and the object is evicted but it remains in the eviction queue. That is, if we have a region size of 10, and put 20 objects in the cache, then 10 get thrown out on the first eviction run; however, those FQNs don't seem to get completely thrown out and then they get evicted AGAIN next cycle. Because super.evict() removed the node, this second time around the cache.peek() call doesn't find the object, calls to the CacheLoader, and recreates the object. Therefore, we're continually cycling over and over again, creating and throwing away new objects (and killing our performance!)
This behaviour does not happen in 1.3; nor does it happen in 1.4 if we remove the .peek call, so this presumably is what's causing the problem.
I have tried converting to 2.2 to see what happens there, but the same process occurs. If our custom LRUPolicy calls:
NodeSPI node = cache_.peek(fqn, false, false);
then that's fine, but if we call
node.get(KEY);
then that seems to prevent the FQN being cleared out and we enter the loop again.
I have tried the (much less hacky!) technique of using a @CacheListener instead, using something like:
| @NodeEvicted
| public void nodeEvicted(NodeEvictedEvent event) {
| if (event.isPre()) {
| Node n = ((CacheSPI) event.getCache()).peek(event.getFqn(), false);
| if (n != null) {
| n.get(KEY);
| }
| }
|
then the same behaviour occurs, a continual eviction loop. If the n.get(KEY) line is commented out (JUST leaving the peek) this behaviour goes away.
What's the "correct" way, if there is one, to retrieve data from nodes that are being evicted without interfering with the eviction behaviour?
Thanks in advance for your help.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223891#4223891
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223891
15 years, 9 months
[JBoss jBPM] - BUILD FAILED and deployment failed: Internal server Error
by mamidalasrinivas
When I Build BPEL process hello example , I am geting below error
xe8][0x6][0xc6][0xa7][0xf9]v[0x8e][0x7][0xe0][0xc4][0xe9]@5[0x1c]t[0xce]:[0xc9][
0xfd]D[0xa8][0x1c]{[0xb3][0x8e][0xf8]*[0xdd]^W[0x8][0x11][0xc3]^[0x97][0x9d]a[0x
97]p[0x99][0xf2][0xdd]0[0x9a]j[0x1d][0x81]?m}[0x84][0x96][0x1f][0x89]FS[0xc2][0x
89]l[0x1][0x92][0xee][0xc1][0xb9][0xfc][0x87][0xf5][0x94][0xf1]RN[0xde]7[0xeb][0
xbf]PK[0x1][0x2][0x14][0x3][\n]"
[deployprocess] 11:35:16,678 DEBUG [content] >> "[0x0][0x0][0x0][0x8][0x0][0xf]j
}7[0x6][0xdc][0x13][0xc5]?[0x2][0x0][0x0][0x9b][0x5][0x0][0x0][\n]"
[deployprocess] 11:35:16,678 DEBUG [content] >> "[0x0][0x0][0x0][0x0][0x0][0x0][
0x0][0x0][0x0][0x0][0x0][0xa4][0x81][0x0][0x0][0x0][0x0]hello.bpelPK[0x1][0x2][0
x14][0x3][\n]"
[deployprocess] 11:35:16,678 DEBUG [content] >> "[0x0][0x0][0x0][0x8][0x0][0xf]j
}7[0xb7][0xc6][0xa1]y[0xee][0x1][0x0][0x0][0xa5][0x4][0x0][0x0][\n]"
[deployprocess] 11:35:16,678 DEBUG [content] >> "[0x0][0x0][0x0][0x0][0x0][0x0][
0x0][0x0][0x0][0x0][0x0][0xa4][0x81]g[0x2][0x0][0x0]hello.wsdlPK[0x5][0x6][0x0][
0x0][0x0][0x0][0x2][0x0][0x2][0x0]p[0x0][0x0][0x0]}[0x4][0x0][0x0][0x0][0x0]"
[deployprocess] 11:35:16,678 DEBUG [content] >> "[\r][\n]"
[deployprocess] 11:35:16,678 DEBUG [content] >> "--"
[deployprocess] 11:35:16,678 DEBUG [content] >> "X6J-lx4RlPCjJ6ZxyI8tzOFSGn9aN5V
r8t"
[deployprocess] 11:35:16,678 DEBUG [content] >> "--"
[deployprocess] 11:35:16,678 DEBUG [content] >> "[\r][\n]"
[deployprocess] 11:35:17,961 DEBUG [header] << "HTTP/1.1 500 Internal Server Err
or[\r][\n]"
[deployprocess] 11:35:17,961 DEBUG [header] << "Server: Apache-Coyote/1.1[\r][\n
]"
[deployprocess] 11:35:17,961 DEBUG [header] << "Content-Type: text/html;charset=
utf-8[\r][\n]"
[deployprocess] 11:35:17,961 DEBUG [header] << "Content-Length: 2154[\r][\n]"
[deployprocess] 11:35:17,961 DEBUG [header] << "Date: Tue, 07 Apr 2009 06:05:17
GMT[\r][\n]"
[deployprocess] 11:35:17,961 DEBUG [header] << "Connection: close[\r][\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "JBossWeb/2.0
.0.GA - Error report<!--H1 {font-family:Tahoma,Arial,sans-serif;c
olor:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Aria
l,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-fami
ly:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;}
B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px
;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--> </he
ad><h1>HTTP Status 500 - </h1>type Exception reportmessage description The
server encountered an internal error () that prevented it from fulfilling this r
equest.exception java.lang.NullPointerException[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.tools.Wscomp
ileTool.getLocation(WscompileTool.java:240)[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.tools.Wscomp
ileTool.formatClasspath(WscompileTool.java:227)[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.tools.Wscomp
ileTool.callWscompile(WscompileTool.java:197)[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.tools.Wscomp
ileTool.generateJavaMappingImpl(WscompileTool.java:156)[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.tools.Wscomp
ileTool.generateJavaMapping(WscompileTool.java:143)[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.tools.WebMod
uleBuilder.callJavaMappingTool(WebModuleBuilder.java:264)[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.tools.WebMod
uleBuilder.buildModuleImpl(WebModuleBuilder.java:102)[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.tools.WebMod
uleBuilder.buildModule(WebModuleBuilder.java:84)[\n]"
[deployprocess] 11:35:17,976 DEBUG [content] << "[0x9]org.jbpm.bpel.web.Deployme
ntServlet.deployWebModule(DeploymentServlet.java:205)[\n]"
[deployprocess] 11:35:17,992 DEBUG [content] << "[0x9]org.jbpm.bpel.web.Deployme
ntServlet.doPost(DeploymentServlet.java:99)[\n]"
[deployprocess] 11:35:17,992 DEBUG [content] << "[0x9]javax.servlet.http.HttpSer
vlet.service(HttpServlet.java:710)[\n]"
[deployprocess] 11:35:17,992 DEBUG [content] << "[0x9]javax.servlet.http.HttpSer
vlet.service(HttpServlet.java:803)[\n]"
[deployprocess] 11:35:17,992 DEBUG [content] << "[0x9]org.jboss.web.tomcat.filte
rs.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)[\n]"
[deployprocess] 11:35:17,992 DEBUG [content] << "note The
full stack trace of the root cause is available in the JBossWeb/2.0.0.GA logs.<
/u><h3>JBossWeb/2.0.0.GA</h3>"
BUILD FAILED
E:\jbpm-bpel-1.1.GA\examples\common\bpel-build.xml:61: deployment failed: Intern
al Server Error
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223875#4223875
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223875
15 years, 9 months
[Installation, Configuration & DEPLOYMENT] - How do deploy old version WAR on Jboss5.x
by higkoo
This packet can deploy on Jboss4.x ,but error on Jboss5.x.
What's the prblem and how to do it ?
anonymous wrote :
| 13:33:54,565 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=higkoo.war
| 13:33:54,565 ERROR [AbstractKernelController] Error installing to Start: name=jboss.web.deployment:w
| ar=/ state=Create mode=Manual requiredState=Installed
| org.jboss.deployers.spi.DeploymentException: Web mapping already exists for deployment URL vfsfile:/
| D:/Server/jboss-5.0.0.GA/server/default/deploy/higkoo.war/
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeplo
| yment.java:192)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.ja
| va:146)
| at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460)
| at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
| at org.jboss.web.deployers.WebModule.start(WebModule.java:96)
| 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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
| at $Proxy36.start(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycle
| Action.java:42)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycle
| Action.java:37)
| at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(Sim
| pleControllerContextAction.java:62)
| at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControlle
| rContextAction.java:71)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerC
| ontextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.
| java:348)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext
| .java:286)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:93
| 4)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1
| 062)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:9
| 84)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
| at org.jboss.system.ServiceController.start(ServiceController.java:460)
| at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(Abstra
| ctSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer
| .java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.ja
| va:1157)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.ja
| va:1178)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.
| java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:93
| 4)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1
| 062)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:9
| 84)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileService
| Bootstrap.java:304)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootst
| rap.java:205)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
| at org.jboss.Main.boot(Main.java:209)
| at org.jboss.Main$1.run(Main.java:547)
| at java.lang.Thread.run(Thread.java:619)
| 13:33:54,643 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/D:/Server/jbos
| s-5.0.0.GA/server/default/deploy/higkoo.war/ state=PreReal mode=Manual requiredState=Real
| org.jboss.deployers.spi.DeploymentException: Web mapping already exists for deployment URL vfsfile:/
| D:/Server/jboss-5.0.0.GA/server/default/deploy/higkoo.war/
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeplo
| yment.java:192)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.ja
| va:146)
| at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460)
| at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
| at org.jboss.web.deployers.WebModule.start(WebModule.java:96)
| 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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
| at $Proxy36.start(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycle
| Action.java:42)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycle
| Action.java:37)
| at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(Sim
| pleControllerContextAction.java:62)
| at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControlle
| rContextAction.java:71)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerC
| ontextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.
| java:348)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext
| .java:286)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:93
| 4)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1
| 062)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:9
| 84)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
| at org.jboss.system.ServiceController.start(ServiceController.java:460)
| at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(Abstra
| ctSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer
| .java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.ja
| va:1157)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.ja
| va:1178)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.
| java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:93
| 4)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1
| 062)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:9
| 84)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileService
| Bootstrap.java:304)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootst
| rap.java:205)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
| at org.jboss.Main.boot(Main.java:209)
| at org.jboss.Main$1.run(Main.java:547)
| at java.lang.Thread.run(Thread.java:619)
| 13:33:54,753 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deploymen
| ts (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| vfsfile:/D:/Server/jboss-5.0.0.GA/server/default/deploy/higkoo.war/ -> org.jboss.deployers.spi.Deploym
| entException: Web mapping already exists for deployment URL vfsfile:/D:/Server/jboss-5.0.0.GA/server
| /default/deploy/higkoo.war/
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223870#4223870
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223870
15 years, 9 months
[JBoss Messaging] - Sending Messages from EJB using container transaction
by eontech
Hello Everyone,
We have a requirement to send thousands of messages using EJB in a day. Thus every time a need arises to send a message, we have a dedicated session bean which will post message to the queue as part of EJB (container) transaction. We are using JBoss EAP 4.3.0.
Our question is what will be the right connection factories to use. Currently we are using /ConnectionFactory to send messages but it seems that it does not uses container transaction. If we use session transacted session it sends message only if we explicitly commit the transaction and it seems to have two transactions running in parallel i.e. container transaction & JMS transaction which are independent of each other. Thus we used session transacted as false and AUTO_ACK true but with this we face another problem that messages are delivered to consumer even before the EJB i.e. container transaction finishes. Thus regardless the originating transaction was successful, complete or failed, the message is delivered to consumer which gives unreliable results
Our requirement is that message should be delivered to consumer only if the originating EJB transaction was successful else the message posted should be de-queued. The whole infrastructure should be fast to process the message.
We want to know what will be the most appropriate approach to get best performance and reliability
1. Which connection factory to use so that JMS uses Container transaction? Currently we are using /ConnectionFactory
2. Do we need to open connection every time we send a message or we can have a connection object initialized in post construct of Session bean. Currently we create it at post construct of session EJB
3. Do we need to create session every time we send a message or we can have a session object initialized in post construct of Session bean. Currently we create it every time.
4. What all points should we take care from performance tuning perspective. We are using MS-SQL Server 2005.
Best Regards,
Abhishek
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223867#4223867
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223867
15 years, 9 months