November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1539) NAKACK2: xmit_interval sometimes triggers unneeded retransmissions

by Bela Ban (JIRA)

Bela Ban created JGRP-1539: ------------------------------ Summary: NAKACK2: xmit_interval sometimes triggers unneeded retransmissions Key: JGRP-1539 URL: https://issues.jboss.org/browse/JGRP-1539 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.3 In NAKACK2 (and UNICAST2 as well), a timer task kicks in every xmit_interval milliseconds. If we just added a message out of order, then the retransmit task might send a spurious retransmission message. Example: - Messages 1,2,3,4,5 are received at time T0 (in ms) - At time T1000, message 20 is received - At time T1001, the retransmit task kicks in and asks the sender for retransmission of messages [6-19] - At time T1009, messages 6-19 are received Problem: the out-of-order message 20 was received just before the retransmit task kicked in. Has the task waited for another 9 ms (until time T1009), the retransmission would not have been necessary. The underlying cause is that the retransmit tasks handles recently added gaps the same as gaps added before xmit_interval, as we don't maintain a timestamp for added messages. Another reason is also that the message bundler on the sender side might send messages in random order (see link below). SOLUTION: Investigate how to change the retransmission task such that it excludes gaps created within the last xmit_interval ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
7
0 / 0

[JBoss JIRA] (AS7-5639) Run OSGi CT with AS7

by David Bosschaert (JIRA)

[ https://issues.jboss.org/browse/AS7-5639?page=com.atlassian.jira.plugin.s... ] David Bosschaert updated AS7-5639: ---------------------------------- Git Pull Request: https://github.com/jbossas/jboss-as/pull/3427, https://github.com/jbossas/jboss-as/pull/3490 (was: https://github.com/jbossas/jboss-as/pull/3427) > Run OSGi CT with AS7 > -------------------- > > Key: AS7-5639 > URL: https://issues.jboss.org/browse/AS7-5639 > Project: Application Server 7 > Issue Type: Task > Components: OSGi > Reporter: David Bosschaert > Assignee: David Bosschaert > > The OSGi CT is currently run with the JBoss OSGi framework standalone. It should also be possible to run the CT with the AS7 integration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5985) accessing custom created datasources in JBOSS 7.1 in JBoss AS 7

by Srinivas Reddy Bijjam (JIRA)

Srinivas Reddy Bijjam created AS7-5985: ------------------------------------------ Summary: accessing custom created datasources in JBOSS 7.1 in JBoss AS 7 Key: AS7-5985 URL: https://issues.jboss.org/browse/AS7-5985 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Environment: Windows XP and JBoss AS 7.2 Alpha1-SNAPSHOT Reporter: Srinivas Reddy Bijjam Priority: Critical I deployed my application in JBoss AS 7.2.0.Alpha1-SNAPSHOT and under standalone\deployments folders I placed -- test.ear --connector.xml I am getting this exception [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "test.ear" [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "connectors.xml" [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.data-source.java:/dataSource-oraclePool (missing) dependents: [service jboss.deployment.subunit."test.ear"."testcmp.jar".component.DIInstObj.jdbc.store-manager.INIT, JBAS014799: ... and 53 more ] My database configuration in standalone-full.xml <subsystem xmlns="urn:jboss:domain:datasources:1.1"> <datasources> <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true"> <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url> <driver>h2</driver> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> <drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> <driver name="ojdbc6" module="com.oracle.ojdbc6"> <driver-class>oracle.jdbc.OracleDriver</driver-class> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class> </driver> <driver name="sqljdbc4" module="com.sqlServer.jdbc"> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class> </driver> </drivers> </datasources> </subsystem> connector-ds.xml ?xml version="1.0" encoding="UTF-8"?> <datasources> <xa-datasource enabled="true" jndi-name="java:/dataSource-oraclePool" pool-name="dataSource-oraclePool" type="javax.sql.DataSource" use-java-context="true"> <xa-datasource-property name="URL">jdbc:oracle:thin:@localhost:1521:orcl</xa-datasource-property> <driver>ojdbc6</driver> <xa-pool> <min-pool-size>1</min-pool-size> <max-pool-size>20</max-pool-size> <prefill>true</prefill> <is-same-rm-override>false</is-same-rm-override> <no-tx-separate-pools>true</no-tx-separate-pools> </xa-pool> <security> <user-name>test</user-name> <password>test</password> </security> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class> </xa-datasource> </datasources> my jboss-deployment-structure.xml <jboss-deployment-structure> <ear-subdeployments-isolated>false</ear-subdeployments-isolated> <deployment> <dependencies> <module name="javaee.api" export="true"/> <module name="sun.jdk" export="true"/> <module name="javax.api" export="true"/> <module name="com.oracle.ojdbc6" export="true"/> <module name="com.sqlServer.jdbc" export="true"/> </dependencies> </deployment> </jboss-deployment-structure> Regards Srini -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
10
0 / 0

[JBoss JIRA] (AS7-6015) Session bean target class around-invoke method called before CDI interceptors

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6015?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger reassigned AS7-6015: ------------------------------------ Assignee: Stuart Douglas (was: Jozef Hartinger) > Session bean target class around-invoke method called before CDI interceptors > ----------------------------------------------------------------------------- > > Key: AS7-6015 > URL: https://issues.jboss.org/browse/AS7-6015 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jozef Hartinger > Assignee: Stuart Douglas > Labels: cdi11, tck11 > Fix For: 7.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6015) Session bean target class around-invoke method called before CDI interceptors

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6015?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger commented on AS7-6015: -------------------------------------- Added testcase org.jboss.as.test.integration.weld.interceptor.ordering.SessionBeanInterceptorOrderingTest https://github.com/jbossas/jboss-as/pull/3488 https://github.com/jbossas/jboss-as/pull/3489 > Session bean target class around-invoke method called before CDI interceptors > ----------------------------------------------------------------------------- > > Key: AS7-6015 > URL: https://issues.jboss.org/browse/AS7-6015 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Labels: cdi11, tck11 > Fix For: 7.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6015) Session bean target class around-invoke method called before CDI interceptors

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6015?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger updated AS7-6015: --------------------------------- Summary: Session bean target class around-invoke method called before CDI interceptors (was: Around-invoke method of the target class should be called after all other interceptors) > Session bean target class around-invoke method called before CDI interceptors > ----------------------------------------------------------------------------- > > Key: AS7-6015 > URL: https://issues.jboss.org/browse/AS7-6015 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Labels: cdi11, tck11 > Fix For: 7.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6015) Around-invoke method of the target class should be called after all other interceptors

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6015?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger moved WELD-1244 to AS7-6015: -------------------------------------------- Project: Application Server 7 (was: Weld) Key: AS7-6015 (was: WELD-1244) Issue Type: Bug (was: Task) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.3.Final (EAP) (was: 2.0.0.Alpha3) Component/s: CDI / Weld EJB (was: Interceptors and Decorators) Fix Version/s: 7.2.0.Alpha1 (was: 2.0.0.Beta1) > Around-invoke method of the target class should be called after all other interceptors > -------------------------------------------------------------------------------------- > > Key: AS7-6015 > URL: https://issues.jboss.org/browse/AS7-6015 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Labels: cdi11, tck11 > Fix For: 7.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5652) POJO subsytem isn't setting the TCCL to the application's class loader

by Michael Vetter (JIRA)

Michael Vetter created AS7-5652: ----------------------------------- Summary: POJO subsytem isn't setting the TCCL to the application's class loader Key: AS7-5652 URL: https://issues.jboss.org/browse/AS7-5652 Project: Application Server 7 Issue Type: Bug Components: POJO Affects Versions: 7.2.0.Alpha1 Reporter: Michael Vetter Assignee: Ales Justin The POJO subsytem isn't setting the TCCL (Thread.currentThread().getContextClassLoader()) to the application's class loader while invoking on the application's lifecycle methods. The TCCL is set to the "ModuleClassLoader for Module "org.jboss.as.pojo:main" from local module loader". It was working in JBoss5.1 to start a bean with an xml file (<deployment xmlns="urn:jboss:bean-deployer:2.0"> ...) and to use the TCCL during deployment to load resources and classes from the ear. With the pojo ModuleClassLoader these resources are not found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
6
0 / 0

[JBoss JIRA] (AS7-6009) JBAS018040: Failed to start context

by B K (JIRA)

B K created AS7-6009: ------------------------ Summary: JBAS018040: Failed to start context Key: AS7-6009 URL: https://issues.jboss.org/browse/AS7-6009 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Environment: Redhat Linux 4 (??). Kernel version is: 2.6.18-194.26.1.el5 Reporter: B K Assignee: Heiko Braun The error found in the server log files was: 13:58:40,009 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.web.deployment.default-host./apex: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./apex: JBAS018040: Failed to start context Occurence details: 1. The issue occured following a restart of the application server Analysis details: 1. From the perspective of the JBOSS 7 admin console ... the admin console shows that the "apex.war" application is deployed and "enabled". I believe it should not display "enabled" as the context has failed to start and it is only capable of servicing requests. Details to reproduce: 1. Download Oracle Apex Listener 1.1.4 from: http://www.oracle.com/technetwork/developer-tools/apex-listener/downloads... 2. Unzip the war file e.g jar xvf apex.war 3. Modify the web.xml by adding: <context-param> <param-name>config.dir</param-name> <param-value>/opt/jboss/apex_config_dir</param-value> </context-param> 4. Create the path "/opt/jboss/apex_config_dir". 5. Zip the war file. cd locationContaining the Web-INF directory jar cvf apex.war * 6. Deploy war file and enable via admin console. Stop Server. Start server. 7. Exception occurs. NOTE: there could be an additional step to reproduce. Will detail if above does not work. NOTE2: I can redeploy the above application and get it working again by removing some files that are auto generated by apex.war (so a partial bit of this issue is probably application related). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (SECURITY-638) The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or

by Tom Fonteyne (Created) (JIRA)

The login modules need to be modified to check for (complain about) configuration options that have been specified but are not used (invalid, unrecognized, etc). This might be helpful in catching situations where the option name was spelled incorrectly or --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SECURITY-638 URL: https://issues.jboss.org/browse/SECURITY-638 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: JBossSecurity_2.0.4.SP9 Reporter: Tom Fonteyne Assignee: Anil Saldhana Priority: Minor Fix For: JBossSecurity_2.0.4.SP9 porting https://issues.jboss.org/browse/JBPAPP-7794 to PicketBox -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012