2:26 p.m.
Uwe Seimet created AS7-5496:
-------------------------------
Summary: Hibernate proxy class not found in remote EJB call
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux 3.5.3
Reporter: Uwe Seimet
Assignee: David Lloyd
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a proxy is
passed as an argument in the remote call the exception is raised.
The classloader settings are the standard JBoss settings.
--
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
2:28 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet updated AS7-5496:
----------------------------
Environment:
Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
was:
Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux 3.5.3
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: David Lloyd
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a proxy is
passed as an argument in the remote call the exception is raised.
The classloader settings are the standard JBoss settings.
--
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
2:32 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
David Lloyd updated AS7-5496:
-----------------------------
Assignee: Scott Marlow (was: David Lloyd)
Component/s: JPA / Hibernate
(was: Class Loading)
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a proxy is
passed as an argument in the remote call the exception is raised.
The classloader settings are the standard JBoss settings.
--
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
2:34 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet updated AS7-5496:
----------------------------
Description:
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
was:
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a proxy is
passed as an argument in the remote call the exception is raised.
The classloader settings are the standard JBoss settings.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
2:46 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Can you attach a test case that reproduces AS7-5496 and the server.log output?
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:47 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet updated AS7-5496:
----------------------------
Attachment: deployments.tar.gz
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:47 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet updated AS7-5496:
----------------------------
Attachment: server.log
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:47 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet updated AS7-5496:
----------------------------
Attachment: test.sql
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:49 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet updated AS7-5496:
----------------------------
Attachment: sources.tar.gz
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:57 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each).
3. deployments.tar.gz: Exploded ear and war that demonstrates the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Add a JNDI entry in JBoss to use this database created by the dump (test.sql).
2. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
3. Start jboss with ./standalone.sh.
4. Open this URL: http://localhost:8080/photo_web/index.html
5. Click on the button "Submit".
6. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
4:01 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet edited comment on AS7-5496 at 9/5/12 5:01 PM:
---------------------------------------------------------
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each).
3. deployments.tar.gz: Exploded ear and war that demonstrate the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Add a JNDI entry in JBoss to use the database created by the dump (test.sql).
2. Execute the SQL script to populate to create the database for this test.
3. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
4. Start jboss with ./standalone.sh.
5. Open this URL: http://localhost:8080/photo_web/index.html
6. Click on the button "Submit".
7. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
was (Author: seimet):
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each).
3. deployments.tar.gz: Exploded ear and war that demonstrates the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Add a JNDI entry in JBoss to use this database created by the dump (test.sql).
2. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
3. Start jboss with ./standalone.sh.
4. Open this URL: http://localhost:8080/photo_web/index.html
5. Click on the button "Submit".
6. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
4:03 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet edited comment on AS7-5496 at 9/5/12 5:01 PM:
---------------------------------------------------------
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each).
3. deployments.tar.gz: Exploded ear and war that demonstrate the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Add a JNDI entry in JBoss to use the database created by the dump (test.sql).
2. Execute the SQL script to create the database for this test.
3. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
4. Start jboss with ./standalone.sh.
5. Open this URL: http://localhost:8080/photo_web/index.html
6. Click on the button "Submit".
7. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
was (Author: seimet):
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each).
3. deployments.tar.gz: Exploded ear and war that demonstrate the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Add a JNDI entry in JBoss to use the database created by the dump (test.sql).
2. Execute the SQL script to populate to create the database for this test.
3. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
4. Start jboss with ./standalone.sh.
5. Open this URL: http://localhost:8080/photo_web/index.html
6. Click on the button "Submit".
7. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
4:03 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet edited comment on AS7-5496 at 9/5/12 5:02 PM:
---------------------------------------------------------
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each).
3. deployments.tar.gz: Exploded ear and war that demonstrate the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Execute the SQL script test.sql to create the database for this test.
2. Add a JNDI entry in JBoss to use the database created in step 1.
3. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
4. Start jboss with ./standalone.sh.
5. Open this URL: http://localhost:8080/photo_web/index.html
6. Click on the button "Submit".
7. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
was (Author: seimet):
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each).
3. deployments.tar.gz: Exploded ear and war that demonstrate the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Add a JNDI entry in JBoss to use the database created by the dump (test.sql).
2. Execute the SQL script to create the database for this test.
3. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
4. Start jboss with ./standalone.sh.
5. Open this URL: http://localhost:8080/photo_web/index.html
6. Click on the button "Submit".
7. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
1:28 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet edited comment on AS7-5496 at 9/6/12 2:26 AM:
---------------------------------------------------------
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each) and one ID
generator table.
3. deployments.tar.gz: Exploded ear and war that demonstrate the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Execute the SQL script test.sql to create the database named 'test' for this
test.
2. Add a JNDI entry in JBoss to use the database created in step 1.
3. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
4. Start jboss with ./standalone.sh.
5. Open this URL: http://localhost:8080/photo_web/index.html
6. Click on the button "Submit".
7. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
was (Author: seimet):
I have attached these files:
1. server.log, with the exception backtrace at the bottom.
2. test.sql: Dump of a very small MySQL database with two tables (one row each).
3. deployments.tar.gz: Exploded ear and war that demonstrate the problem.
4. sources.tar.gz: The sources, created from my Eclipse workspace.
To reproduce the exception please do this:
1. Execute the SQL script test.sql to create the database for this test.
2. Add a JNDI entry in JBoss to use the database created in step 1.
3. Unpack the archive deployments.tar.gz in the JBoss standalone/deployments folder.
4. Start jboss with ./standalone.sh.
5. Open this URL: http://localhost:8080/photo_web/index.html
6. Click on the button "Submit".
7. The result is the stack backtrace in the attached logfile.
Thank you for investigating this issue.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
2:21 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
<quote>The behavior is reproducible with different applications on different
platforms.
<quote>
What do you mean by "different platforms"? Have you tried this on other
versions of JBoss AS? Does this work anywhere?
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
2:21 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow edited comment on AS7-5496 at 9/6/12 3:20 PM:
-----------------------------------------------------------
{quote}The behavior is reproducible with different applications on different platforms.
{quote}
What do you mean by "different platforms"? Have you tried this on other
versions of JBoss AS? Does this work anywhere?
was (Author: smarlow):
<quote>The behavior is reproducible with different applications on different
platforms.
<quote>
What do you mean by "different platforms"? Have you tried this on other
versions of JBoss AS? Does this work anywhere?
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:55 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
With platforms I meant different operating systems. As far as JBoss is concerned it worked
with JBoss 5.0.1. It also works with EclipseLink 2.4.0 instead of Hibernate, by the way.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:57 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet edited comment on AS7-5496 at 9/6/12 4:55 PM:
---------------------------------------------------------
With platforms I meant different operating systems. As far as JBoss is concerned it worked
with JBoss 5.0.1. It also works with JBoss 7.1 and EclipseLink 2.4.0 instead of Hibernate,
by the way.
was (Author: seimet):
With platforms I meant different operating systems. As far as JBoss is concerned it
worked with JBoss 5.0.1. It also works with EclipseLink 2.4.0 instead of Hibernate, by the
way.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
10:14 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-5496:
-------------------------------------
Can you give more details on how your application is packaged?
It looks like the calling application (or at least the calling sub deployment) does not
use hibernate, as as a result a module reference to hibernate is never added to the
deployment.
You should be able to work around it by adding:
Dependencies: org.hibernate
to the MANIFEST.MF of the calling application.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
1:15 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
This dependency is already listed in the MANIFEST.MF file of the calling application. You
can verify this by having a look at the attached deployments
(photo_web.war/META-INF/MANIFEST.MF).
Have you been able to reproduce the problem with the deployments I provided?
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
1:20 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-5496:
-------------------------------------
Oops, I did not see the attachments, I will have a look.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
8:57 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
I probably could recreate with the attachment but it would be easier to hack it a little
to not need mysql. I tried to build from source but the parent artifact is missing.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:40 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
I still haven't figured out why EclipseLink works but Hibernate doesn't. I'm
thinking that EclipseLink might not be generating a proxy for the lazy association.
The full exception stack trace is:
{quote}
20:03:43,598 SEVERE [javax.enterprise.resource.webcontainer.jsf.application]
(http-localhost/127.0.0.1:8080-1) Error Rendering View[/index.xhtml]:
javax.el.ELException: /thumbnails.xhtml @11,53
rendered="#{thumbnailBean.hasPhotos}": java.lang.RuntimeException: JBAS014154:
Failed to marshal EJB parameters
at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:114)
[jsf-impl-2.1.11-jbossorg-3.jar:]
at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:413)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1773)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at javax.faces.render.Renderer.encodeChildren(Renderer.java:168)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:845)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at
com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:424)
[jsf-impl-2.1.11-jbossorg-3.jar:]
at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125)
[jsf-impl-2.1.11-jbossorg-3.jar:]
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121)
[jsf-impl-2.1.11-jbossorg-3.jar:]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
[jsf-impl-2.1.11-jbossorg-3.jar:]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
[jsf-impl-2.1.11-jbossorg-3.jar:]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
[jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[jbossweb-7.0.17.Final.jar:]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.17.Final.jar:]
at de.seimet.photo.filter.DownloadFilter.doFilter(DownloadFilter.java:76) [classes:]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[jbossweb-7.0.17.Final.jar:]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.17.Final.jar:]
at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
[weld-core-1.1.9.Final.jar:2012-08-06 19:12]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
[jbossweb-7.0.17.Final.jar:]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[jbossweb-7.0.17.Final.jar:]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[jbossweb-7.0.17.Final.jar:]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[jbossweb-7.0.17.Final.jar:]
at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165)
[jboss-as-web-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[jbossweb-7.0.17.Final.jar:]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.17.Final.jar:]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.17.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
[jbossweb-7.0.17.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.17.Final.jar:]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
[jbossweb-7.0.17.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
[jbossweb-7.0.17.Final.jar:]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
Caused by: java.lang.RuntimeException: JBAS014154: Failed to marshal EJB parameters
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:269)
[jboss-as-ejb3-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT]
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:258)
[jboss-as-ejb3-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT]
at org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:169)
[jboss-as-ejb3-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT]
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
[jboss-ejb-client-1.0.11.Final.jar:1.0.11.Final]
at
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
[jboss-ejb-client-1.0.11.Final.jar:1.0.11.Final]
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
[jboss-ejb-client-1.0.11.Final.jar:1.0.11.Final]
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
[jboss-ejb-client-1.0.11.Final.jar:1.0.11.Final]
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
[jboss-ejb-client-1.0.11.Final.jar:1.0.11.Final]
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
[jboss-ejb-client-1.0.11.Final.jar:1.0.11.Final]
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
[jboss-ejb-client-1.0.11.Final.jar:1.0.11.Final]
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
[jboss-ejb-client-1.0.11.Final.jar:1.0.11.Final]
at $Proxy59.test(Unknown Source) at
de.seimet.photo.backing.ThumbnailBean.getHasPhotos(ThumbnailBean.java:81) [classes:]
at
de.seimet.photo.backing.ThumbnailBean$Proxy$_$$_WeldClientProxy.getHasPhotos(ThumbnailBean$Proxy$_$$_WeldClientProxy.java)
[classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_07]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[rt.jar:1.7.0_07]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.7.0_07]
at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07]
at javax.el.BeanELResolver.getValue(BeanELResolver.java:302)
[jboss-el-api_2.2_spec-1.0.2.Final.jar:1.0.2.Final]
at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
[jsf-impl-2.1.11-jbossorg-3.jar:]
at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
[jsf-impl-2.1.11-jbossorg-3.jar:]
at org.apache.el.parser.AstValue.getValue(AstValue.java:169)
[jbossweb-7.0.17.Final.jar:]
at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:189)
[jbossweb-7.0.17.Final.jar:]
at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
[weld-core-1.1.9.Final.jar:2012-08-06 19:12]
at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
[jsf-impl-2.1.11-jbossorg-3.jar:]
... 35 more
Caused by: java.lang.ClassNotFoundException:
de.seimet.photo.entity.Location_$$_javassist_2 from [Module
"deployment.photo_ear.ear.photo_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_07]
at java.lang.Class.forName(Class.java:264) [rt.jar:1.7.0_07]
at
org.jboss.marshalling.cloner.ClassLoaderClassCloner.clone(ClassLoaderClassCloner.java:49)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:157)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:186)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at
org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:348)
at
org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:309)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:253)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:267)
[jboss-as-ejb3-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT]
... 59 more
{quote}
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
10:06 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Stuart,
how about if we add a "jboss-deployment-dependencies" from the calling
application to the app that has the de.seimet.photo.entity.Location_$$_javassist_2 proxy
(so that deployment order is correct) and a jboss-deployment-structure to add a
classloader dependency for the same? Would that work to share the classloader properly?
Scott
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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:07 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet updated AS7-5496:
----------------------------
Attachment: sources2.tar.gz
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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:09 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
I uploaded sources2.tar.gz, which should contain any source files that might have been
missing.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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:12 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
I'm not aclass loader expert, but please keep in mind that passing the proxy via a
remote interface also should work in a distributed environment, with the remote JBoss
instance running on a different server than the local JBoss instance. Configuring
deployment dependencies would probably not work in the case of two independent servers.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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:12 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet edited comment on AS7-5496 at 9/7/12 1:12 PM:
---------------------------------------------------------
I'm not a class loader expert, but please keep in mind that passing the proxy via a
remote interface also should work in a distributed environment, with the remote JBoss
instance running on a different server than the local JBoss instance. Configuring
deployment dependencies would probably not work in the case of two independent servers.
was (Author: seimet):
I'm not aclass loader expert, but please keep in mind that passing the proxy via a
remote interface also should work in a distributed environment, with the remote JBoss
instance running on a different server than the local JBoss instance. Configuring
deployment dependencies would probably not work in the case of two independent servers.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
1:02 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Uwe, good point. It sounds like we need a [Serialization
Proxy|http://lingpipe-blog.com/2009/08/10/serializing-immutable-singleton...]
that re-establishes itself at deserialization time.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
1:25 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
Hi, any idea when you can address this issue? It appears as if using JBoss 7.1 with remote
interfaces and lazy loading is not possible, even though both features are key features of
a Java EE environment. This most likely affects many projects that are being ported from
JBoss 5 to 7.1.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
8:59 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Adding a (failing) unit test to the Hibernate upstream project would probably be the next
step.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:07 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-5496:
------------------------------
Affects Version/s: 7.1.1.Final
(was: 7.1.2.Final (EAP))
(was: 7.1.3.Final (EAP))
changed "found in version" from EAP to 7.1.1.
For EAP issues, the following links can be used:
[Red Hat knowledgebase, videos, Groups discussions, and many more technical
resources|http://access.redhat.com]
[Red Hat Support phone numbers and case management
information|https://access.redhat.com/support]
[Red Hat Customer service
team|https://access.redhat.com/support/contact/customerService.html]
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:32 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
To answer your question about *when* this can be addressed. Once we have a patch for it,
it can be applied for a future community release. From everything that you have said so
far, it is sounding like something that should be fixed in Hibernate (or possibly
Javassist if needed).
Creating the patch, would probably involve:
* checkout Hibernate sources
* add a unit test to Hibernate that serializes the proxy class and then tries to
deserialize it from a different classloader. There might already be a similar test that
could be modified to do this.
* fix the bug (after debugging to investigate further)
The last step is kind of open, depending on what the actual cause is.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
10 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
This means somebody will forward this issue to the Hibernate team or the Hibernate Jira?
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
11:10 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Its more than just forwarding the issue.
I asked the Hibernate team on IRC, if they are aware of any issues with Hibernate proxies
not being deserializable on a different classloader and they aren't aware of it.
When I have time, I will try to build your test case again. The first change that I would
like to make to your test case, is to not require MySQL (its quicker for me to test with
H2). The test case should just create the entities that are needed and return them from
the remote method call. With that change, I might be able to find time sooner to look at
this (no promises when though).
Running AS in a debugger and trying to see why the HibernateProxy.writeReplace() is not
doing the expected thing, would be the first thing to check (IMO). Whether that will help
or not, I'm not sure.
Since you reported this against EAP (not sure if that was a mistake or not), I also added
links for getting more timely support for that (EAP issues should be reported directly for
quicker resolution).
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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:53 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
I reported it against EAP because the community version 7.1.1 has so many problems with
serialization that I could not use it at all. 7.1.2 (EAP) is broken with respect to nested
JSF custom components, that's why I also could not use it. With 7.1.3 (EAP) these
problems are fixed, and 7.1.3 worked fine up to the point where I stumbled upon this new
issue.
As far as using Hibernate is concerned this is unfortunately a blocker for me. Too bad,
because there are many things about JBoss 7.1 I really like and running JBoss with
Hibernate would be more natural than running JBoss with EclipseLink.
With the current version of Javassist the error is the same, by the way. I tried it some
time ago.
Thank you again for your support!
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
8:45 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
I was able to recreate this but not sure of the root cause yet.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:07 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
{quote}
SerializableProxy.readResolve returns a proxy object but we hit the ClassNotFoundException
in org.jboss.marshalling.reflect.SerializableClass.callReadResolve()
Object passed to SerializableClass.callReadResolve is:
instance of org.hibernate.proxy.pojo.javassist.SerializableProxy
SerializableProxy contents:
PersistenceClass=de.seimet.photo.entity.Location
interfaces[0]=org.hibernate.proxy.HibernateProxy
getIdentifierMethodClass=null
setIdentifierMethodClass=null
getIdentifierMethodName=null
setIdentifierMethodName=null
setIdentifierMethodParams=null
componentIdType=null
entityName=de.seimet.photo.entity.Location
id="1"
readOnly=null
Thread call stack from the SerializableProxy.readResolve is below:
at
org.hibernate.proxy.pojo.javassist.SerializableProxy.readResolve(SerializableProxy.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.jboss.marshalling.reflect.SerializableClass.callReadResolve(SerializableClass.java:338)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:259)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:231)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at
org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:348)
at
org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:309)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:253)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:267)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:258)
at
org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:230)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy46.test1(Unknown Source:-1)
at de.seimet.photo.backing.ThumbnailBean.action(ThumbnailBean.java:27)
{quote}
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:27 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow edited comment on AS7-5496 at 9/26/12 10:25 AM:
-------------------------------------------------------------
{quote}
SerializableProxy.readResolve returns a proxy object (no cnfe yet, just incorrect java
sources ;).
Object passed to SerializableClass.callReadResolve is:
instance of org.hibernate.proxy.pojo.javassist.SerializableProxy
SerializableProxy contents:
PersistenceClass=de.seimet.photo.entity.Location
interfaces[0]=org.hibernate.proxy.HibernateProxy
getIdentifierMethodClass=null
setIdentifierMethodClass=null
getIdentifierMethodName=null
setIdentifierMethodName=null
setIdentifierMethodParams=null
componentIdType=null
entityName=de.seimet.photo.entity.Location
id="1"
readOnly=null
Thread call stack from the SerializableProxy.readResolve is below:
at
org.hibernate.proxy.pojo.javassist.SerializableProxy.readResolve(SerializableProxy.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.jboss.marshalling.reflect.SerializableClass.callReadResolve(SerializableClass.java:338)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:259)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:231)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at
org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:348)
at
org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:309)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:253)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:267)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:258)
at
org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:230)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy46.test1(Unknown Source:-1)
at de.seimet.photo.backing.ThumbnailBean.action(ThumbnailBean.java:27)
{quote}
was (Author: smarlow):
{quote}
SerializableProxy.readResolve returns a proxy object but we hit the ClassNotFoundException
in org.jboss.marshalling.reflect.SerializableClass.callReadResolve()
Object passed to SerializableClass.callReadResolve is:
instance of org.hibernate.proxy.pojo.javassist.SerializableProxy
SerializableProxy contents:
PersistenceClass=de.seimet.photo.entity.Location
interfaces[0]=org.hibernate.proxy.HibernateProxy
getIdentifierMethodClass=null
setIdentifierMethodClass=null
getIdentifierMethodName=null
setIdentifierMethodName=null
setIdentifierMethodParams=null
componentIdType=null
entityName=de.seimet.photo.entity.Location
id="1"
readOnly=null
Thread call stack from the SerializableProxy.readResolve is below:
at
org.hibernate.proxy.pojo.javassist.SerializableProxy.readResolve(SerializableProxy.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.jboss.marshalling.reflect.SerializableClass.callReadResolve(SerializableClass.java:338)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:259)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:231)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at
org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:348)
at
org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:309)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:253)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:267)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:258)
at
org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:230)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy46.test1(Unknown Source:-1)
at de.seimet.photo.backing.ThumbnailBean.action(ThumbnailBean.java:27)
{quote}
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:53 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow edited comment on AS7-5496 at 9/26/12 10:52 AM:
-------------------------------------------------------------
Trying to unravel if this is a packaging issue or a bug. It looks like a bug but not 100%
sure.
As mentioned above the, readResolve() PersistenceClass=de.seimet.photo.entity.Location and
the PersistenceClass.getClassLoader() = ModuleClassLoader for Module
"deployment.photo_web.war:main" from Service Module Loader
The class nfe for: classname= de.seimet.photo.entity.Location_$$_javassist_2
ModuleClassLoader for Module "deployment.photo_ear.ear.photo_ejb.jar:main" from
Service Module Loader
Module "deployment.photo_ear.ear.photo_ejb.jar:main" from Service Module Loader
callstack for cnfe=
{quote}
http-/127.0.0.1:8080-1@11944 daemon, prio=5, in group 'main', status:
'RUNNING'
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Class.java:-1)
at java.lang.Class.forName(Class.java:264)
at
org.jboss.marshalling.cloner.ClassLoaderClassCloner.clone(ClassLoaderClassCloner.java:49)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:157)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:186)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at
org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:348)
at
org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:309)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:253)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:267)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:258)
at
org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:169)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy46.test2(Unknown Source:-1)
at de.seimet.photo.backing.ThumbnailBean.action(ThumbnailBean.java:29)
at
de.seimet.photo.backing.ThumbnailBean$Proxy$_$$_WeldClientProxy.action(ThumbnailBean$Proxy$_$$_WeldClientProxy.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.el.parser.AstValue.invoke(AstValue.java:264)
at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278)
at
org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39)
at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
at
javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
at
com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:101)
at javax.faces.component.UICommand.broadcast(UICommand.java:315)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
at java.lang.Thread.run(Thread.java:722)
{quote}
was (Author: smarlow):
Trying to unravel if this is a packaging issue or a bug. It looks like a bug but not
100% sure.
As mentioned above the, readResolve() PersistenceClass=de.seimet.photo.entity.Location and
the PersistenceClass.getClassLoader() = ModuleClassLoader for Module
"deployment.photo_web.war:main" from Service Module Loader
The class nfe for: classname= de.seimet.photo.entity.Location_$$_javassist_2
ModuleClassLoader for Module "deployment.photo_ear.ear.photo_ejb.jar:main" from
Service Module Loader
Module "deployment.photo_ear.ear.photo_ejb.jar:main" from Service Module Loader
callstack=
{quote}
http-/127.0.0.1:8080-1@11944 daemon, prio=5, in group 'main', status:
'RUNNING'
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Class.java:-1)
at java.lang.Class.forName(Class.java:264)
at
org.jboss.marshalling.cloner.ClassLoaderClassCloner.clone(ClassLoaderClassCloner.java:49)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:157)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:186)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at
org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:348)
at
org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:309)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:253)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:267)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:258)
at
org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:169)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy46.test2(Unknown Source:-1)
at de.seimet.photo.backing.ThumbnailBean.action(ThumbnailBean.java:29)
at
de.seimet.photo.backing.ThumbnailBean$Proxy$_$$_WeldClientProxy.action(ThumbnailBean$Proxy$_$$_WeldClientProxy.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.el.parser.AstValue.invoke(AstValue.java:264)
at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278)
at
org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39)
at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
at
javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
at
com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:101)
at javax.faces.component.UICommand.broadcast(UICommand.java:315)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
at java.lang.Thread.run(Thread.java:722)
{quote}
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:53 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Trying to unravel if this is a packaging issue or a bug. It looks like a bug but not 100%
sure.
As mentioned above the, readResolve() PersistenceClass=de.seimet.photo.entity.Location and
the PersistenceClass.getClassLoader() = ModuleClassLoader for Module
"deployment.photo_web.war:main" from Service Module Loader
The class nfe for: classname= de.seimet.photo.entity.Location_$$_javassist_2
ModuleClassLoader for Module "deployment.photo_ear.ear.photo_ejb.jar:main" from
Service Module Loader
Module "deployment.photo_ear.ear.photo_ejb.jar:main" from Service Module Loader
callstack=
{quote}
http-/127.0.0.1:8080-1@11944 daemon, prio=5, in group 'main', status:
'RUNNING'
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Class.java:-1)
at java.lang.Class.forName(Class.java:264)
at
org.jboss.marshalling.cloner.ClassLoaderClassCloner.clone(ClassLoaderClassCloner.java:49)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:157)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:186)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at
org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:348)
at
org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:309)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:253)
at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:134)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:267)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:258)
at
org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:169)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy46.test2(Unknown Source:-1)
at de.seimet.photo.backing.ThumbnailBean.action(ThumbnailBean.java:29)
at
de.seimet.photo.backing.ThumbnailBean$Proxy$_$$_WeldClientProxy.action(ThumbnailBean$Proxy$_$$_WeldClientProxy.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.el.parser.AstValue.invoke(AstValue.java:264)
at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278)
at
org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39)
at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
at
javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
at
com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:101)
at javax.faces.component.UICommand.broadcast(UICommand.java:315)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
at java.lang.Thread.run(Thread.java:722)
{quote}
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
11:59 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
The ejb client can invoke a server side method that returns the HibernateProxy for
de.seimet.photo.entity.Location but the client cannot pass the same returned object back
into the server side.
earlier, the class de.seimet.photo.entity.Location is loaded from:
ModuleClassLoader for Module "deployment.photo_ear.ear:main" from Service Module
Loader (contained in lib/photo_ejb_client.jar).
Which is different than the cl we get the cnfe with
deployment.photo_ear.ear.photo_ejb.jar:main
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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:44 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Moved the entity classes into the ejb jar (photo_ejb.jar), but still get a CNFE when
trying to clone the client (deployment.photo_web.war:main") copy of the
de.seimet.photo.entity.Location_$$_javassist_2 proxy class.
We are calling "Class.forName(name, true, destClassLoader)" with name =
de.seimet.photo.entity.Location_$$_javassist_2 and destClassLoader =
"deployment.photo_ear.ear.photo_ejb.jar:main"
ClassLoader deployment.photo_ear.ear.photo_ejb.jar:main does have
de.seimet.photo.entity.Location_$$_javassist_0 loaded but doesn't know about
de.seimet.photo.entity.Location_$$_javassist_2.
de.seimet.photo.entity.Location_$$_javassist_2 came from the client sides call to
JavassistLazyInitializer.getProxy() in readResolve().
When the client side is passing the de.seimet.photo.entity.Location_$$_javassist_2
parameter to the server side (ear), we don't seem to reach readResolve() for the
parameter.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
1:58 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
On the first client call to test1, we reach the readResolve() for the Location (associated
with the entity returned from test1()). In SerializingCloner.clone(), we have:
objClass=org.hibernate.proxy.pojo.javassist.SerializableProxy
orig = org.hibernate.proxy.pojo.javassist.SerializableProxy@634bfc56
The above call to test1() works.
During the test1 call, the readResolve() generates a new proxy class (as expected) but the
server side doesn't know about the generated proxy class when the entity is passed
back to the server (test2 method). That seems to lead to the cnfe.
For the call to test2(), we are passing the entity returned from test1() but fail due to
the CNFE.
In SerializingCloner.clone(), we have:
objClass = class de.seimet.photo.entity.Location_$$_javassist_2
orig.getClass() = class de.seimet.photo.entity.Location_$$_javassist_2
orig.getClass().getClassLoader() = "deployment.photo_web.war:main"
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
1:35 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-5496:
------------------------------
Forum Reference:
http://lists.jboss.org/pipermail/jboss-as7-dev/2012-September/006928.html
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:27 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
David's fix for JBMAR-142 addresses this issue.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
3:42 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-5496:
------------------------------
Fix Version/s: 7.2.0.Alpha1
Forum Reference:
http://lists.jboss.org/pipermail/jboss-as7-dev/2012-September/006928.html (was:
http://lists.jboss.org/pipermail/jboss-as7-dev/2012-September/006928.html)
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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:47 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
Does this mean that replacing jboss-marshalling-1.3.15.GA.jar by 1.3.16 will fix this
issue for JBoss 7.1.3?
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:36 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Uwe, at this point, I think it will important to simplify your use case into an AS7 unit
test. If you can help with that, I think you will also help answer your above question.
I didn't try replacing the jar (I rebuilt both AS7 + jboss-marshalling from git source
control).
https://community.jboss.org/wiki/HackingOnAS7 explains how to build AS from source, if
your interested in giving that a try, I can advise you on the easiest way to add a simple
test case (in the AS7/testsuite/ subfolder). Then, you could contribute the unit test
case, which will help make sure that this bug doesn't happen again.
What do you think?
Scott
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
10:20 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
I started to work on a unit test for this issue.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
4:18 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
I'm sorry for my late response.
Thank you for working on a unit test! I'm afraid it don't have the time to engage
in writing unit tests for JBoss.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
10:47 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
I tried adding a few different tests but didn't recreate the issue.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
1 p.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Uwe Seimet commented on AS7-5496:
---------------------------------
I noticed that the latest JBoss 7.1 branch has been updated with
jboss-marshalling-1.3.16.GA.jar. Now my sample application works as expected, i.e. it
looks as if this issue is resolved, indeed.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:22 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-5496:
-----------------------------------
Uwe, thanks for your help with verifying this! :)
I'm going to close this now.
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:24 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow resolved AS7-5496.
-------------------------------
Resolution: Done
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
9:24 a.m.
[
https://issues.jboss.org/browse/AS7-5496?page=com.atlassian.jira.plugin.s...
]
Scott Marlow closed AS7-5496.
-----------------------------
Hibernate proxy class not found in remote EJB call
--------------------------------------------------
Key: AS7-5496
URL: https://issues.jboss.org/browse/AS7-5496
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: Java 1.6.0_35 and Java 1.7.0_07
Mac OS X 10.8.1, Windows XP and Gentoo Linux with Kernel 3.5.3
Reporter: Uwe Seimet
Assignee: Scott Marlow
Fix For: 7.2.0.Alpha1
Attachments: deployments.tar.gz, server.log, sources.tar.gz, sources2.tar.gz,
test.sql
Prerequisites:
1. A JPA entity A with a reference to a different JPA entity B. FetchType is
FetchType.LAZY, e.g.
@Entity
public class A {
@ManyToOne(fetch = FetchType.LAZY)
private B refToB;
}
@Entity
public class B {
}
2. A remote interface with methods passing an instance of A, .e.g.
@Remote
public interface ITest {
A test1();
void test2(A a);
}
3. A process calling test1() and then test2() on the remote interface like this:
@EJB(lookup = "...")
private ITest iTest;
public void ITest() {
final A a = iTest.test1();
iTest.test2(a); }
}
Error description: When calling test1() an instance of A is returned. This instance is
valid and works as expected. The reference to B is a proxy (something like
B_$$_javassist_2), which was expected because B was loaded lazily and was never accessed
in the remote process before. When passing the instance of A back by calling test2(a) an
exception of this type is raised:
java.lang.ClassNotFoundException: B_$$_javassist_2 from [Module
"deployment.x.ear.y_ejb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Concurrent
ClassLoader.java:468)
It looks as if the proxy cannot be serialized or deserialized. The behavior is
reproducible with different applications on different platforms. As soon as a Hibernate
javassist proxy, which was received via a remote call, is passed back as an argument in
another remote call (the remote process is the same in all calls) the exception is
raised.
The classloader settings are the standard JBoss settings.
--
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
4967
days inactive
5000
days old
55 comments
4 participants
participants (4)
-
David Lloyd (JIRA) -
Scott Marlow (JIRA)
-
Stuart Douglas (JIRA)
-
Uwe Seimet (JIRA)