[JBoss JIRA] Created: (JBAS-3972) incorrect synchronization in JmsServerSessionPool
by james ahlborn (JIRA)
incorrect synchronization in JmsServerSessionPool
-------------------------------------------------
Key: JBAS-3972
URL: http://jira.jboss.com/jira/browse/JBAS-3972
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.5.GA
Reporter: james ahlborn
Assigned To: Adrian Brock
Priority: Minor
the code within connector/src/main/org/jboss/resource/adapter/jms/inflow/JmsServerSessionPool.java setupSessions() incorrectly synchronizes on the serverSessions (serverSessions is used on lines 202 and 205 outside the synch block). the method should look like (starting at line 190):
// Create the sessions
ArrayList clonedSessions = null;
synchronized (serverSessions)
{
for (int i = 0; i < spec.getMaxSessionInt(); ++i)
{
JmsServerSession session = new JmsServerSession(this);
serverSessions.add(session);
}
sessionCount = serverSessions.size();
clonedSessions = (ArrayList) serverSessions.clone();
}
// Start the sessions
for (int i = 0; i < clonedSessions.size(); ++ i)
{
JmsServerSession session = (JmsServerSession) clonedSessions.get(i);
session.setup();
}
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBMESSAGING-734) Create failover tests for failover of XASesions
by Tim Fox (JIRA)
Create failover tests for failover of XASesions
-----------------------------------------------
Key: JBMESSAGING-734
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-734
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.2.0.Beta1
Reporter: Tim Fox
Fix For: 1.2.0.CR1
We need to make sure failover of XAsesions works ok.
Current test coverage only tests failover of non XA sessions.
Need to do something like:
Create a couple of XASessions on different XAConnections on different servers
Do some work in the sessions.
Failover one of the servers
Complete the transaction
Verify outcome is as expected (correct messags are sent, and correct message are acked - must test both send and ack)
Failover should happen at different times, in the commit process
Need to test failover at:
before being
after begin
after end
before prepare
after prepare
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBAS-3776) Update SerialVersionUIDUnitTestCase to test against new versions
by Ryan Campbell (JIRA)
Update SerialVersionUIDUnitTestCase to test against new versions
----------------------------------------------------------------
Key: JBAS-3776
URL: http://jira.jboss.com/jira/browse/JBAS-3776
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Ryan Campbell
Priority: Critical
Fix For: JBossAS-4.0.6.CR1
Here is how to build the .ser database of serialVersionUIDs:
Builid jboss-4.0.5 with jdk14
cd build/output
java -XX:MaxPermSize=512m -Xmx2000m -cp ../../varia/output/classes org.jboss.tools.SerialVersionUID jboss-4.0.5.GA/
cp serialuid.ser $WORK/Branch_4_0/testsuite/src/etc/serialVersionUID/405.ser
Then the SerialVersionUIDUnitTestCase needs to be updated to test against 4.0.3SP1, 4.0.4, and 4.0.5.
The badpackages list will probably need to be different for each version.
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBAS-3838) ServerInfo does not check response from getThreadInfo for null
by Darran Lofthouse (JIRA)
ServerInfo does not check response from getThreadInfo for null
--------------------------------------------------------------
Key: JBAS-3838
URL: http://jira.jboss.com/jira/browse/JBAS-3838
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: MicroContainer bus
Affects Versions: JBossAS-4.0.5.GA
Reporter: Darran Lofthouse
Assigned To: Darran Lofthouse
Fix For: JBossAS-4.2.0.CR1
The ServerInfo MBean does not check the response from getThreadInfo for null. If getThreadInfo is called for a thread that no longer exists it returns null. Currently it is possible for the following NullPointerException to be logged: -
java.lang.NullPointerException
at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.system.server.ServerInfo.getThreadCpuUtilization(ServerInfo.java:557)
at org.jboss.system.server.ServerInfo.listThreadCpuUtilization(ServerInfo.java:510)
at sun.reflect.GeneratedMethodAccessor113.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
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
19 years, 4 months
[JBoss JIRA] Created: (JBPORTAL-1217) User registration, usability issue
by Thomas Heute (JIRA)
User registration, usability issue
----------------------------------
Key: JBPORTAL-1217
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1217
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.Alpha1
Reporter: Thomas Heute
Assigned To: Roy Russo
Fix For: 2.6.Beta1
There is a usability problem with user registration:
- Click on "You can create an account"
- Fill the form
- Submit
- it leads to a maximized user portlet with a unique link: "Standard login"
- Click on the unique link
- It brings you to a page saying "You are currently not logged in"
Confusing :)
I guess that after submission it should show the "You are currently not logged in" in a minimized window, where there is a "Login" link on the theme.
--
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
19 years, 4 months