[JBoss JIRA] (JASSIST-187) Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/JASSIST-187?page=com.atlassian.jira.plugi... ]
Scott Marlow commented on JASSIST-187:
--------------------------------------
Perhaps javassist is being used to lazy fetch the entity (which doesn't require hibernate.ejb.use_class_enhancer persistence to be set)
> Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux
> ---------------------------------------------------------------------------------------
>
> Key: JASSIST-187
> URL: https://issues.jboss.org/browse/JASSIST-187
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.16.0-GA, 3.16.1-GA, 3.17.0-GA
> Environment: Windows 7 x64 Oracle JVM x86/x64 1.6.37 - no error
> Linux Ubuntu x64 Oracle JVM x64 1.6.37 - error
> Reporter: Alexander Zinin
> Assignee: Shigeru Chiba
> Attachments: javassist-test.rar, javassist-test.zip
>
>
> It will be difficult to describe what the error.
> I will attach source code that reproduce error.
> If you have hibernate entity with overrided getId() method, in hibernate session this method returns null instead of correct value.
> Running on Windows:
> 2012-12-16 17:33:19,332 INFO ru.zinin.service.SomeServiceImpl :44 - ID = 1
> Running on Linux:
> 2012-12-16 17:41:47,772 INFO ru.zinin.service.SomeServiceImpl :44 - ID = null
> 2012-12-16 17:41:47,772 ERROR ru.zinin.service.SomeServiceImpl :46 - ID IS NULL!!!
> Bug appeared in version 3.16.0.
--
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, 3 months
[JBoss JIRA] (WFLY-1769) 2 config updates for OpenJDK 8
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1769?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-1769:
------------------------------
Fix Version/s: 8.0.0.Alpha4
> 2 config updates for OpenJDK 8
> ------------------------------
>
> Key: WFLY-1769
> URL: https://issues.jboss.org/browse/WFLY-1769
> Project: WildFly
> Issue Type: Feature Request
> Components: EE
> Reporter: Juergen Zimmermann
> Assignee: David Lloyd
> Fix For: 8.0.0.Alpha4
>
>
> JDK 8 uses the Javascript Engine Nashorn instead of Rhino in JDK 7 (and 6).
> Therefore, 2 additional config lines are required to support JDK 8 in addition to JDK 7:
> After making the following 2 config updates for bean validation my web app is running with WildFly and OpenJDK 8:
> 1) In modules/system/layers/base/sun/jdk/main/module.xml: add the following <path> declaration as the 2nd subtag inside <paths>, i.e. after the "com/sun/script/javascript" for JDK 7:
> {code}
> <path name="jdk/nashorn/api/scripting"/>
> {code}
> 2) In modules/system/layers/base/sun/jdk/main/service-loader-resources/META-INF/services/javax.script.ScriptEngineFactory add the following line as the 2nd service, i.e. as a alternative service for JDK 7:
> {code}
> jdk.nashorn.api.scripting.NashornScriptEngineFactory
> {code}
--
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, 3 months
[JBoss JIRA] (DROOLS-208) Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-208?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet updated DROOLS-208:
------------------------------------
Assignee: Michael Biarnes Kiefer (was: Geoffrey De Smet)
> Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release
> -------------------------------------------------------------------
>
> Key: DROOLS-208
> URL: https://issues.jboss.org/browse/DROOLS-208
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Davide Sottara
> Assignee: Michael Biarnes Kiefer
>
> Requirements:
> 1) All repositories in the 5.6.x repository-list need to be branched from 5.5.x.
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/5.6.x/scrip...
> Note: the repository list is far less than master (so you can safely ignore uberfire etc).
> Warning 1: some repo's are already branched! Do not rebranch these: droolsjbpm-build-bootstrap, droolsjbpm-knowledge, drools
> Warning 2: You need to branch from 5.5.x (NOT master!) to this new branch 5.6.x
> Warning 3: jbpm uses different version numbering. You need to branch from jbpm 5.4.x to 5.5.x (NOT 5.6.x). All other repo's use the normal version.
> 2) All the 5.6.x branches (and 5.5.x for jbpm)'s versions need to change from 5.5.1-SNAPSHOT to 5.6.0-SNAPSHOT (and from 5.4.0-SNAPSHOT to 5.5.0-SNAPSHOT for jbpm).
> Note: droolsjbpm-tools's will need changes from 5.5.1.qualifier to 5.6.0.qualifier
> 3) Create a new jenkins view for "drools 5.6.x and jbpm 5.5.x"
> 4) Clone the 5.5.x jobs for all these repo's as 5.6.x jobs.
--
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, 3 months
[JBoss JIRA] (DROOLS-208) Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-208?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet updated DROOLS-208:
------------------------------------
Description:
Requirements:
1) All repositories in the 5.6.x repository-list need to be branched from 5.5.x.
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/5.6.x/scrip...
Note: the repository list is far less than master (so you can safely ignore uberfire etc).
Warning 1: some repo's are already branched! Do not rebranch these: droolsjbpm-build-bootstrap, droolsjbpm-knowledge, drools
Warning 2: You need to branch from 5.5.x (NOT master!) to this new branch 5.6.x
Warning 3: jbpm uses different version numbering. You need to branch from jbpm 5.4.x to 5.5.x (NOT 5.6.x). All other repo's use the normal version.
2) All the 5.6.x branches (and 5.5.x for jbpm)'s versions need to change from 5.5.1-SNAPSHOT to 5.6.0-SNAPSHOT (and from 5.4.0-SNAPSHOT to 5.5.0-SNAPSHOT for jbpm).
Note: droolsjbpm-tools's will need changes from 5.5.1.qualifier to 5.6.0.qualifier
3) Create a new jenkins view for "drools 5.6.x and jbpm 5.5.x"
4) Clone the 5.5.x jobs for all these repo's as 5.6.x jobs.
> Build 5.6.0-SNAPSHOT on jenkins and prepare for 5.6.0.Final release
> -------------------------------------------------------------------
>
> Key: DROOLS-208
> URL: https://issues.jboss.org/browse/DROOLS-208
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Davide Sottara
> Assignee: Geoffrey De Smet
>
> Requirements:
> 1) All repositories in the 5.6.x repository-list need to be branched from 5.5.x.
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/5.6.x/scrip...
> Note: the repository list is far less than master (so you can safely ignore uberfire etc).
> Warning 1: some repo's are already branched! Do not rebranch these: droolsjbpm-build-bootstrap, droolsjbpm-knowledge, drools
> Warning 2: You need to branch from 5.5.x (NOT master!) to this new branch 5.6.x
> Warning 3: jbpm uses different version numbering. You need to branch from jbpm 5.4.x to 5.5.x (NOT 5.6.x). All other repo's use the normal version.
> 2) All the 5.6.x branches (and 5.5.x for jbpm)'s versions need to change from 5.5.1-SNAPSHOT to 5.6.0-SNAPSHOT (and from 5.4.0-SNAPSHOT to 5.5.0-SNAPSHOT for jbpm).
> Note: droolsjbpm-tools's will need changes from 5.5.1.qualifier to 5.6.0.qualifier
> 3) Create a new jenkins view for "drools 5.6.x and jbpm 5.5.x"
> 4) Clone the 5.5.x jobs for all these repo's as 5.6.x jobs.
--
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, 3 months
[JBoss JIRA] (WFLY-1629) LSB init script for Debian based distros
by Jorge Solorzano (JIRA)
[ https://issues.jboss.org/browse/WFLY-1629?page=com.atlassian.jira.plugin.... ]
Jorge Solorzano closed WFLY-1629.
---------------------------------
> LSB init script for Debian based distros
> ----------------------------------------
>
> Key: WFLY-1629
> URL: https://issues.jboss.org/browse/WFLY-1629
> Project: WildFly
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 8.0.0.Alpha1, 8.0.0.Alpha2, 8.0.0.Alpha3
> Environment: Debian/Ubuntu based
> Reporter: Jorge Solorzano
> Assignee: Brian Stansberry
> Priority: Minor
> Labels: Debian,, Ubuntu, init.d
> Fix For: 8.0.0.Alpha4
>
>
> init.d scripts provided by WildFly are designed for RedHat/Fedora, and it should provide a script that works well in Debian/Ubuntu based distributions.
> I could provide a LSB-compliant init script with all the features required for a complete startup script.
--
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, 3 months
[JBoss JIRA] (JBCLUSTER-300) Upgrade jboss-ha-server-core to use JGroup 3.x
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/JBCLUSTER-300?page=com.atlassian.jira.plu... ]
Paul Ferraro closed JBCLUSTER-300.
----------------------------------
Resolution: Out of Date
The jboss-ha-server-core module is obsolete.
> Upgrade jboss-ha-server-core to use JGroup 3.x
> -----------------------------------------------
>
> Key: JBCLUSTER-300
> URL: https://issues.jboss.org/browse/JBCLUSTER-300
> Project: JBoss Clustering
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: HA-Server-Core
> Affects Versions: HA-Server-Core 1.0.0.Final
> Reporter: Rick Dong
> Assignee: Paul Ferraro
>
> JGroup 3.x is not backward compatible with its 2.x versions. This makes it difficult for projects that is using it and others such as HSearch and Infinispan to upgrade since HSearch 4.x and Infinispan 5.1.x have moved to 3.x while the cluster project is still on 2.x.
--
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, 3 months
[JBoss JIRA] (JBCLUSTER-303) [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (Incoming-4, null) Problems unmarshalling remote command from byte buffer: org.infinispan.CacheException: Type of data read is unknown. Id=85 is not amongst known reader indexes.
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/JBCLUSTER-303?page=com.atlassian.jira.plu... ]
Paul Ferraro closed JBCLUSTER-303.
----------------------------------
Resolution: Out of Date
This module is obsolete.
> [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (Incoming-4,null) Problems unmarshalling remote command from byte buffer: org.infinispan.CacheException: Type of data read is unknown. Id=85 is not amongst known reader indexes.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBCLUSTER-303
> URL: https://issues.jboss.org/browse/JBCLUSTER-303
> Project: JBoss Clustering
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: HA-Server-Cache-ISPN
> Environment: JBOSS 7.1.1 FINAL , REDHAT LINUX ENTERPRISE
> Reporter: pankaj pandey
> Assignee: Paul Ferraro
>
> I am getting problem while implementing jboss 7 clustering with session persistence.
> ava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] Caused by: an exception which occurred: in element at index [0] of size [1]
> 02:41:08,277 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (Incoming-4,null) Problems unmarshalling remote command from byte buffer: org.infinispan.CacheException: Type of data read is unknown. Id=85 is not amongst known reader indexes. at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:216) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) at org.jboss.marshalling.river.RiverUnmarshaller.doReadCollectionObject(RiverUnmarshaller.java:180) at org.jboss.marshalling.river.RiverUnmarshaller.readCollectionData(RiverUnmarshaller.java:772) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:669) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.14.GA-redhat-1.jar:1.3.14.GA-redhat-1] at org.infinispan.marshall.exts.ReplicableCommandExternalizer.readParameters(ReplicableCommandExternalizer.java:119) at org.infinispan.marshall.exts.ReplicableCommandExternalizer.readObject(ReplicableCommandExternalizer.java:107) at org.infinispan.marshall.exts.ReplicableCommandExternalizer.readObject(ReplicableCommandExternalizer.java:58) at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.readObject(ExternalizerTable.java:391) at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.14.GA-redhat-1.jar:1.3.14.GA-redhat-1] at org.infinispan.marshall.exts.ReplicableCommandExternalizer.readParameters(ReplicableCommandExternalizer.java:119) at org.infinispan.marshall.exts.CacheRpcCommandExternalizer.readObject(CacheRpcCommandExternalizer.java:163) at org.infinispan.marshall.exts.CacheRpcCommandExternalizer.readObject(CacheRpcCommandExternalizer.java:67) at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.readObject(ExternalizerTable.java:391) at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351) at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.14.GA-redhat-1.jar:1.3.14.GA-redhat-1] at org.infinispan.marshall.jboss.AbstractJBossMarshaller.objectFromObjectStream(AbstractJBossMarshaller.java:154) at org.infinispan.marshall.VersionAwareMarshaller.objectFromByteBuffer(VersionAwareMarshaller.java:114) at org.infinispan.marshall.AbstractDelegatingMarshaller.objectFromByteBuffer(AbstractDelegatingMarshaller.java:85) at org.infinispan.remoting.transport.jgroups.MarshallerAdapter.objectFromBuffer(MarshallerAdapter.java:50) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:200) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:456) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:363) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:238) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:543) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.JChannel.up(JChannel.java:716) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1026) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.RSVP.up(RSVP.java:192) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.FlowControl.up(FlowControl.java:400) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.pbcast.GMS.up(GMS.java:889) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:383) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:739) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:566) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.BARRIER.up(BARRIER.java:126) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:143) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.FD.up(FD.java:273) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:288) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.Discovery.up(Discovery.java:359) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.stack.Protocol.up(Protocol.java:363) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.TP.passMessageUp(TP.java:1180) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1728) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1710) [jgroups-3.0.9.Final-redhat-1.jar:3.0.9.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] Caused by: an exception which occurred: in element at index [0] of size [1]
--
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, 3 months