August 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-1008) Socket keep alive with client EJB and RMI over HTTP

by amar slimane (JIRA)

Socket keep alive with client EJB and RMI over HTTP --------------------------------------------------- Key: JBREM-1008 URL: http://jira.jboss.com/jira/browse/JBREM-1008 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.4.0.CR2 (Pinto) Environment: CentOS release 4.4 (Final) Reporter: amar slimane With the parameter 'invokerDestructionDelay', the same socket connection is reused for all client requests to the Server. This works fine with the socket transport but not with HTTP transport. The parameter 'invokerDestructionDelay' is taken into account and the HTTPClientInvoker is not removed but the socket is closed at each call. -- 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, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1712) BRMS popup window disappears when clicking on browser scrollbars

by Seegler Ittyavirah (JIRA)

BRMS popup window disappears when clicking on browser scrollbars ----------------------------------------------------------------- Key: JBRULES-1712 URL: https://jira.jboss.org/jira/browse/JBRULES-1712 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.7 Reporter: Seegler Ittyavirah Assignee: Mark Proctor Resize the browser window so that following steps gives a browser scrollbar Click on new package icon, select import from drl file option (this should show scrollbars) Now click on the scrollbars to drag Import drl popup window disappears. -- 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

17 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBASM-10) Release JBASM 0.1.1.GA

by Shelly McGowan (JIRA)

Release JBASM 0.1.1.GA ---------------------- Key: JBASM-10 URL: https://jira.jboss.org/jira/browse/JBASM-10 Project: JBoss AS Server Manager Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 0.1.1.GA Release needed to push out changes documented in JBASM-4 -- 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

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBAOP-620) ClassAdvisor.rebuildInterceptorsFor[Removed/Added]Binding methods do not update deprecated collections

by Flavia Rainone (JIRA)

[ https://jira.jboss.org/jira/browse/JBAOP-620?page=com.atlassian.jira.plug... ] Flavia Rainone updated JBAOP-620: --------------------------------- Summary: ClassAdvisor.rebuildInterceptorsFor[Removed/Added]Binding methods do not update deprecated collections (was: ClassAdvisor.rebuildInterceptorsForRemovedBinding does not update deprecated collections) Description: Those methods must update the deprecated interceptor collections of Advisor. (was: The method must update the deprecated interceptor collections of Advisor.) > ClassAdvisor.rebuildInterceptorsFor[Removed/Added]Binding methods do not update deprecated collections > ------------------------------------------------------------------------------------------------------ > > Key: JBAOP-620 > URL: https://jira.jboss.org/jira/browse/JBAOP-620 > Project: JBoss AOP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Fix For: 2.0.0.GA > > > Those methods must update the deprecated interceptor collections of Advisor. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1447) NPE when calling sessionContext.getCallerIdentity() with JNDILoginInitialContextFactory

by johan micoud (JIRA)

NPE when calling sessionContext.getCallerIdentity() with JNDILoginInitialContextFactory --------------------------------------------------------------------------------------- Key: EJBTHREE-1447 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1447 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: AS 5.0.0.CR1 Environment: Windows & Linux (client & server) Reporter: johan micoud Priority: Critical When using a JNDILoginInitialContextFactory, the security credentials are not propagated and every call to getCallerIdentity raises a NPE This is a regression, the same code works well with beta 2, 3 & 4. see : http://www.jboss.com/index.html?module=bb&op=viewtopic&t=140070 -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1366) state transfer optimisation (with preload, and in memory state transfer)

by Mircea Markus (JIRA)

state transfer optimisation (with preload, and in memory state transfer) ------------------------------------------------------------------------ Key: JBCACHE-1366 URL: http://jira.jboss.com/jira/browse/JBCACHE-1366 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assigned To: Manik Surtani Priority: Minor Fix For: 3.0.0 Optimization can be done in in a configuration where the following are true: - prelaod - in-memory state transfer is enabled - no passivation - a) shared cache loader OR b)fetch persistent state Optimization:during in-memory state transfer frome cache ONE to cache TWO, do not transfer the regions which in cache TWO were set for preloading. a) is shared cache loader is on that these regions will be loaded from the store anyhow, so transfer of these regions is redundant b) the content of these regions will be transfered at persistent state transfer anyway, so again redundancy during in-memory state transfer -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBAS-3343) JCA 1.5 Resource Adapter Config Properties cannot be specified

by Vicky Kak (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3343?page=com.atlassian.jira.plug... ] Vicky Kak resolved JBAS-3343. ----------------------------- Resolution: Done jboss-ra.xml can be used to override the properties as specified in ra.xml . > JCA 1.5 Resource Adapter Config Properties cannot be specified > -------------------------------------------------------------- > > Key: JBAS-3343 > URL: https://jira.jboss.org/jira/browse/JBAS-3343 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.4.GA > Environment: All. > Reporter: Andreas Mueller > Assignee: Vicky Kak > Fix For: JBossAS-5.0.0.CR2 > > Attachments: ra.xml > > > A JCA 1.5 resource adapter might contain config properties in ra.xml. It is not possible in JBoss to override them with -ds.xml file. > For example, here is an excert of SwiftMQ's intraVM ra.xml: > <resourceadapter> > <resourceadapter-class> > com.swiftmq.connector.v15.ResourceAdapterImpl > </resourceadapter-class> > <config-property> > <config-property-name>ProviderURL</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value>smqp://intravm/timeout=10000</config-property-value> > </config-property> > <config-property> > <config-property-name>IntraVM</config-property-name> > <config-property-type>java.lang.Boolean</config-property-type> > <config-property-value>true</config-property-value> > </config-property> > <config-property> > <config-property-name>DebugMode</config-property-name> > <config-property-type>java.lang.Boolean</config-property-type> > <config-property-value>false</config-property-value> > </config-property> > <config-property> > <config-property-name>RouterWorkingDirectory</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value><swiftmq_dir>/scripts/unix</config-property-value> > </config-property> > <config-property> > <config-property-name>ConfigurationFilename</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value>../../config/router1/routerconfig.xml</config-property-value> > </config-property> > It is not possible to overwrite them during deployment. It is only possible to specify the config properties of the ManagedConnectionFactory in -ds.xml. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-315) JBossXB for aspect domain does not set the parentFirst, extends, inheritBindings and inheritDefinitions attributes

by Kabir Khan (JIRA)

JBossXB for aspect domain does not set the parentFirst, extends, inheritBindings and inheritDefinitions attributes ------------------------------------------------------------------------------------------------------------------ Key: JBMICROCONT-315 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-315 Project: JBoss MicroContainer Issue Type: Bug Affects Versions: JBossMC.2.0.0.Beta16 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossMC.2.0.0.CR1 -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1388) benchmark against http://www.xstm.net/

by Mircea Markus (JIRA)

benchmark against http://www.xstm.net/ -------------------------------------- Key: JBCACHE-1388 URL: http://jira.jboss.com/jira/browse/JBCACHE-1388 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Environment: add http://www.xstm.net/ as a product to the cache benchmark framework Reporter: Mircea Markus Assigned To: Manik Surtani -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1382) Investigate use of ExposedBAOS instead of BAOS when marshalling objects

by Manik Surtani (JIRA)

Investigate use of ExposedBAOS instead of BAOS when marshalling objects ----------------------------------------------------------------------- Key: JBCACHE-1382 URL: http://jira.jboss.com/jira/browse/JBCACHE-1382 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.2.0.GA, 3.0.0 >From Bela's email: "At least in AbstractMarshaller: public byte[] objectToByteBuffer(Object obj) throws Exception { ByteArrayOutputStream baos = new ByteArrayOutputStream(); ObjectOutputStream out = ObjectSerializationFactory.createObjectOutputStream(baos); objectToObjectStream(obj, out); out.close(); return baos.toByteArray(); } Here, an ExposedByteArrayOutputStream instead of a BAOS would prevent the COPY of the byte buffer. We also don't need to be concerned about reentrancy as the output streams are local (stack) variables... Maybe you guys should take a look at all occurrences of BAOS !" -- 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, 11 months

1
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 August 2008