[JBoss JIRA] Created: (JBAS-4972) jboss 4.2.1 with spring 2.0.6 causes NoTransactionException
by Adrian Brock (JIRA)
jboss 4.2.1 with spring 2.0.6 causes NoTransactionException
-----------------------------------------------------------
Key: JBAS-4972
URL: http://jira.jboss.com/jira/browse/JBAS-4972
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
This issue was raised in the forums and the attachments sent to me private e-mail.
"
Hi Adrian,
In the topic http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4084161
you were asking for more information or some code that reproduces the problem.
I created a small ear that contains an EJB, a spring bean and a JSP.
The JSP calls the EJB which calls the Spring bean.
I tested the ear with both jboss 4.2.1 and 4.2.2 and got the same error.
In order to simulate the error, please do the following:
- Install jboss 4.2.1 or 4.2.2
- Copy the earmodule-1.0.ear to
<jboss_home>\server\default\deploy\
- Copy spring.jar, from <springframework 2.0.6 distribution>\dist\ to <jboss_home>\server\default\lib\
(I could not attach the jar to this email because your email server complains that the zip is too big)
- Additionally add to <jboss_home>\server\default\conf\jboss-log4j.xml the
following in order to see how spring is using the transaction started by EJB
to enlist the spring bean (UserBo):
<category name="org.springframework.transaction">
<appender-ref ref="CONSOLE"/>
<appender-ref ref="FILE"/>
<priority value="DEBUG"/>
</category>
and if you want to see more details at console about spring transaction manager,
change the Threshold of CONSOLE appender to DEBUG.
- Start jboss
- To trigger the error, open in a browser the URL:
http://localhost:8080/test/
I attached the source and the ear to this email + the server log from jboss 4.2.2.
Like I said in the topic, this was not happening on jboss 4.0.4.
Could you please take a look and do a debug perhaps.
Thank you.
I look forward to hearing from you.
Best Regards,
Bucegi Omu
"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months
[JBoss JIRA] Created: (JBPORTAL-1806) Portlet window state cached when window re-created
by Ovidiu Nichifor (JIRA)
Portlet window state cached when window re-created
--------------------------------------------------
Key: JBPORTAL-1806
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1806
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.1 Final
Environment: JBoss AS 4.0.5 installed with JEMS 1.2.0.GA
Reporter: Ovidiu Nichifor
Assigned To: Julien Viet
1. Create a window.
2. Minimize it.
3. Close the window.
4. Re-create the window (exact name, page, coordinates etc).
5. Notice that the window is displayed in the minimized view, instead of normal view.
If you re-login to portal or restart the AS it will work properly (the new window is created in normal view).
Also note that once a window gets maximized and you re-login/restart the AS the window looses state (is displayed in normal view).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 8 months