> How could I reproduce it? Do you have a testcase?
I'll try to make a small test case tonight or tomorrow.
/Markus
>
> Thanks.
>
> Markus Härnvi wrote:
>
> >>Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
> >>be the cause of your problem. Thanks.
> >
> >
> >
The same way as in 3.2.2: by increasing log level to DEBUG for category
org.jboss.ejb.plugins.cmp.
How could I reproduce it? Do you have a testcase?
Thanks.
Markus Härnvi wrote:
Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
be the cause of your problem. Thanks.
I g
> Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
> be the cause of your problem. Thanks.
I got the same error as with 3.2.2.
If I set log4j to DEBUG (in Branch_3_2) I don't get the SQL statements from the
CMP engine any longer. Maybe they could shed som light on my pr
> Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
> be the cause of your problem. Thanks.
Ok, I'll try that in the weekend. Thanks!
/Markus
> Markus Härnvi wrote:
>
> > Thanks Scott for the answer about SSL/Tomcat!
> >
> > Next one: :)
> >
> > I'm using cascade-
Please, try with fresh Branch_3_2 in 24 hours. I fixed a bug that could
be the cause of your problem. Thanks.
Markus Härnvi wrote:
Thanks Scott for the answer about SSL/Tomcat!
Next one: :)
I'm using cascade-delete between a few CMP beans. My test cases that works in
3.2.2RC4 now fails in 3.2.
Yes, sorry. Of course, sync-on-commit-only must be false if you have
foreign key contraints.
Could you, please, submit a bug report with the detailed info? Thank you.
Markus Härnvi wrote:
Hi again!
It's set to false in both environments. I tried setting it to true in 3.2.2 but
that didn't help.
Hi again!
It's set to false in both environments. I tried setting it to true in 3.2.2 but
that didn't help.
/Markus
> Is sync-on-commit-only set to true in RC4? I guess, it is false in final
> and, hence, is the expected behaviour.
>
> Markus Härnvi wrote:
>
> > Hi!
> >
> >
> >>Could
Is sync-on-commit-only set to true in RC4? I guess, it is false in final
and, hence, is the expected behaviour.
Markus Härnvi wrote:
Hi!
Could you post a stacktrace, please? And some description of what was
going to be cascade-deleted?
Sure.
SearchCriteria has zero or more children called
Hi!
> Could you post a stacktrace, please? And some description of what was
> going to be cascade-deleted?
Sure.
SearchCriteria has zero or more children called HostCriteria. Deleting a
SearchCriteria should delete all related HostCriteria.
The key fields in the database looks like this:
Could you post a stacktrace, please? And some description of what was
going to be cascade-deleted?
Thanks.
Markus Härnvi wrote:
Thanks Scott for the answer about SSL/Tomcat!
Next one: :)
I'm using cascade-delete between a few CMP beans. My test cases that works in
3.2.2RC4 now fails in 3.2.2
Thanks Scott for the answer about SSL/Tomcat!
Next one: :)
I'm using cascade-delete between a few CMP beans. My test cases that works in
3.2.2RC4 now fails in 3.2.2 with the following message:
javax.ejb.RemoveException: Could not remove 16 at
org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityComma
11 matches
Mail list logo