December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1755) TP: dropping message to wrong destination in a shared transport

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1755?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1755 at 12/23/13 4:00 AM: ---------------------------------------------------------- Note that this only occurs when a *shared transport is used*. Hmm, the {{LEAVE_RSP}} *is* actually received quickly, so the question is why the coordinator keeps resending it. Perhaps the leaver hasn't yet acked it ? was (Author: belaban): Hmm, the {{LEAVE_RSP}} *is* actually received quickly, so the question is why the coordinator keeps resending it. Perhaps the leaver hasn't yet acked it ? > TP: dropping message to wrong destination in a shared transport > --------------------------------------------------------------- > > Key: JGRP-1755 > URL: https://issues.jboss.org/browse/JGRP-1755 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4.2, 3.5 > > Attachments: bla3.java, shared.xml > > > TP has a check whether the dest of incoming unicast messages matches its local address (or the local address in the ProtocolAdapter if a shared transport is used). Messages whose dest != local address are dropped. > However, in the following scenario, we can have spurious warnings for 2 minutes (by default): > * 2 processes with 2 members on a shared transport each (see attached shared.xml and bla3.java) > ** Start 2 bla2 instances on the same box > * On the second instance, a member leaves and immediately rejoins (press [2] on the second member) > * For some reason, the leaving member didn't receive the {{LEAVE_RSP}} unicast message from the coordinator (first member) > * The newly joined member now receives the {{LEAVE_RSP}} unicast from the coordinator, but now it is a different member and therefore has a different local address, so we see the warning > * This will continue for 2 minutes, until the connection to the unknown member is closed by the coordinator (configurable) > TODOs: > * Investigate why the {{LEAVE_RSP}} unicast is not received by the leaving member > * In the warning, add the sender's address and print the headers of the message so it's easier to find the culprit -- 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
0
0 / 0

[JBoss JIRA] (WFLY-2680) java:comp/DefaultDataSource doesn't work in persistence.xml

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-2680?page=com.atlassian.jira.plugin.... ] jaikiran pai updated WFLY-2680: ------------------------------- Assignee: David Lloyd Affects Version/s: 8.0.0.CR1 Component/s: EE JPA / Hibernate > java:comp/DefaultDataSource doesn't work in persistence.xml > ----------------------------------------------------------- > > Key: WFLY-2680 > URL: https://issues.jboss.org/browse/WFLY-2680 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EE, JPA / Hibernate > Affects Versions: 8.0.0.CR1 > Reporter: arjan tijms > Assignee: David Lloyd > Labels: javaee7, jdbc > > Having a persistence.xml with the following content fails the deployment on WildFly 8 CR1: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd"> > > <persistence-unit name="testPU"> > <jta-data-source>java:comp/DefaultDataSource</jta-data-source> > </persistence-unit> > </persistence> > {code} > It results in the following error: > {noformat} > 13:51:40,367 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "dynamic-named-query.war")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"dynamic-named-query.war#testPU\".__FIRST_PHASE__ is missing [jboss.naming.context.java.module.dynamic-named-query.dynamic-named-query.DefaultDataSource]"]} > {noformat} > When I proposed the feature for the default data source over at the Java EE JIRA (https://java.net/jira/browse/JAVAEE_SPEC-4) I intended this to work. In the description I hinted that the standard JNDI name would be the standard alternative for {{java:jboss/datasources/ExampleDS}} on JBoss. The latter indeed does work in {{persistence.xml}} using WildFly 8 CR1. > Omitting the {{jta-data-source}} element altogether *does* work, which is great. However, I foresee a lot of users tripping over this in the future and just giving up the idea of using a default data source, especially since the error message is very cryptic for new developers. > In GlassFish 4 using {{java:comp/DefaultDataSource}} in {{persistence.xml}} does work. > See also WFLY-2027 and WFLY-2158 -- 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
0
0 / 0

[JBoss JIRA] (SECURITY-769) Initialize AbstractServerLoginModule#validOptions with correct size

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/SECURITY-769?page=com.atlassian.jira.plug... ] Philippe Marschall updated SECURITY-769: ---------------------------------------- Fix Version/s: PicketBox_4_0_20.Final > Initialize AbstractServerLoginModule#validOptions with correct size > ------------------------------------------------------------------- > > Key: SECURITY-769 > URL: https://issues.jboss.org/browse/SECURITY-769 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JBossSX > Reporter: Philippe Marschall > Assignee: Stefan Guilhen > Fix For: PicketBox_4_0_20.Final > > > {{AbstractServerLoginModule#validOptions}} is initialized with the default {{HashSet}} size (which is the default {{HashMap}}) size. However since it's lazily initialized in {{addValidOptions}} and we have the valid module options there we know what the right size will be. -- 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
0
0 / 0

[JBoss JIRA] (SECURITY-769) Initialize AbstractServerLoginModule#validOptions with correct size

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/SECURITY-769?page=com.atlassian.jira.plug... ] Philippe Marschall resolved SECURITY-769. ----------------------------------------- Resolution: Done Pull request has been merged. > Initialize AbstractServerLoginModule#validOptions with correct size > ------------------------------------------------------------------- > > Key: SECURITY-769 > URL: https://issues.jboss.org/browse/SECURITY-769 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JBossSX > Reporter: Philippe Marschall > Assignee: Stefan Guilhen > Fix For: PicketBox_4_0_20.Final > > > {{AbstractServerLoginModule#validOptions}} is initialized with the default {{HashSet}} size (which is the default {{HashMap}}) size. However since it's lazily initialized in {{addValidOptions}} and we have the valid module options there we know what the right size will be. -- 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
0
0 / 0

[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-2533: ------------------------------ Comment: was deleted (was: Vielen Dank für Ihre Nachricht. Ich bin aktuell nicht im Büro und werde am Montag, den 13. Januar 2014 zurückkehren. Nachrichten die eine Antwort benötigen werde ich dann beantworten. Markus Karnik === Thank you for your email. I am away from the office and will return on Monday, January 13, 2014. If your message requires a reply, I will respond when I return. Markus Karnik ) > Add ability to set default character encoding on a subsystem level > ------------------------------------------------------------------ > > Key: WFLY-2533 > URL: https://issues.jboss.org/browse/WFLY-2533 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Stuart: the charset one should be pretty simple, just an attribute on <servlet-container? > Stuart: ideally we would also have it in jboss-web.xml as well > Stuart: I should also add an option to use the connector encoding > Stuart: as connectors have their own encoding set > Stuart: that is used to decode the URL > Stuart: we should have an option to use the connector encoding as the default encoding -- 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
0
0 / 0

[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level

by Markus Karnik (JIRA)

[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ] Markus Karnik commented on WFLY-2533: ------------------------------------- Vielen Dank für Ihre Nachricht. Ich bin aktuell nicht im Büro und werde am Montag, den 13. Januar 2014 zurückkehren. Nachrichten die eine Antwort benötigen werde ich dann beantworten. Markus Karnik === Thank you for your email. I am away from the office and will return on Monday, January 13, 2014. If your message requires a reply, I will respond when I return. Markus Karnik > Add ability to set default character encoding on a subsystem level > ------------------------------------------------------------------ > > Key: WFLY-2533 > URL: https://issues.jboss.org/browse/WFLY-2533 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Stuart: the charset one should be pretty simple, just an attribute on <servlet-container? > Stuart: ideally we would also have it in jboss-web.xml as well > Stuart: I should also add an option to use the connector encoding > Stuart: as connectors have their own encoding set > Stuart: that is used to decode the URL > Stuart: we should have an option to use the connector encoding as the default encoding -- 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
0
0 / 0

[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-2533: ----------------------------------- Yes it was bug in parser, not sure how I missed that. Added a test to address that. PR with a fix https://github.com/wildfly/wildfly/pull/5651 > Add ability to set default character encoding on a subsystem level > ------------------------------------------------------------------ > > Key: WFLY-2533 > URL: https://issues.jboss.org/browse/WFLY-2533 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Stuart: the charset one should be pretty simple, just an attribute on <servlet-container? > Stuart: ideally we would also have it in jboss-web.xml as well > Stuart: I should also add an option to use the connector encoding > Stuart: as connectors have their own encoding set > Stuart: that is used to decode the URL > Stuart: we should have an option to use the connector encoding as the default encoding -- 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
0
0 / 0

[JBoss JIRA] (JBASM-43) jsch object can not be created

by ali ahmed (JIRA)

ali ahmed created JBASM-43: ------------------------------ Summary: jsch object can not be created Key: JBASM-43 URL: https://issues.jboss.org/browse/JBASM-43 Project: JBoss AS Server Manager Issue Type: Bug Reporter: ali ahmed Assignee: Shelly McGowan create a singleton ejb that contains a scheduler method which tries to create Jsch object (to create a session to list directories). the debug hangs and no exception is thrown. tried using of jsch-0.1.40 and jsch-0.1.50 and same result -- 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
0
0 / 0

[JBoss JIRA] (EJBTHREE-2302) When using Weld the backing EJB is called 27 times.

by Robb Greathouse (JIRA)

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-364) ClasspathKieProject fails vfs: path for jar deployments and exploded ear

by Nicolas-Xavier Vanderlinden (JIRA)

[ https://issues.jboss.org/browse/DROOLS-364?page=com.atlassian.jira.plugin... ] Nicolas-Xavier Vanderlinden updated DROOLS-364: ----------------------------------------------- Environment: JBoss AS 7.1.1 > ClasspathKieProject fails vfs: path for jar deployments and exploded ear > ------------------------------------------------------------------------ > > Key: DROOLS-364 > URL: https://issues.jboss.org/browse/DROOLS-364 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Environment: JBoss AS 7.1.1 > Reporter: Nicolas-Xavier Vanderlinden > Assignee: Mark Proctor > > Drools is not able to load kmodule.xml from an exploded ear. > 17:24:45,116 WARN Unable to load pom.properties tried recursing down from\Project\Geline\jboss-as-7.1.1.Final\standalone\deployments\geline.ear\service-impl-1.4.0-SNAPcontent > null > 17:24:45,116 ERROR Unable to build index of kmodule.xml url=vfs:/E:/Project/Geline/jboss-as-7.1.1.Final/standalone/deployments/geline.ear/service-impl-1.4.0-SNAPSHOT.jar/META-INF/kmodule.xml > null -- 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
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2013