[JBoss JIRA] Created: (JBAS-5413) Build is broken (so is mail)
by Carlo de Wolf (JIRA)
Build is broken (so is mail)
----------------------------
Key: JBAS-5413
URL: http://jira.jboss.com/jira/browse/JBAS-5413
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Carlo de Wolf
Assigned To: Anil Saldhana
Priority: Blocker
Fix For: JBossAS-5.0.0.CR1
compile-classes:
[mkdir] Created dir: /home/hudson/.hudson/jobs/JBoss_EJB3_Plugin/workspace/trunk/ejb3/output/classes
[javac] Compiling 19 source files to /home/hudson/.hudson/jobs/JBoss_EJB3_Plugin/workspace/trunk/ejb3/output/classes
/home/hudson/.hudson/jobs/JBoss_EJB3_Plugin/workspace/trunk/ejb3/src/main/org/jboss/ejb3/deployers/Ejb3JBoss5Deployment.java:34: cannot find symbol
symbol : class JaccHelper
location: package org.jboss.ejb3.security
import org.jboss.ejb3.security.JaccHelper;
^
/home/hudson/.hudson/jobs/JBoss_EJB3_Plugin/workspace/trunk/ejb3/src/main/org/jboss/ejb3/deployers/Ejb3JBoss5Deployment.java:64: cannot find symbol
symbol : variable JaccHelper
location: class org.jboss.ejb3.deployers.Ejb3JBoss5Deployment
return JaccHelper.initialiseJacc(getJaccContextId());
^
/home/hudson/.hudson/jobs/JBoss_EJB3_Plugin/workspace/trunk/ejb3/src/main/org/jboss/ejb3/deployers/Ejb3JBoss5Deployment.java:71: cannot find symbol
symbol : variable JaccHelper
location: class org.jboss.ejb3.deployers.Ejb3JBoss5Deployment
JaccHelper.putJaccInService(pc, jbossUnit);
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/hudson/.hudson/jobs/JBoss_EJB3_Plugin/workspace/trunk/ejb3/src/main/org/jboss/ejb3/deployers/JBoss5DeploymentScope.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
3 errors
BUILD FAILED
--
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, 1 month
[JBoss JIRA] Moved: (JBAS-5421) Make session clustering's "useJK" handling a pluggable policy so we can integrate with other load balancers
by Brian Stansberry (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-5421?page=all ]
Brian Stansberry moved JBCLUSTER-101 to JBAS-5421:
--------------------------------------------------
Project: JBoss Application Server (was: JBoss Clustering)
Key: JBAS-5421 (was: JBCLUSTER-101)
Component/s: Clustering
Web (Tomcat) service
(was: Web Tier)
Fix Version/s: Backlog
(was: Q3Y8)
> Make session clustering's "useJK" handling a pluggable policy so we can integrate with other load balancers
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBAS-5421
> URL: http://jira.jboss.com/jira/browse/JBAS-5421
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering, Web (Tomcat) service
> Reporter: Brian Stansberry
> Assigned To: Brian Stansberry
> Fix For: Backlog
>
>
> Session replication uses the JvmRouteValve to detect session failover and modify the session id so mod_jk knows to thereafter pin the the session to the new node.
> JBossCacheManager also has logic that understands how to strip out the jvmRoute from the session id.
> Need to make this logic a pluggable policy, so we can deal with other load balancers that may have a different mechanism for tracking to which node a session is pinned.
--
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, 1 month
[JBoss JIRA] Updated: (JBCLUSTER-97) Integrated Replication for EJB3 and HttpSession
by Brian Stansberry (JIRA)
[ http://jira.jboss.com/jira/browse/JBCLUSTER-97?page=all ]
Brian Stansberry updated JBCLUSTER-97:
--------------------------------------
Fix Version/s: Q3Y8
(was: Q1Y8)
Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial, Compatibility/Configuration] (was: [Compatibility/Configuration, Interactive Demo/Tutorial, Documentation (Ref Guide, User Guide, etc.)])
> Integrated Replication for EJB3 and HttpSession
> -----------------------------------------------
>
> Key: JBCLUSTER-97
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-97
> Project: JBoss Clustering
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Brian Stansberry
> Assigned To: Brian Stansberry
> Fix For: Q3Y8
>
>
> We need to have the ability to replicate any EJB3 and http session state changes associated with a request at the same time. Otherwise, we just double the replication-related latency of the request. This is critical in the case of SEAM.
--
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, 1 month
[JBoss JIRA] Updated: (JBCLUSTER-25) HA JMS
by Brian Stansberry (JIRA)
[ http://jira.jboss.com/jira/browse/JBCLUSTER-25?page=all ]
Brian Stansberry updated JBCLUSTER-25:
--------------------------------------
Fix Version/s: Q2Y8
(was: Q1Y8)
In progress.
> HA JMS
> ------
>
> Key: JBCLUSTER-25
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-25
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Brian Stansberry
> Fix For: Q2Y8
>
>
> Currently JBossMQ is using HA-Singleton for limited high availbility. There is no fail over for state, per se.
> We don't have plan to enhance any HA in JBossMQ (4.0x release).
> Ovidiu's new messaging system has a built-in high-availbility capability in there through the servless nature of the system. So when his new system is ready for JMS, this piece should be built in.
> Remaining issues are to integrate with the current clustering framework.
--
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, 1 month