On Tue, Dec 5, 2017 at 02:19 am, Trond Arild Lode Tobiassen Heidelberg wrote: changed form this: @OneToMany(cascade = CascadeType.ALL) @JoinColumn(name = "MESSAGE_ID", nullable = true, unique = false,

https://github.com/javaee/glassfish/issues/11348 Happens on glassfish 5 as well.

5.0 Build 25 Does anyone have an idea why? More info: When the app is first deployed it works, but not after restarts.

The above works well on embedded glassfish but not when deploying the application on the server. A telnet to the port does not connect anymore. Does anyone have a clue as to what might be causing this

Hi I have this code: @Entity(name = "ABSTRACT_MESSAGE_TABLE") @DiscriminatorColumn(length=64) public abstract class AbstractMessage<T extends AbstractMessage<T, U, X>, U extends StartLine<U>, X extend

Problem might ave been reated to missing @Transient on non-persistable guava types.

Turns out it did not work on 4.1 either. But the error message was a lot more descriptive. I removedan accidental comment of annotations and the metamodel and code matched again. The code now runs und

java.lang.NullPointerException at org.eclipse.persistence.internal.jpa.metamodel.proxy.AttributeProxyImpl.getPersistentAttributeType(AttributeProxyImpl.java:78) at org.eclipse.persistence.internal.jpa

Found the problem. Ho-ho. Santa brought som insight. Turns out i was not annotating my nonpersistable guava types with @Transient. Maybe 5.0.1 can bring a clearer exception message to this case.

Please note that before upgrading to 5.0 the below case/topic describes what happens when running the code (no id gets injected into a row of the the twentifirst table handled by the server) I notice

The below happens when a number of table-rows have been inserted successfully in other tables, using the exact same setup. Note that the sequence is reported to not being deleted during startup (of gl

OK.Solved. I had two classes with the same name, different package. Had I only read the package path I had seen that the other one specified i the stacktrace didn't have the "targeEntity" specified. N

Turns out I needed to use InitialContext for my application. At least going from JUnit testst or from netty callback methods. Making them session beans and trying to inject (@Resource) does not work.

Hi and thanks for you swift reply. The version is 4.1 and there is no stack trace except nullpointer when i access methods on the connection factory. Best Regards Trond

Hi. tried to use this feature, However injection does not happen and nullpointer results. The test succeeds using jndi lookup directly, implying all is correct on glassfish for sending messages to MDB