headers
Za Ah (JIRA | 16 Jun 2013 08:00

[JBoss JIRA] (SEAM-99) java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction!


    [
https://issues.jboss.org/browse/SEAM-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781919#comment-12781919
] 

Za Ah edited comment on SEAM-99 at 6/16/13 1:58 AM:
----------------------------------------------------

Hi,

The fix is not working in drools-5.5.0-Final. Its using seam 3.1.1-Final version but, the fix is not
working for below environment. 

1. drools-guvnor-5.5.0-Final
2. JBOSS ASS 7.1.0

We have processes and forms in in Guvnor repository in a package. Our web application accesses the process
definitions and forms from guvnor. This issue gets fixed on restart of server. But, once this issue
occurs, application can't access any asset or process definition from Guvnor using rest APIs. Even the
Guvnor web-interface starts giving error.

Only 4 users are using the application and getting this transaction association error.

                
      was (Author: ahmedza):
    Hi,

Is there any planned fix for this. I am facing the same issue with following Environment

1. drools-guvnor-5.5.0-Final
(Continue reading)

Permalink | Reply | 0 comments |
headers
Za Ah (JIRA | 16 Jun 2013 07:58

[JBoss JIRA] (SEAM-99) java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction!


    [
https://issues.jboss.org/browse/SEAM-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781919#comment-12781919
] 

Za Ah commented on SEAM-99:
---------------------------

Hi,

Is there any planned fix for this. I am facing the same issue with following Environment

1. drools-guvnor-5.5.0-Final
2. JBOSS ASS 7.1.0

We have processes and forms in in Guvnor repository in a package. Our web application accesses the process
definitions and forms from guvnor. This issue gets fixed on restart of server. But, once this issue
occurs, application can't access any asset or process definition from Guvnor using rest APIs. Even the
Guvnor web-interface starts giving error.

Only 4 users are using the application and getting this transaction association error.

                
> java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already
associated with a transaction!
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SEAM-99
>                 URL: https://issues.jboss.org/browse/SEAM-99
>             Project: Seam 3 Distribution
(Continue reading)

Permalink | Reply | 0 comments |
headers
Za Ah (JIRA | 16 Jun 2013 07:56

[JBoss JIRA] (SEAM-138) ...thread is already associated with a transaction!


    [
https://issues.jboss.org/browse/SEAM-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781917#comment-12781917
] 

Za Ah edited comment on SEAM-138 at 6/16/13 1:54 AM:
-----------------------------------------------------

Hi,

Is there any planned fix for this. I am facing the same issue with following Environment

1. drools-guvnor-5.5.0-Final
2. JBOSS ASS 7.1.0

We have processes and forms in in Guvnor repository in a package. Our web application accesses the process
definitions and forms from guvnor. This issue gets fixed on restart of server. But, once this issue
occurs, application can't access any asset or process definition from Guvnor using rest APIs. Even the
Guvnor web-interface starts giving error.

Only 4 users are using the application and getting this transaction association error.

                
      was (Author: ahmedza):
    Hi,

Is there any planned fix for this. I am facing the same issue with following Environment

1. drools-guvnor-5.5.0-Final
2. JBOSS ASS 7.1.0
(Continue reading)

Permalink | Reply | 0 comments |
headers
Za Ah (JIRA | 16 Jun 2013 07:52

[JBoss JIRA] (SEAM-138) ...thread is already associated with a transaction!


    [
https://issues.jboss.org/browse/SEAM-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781917#comment-12781917
] 

Za Ah commented on SEAM-138:
----------------------------

Hi,

Is there any planned fix for this. I am facing the same issue with following Environment

1. drools-guvnor-5.5.0-Final
2. JBOSS ASS 7.1.0

                
> ...thread is already associated with a transaction!
> ---------------------------------------------------
>
>                 Key: SEAM-138
>                 URL: https://issues.jboss.org/browse/SEAM-138
>             Project: Seam 3 Distribution
>          Issue Type: Bug
>    Affects Versions: 3.1.0.Final
>         Environment: Windows, JBPM 5.3.0 Final, Drools 5.4.0 Final, JBOSS 7.0.2 Final
>            Reporter: Andrea Carpineti
>              Labels: jta, transaction
>
> I believe the issue is related to Seam but I'm not completely sure...
> Using the JBPM console sometimes we experienced an issue due to which the deployed processes are no longer
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Becker (JIRA | 14 Jun 2013 11:33

[JBoss JIRA] (JBSEAM-5115) Add compatibility to hibernate 3.6 because of JBPM3


    [
https://issues.jboss.org/browse/JBSEAM-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781625#comment-12781625
] 

Robert Becker commented on JBSEAM-5115:
---------------------------------------

I'll try org.jbpm.jbpm3:jbpm-jpdl:jar:3.2.10.SP3_seam2. Thanks for the help!

> Add compatibility to hibernate 3.6 because of JBPM3
> ---------------------------------------------------
>
>                 Key: JBSEAM-5115
>                 URL: https://issues.jboss.org/browse/JBSEAM-5115
>             Project: Seam 2
>          Issue Type: Enhancement
>          Components: BPM
>    Affects Versions: 2.3.0.ALPHA, 2.3.0.BETA1, 2.3.0.BETA2, 2.3.0.CR1, 2.3.0.Final, 2.3.1.CR1
>            Reporter: Robert Becker
>            Priority: Blocker
>
> As Seam 2.3 is still bundled with JBPM 3 (which is good), it needs to be compatible with at least hibernate
3.6 since JBPM 3 does not work with hibernate 4. For many users, upgrading to a newer JBPM version is not an
option as there are many running business processes which can not be converted or migrated. In my case,
this dependency keeps me, and essentially all other users who integrated JBPM into their application,
from migrating to Seam 2.3 and JSF 2.
> When trying to use Hibernate 3.6 with seam 2.3 on AS7, the following exception occurs:
> {code}
> 16:03:16,837 WARN  [org.jboss.modules] (MSC service thread 1-6) Failed to define class
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marek Novotny (JIRA | 14 Jun 2013 10:59

[JBoss JIRA] (JBSEAM-5115) Add compatibility to hibernate 3.6 because of JBPM3


    [
https://issues.jboss.org/browse/JBSEAM-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781616#comment-12781616
] 

Marek Novotny commented on JBSEAM-5115:
---------------------------------------

No chance, jbpm3 is out of date in upstream. Currently jbpm5 is in development, but updating integration
for jbpm5 is too much effort for Seam team as we are here just for maintenance now after releasing 2.3.

org.jbpm.jbpm3:jbpm-jpdl:jar:3.2.10.SP3_seam2 should work with hibernate 4 just fine.

                
> Add compatibility to hibernate 3.6 because of JBPM3
> ---------------------------------------------------
>
>                 Key: JBSEAM-5115
>                 URL: https://issues.jboss.org/browse/JBSEAM-5115
>             Project: Seam 2
>          Issue Type: Enhancement
>          Components: BPM
>    Affects Versions: 2.3.0.ALPHA, 2.3.0.BETA1, 2.3.0.BETA2, 2.3.0.CR1, 2.3.0.Final, 2.3.1.CR1
>            Reporter: Robert Becker
>            Priority: Blocker
>
> As Seam 2.3 is still bundled with JBPM 3 (which is good), it needs to be compatible with at least hibernate
3.6 since JBPM 3 does not work with hibernate 4. For many users, upgrading to a newer JBPM version is not an
option as there are many running business processes which can not be converted or migrated. In my case,
this dependency keeps me, and essentially all other users who integrated JBPM into their application,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marek Novotny (JIRA | 13 Jun 2013 23:05

[JBoss JIRA] (JBSEAM-5004) Update Clustering chapter for AS7


     [
https://issues.jboss.org/browse/JBSEAM-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny reassigned JBSEAM-5004:
-------------------------------------

    Assignee: Marek Novotny

    
> Update Clustering chapter for AS7
> ---------------------------------
>
>                 Key: JBSEAM-5004
>                 URL: https://issues.jboss.org/browse/JBSEAM-5004
>             Project: Seam 2
>          Issue Type: Task
>          Components: Documentation Issues
>    Affects Versions: 2.3.0.BETA2
>            Reporter: Marek Novotny
>            Assignee: Marek Novotny
>             Fix For: 2.3.1.Final
>
>
> We need to update Seam reference guide to mention or point to https://docs.jboss.org/author/display/AS71/AS7+Cluster+Howto

--
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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Becker (JIRA | 13 Jun 2013 13:53

[JBoss JIRA] (JBSEAM-5115) Add compatibility to hibernate 3.6 because of JBPM3


    [
https://issues.jboss.org/browse/JBSEAM-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781386#comment-12781386
] 

Robert Becker commented on JBSEAM-5115:
---------------------------------------

So are there any chances that jbpm3 will eventually work with hibernate 4? That would be great news and an
even better solution.

> Add compatibility to hibernate 3.6 because of JBPM3
> ---------------------------------------------------
>
>                 Key: JBSEAM-5115
>                 URL: https://issues.jboss.org/browse/JBSEAM-5115
>             Project: Seam 2
>          Issue Type: Enhancement
>          Components: BPM
>    Affects Versions: 2.3.0.ALPHA, 2.3.0.BETA1, 2.3.0.BETA2, 2.3.0.CR1, 2.3.0.Final, 2.3.1.CR1
>            Reporter: Robert Becker
>            Priority: Blocker
>
> As Seam 2.3 is still bundled with JBPM 3 (which is good), it needs to be compatible with at least hibernate
3.6 since JBPM 3 does not work with hibernate 4. For many users, upgrading to a newer JBPM version is not an
option as there are many running business processes which can not be converted or migrated. In my case,
this dependency keeps me, and essentially all other users who integrated JBPM into their application,
from migrating to Seam 2.3 and JSF 2.
> When trying to use Hibernate 3.6 with seam 2.3 on AS7, the following exception occurs:
> {code}
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marek Novotny (JIRA | 13 Jun 2013 13:22

[JBoss JIRA] (JBSEAM-5115) Add compatibility to hibernate 3.6 because of JBPM3


    [
https://issues.jboss.org/browse/JBSEAM-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781380#comment-12781380
] 

Marek Novotny commented on JBSEAM-5115:
---------------------------------------

Robert, we don't support Hibernate 3.6 (obsolete version) because we need to support Hibernate 4.x and
they both are not compatible. If you have noticed jbpm3 integration is now available just with my fork of
jbpm 3 and that is experimental, so no real recommendation to use it.

> Add compatibility to hibernate 3.6 because of JBPM3
> ---------------------------------------------------
>
>                 Key: JBSEAM-5115
>                 URL: https://issues.jboss.org/browse/JBSEAM-5115
>             Project: Seam 2
>          Issue Type: Enhancement
>          Components: BPM
>    Affects Versions: 2.3.0.ALPHA, 2.3.0.BETA1, 2.3.0.BETA2, 2.3.0.CR1, 2.3.0.Final, 2.3.1.CR1
>            Reporter: Robert Becker
>            Priority: Blocker
>
> As Seam 2.3 is still bundled with JBPM 3 (which is good), it needs to be compatible with at least hibernate
3.6 since JBPM 3 does not work with hibernate 4. For many users, upgrading to a newer JBPM version is not an
option as there are many running business processes which can not be converted or migrated. In my case,
this dependency keeps me, and essentially all other users who integrated JBPM into their application,
from migrating to Seam 2.3 and JSF 2.
> When trying to use Hibernate 3.6 with seam 2.3 on AS7, the following exception occurs:
(Continue reading)

Permalink | Reply | 0 comments |
headers
RH Bugzilla Integration (JIRA | 13 Jun 2013 10:24

[JBoss JIRA] (JBSEAM-5083) SeamViewHandler adds conversation id even if conversation is not long running


    [
https://issues.jboss.org/browse/JBSEAM-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781315#comment-12781315
] 

RH Bugzilla Integration commented on JBSEAM-5083:
-------------------------------------------------

Tomas Remes <tremes@...> made a comment on [bug 921660|https://bugzilla.redhat.com/show_bug.cgi?id=921660]

Verified on 2.3.0.ER1 release.

> SeamViewHandler adds conversation id even if conversation is not long running
> -----------------------------------------------------------------------------
>
>                 Key: JBSEAM-5083
>                 URL: https://issues.jboss.org/browse/JBSEAM-5083
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Integration
>            Reporter: Marek Schmidt
>            Assignee: Marek Novotny
>             Fix For: 2.3.1.CR1
>
>
> Seam adds a conversation id even if the conversation is not long running into URL.
> Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the
cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be
correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application.
(Continue reading)

Permalink | Reply | 0 comments |
headers
RH Bugzilla Integration (JIRA | 13 Jun 2013 10:24

[JBoss JIRA] (JBSEAM-5083) SeamViewHandler adds conversation id even if conversation is not long running


    [
https://issues.jboss.org/browse/JBSEAM-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781314#comment-12781314
] 

RH Bugzilla Integration commented on JBSEAM-5083:
-------------------------------------------------

Tomas Remes <tremes@...> changed the Status of [bug
921660|https://bugzilla.redhat.com/show_bug.cgi?id=921660] from ON_QA to VERIFIED

> SeamViewHandler adds conversation id even if conversation is not long running
> -----------------------------------------------------------------------------
>
>                 Key: JBSEAM-5083
>                 URL: https://issues.jboss.org/browse/JBSEAM-5083
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Integration
>            Reporter: Marek Schmidt
>            Assignee: Marek Novotny
>             Fix For: 2.3.1.CR1
>
>
> Seam adds a conversation id even if the conversation is not long running into URL.
> Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the
cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be
correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application.

--
(Continue reading)

Permalink | Reply | 0 comments |

Gmane