December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1116) Clustered container sees requests during shutdown

by Brian Stansberry (JIRA)

Clustered container sees requests during shutdown ------------------------------------------------- Key: EJBTHREE-1116 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1116 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.2.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=123677 -- during undeploy the cache is being asked for beans after it has already gone into cleanup. It should not be exposed to requests at this point. A couple points: 1) StatefulContainer.stop() does this: if (cache != null) cache.stop(); super.stop(); Basically the cache is stopped before anything else. 2) The HA versions of the old detached invokers included this kind of logic in invoke(): HATarget target = (HATarget)beanMap.get(invocation.getObjectName()); if (!target.invocationsAllowed ()) throw new GenericClusteringException(GenericClusteringException.COMPLETED_NO, "invocations are currently not allowed on this target"); .... else continue on and handle call An HA proxy will catch the GenericClusteringException and fail over. There is no equivalent interceptor in EJB3. In the container stop() methods there is a usage of Dispatcher.singleton.unregisterTarget(...) which will lead to an exception being thrown if a call comes in for the container, and an HA proxy will catch that exception and fail over. So, adding an interceptor to check the HATarget *may* not be necessary, if we are sure that Dispatcher.singleton.unregisterTarget(...) is always called very early in the stop() process. -- 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

16 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1757) Update workflow chapter as it doesn't take into account the fact that the workflow service has been extracted... Should also document how to use the service in portlets.

by Chris Laprun (JIRA)

Update workflow chapter as it doesn't take into account the fact that the workflow service has been extracted... Should also document how to use the service in portlets. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1757 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1757 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun -- 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

16 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1726) Failed status of service factories is not always properly managed.

by Chris Laprun (JIRA)

Failed status of service factories is not always properly managed. ------------------------------------------------------------------ Key: JBPORTAL-1726 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1726 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.2 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.3 Final, 2.8 Final -- 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

16 years, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWEB-83) When the native libraries are missing it is not possible to use ajp

by Jean-Frederic Clere (JIRA)

When the native libraries are missing it is not possible to use ajp ------------------------------------------------------------------- Key: JBWEB-83 URL: http://jira.jboss.com/jira/browse/JBWEB-83 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.1 GA Environment: Any Reporter: Jean-Frederic Clere Assigned To: Mladen Turk When the ./bin/native/libtcnative-1.so or one of the components of Jboss Web native is missing. The ajp connector is defaulted to a http one: +++ 17:37:05,565 ERROR [AprLifecycleListener] The Apache Tomcat Native library that JBoss Web requires (only the HTTP connector will be available) was not found on the java.library.path: /home/jfclere/TMP/jbossweb-1.0.1.GA/bin/native 17:37:05,636 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080 17:37:05,637 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8009 +++ -- 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

16 years, 2 months

2
2
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

16 years, 2 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

16 years, 2 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

16 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBWEB-75) Contention in ApplicationContext

by Phillip Thurmond (JIRA)

Contention in ApplicationContext -------------------------------- Key: JBWEB-75 URL: http://jira.jboss.com/jira/browse/JBWEB-75 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 4.0.5, Linux, Java 5 Reporter: Phillip Thurmond Assigned To: Mladen Turk I'm seeing some contention inside Tomcat on ApplicationContext.getAttribute() when I run performance tests using a Seam application. With a load of 200 threads, I often see over 150 "waiting to lock" messages on the attributes object. It looks like this contention has already been fixed in Tomcat 6 using the Java 5 concurrent objects. I also posted to the Tomcat development list about this issue, but Remy did not want to fix it because he didn't want to introduce any new dependencies into the project. I think this is important to fix if we expect users to deploy Seam on 4.0.5. Example thread dump: "http-10.68.0.196-8080-301" daemon prio=1 tid=0x0000002b51e425b0 nid=0x78a5 waiting for monitor entry [0x000000005b86c000..0x000000005b86cdb0] at org.apache.catalina.core.ApplicationContext.getAttribute(ApplicationContext.java:175) - waiting to lock <0x0000002aabd633b0> (a java.util.HashMap) at org.apache.catalina.core.ApplicationContextFacade.getAttribute(ApplicationContextFacade.java:315) at org.apache.myfaces.context.servlet.ApplicationMap.getAttribute(ApplicationMap.java:41) at org.apache.myfaces.context.servlet.AbstractAttributeMap.get(AbstractAttributeMap.java:87) at org.jboss.seam.contexts.FacesApplicationContext.get(FacesApplicationContext.java:47) at org.jboss.seam.Component.forName(Component.java:1588) at org.jboss.seam.Component.getInstance(Component.java:1636) at org.jboss.seam.Component.getInstance(Component.java:1631) at org.jboss.seam.Component.getInstance(Component.java:1608) at org.jboss.seam.Component.getInstance(Component.java:1603) at org.jboss.seam.core.Events.instance(Events.java:158) at org.jboss.seam.jsf.AbstractSeamPhaseListener.afterPhase(AbstractSeamPhaseListener.java:139) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:69) -- 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

16 years, 2 months

2
1
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

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWEB-93) JBoss Web 2.0.1

by Remy Maucherat (JIRA)

JBoss Web 2.0.1 --------------- Key: JBWEB-93 URL: http://jira.jboss.com/jira/browse/JBWEB-93 Project: JBoss Web Issue Type: Release Security Level: Public (Everyone can see) Reporter: Remy Maucherat Assigned To: Mladen Turk JBoss Web release mirroring Apache Tomcat 6.0.15. No standalone release, only available integrated with 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

16 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007