[JBoss JIRA] (JGRP-1919) SimpleChat example doesn't work
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/JGRP-1919?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on JGRP-1919:
---------------------------------------
I think this can be closed as out of date? The OSX routing issues do not apply since version 3.7
> SimpleChat example doesn't work
> -------------------------------
>
> Key: JGRP-1919
> URL: https://issues.jboss.org/browse/JGRP-1919
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.2
> Reporter: rama rama
> Assignee: Bela Ban
> Fix For: 3.4.8
>
>
> Hello,
> i have try to run SimpleChat.java class (provided on example) but it doesn't work... with version 3.6.2 i run two java but they doesn't 'connect' eachother..
> i got this error (if i use ipv4 the error persist, it change only the fact that is an ipv4 ip)
> ----
> WARNING: JGRP000034: iMac-di-Rama-78: failure sending message to /ff0e:0:0:0:0:8:8:8: java.io.IOException: No route to host
> ----
> version 3.4.8 isn't affected, and two process
> runned with this version connect and i can see the messages.
> Also, no error is displayed on 3.4.8
> just to avoid misunderstanding
> 1. i have read the other 'similar' message
> 2. i have try
> java org.jgroups.tests.McastReceiverTest +
> java org.jgroups.tests.McastSenderTest
> and work
> 3. i have try to use ipv4 and jgroups.bind_addr props
> what is strange is that with 3.4.8 the example work out of the box.
> os: osx
> java: 1.7.0_76
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6377) Composite Keys -- org.hibernate.property.access.spi.PropertyAccessException: Error accessing field
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-6377?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-6377:
------------------------------------
Did you also create a [https://hibernate.atlassian.net/browse/HHH] jira? This sounds to me like it needs a HHH jira.
[~gbadner] what do you think?
> Composite Keys -- org.hibernate.property.access.spi.PropertyAccessException: Error accessing field
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-6377
> URL: https://issues.jboss.org/browse/WFLY-6377
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Environment: Mac OSX, Wildfly 10.0, Hibernate 5.0/5.1, PostgreSQL 9.3
> Reporter: Akhbar Falafel
> Assignee: Scott Marlow
>
> I have 2 entity classes mapped in Hibernate 5.1: ProductBean and CommentBean. They are pretty simple, and look something like this...
> {code:java}
> @Entity(name = "Comment")
> @Table(name = "tbl_comment")
> public class CommentBean implements Serializable {
> @Id
> @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "seq_comment_id")
> @SequenceGenerator(name = "seq_comment_id", sequenceName = "seq_comment_id", allocationSize = 1)
> private Long id = null;
> ...
> }
> @Entity(name = "Product")
> @Table(name = "tbl_product")
> public class CommentBean implements Serializable {
> @Id
> @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "seq_product_id")
> @SequenceGenerator(name = "seq_product_id", sequenceName = "seq_product_id", allocationSize = 1)
> private Long id = null;
> @ManyToMany(cascade = CascadeType.MERGE)
> @JoinTable(name = "tbl_product_comments", joinColumns = {
> @JoinColumn(name = "product_id", referencedColumnName = "id") }, inverseJoinColumns = {
> @JoinColumn(name = "comment_id", referencedColumnName = "id") }, uniqueConstraints = {
> @UniqueConstraint(columnNames = { "product_id", "comment_id" }) })
> @IndexedEmbedded
> @OrderBy(value = "createdDate ASC")
> private Set<CommentBean> comments = new LinkedHashSet<>();
> ...
> }
> {code}
> I'm trying to map the Many-To-Many relation for the comments property in its own class, so that I can add additional properties to the relation in the future. The mapping class looks like this:
> {code:java}
> @Entity(name = "ProductComment")
> @Table(name = "tbl_product_comments")
> public class ProductCommentBean implements Serializable {
> private static final long serialVersionUID = 4730115318809856150L;
> @ManyToOne(optional = false)
> @JoinColumn(name = "productID", referencedColumnName = "id", nullable = false, insertable = false, updatable = false)
> @NotNull
> private ProductBean answer = null;
> @ManyToOne(optional = false)
> @JoinColumn(name = "comment_id", referencedColumnName = "id", nullable = false, insertable = false, updatable = false)
> @NotNull
> private CommentBean comment = null;
> @EmbeddedId
> private ID id = new ID();
> @Embeddable
> public static class ID implements Serializable {
> @Column(name = "product_id")
> private Long productID = null;
> @Column(name = "comment_id")
> private Long commentID = null;
> @Override
> public boolean equals(final Object other) {
> if (this == other) {
> return true;
> }
> if (!(other instanceof ID)) {
> return false;
> }
> ID castOther = (ID) other;
> return new EqualsBuilder().append(productID, castOther. productID).append(commentID, castOther.commentID)
> .isEquals();
> }
> @Override
> public int hashCode() {
> return new HashCodeBuilder(-2081682373, -1619249).append(productID).append(commentID).toHashCode();
> }
> public ID() {
> super();
> // TODO Auto-generated constructor stub
> }
> public ID(Long productID, Long commentID) {
> super();
> this.productID = productID;
> this.commentID = commentID;
> }
> }
> public ProductCommentBean(ProductBean product, CommentBean comment) {
> super();
> this.product = product;
> this.comment = comment;
> this.id.productID =product.getId();
> this.id.commentID = comment.getId();
> }
> }
> ...
> }
> {code}
> Upon my first deployment, I am able to create a ProductCommentBean object and save it to the database successfully. However, if I run a "clean" during development, the subsequent call to save a ProductCommentBean object results in the following exception:
> ISPN000136: Error executing command GetKeyValueCommand, writing keys []: org.hibernate.property.access.spi.PropertyAccessException: Error accessing field [private java.lang.Long com.test.ProductCommentBean$ID.productID] by reflection for persistent property [com.test.ProductCommentBean$ID#productID] : com.test.ProductCommentBean$ID@a8a90e31
> If I do a shutdown and restart of the server, I am once again able to save a ProductCommentBean object the first time. A clean again, however, will set it back to the error state.
> I have tested this code on Wildfly 10 and JBoss EAP 7.0 Beta, and receive the same results. I've also tested it using Hibernate 5.0 and 5.1, also with the same results.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6375) Identify colliding JBoss modules WRT JEP 200, section 6
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-6375?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-6375:
-----------------------------------
Depending on how Jigsaw pans out, we might have to do some special packaging in order to get around this one.
> Identify colliding JBoss modules WRT JEP 200, section 6
> -------------------------------------------------------
>
> Key: WFLY-6375
> URL: https://issues.jboss.org/browse/WFLY-6375
> Project: WildFly
> Issue Type: Sub-task
> Affects Versions: 10.0.0.Final
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> JKD9 with jigsaw throws ClassNotFound exception if we're trying to 'override/enrich' JDK9 exported packages. This is collision with JEP 200, section 6: *A non-standard module must not export any standard API packages. A non-standard module may grant implied readability to a standard module.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6377) Composite Keys -- org.hibernate.property.access.spi.PropertyAccessException: Error accessing field
by Akhbar Falafel (JIRA)
Akhbar Falafel created WFLY-6377:
------------------------------------
Summary: Composite Keys -- org.hibernate.property.access.spi.PropertyAccessException: Error accessing field
Key: WFLY-6377
URL: https://issues.jboss.org/browse/WFLY-6377
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 10.0.0.Final
Environment: Mac OSX, Wildfly 10.0, Hibernate 5.0/5.1, PostgreSQL 9.3
Reporter: Akhbar Falafel
Assignee: Scott Marlow
I have 2 entity classes mapped in Hibernate 5.1: ProductBean and CommentBean. They are pretty simple, and look something like this...
{code:java}
@Entity(name = "Comment")
@Table(name = "tbl_comment")
public class CommentBean implements Serializable {
@Id
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "seq_comment_id")
@SequenceGenerator(name = "seq_comment_id", sequenceName = "seq_comment_id", allocationSize = 1)
private Long id = null;
...
}
@Entity(name = "Product")
@Table(name = "tbl_product")
public class CommentBean implements Serializable {
@Id
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "seq_product_id")
@SequenceGenerator(name = "seq_product_id", sequenceName = "seq_product_id", allocationSize = 1)
private Long id = null;
@ManyToMany(cascade = CascadeType.MERGE)
@JoinTable(name = "tbl_product_comments", joinColumns = {
@JoinColumn(name = "product_id", referencedColumnName = "id") }, inverseJoinColumns = {
@JoinColumn(name = "comment_id", referencedColumnName = "id") }, uniqueConstraints = {
@UniqueConstraint(columnNames = { "product_id", "comment_id" }) })
@IndexedEmbedded
@OrderBy(value = "createdDate ASC")
private Set<CommentBean> comments = new LinkedHashSet<>();
...
}
{code}
I'm trying to map the Many-To-Many relation for the comments property in its own class, so that I can add additional properties to the relation in the future. The mapping class looks like this:
{code:java}
@Entity(name = "ProductComment")
@Table(name = "tbl_product_comments")
public class ProductCommentBean implements Serializable {
private static final long serialVersionUID = 4730115318809856150L;
@ManyToOne(optional = false)
@JoinColumn(name = "productID", referencedColumnName = "id", nullable = false, insertable = false, updatable = false)
@NotNull
private ProductBean answer = null;
@ManyToOne(optional = false)
@JoinColumn(name = "comment_id", referencedColumnName = "id", nullable = false, insertable = false, updatable = false)
@NotNull
private CommentBean comment = null;
@EmbeddedId
private ID id = new ID();
@Embeddable
public static class ID implements Serializable {
@Column(name = "product_id")
private Long productID = null;
@Column(name = "comment_id")
private Long commentID = null;
@Override
public boolean equals(final Object other) {
if (this == other) {
return true;
}
if (!(other instanceof ID)) {
return false;
}
ID castOther = (ID) other;
return new EqualsBuilder().append(productID, castOther. productID).append(commentID, castOther.commentID)
.isEquals();
}
@Override
public int hashCode() {
return new HashCodeBuilder(-2081682373, -1619249).append(productID).append(commentID).toHashCode();
}
public ID() {
super();
// TODO Auto-generated constructor stub
}
public ID(Long productID, Long commentID) {
super();
this.productID = productID;
this.commentID = commentID;
}
}
public ProductCommentBean(ProductBean product, CommentBean comment) {
super();
this.product = product;
this.comment = comment;
this.id.productID =product.getId();
this.id.commentID = comment.getId();
}
}
...
}
{code}
Upon my first deployment, I am able to create a ProductCommentBean object and save it to the database successfully. However, if I run a "clean" during development, the subsequent call to save a ProductCommentBean object results in the following exception:
ISPN000136: Error executing command GetKeyValueCommand, writing keys []: org.hibernate.property.access.spi.PropertyAccessException: Error accessing field [private java.lang.Long com.test.ProductCommentBean$ID.productID] by reflection for persistent property [com.test.ProductCommentBean$ID#productID] : com.test.ProductCommentBean$ID@a8a90e31
If I do a shutdown and restart of the server, I am once again able to save a ProductCommentBean object the first time. A clean again, however, will set it back to the error state.
I have tested this code on Wildfly 10 and JBoss EAP 7.0 Beta, and receive the same results. I've also tested it using Hibernate 5.0 and 5.1, also with the same results.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFCORE-1435) Users with low privileges can see logged operations they shouldn't be able to see
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1435?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet moved JBEAP-3835 to WFCORE-1435:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1435 (was: JBEAP-3835)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.1.0.CR1
(was: 7.0.0.ER6)
> Users with low privileges can see logged operations they shouldn't be able to see
> ---------------------------------------------------------------------------------
>
> Key: WFCORE-1435
> URL: https://issues.jboss.org/browse/WFCORE-1435
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.1.0.CR1
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
> Priority: Critical
>
> If a SuperUser performs for example this:
> {noformat}
> /core-service=management/access=audit/in-memory-handler=y:add
> /core-service=management/access=audit/in-memory-handler=y:write-attribute(name=max-history,value=50)
> {noformat}
> then a Monitor user shouldn't be able to see this in the configuration change log (as decided in EAP7-89), because he doesn't even have the permission to "read" the manipulated resource.. But actually he can see it:
> {noformat}
> /core-service=management/service=configuration-changes:list-changes
> {
> "outcome" => "success",
> "result" => [
> {
> "operation-date" => "2016-03-15T08:40:25.807Z",
> "access-mechanism" => "NATIVE",
> "remote-address" => "127.0.0.1/127.0.0.1",
> "outcome" => "success",
> "operations" => [{
> "operation" => "write-attribute",
> "address" => [
> ("core-service" => "management"),
> ("access" => "audit"),
> ("in-memory-handler" => "y")
> ]
> }]
> },
> {
> "operation-date" => "2016-03-15T08:40:25.809Z",
> "access-mechanism" => "NATIVE",
> "remote-address" => "127.0.0.1/127.0.0.1",
> "outcome" => "success",
> "operations" => [{
> "operation" => "add",
> "address" => [
> ("core-service" => "management"),
> ("access" => "audit"),
> ("in-memory-handler" => "y")
> ]
> }]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6376) Class loader leak due to Infinispan ExpirationManagerImpl
by Harald Wellmann (JIRA)
Harald Wellmann created WFLY-6376:
-------------------------------------
Summary: Class loader leak due to Infinispan ExpirationManagerImpl
Key: WFLY-6376
URL: https://issues.jboss.org/browse/WFLY-6376
Project: WildFly
Issue Type: Bug
Components: Clustering, JPA / Hibernate
Affects Versions: 10.0.0.Final
Reporter: Harald Wellmann
Assignee: Paul Ferraro
h3. Scenario
Given a WAR containing a persistence unit with second level cache and query cache enabled, I'm consistently hitting a Metaspace OutOfMemoryError after redeploying the unchanged application a couple of times.
Analyzing the situation with Eclipse Memory Analyzer, I found one cause to be WFLY-6348, but even after applying that fix locally, I'm still having a Classloader leak which I can trace to a thread used by Infinispan referencing an obsolete web app classloader as context classloader.
Just to rule out that this might be related to WFLY-6283, WFLY-6285, I repeated my experiments with a local build of WildFly master (2f11a59aee0dbdd52b65c5c684eafa83c3f418da), with Hibernate locally upgraded to 5.0.9.
I'm still getting a classloader leak with that build.
h3. Analysis
{{org.infinispan.expiration.impl.ExpirationManagerImpl}} uses a {{LazyInitializingScheduledExecutorService}}. Due to lazy initialization, the {{ExecutorService}} and the underlying thread pool is not created until my web app is deployed. Thus, when the {{ExecutorService}} is created, the context class loader is set to the web app class loader, and this appears to propagate to the threads of the executor thread pool.
When the application is undeployed, {{ExpirationManagerImpl.stop()}} gets invoked to cancel any running expiration task. However, the {{ExecutorService}} is not shut down, the threads remain alive and still keep a reference to the now obsolete context classloader.
h3. Remarks
I'm not sure if this analysis is correct, at least I hope there's a clue for WildFly and Infinispan experts to identify the real cause.
By the way, it would be helpful if all threads created by Infinispan had meaningful names, rather than default names like {{pool-5-thread-1}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6375) Identify colliding JBoss modules WRT JEP 200, section 6
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6375?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on WFLY-6375:
--------------------------------------
After detailed analysis I identified the following jars colliding with JEP 200, section 6:
{code}
JDK9 Module -> Colliding JBoss Module (see http://openjdk.java.net/jeps/200, section 6)
------------------------------------------------------------------------------------------------------
[java.transaction] -> javax/transaction/api/main/jboss-transaction-api_1.2_spec-1.0.0.Final.jar
[java.annotations.common] -> javax/annotation/api/main/jboss-annotations-api_1.2_spec-1.0.0.Final.jar
[java.activation] -> javax/activation/api/main/activation-1.1.1.jar
[java.xml.bind] -> javax/xml/bind/api/main/jboss-jaxb-api_2.2_spec-1.0.4.Final.jar
[java.xml.ws] -> javax/xml/soap/api/main/jboss-saaj-api_1.3_spec-1.0.3.Final.jar
[java.xml.ws] -> javax/xml/ws/api/main/jboss-jaxws-api_2.2_spec-2.0.2.Final.jar
[java.xml.ws] -> javax/jws/api/main/jsr181-api-1.0-MR1.jar
[java.corba] -> javax/orb/api/main/openjdk-orb-8.0.5.Final.jar
[java.corba] -> javax/orb/api/main/openjdk-orb-8.0.5.Final.jar
[java.corba] -> javax/orb/api/main/openjdk-orb-8.0.5.Final.jar
{code}
> Identify colliding JBoss modules WRT JEP 200, section 6
> -------------------------------------------------------
>
> Key: WFLY-6375
> URL: https://issues.jboss.org/browse/WFLY-6375
> Project: WildFly
> Issue Type: Sub-task
> Affects Versions: 10.0.0.Final
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> JKD9 with jigsaw throws ClassNotFound exception if we're trying to 'override/enrich' JDK9 exported packages. This is collision with JEP 200, section 6: *A non-standard module must not export any standard API packages. A non-standard module may grant implied readability to a standard module.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6375) Identify colliding JBoss modules WRT JEP 200, section 6
by Richard Opalka (JIRA)
Richard Opalka created WFLY-6375:
------------------------------------
Summary: Identify colliding JBoss modules WRT JEP 200, section 6
Key: WFLY-6375
URL: https://issues.jboss.org/browse/WFLY-6375
Project: WildFly
Issue Type: Sub-task
Affects Versions: 10.0.0.Final
Reporter: Richard Opalka
Assignee: Richard Opalka
JKD9 with jigsaw throws ClassNotFound exception if we're trying to 'override/enrich' JDK9 exported packages. This is collision with JEP 200, section 6: *A non-standard module must not export any standard API packages. A non-standard module may grant implied readability to a standard module.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ELY-453) SecurityDomain enhancement to transform SecurityIdentity after login
by David Lloyd (JIRA)
David Lloyd created ELY-453:
-------------------------------
Summary: SecurityDomain enhancement to transform SecurityIdentity after login
Key: ELY-453
URL: https://issues.jboss.org/browse/ELY-453
Project: WildFly Elytron
Issue Type: Feature Request
Components: API / SPI
Reporter: David Lloyd
Fix For: 1.1.0.Beta5
Security domains need to be able to transform a SecurityIdentity before handing it to the caller, in order to add (e.g.) a PeerIdentity for PicketBox integration, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month