November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8565) Implement managed bean resource ref provider

by jaikiran pai (JIRA)

Implement managed bean resource ref provider -------------------------------------------- Key: JBAS-8565 URL: https://jira.jboss.org/browse/JBAS-8565 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: jaikiran pai Assignee: jaikiran pai -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8425) UrlIntegrationDeployer.undeploy() doesn't remove from classpath

by Stan Silvert (JIRA)

UrlIntegrationDeployer.undeploy() doesn't remove from classpath --------------------------------------------------------------- Key: JBAS-8425 URL: https://jira.jboss.org/browse/JBAS-8425 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.M4 Reporter: Stan Silvert Assignee: Ales Justin When a deployment has more than one instance of UrlIntegrationDeployer, undeploy() will not behave properly. The problem is that INTEGRATION_FLAG_KEY is static: public static final String IS_INTEGRATION_FLAG_KEY = UrlIntegrationDeployer.class.getSimpleName() + "::isIntegrationDeployment"; During undeploy(), the first UrlIntegrationDeployer instance will remove the attachment from the deployment unit. Then when undeploy() is called on other instances of UrlIntegrationDeployer, it will not find the flag and thus skip removeFromClassPath(). It looks like IS_INTEGRATION_FLAG_KEY should be an instance variable instead of static. Perhaps something like this would be an acceptable fix? public final String IS_INTEGRATION_FLAG_KEY = UrlIntegrationDeployer.class.getSimpleName() + "::isIntegrationDeployment" + "::" + hashCode(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2191) StrictMaxPool retains permit on PostConstruct exceptions

by Carlo de Wolf (JIRA)

StrictMaxPool retains permit on PostConstruct exceptions -------------------------------------------------------- Key: EJBTHREE-2191 URL: https://jira.jboss.org/browse/EJBTHREE-2191 Project: EJB 3.0 Issue Type: Bug Components: core Reporter: Carlo de Wolf Priority: Critical Fix For: bom-eap5-1.0.2, depchain-1.0.0 If an EJB uses StrictMaxPool and throws an exception from PostConstruct the permit is never released back to the semaphore, thus limiting the instances that can be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2303) Clustering Seam Application + Drools Serialization error

by Karl Max (JIRA)

Clustering Seam Application + Drools Serialization error -------------------------------------------------------- Key: JBRULES-2303 URL: https://jira.jboss.org/jira/browse/JBRULES-2303 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.0.M1 Environment: Windows Vista, JBoss 5.1.0.GA, Seam 2.2.0.GA, Drools latest version Reporter: Karl Max Assignee: Mark Proctor I would like to use http session replication, but I always get Drools Serialization exception, when the either node is fail over(killed manually), and another node is begin serving the request. If I remove drools settings from components.xml everything works fine, except the security. my drools config in my components.xml: <security:rule-based-permission-resolver security-rules="#{securityRules}" /> <drools:rule-base name="securityRules" > <drools:rule-files> <value>/META-INF/rules/first.drl</value> <value>/META-INF/rules/second.drl</value> </drools:rule-files> </drools:rule-base> and the exception that I get when I stopped the either node, and the other note is begin handle the request 2009-10-13 14:57:18,277 ERROR [org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.SessionBasedJBossCacheService] (ajp-192.168.1.140-8009-1) IOException occurred unmarshalling value java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2281) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280) at org.drools.common.DroolsObjectInputStream.<init>(DroolsObjectInputStream.java:55) at org.drools.common.DroolsObjectInputStream.<init>(DroolsObjectInputStream.java:49) at org.drools.common.AbstractRuleBase.readExternal(AbstractRuleBase.java:232) at org.drools.reteoo.ReteooRuleBase.readExternal(ReteooRuleBase.java:179) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at java.util.HashMap.readObject(HashMap.java:1030) at sun.reflect.GeneratedMethodAccessor304.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at org.jboss.ha.framework.server.SimpleCachableMarshalledValue.get(SimpleCachableMarshalledValue.java:94) at org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.AbstractJBossCacheService.getUnMarshalledValue(AbstractJBossCacheService.java:660) at org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.SessionBasedJBossCacheService.getSessionAttributes(SessionBasedJBossCacheService.java:114) at org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.AbstractJBossCacheService.getDistributableSessionData(AbstractJBossCacheService.java:581) at org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.AbstractJBossCacheService.getSessionData(AbstractJBossCacheService.java:364) at org.jboss.web.tomcat.service.session.JBossCacheManager.loadSession(JBossCacheManager.java:1832) at org.jboss.web.tomcat.service.session.JBossCacheManager.findSession(JBossCacheManager.java:489) at org.apache.catalina.connector.Request.doGetSession(Request.java:2320) at org.apache.catalina.connector.Request.getSessionInternal(Request.java:2239) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:394) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:436) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:384) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-8488) Domain model paths

by Brian Stansberry (JIRA)

Domain model paths ------------------ Key: JBAS-8488 URL: https://jira.jboss.org/browse/JBAS-8488 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 Ability to define paths in the domain model and then refer to them in other model elements. Similar notion to interfaces and socket bindings. Paths can be declared at the domain level but not fully specified: <path name="tmp.dir"/> At the server level they would need to be fully specified. This could be done at the host or server level: <path name="tmp.dir" path="/tmp"/> Paths can reference other paths: <path name="tmp.examples" path="examples" relative-to"tmp.dir"/> The system will some default paths that are not changeable by the user but can be referenced in other paths' "relative-to" attribute or in other model elements, e.g.: jboss.home user.home jboss.server.dir These paths are not changeable by the user because the system needs to know what they are before configuration file parsing can be done. The system will also include some other "standard" paths that can be referenced in other paths' "relative-to" attribute or in other model elements and whose meaning can be changed by the user, e.g.: jboss.server.data.dir jboss.server.log.dir jboss.server.tmp.dir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2664) Soap support in drools-camel

by Lucas Amador (JIRA)

Soap support in drools-camel ---------------------------- Key: JBRULES-2664 URL: https://jira.jboss.org/browse/JBRULES-2664 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Lucas Amador Assignee: Lucas Amador SOAP support is needed in drools-camel to implement it in drools-server -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2546) Fix drools commands inconsistencies

by Lucas Amador (JIRA)

Fix drools commands inconsistencies ----------------------------------- Key: JBRULES-2546 URL: https://jira.jboss.org/browse/JBRULES-2546 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Lucas Amador Assignee: Mark Proctor Priority: Minor Fix inconsistencies on JAXB, XStream & JSON marshalling. Add missing commands annotations -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8184) Object model for domain management

by Brian Stansberry (JIRA)

Object model for domain management ---------------------------------- Key: JBAS-8184 URL: https://jira.jboss.org/browse/JBAS-8184 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 The actual object model that represents the domain model. This is a container task for subtasks related to pieces of the overall model. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8172) Domain schema for M1

by Brian Stansberry (JIRA)

Domain schema for M1 -------------------- Key: JBAS-8172 URL: https://jira.jboss.org/browse/JBAS-8172 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Container task for domain schema design work for elements needed for 7.0.0.M1 Some subtasks may be for subsystems that won't be integrated in M1, but for which schema work should be complete by M1 so integration can proceed quickly after the release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8584) AS7 datasources support

by Stefano Maestri (JIRA)

AS7 datasources support ----------------------- Key: JBAS-8584 URL: https://jira.jboss.org/browse/JBAS-8584 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.0.0.M1 Deploy datasources in AS environment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

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