October 2007 - jboss-user - Jboss List Archives

[JCA/JBoss] - Re: How to configure the minsize and maxsize of connectionpo

by adrian＠jboss.org

"liujw2001" wrote : Thank you for your help. | | I have another question. If a ManagedConnection is used by connection, Can this ManagedConnection be matched with a new connecion? | PLEASE CREATE ONE THREAD PER QUESTION. Multiple questions on one thread makes it very difficult to follow, both for those answering the questions and those searching for answers to similar questions later. anonymous wrote : | If so, I have the following question: | | If one connection "A" get a ManagedConnection from pool which is used by another connection "B". After the first one "A" finished and want to close, dose it have some effection to connection "B"? for example, if "A" invokes "close()", the ManagedConnection will invoke the "cleanup()" function, does it effect the connection "B"? Is the ManagedConnection pushed into pool before the "A" finished ? | The connection does not "get" a ManagedConnection. The ConnectionManager retrieves a "connection handle" for a ManagedConnection to give to the user application. Whether there are mutliple connection handles for a ManagedConnection depends upon the ConnectionManager configuration (e.g. transaction affinity or interleaving - not relevant in your case) and what the application is doing (e.g. opening multiple connections handles in the same transaction) Regardless, the ManagedConnection won't be returned to the pool until ALL connection handles associated with it are closed by the application(s) (and in the case of transaction affinity until the transaction ends). THIS IS ANSWERED IN THE SPEC. See the javaee connector architecture 1.5 spec available from www.jcp.org If you think the spec is unclear, speak to the author(s). :-) There will be an e-mail address associated with the spec where you can post comments. anonymous wrote : | The second question is why jobss service does't invoke "mat{c}hManagedConnection{s}()" which is implemented in MyManagecConnectionFactory? | THIS IS ALSO SPEC DEFINED BEHAVIOUR, see the section on pooling. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096101#4096101 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096101

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Very slow initialization of Captcha

by Toby451

Hi Peter & Shane, As can be seen below it seems that HeirarchicalLoaderRepository3 is slow at two points during Captcha init. I am still clueless on this one bu will continue to investigate. Any insightful points will be much appreciated. Cheers, Tobias | 15:57:45,974 INFO [Contexts] starting up: org.jboss.seam.captcha.captchaImage | 15:57:45,974 DEBUG [Component] instantiating Seam component: org.jboss.seam.captcha.captchaImage | 15:57:45,974 DEBUG [Component] initializing new instance of: org.jboss.seam.captcha.captchaImage | 15:57:45,974 DEBUG [Component] done initializing: org.jboss.seam.captcha.captchaImage | 15:57:45,974 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Events] Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.captcha.captchaImage | 15:57:45,974 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:57:45,974 DEBUG [Events] Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.captcha.captchaImage | 15:57:45,992 DEBUG [RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@119ca2c, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@8d02eb{ url=null ,addedOrder=0} | 15:57:45,992 DEBUG [RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@119ca2c, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@1ba9aca{ url=null ,addedOrder=0} | 15:57:46,032 DEBUG [RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@119ca2c, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@92949f{ url=null ,addedOrder=0} | 15:57:55,165 DEBUG [RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@119ca2c, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@1ae30a{ url=null ,addedOrder=0} | 15:58:25,241 DEBUG [RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@119ca2c, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@4b44f0{ url=null ,addedOrder=0} | 15:58:25,242 DEBUG [RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@119ca2c, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@19afa26{ url=null ,addedOrder=0} | 15:58:25,243 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,243 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,243 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,243 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,243 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,243 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,244 DEBUG [Events] Processing event:org.jboss.seam.postCreate.org.jboss.seam.captcha.captchaImage | 15:58:25,244 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,244 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,244 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,244 DEBUG [Events] Processing event:org.jboss.seam.postInitialization | 15:58:25,244 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,244 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,245 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,245 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,245 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,245 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,245 DEBUG [Events] Processing event:org.jboss.seam.preDestroyContext.CONVERSATION | 15:58:25,245 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,246 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,246 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,246 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,246 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,246 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,246 DEBUG [Events] Processing event:org.jboss.seam.postDestroyContext.CONVERSATION | 15:58:25,247 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,247 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,247 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,247 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,247 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,247 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,247 DEBUG [Events] Processing event:org.jboss.seam.preDestroyContext.EVENT | 15:58:25,248 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,248 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,248 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,248 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events | 15:58:25,248 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events | 15:58:25,248 DEBUG [Component] done initializing: org.jboss.seam.core.events | 15:58:25,248 DEBUG [Events] Processing event:org.jboss.seam.postDestroyContext.EVENT | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096100#4096100 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096100

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: s:selectItems once again

by w17chm4n

Thx it worked ! Nevertheless I didn`t have to override the hashCode method. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096097#4096097 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096097

18 years, 9 months

1
0
0 / 0

[Performance Tuning] - Re: High System CPU Time

by hamilrk1

Found the problem in the custom application code. Apparently there was a system call to get the system time which was executing 1000's of times per transaction ... :) Thanks for all the assist/ideas .... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096092#4096092 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096092

18 years, 9 months

1
0
0 / 0

[JBossWS] - How to handle namespace generation?

by cch＠jboss

Hi everyone, I have the following problem: In a jboss 4.0.5GA with ejb3 (installed from jems-installer-1.2.0.GA.jar) I want to publish a web service. Therefor I annotate a class with | @WebService(name="service", | portName="service", | serviceName="TestService", | targetNamespace="http://foo.com" | ) | One of the method I annotate with @WebMethod uses a class Bar from package com.foo Now if I inspect the automatically generated wsdl I have a targetNamespace http://foo.com but in the types-section I have a targetNamespace http://foo.com/jaws. I tried to put a package-info.java in the package com.foo with | @javax.xml.bind.annotation.XmlSchema(namespace="http://com.foo") | package com.foo; | But the result is still the same. Am a missing any obvious switch or do I just have a serious misunderstanding of how the wsdl should work? Christian View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096090#4096090 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096090

18 years, 9 months

1
0
0 / 0

[JCA/JBoss] - Re: Merge xa and no-xa Connections - CMT problem

by adrian＠jboss.org

If you configure the timeten datasource as a local datasource (jdbc driver) then JBoss will use the "last resource gambit" for that datasource as long as there are no other local resources in the transaction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096087#4096087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096087

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Additional filter outside Seam-filter messes up encoding

by Toby451

Ok ... the scandinavian characters åäöÅÄÖ got scrambled when they where part of a post-data. Adding this (below) filter in front of the timing seems to solve it! | <filter> | <filter-name>Character Encoding</filter-name> | <filter-class> | org.jboss.seam.servlet.SeamCharacterEncodingFilter | </filter-class> | <init-param> | <param-name>encoding</param-name> | <param-value>UTF-8</param-value> | </init-param> | <init-param> | <param-name>overrideClient</param-name> | <param-value>true</param-value> | </init-param> | </filter> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096086#4096086 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096086

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: s:selectItems once again

by pete.muir＠jboss.org

Try using id.equals(id) - you're comparing objects not primitives. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096084#4096084 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096084

18 years, 9 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: JMS msg get redelivered although setting retry to 0

by adrian＠jboss.org

Bug report: http://jira.jboss.com/jira/browse/JBAS-4870 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096083#4096083 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096083

18 years, 9 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: Using DeliveryMode.NON_PERSISTENT

by adrian＠jboss.org

This is another FAQ, but it's not in the FAQ (since its basic computer optimization NOT a JMS question :-). The answer is the answer to the following question "what is the bottleneck"? e.g. is the frontend network, (100Mbps ~ 12 Megabytes per second) getting saturated? e.g. is the cpu at 100% utilization e.g. etc. All you've shown so far is that the database (for hypersonic the local file system) is NOT the bottleneck. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096081#4096081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096081

18 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user October 2007