September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAOP-253) Before release, submit the jar to the Messaging team for testing

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ] Kabir Khan updated JBAOP-253: ----------------------------- Attachment: (was: jboss-aop.jar) > Before release, submit the jar to the Messaging team for testing > ---------------------------------------------------------------- > > Key: JBAOP-253 > URL: http://jira.jboss.com/jira/browse/JBAOP-253 > Project: JBoss AOP > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-253) Before release, submit the jar to the Messaging team for testing

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ] Kabir Khan updated JBAOP-253: ----------------------------- Attachment: (was: jboss-aop-jdk50.jar) > Before release, submit the jar to the Messaging team for testing > ---------------------------------------------------------------- > > Key: JBAOP-253 > URL: http://jira.jboss.com/jira/browse/JBAOP-253 > Project: JBoss AOP > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-286) Weaken dependencies on unreleased MC 2.0

by Kabir Khan (JIRA)

Weaken dependencies on unreleased MC 2.0 ---------------------------------------- Key: JBAOP-286 URL: http://jira.jboss.com/jira/browse/JBAOP-286 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha1 -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3681) EJB3.0 Session bean lookup

by madan srinivas (JIRA)

EJB3.0 Session bean lookup -------------------------- Key: JBAS-3681 URL: http://jira.jboss.com/jira/browse/JBAS-3681 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.0.4.CR2 Environment: JBoss4.0.4CR2 Reporter: madan srinivas Assigned To: Bill Burke I get ejb not bound exception when i look up session bean sessoin bean jndi name is mentioned using annotation in hte code as @Stateless @RemoteBinding(jndiBinding="ejb/remote/FileDetails") the look up code is Properties env = new java.util.Properties(); env.setProperty("java.naming.provider.url", "http://localhost:8080/invoker/JNDIFactory"); env.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); env.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory"); InitialContext ctx = new InitialContext(env); FileDetailsClientBean filesession = (FileDetailsClientBean)ctx.lookup("ejb/remote/FileDetails"); filesession.addFileDetails(); Pls help me resolve this and let me know if the code is correct -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3680) URLDeployer deploys before JAR/WAR/EAR available

by warren crossing (JIRA)

URLDeployer deploys before JAR/WAR/EAR available ------------------------------------------------ Key: JBAS-3680 URL: http://jira.jboss.com/jira/browse/JBAS-3680 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Installer Affects Versions: JBossAS-4.0.4.GA Environment: Linux SCP Reporter: warren crossing Assigned To: Alex Pinkin I scp my war into the deployment directory and I get spewage below. you must scan the lastmodified to see if it has changed if is has changed you must add additional logic.. sleep for 1/2 a second and then check lastmodified again that means wait until file is complete! org.jboss.deployment.DeploymentException: invalid distance code; - nested throwable: (java.util.zip.ZipException: invalid distance code) at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:374) 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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.deployment.SubDeployerInterceptorSupport.init(SubDeployerInterceptorSupport.java:119) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.init(SubDeployerInterceptorSupport.java:172) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:87) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy42.init(Unknown Source) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:861) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:798) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy6.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: java.util.zip.ZipException: invalid distance code at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:140) at java.util.zip.ZipInputStream.read(ZipInputStream.java:139) at java.util.jar.JarInputStream.read(JarInputStream.java:171) at org.jboss.util.file.JarUtils.unjar(JarUtils.java:300) at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.j -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-998) Eclipse project files are not up to date with structure of third party libraries

by Sverker Abrahamsson (JIRA)

Eclipse project files are not up to date with structure of third party libraries -------------------------------------------------------------------------------- Key: JBPORTAL-998 URL: http://jira.jboss.com/jira/browse/JBPORTAL-998 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Environment: Windows XP, Eclipse 3.2 Reporter: Sverker Abrahamsson Priority: Minor When importing the JBoss portal into workspace there are a lot of unresolved dependancies since the structure on third party libraries has changed. -- 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-3620) JBossMQ's PersistenceManager RecoveryRetries doesn't work if failure is creating the schema

by Adrian Brock (JIRA)

JBossMQ's PersistenceManager RecoveryRetries doesn't work if failure is creating the schema ------------------------------------------------------------------------------------------- Key: JBAS-3620 URL: http://jira.jboss.com/jira/browse/JBAS-3620 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Fix For: JBossAS-4.0.5.GA JBossMQ's PersistenceManager has a mechanism to retry recovery a number of times "RecoveryRetries". However, this only applies to the data recovery. If it fails (e.g. due to database or network glitch) while checking/creating the database schema then no retries are done. -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3627) Write test to test rollback of a NACK in 2PC

by Luc Texier (JIRA)

Write test to test rollback of a NACK in 2PC -------------------------------------------- Key: JBAS-3627 URL: http://jira.jboss.com/jira/browse/JBAS-3627 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service Reporter: Luc Texier Assigned To: Adrian Brock Fix For: JBossAS-4.0.5.GA Need to test BasicQueue.acknowledge() whether it should also add a PostRollback task for a NACK under a transaction. i.e. // Was it a negative acknowledge?? if (!item.isAck) { Runnable task = new RestoreMessageTask(m); server.getPersistenceManager().getTxManager().addPostCommitTask(txId, task); + server.getPersistenceManager().getTxManager().addPostRollbackjTask(txId, task); } The hard part is wrting such a test since it is a normal condition. Probably need to use direct invocation on the server invoker ? -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3628) Invalid fix for JBAS-3573

by Luc Texier (JIRA)

Invalid fix for JBAS-3573 ------------------------- Key: JBAS-3628 URL: http://jira.jboss.com/jira/browse/JBAS-3628 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Luc Texier Assigned To: Luc Texier Fix For: JBossAS-4.0.5.GA in case of an exception, both a PostCommit Task and a PostRollback Task should be added try { if (m.isPersistent()) server.getPersistenceManager().remove(m, txId); } catch (Throwable t) { // Something is wrong with the persistence manager, // force a NACK with a rollback/error Runnable task = new RestoreMessageTask(m); TxManager txManager = server.getPersistenceManager().getTxManager(); + txManager.addPostCommitTask(txId, task); txManager.addPostRollbackTask(txId, task); SpyJMSException.rethrowAsJMSException("Error during ACK ref=" + m, t); } -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3634) Acknowledgement of transacted message in MessageListener should be inside delivery lock

by Adrian Brock (JIRA)

Acknowledgement of transacted message in MessageListener should be inside delivery lock --------------------------------------------------------------------------------------- Key: JBAS-3634 URL: http://jira.jboss.com/jira/browse/JBAS-3634 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-4.0.5.GA The acknowledgement of a transacted message for a MessageListener should be inside the delivery lock. Otherwise the addition of the acknowledgement could be competing with other operations on the session, e.g. commit/rollback/recover. org.jboss.mq.SpyMessageConsumer::run() + // Try to obtain the session delivery lock + // This avoids concurrent delivery to message listeners in the same session as per spec + boolean gotDeliveryLock = false; + while (gotDeliveryLock == false) + { if (session.transacted) { // REVIEW: for an XASession without a transaction this will ack the message // before it has been processed. Plain message listeners // are not supported in a j2ee environment, but what if somebody is trying // to be clever? if (trace) log.trace("run() acknowledging message in tx mes=" + mes.getJMSMessageID() + " " + this); session.connection.spyXAResourceManager.ackMessage(session.getCurrentTransactionId(), mes); } - // Try to obtain the session delivery lock - // This avoids concurrent delivery to message listeners in the same session as per spec - boolean gotDeliveryLock = false; - while (gotDeliveryLock == false) - { -- 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, 10 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006