February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3911) Default max-pool-size in DataSource configuration

by Shrinivas Joshi (JIRA)

Default max-pool-size in DataSource configuration ------------------------------------------------- Key: JBAS-3911 URL: http://jira.jboss.com/jira/browse/JBAS-3911 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA Reporter: Shrinivas Joshi Assigned To: Weston Price In *-[xa]-ds.xml if max-pool-size is not specified and only min-pool-size is specified then max-pool-size should be set = min-pool-size whereas it defaults to 20 rendering min-pool-size setting of no use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

6
8
0 / 0

[JBoss JIRA] Created: (JBWEB-66) basic-auth broken

by Mark Stewart (JIRA)

basic-auth broken ----------------- Key: JBWEB-66 URL: http://jira.jboss.com/jira/browse/JBWEB-66 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.0 GA Environment: Linux Reporter: Mark Stewart Assigned To: Mladen Turk Assuming that Jboss Web is configured identically to the web container in AS, it seems that basic-auth support is broken. That is, the server doesn't send a 401 for protected urls. Here's the post I made three weeks ago on the Jboss Web Server forum: "I have a webapp I usually run in JBoss AS that I'm trying to get running under JBossWeb. I've added the same entry to login-module.xml in the default/conf/ directory and a jboss-web.xml file whose <security-domain> tag points at the entry in default/deploy/<my-web-app.war>/WEB-INF. JBossWeb doesn't block the access to the protected pages, however." This is tested by the J2EE CTS so I guess JBossWeb wasn't tested against it (or the failure was ignored) prior to the GA release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWEB-73) Context defined in the server.xml of the jbossweb.sar does not get installed properly .

by Vicky Kak (JIRA)

Context defined in the server.xml of the jbossweb.sar does not get installed properly . --------------------------------------------------------------------------------------- Key: JBWEB-73 URL: http://jira.jboss.com/jira/browse/JBWEB-73 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.1 GA Reporter: Vicky Kak Assigned To: Mladen Turk The context element defined in the server.xml of the jbossweb.sar is not honored . The context defined in the server.xml are not deployed when the Tomcat boots , this works properly with standalone Tomcat and Jboss AS . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1152) testsuite problem with sybase

by Prabhat Jha (JIRA)

testsuite problem with sybase ----------------------------- Key: JBPORTAL-1152 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1152 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Prabhat Jha Assigned To: Roy Russo During portal testsuite run with sybase database, tables are not getting created successfully. These are two major errors that I see: 1. ERROR [SchemaExport] Unsuccessful: create table jbp_cms_cmsentry (PK int identity not null, FSENTRY_NAME varchar(255) null, FSENTRY_PATH varchar(245) not null, FSENTRY_DATA image nu\ ll, FSENTRY_LASTMOD numeric(19,0) not null, FSENTRY_LENGTH numeric(19,0) not null, primary key (PK)) [junit_] 17:50:33,387 ERROR [SchemaExport] Identity field 'PK' must be a numeric with a scale of 0 and not null allowed. 2. ERROR [SchemaExport] Unsuccessful: create table jbp_cms_version_refs (PK int identity not null, NODE_ID varchar(36) null, REFS_DATA varbinary(100000000) not null, primary key (PK)) [junit_] 17:50:33,413 ERROR [SchemaExport] Length or precision specification 100000000 is not within the range of 1 to 16384. Assigning it to Roy since you seem to be the most involved with it. ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBWEB-74) tomcat config files fail to support default sysprop values like other jboss-service.xml type configs

by John Mazzitelli (JIRA)

tomcat config files fail to support default sysprop values like other jboss-service.xml type configs ---------------------------------------------------------------------------------------------------- Key: JBWEB-74 URL: http://jira.jboss.com/jira/browse/JBWEB-74 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Reporter: John Mazzitelli Assigned To: Mladen Turk >From my JBoss forum post and Dimitris' reply: In jboss-service.xml, you can define values via properties like this: ${my.prop:123} where the value will be 123 if and only if my.prop property is not explictly set. However, this syntax does not seem to work on JBossAS 4.0.5 within the jbossweb-tomcat55.sar's server.xml. If I use ${my.prop} in server.xml, it works fine. But if I define a default value like ${my.prop:123}, it doesn't work - the value becomes literally ${my.prop}. Dimitris Andreadis reply: "JBoss uses org.jboss.util.StringPropertyReplacer for substituting variables. Tomcat/jboss-web must be using a different way to do this, so this is really a feature request for jboss-web." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-905) Perform code coverage analysis and add missing unit tests

by Manik Surtani (JIRA)

Perform code coverage analysis and add missing unit tests --------------------------------------------------------- Key: JBCACHE-905 URL: http://jira.jboss.com/jira/browse/JBCACHE-905 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Hany Mesha Fix For: 1.4.1.GA, 2.0.0.GA Using a code coverage tool like Clover: 1) Analyse current test suite on Branch_JBossCache_1_4_0 2) Put up results on a wiki page 3) Link wiki page to this JIRA task as well as the JBossCache wiki page 4) Analyse gaps in the test suite and either document (on the wiki) as being too simple/obvious to test or create a unit test for this. Once 2.0.0 reaches CR1, perform the same on HEAD (or Branch_JBossCache_2_0_0 by then...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

6
32
0 / 0

[JBoss JIRA] Created: (JASSIST-30) Memory Leak - failure to clean up javassisst instances after EJB3 remote calls

by Grant Quimby (JIRA)

Memory Leak - failure to clean up javassisst instances after EJB3 remote calls ------------------------------------------------------------------------------ Key: JASSIST-30 URL: http://jira.jboss.com/jira/browse/JASSIST-30 Project: Javassist Issue Type: Bug Environment: JBoss 4.0.4.GA, Windows Xp JBoss 4.0.4.GA, LInux (Debian) JBoss 4.0.4.GA, Solaris Reporter: Grant Quimby Assigned To: Shigeru Chiba Priority: Blocker Quote from related JIRA issue EJBTHREE-736 PermGen in EJB3 client aplication by remote interface. The application is as sample as it can be: -get remote interface of stateless EJB3 (by JNDI) - ask 1000 times to get a Collection (List) of 10 EntityBeans. After 255 there is OutOfMemory: PermGen. JVM options changes nothing (eventualy more PermSpace => longer run). The reason looks like the Javassist create lazyinitializer classes for every EntityBean retrived from the server. So: When I debug on server-side, I got before sending Entity to client: I got: myEntity[0].id=143534 myEntity[0].flow=<FlowEntity_$$_javassist_7> 13434 ... myEntity[0].user=<UserEntity_$$_javassist_15>... myEntity[0].stage=<StageEntity_$$_javassist_17>... And every remote call the class names (name)_$..._javassist_(index) got the same indexes (7,15,17) on server side (end every entity in returned collections of entities) But when I debug on client site - after return from remote call - the indexes of all returned entities are different (Each next increments index). So after first call I got: myEntity[0].id=143534 myEntity[0].flow=<FlowEntity_$$_javassist_0>... ... myEntity[0].user=<UserEntity_$$_javassist_1>... myEntity[0].stage=<StageEntity_$$_javassist_2>... ... myEntity[1].id=143534 myEntity[1].flow=<FlowEntity_$$_javassist_3> ... myEntity[1].user=<UserEntity_$$_javassist_4>... myEntity[1].stage=<StageEntity_$$_javassist_5>... ... After secund call: myEntity[0].id=143534 myEntity[0].flow=<FlowEntity_$$_javassist_6>... ... myEntity[0].user=<UserEntity_$$_javassist_7>... myEntity[0].stage=<StageEntity_$$_javassist_8>... ... myEntity[1].id=143534 myEntity[1].flow=<FlowEntity_$$_javassist_9> ... myEntity[1].user=<UserEntity_$$_javassist_10>... myEntity[1].stage=<StageEntity_$$_javassist_11>... ... And so on... ... and permGen after 260 iterations... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JASSIST-28) javassist enhancement failed on deserializing hibernate proxies

by Armin Haaf (JIRA)

javassist enhancement failed on deserializing hibernate proxies --------------------------------------------------------------- Key: JASSIST-28 URL: http://jira.jboss.com/jira/browse/JASSIST-28 Project: Javassist Issue Type: Bug Environment: hibernate 3.2.0GA, javassist 3.3, jboss 4.0.4GA Reporter: Armin Haaf Assigned To: Shigeru Chiba on deserializing objects load by hibernate on a jbossas with uninitialized proxies we the following exception on a performance/concurrent testing: Exception in thread "Thread-7" org.hibernate.HibernateException: Javassist Enhancement failed: de.mueller.wms.base.model.impl.StorageImpl at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.getProxy(JavassistLazyInitializer.java:88) at org.hibernate.proxy.pojo.javassist.SerializableProxy.readResolve(SerializableProxy.java:54) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1033) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1728) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:122) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128) at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66) at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) at $Proxy2.executeCommand(Unknown Source) at de.mueller.wms.base.service.JndiRemoteLookupDelegateImpl$CommandExecutionInvocationHandler.invoke(JndiRemoteLookupDelegateImpl.java:57) at $Proxy1.changeStock(Unknown Source) at de.mueller.wms.base.TestJBossPerformance$1.run(TestJBossPerformance.java:58) Caused by: java.lang.RuntimeException: by java.lang.LinkageError: duplicate class definition: de/mueller/wms/base/model/impl/StorageImpl_$$_javassist_1272 at javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:174) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.getProxy(JavassistLazyInitializer.java:79) ... 44 more Caused by: javassist.CannotCompileException: by java.lang.LinkageError: duplicate class definition: de/mueller/wms/base/model/impl/StorageImpl_$$_javassist_1272 at javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:167) at javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:170) ... 45 more Caused by: java.lang.LinkageError: duplicate class definition: de/mueller/wms/base/model/impl/StorageImpl_$$_javassist_1272 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:159) ... 46 more The performance is also very bad in comparison with cglib proxies (in our performance test with cglib proxies the test runs 3x faster) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

5
33
0 / 0

[JBoss JIRA] Created: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node

by Brian Stansberry (JIRA)

Use InvocationContext to avoid multiple searches for a node ----------------------------------------------------------- Key: JBCACHE-811 URL: http://jira.jboss.com/jira/browse/JBCACHE-811 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani When an interceptor finds a node, why not throw it in the InvocationContext or something similar and pass it through the stack that way? Subsequent calls to find the node can check the context first before walking the cache tree. Saves redundant walking of the tree. We'd need to think very carefully about this, as it exposes 2 paths to access a node -- from a thread's context and from the tree. Need to ensure concurrent threads always access the same node object for a given Fqn. (Side thought -- perhaps disable this for weak isolation levels where the locking behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same Fqn). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
11
0 / 0

[JBoss JIRA] Created: (JBWEB-68) Servlet.init(ServletConfig) not called

by Thomas Diesler (JIRA)

Servlet.init(ServletConfig) not called -------------------------------------- Key: JBWEB-68 URL: http://jira.jboss.com/jira/browse/JBWEB-68 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Remy Maucherat <componentref name="apache-tomcat" version="6.0-snapshot"/> [tdiesler@tdvaio trunk]$ svn info Path: . URL: https://svn.jboss.org/repos/jbossas/trunk Repository Root: https://svn.jboss.org/repos/jbossas Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1 Revision: 55837 Node Kind: directory Schedule: normal Last Changed Author: rrajesh Last Changed Rev: 55837 Last Changed Date: 2006-08-11 22:26:36 +0200 (Fri, 11 Aug 2006) <servlet> <servlet-name>TestService</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.endpoint.EndpointServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007