January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBCLUSTER-102) How to run jbento2

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-102?page=all ] Brian Stansberry closed JBCLUSTER-102. -------------------------------------- Resolution: Out of Date > How to run jbento2 > ------------------ > > Key: JBCLUSTER-102 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-102 > Project: JBoss Clustering > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > > Under atl lab, jbento account, I have created jebnto2 so we can run it accordingly. > 1. Machines: dev02, dev03 are for jboss instanaces, dev14 (actually dev14-priv) is for the driver. Note that there is no apache load balancing yet. So it will just hit dev02. > 2. Jboss is sym link as jboss4-4 and jboss4-3 on home dir. > 3. jboss has sync and async config names under respective /tmp/jbento dir > 4. Check run.sh and shutdown.sh for the binding. > 5. Use sh driver.sh Repo to run jbento2. Check either JBento-Result or Work for results. Looks for analyzer.txt under report dir. > 6. To modify, use loop.conf and jboss4.sh under Repo/conf dir. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-119) Effect of different JGroups transports

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-119?page=all ] Brian Stansberry updated JBCLUSTER-119: --------------------------------------- Fix Version/s: Q2Y8 (was: Q2Y7) > Effect of different JGroups transports > -------------------------------------- > > Key: JBCLUSTER-119 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-119 > Project: JBoss Clustering > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Web Tier > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: Q2Y8 > > Attachments: ResultsExtract.pdf, tc5-cluster-service.xml.nio, tc5-cluster-service.xml.tcp, tc5-cluster-service.xml.udp > > > Need to see in which cluster topologies UDP, TCP and TCP_NIO perform best. Particularly, how big of a cluster before UDP pays off. Need to factor buddy replication into this. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-23) Consolidate clustering configuration frontend for state replication

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-23?page=all ] Brian Stansberry updated JBCLUSTER-23: -------------------------------------- Fix Version/s: Q2Y8 (was: Q2Y7) > Consolidate clustering configuration frontend for state replication > ------------------------------------------------------------------- > > Key: JBCLUSTER-23 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-23 > Project: JBoss Clustering > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Priority: Critical > Fix For: Q2Y8 > > Original Estimate: 8 weeks > Remaining Estimate: 8 weeks > > Currently we have cluster-service.xml, tc5-cluster-serviec.xml, and other tree-cache.xml to run on tops of JGroups for various replication and clustering purpose. In ejb3, we will run into this problem of SFSB and entity bean using JBossCache. > There comes a need to consolidate all these configuration so to a end user it is consistent. > Solution may be to put in another integration layer to hide JBossCache configuration somewhat. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-8) Stateful session bean (SFSB) replication in EJB3

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-8?page=all ] Brian Stansberry updated JBCLUSTER-8: ------------------------------------- Fix Version/s: Q1Y8 (was: Q2Y7) > Stateful session bean (SFSB) replication in EJB3 > ------------------------------------------------ > > Key: JBCLUSTER-8 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-8 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Components: EJB3 > Reporter: Ben Wang > Assigned To: Brian Stansberry > Priority: Critical > Fix For: Q1Y8 > > > Currently Bill has implemented SFSB in ejb3 using JBossCache. Need to track further integration issue(s). -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-117) Clustered deployments using the Profile Service

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-117?page=all ] Brian Stansberry updated JBCLUSTER-117: --------------------------------------- Fix Version/s: Q2Y8 (was: Q2Y7) Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)]) > Clustered deployments using the Profile Service > ----------------------------------------------- > > Key: JBCLUSTER-117 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-117 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Blocker > Fix For: Q2Y8 > > > Basic farmed and singleton deployments using microcontainer services (Profile Service, Virtual Deployment 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-11) Unified clustering configuration and management

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-11?page=all ] Brian Stansberry updated JBCLUSTER-11: -------------------------------------- Fix Version/s: Q2Y8 (was: Q2Y7) > Unified clustering configuration and management > ----------------------------------------------- > > Key: JBCLUSTER-11 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-11 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Priority: Blocker > Fix For: Q2Y8 > > Original Estimate: 12 weeks > Remaining Estimate: 12 weeks > > Will need a more unified management frontend for the new clustering: > 1. Unified JGroups MBean to configure the channel running inside the JBoss AS. > 2. Unified JBossCache configuration to select cache instance used for http session, SFSB, entity, and others. > 3. Unified clustering web console. > This issue is a duplicate of JBAS-2960. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-142) Determine binaries

by Brian Stansberry (JIRA)

Determine binaries ------------------ Key: JBCLUSTER-142 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-142 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Need to determine what binaries should be built. Projects like Remoting want a lightweight binary, so we may need to create more than one. -- 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

16 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-143) Create initial release schedule

by Brian Stansberry (JIRA)

Create initial release schedule ------------------------------- Key: JBCLUSTER-143 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-143 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Analyze when things need to be done so they can be integrated into dependent projects. -- 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

16 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5029) Integrate jboss-ha-server-api.jar

by Brian Stansberry (JIRA)

Integrate jboss-ha-server-api.jar --------------------------------- Key: JBAS-5029 URL: http://jira.jboss.com/jira/browse/JBAS-5029 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Extract the server-side API classes from the AS codebase. -- 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

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1182) Specifying security Identity in ejb-jar.xml is ignored for MDB using the quartz-ra.rar resource adapter

by alex soto (JIRA)

Specifying security Identity in ejb-jar.xml is ignored for MDB using the quartz-ra.rar resource adapter ------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1182 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1182 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: AS 4.2.2.GA Environment: Java 5 Windows XP Mac OS X 10.4.11 Reporter: alex soto A MDB calling an EJB fails with Authorization failure exception when the run-as identity of the MDB is specified in the deployment descriptor files rather than with annotations. The MDB uses the quartz-ra resource adapter, but I'm not sure if this makes any difference. Here is the call stack: 16:23:00,016 INFO [CronJob] CronJob called. 16:23:00,017 ERROR [RoleBasedAuthorizationInterceptor] Insufficient permissions, principal=null, requiredRoles=[admin], principalRoles=[] 16:23:00,020 ERROR [JobRunShell] Job default.job.0.1200691035489 threw an unhandled Exception: javax.ejb.EJBTransactionRolledbackException: Authorization failure at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy72.execute(Unknown Source) at org.jboss.resource.adapter.quartz.inflow.QuartzJob.execute(QuartzJob.java:57) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: javax.ejb.EJBAccessException: Authorization failure at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:120) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:81) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107) at $Proxy67.doit(Unknown Source) at test.CronJob.execute(CronJob.java:21) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) ... 11 more 16:23:00,021 ERROR [ErrorLogger] Job (default.job.0.1200691035489 threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: javax.ejb.EJBTransactionRolledbackException: Authorization failure] at org.quartz.core.JobRunShell.run(JobRunShell.java:214) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) * Nested Exception (Underlying Cause) --------------- javax.ejb.EJBTransactionRolledbackException: Authorization failure at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy72.execute(Unknown Source) at org.jboss.resource.adapter.quartz.inflow.QuartzJob.execute(QuartzJob.java:57) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: javax.ejb.EJBAccessException: Authorization failure at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:120) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:81) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107) at $Proxy67.doit(Unknown Source) at test.CronJob.execute(CronJob.java:21) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) ... 11 more -- 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

16 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008