January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8793) Update JRMPInvoker to not cast exported object to RemoteStub

by Jiri Kiml (JIRA)

Update JRMPInvoker to not cast exported object to RemoteStub ------------------------------------------------------------ Key: JBAS-8793 URL: https://issues.jboss.org/browse/JBAS-8793 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Release Notes Affects Versions: JBossAS-5.1.0.GA Environment: Microsoft Windows XP [Verze 5.1.2600] java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode) Reporter: Jiri Kiml Fix For: JBossAS-5.1.0.GA I am facing same problem as described/fixed here: https://issues.jboss.org/browse/JBAS-3703?page=com.atlassian.jira.plugin.... Please integrate this fix to jboss-5.1.0.GA. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8013) Complete Site and Documentation for AS6 Twiddle

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 Twiddle ----------------------------------------------- Key: JBAS-8013 URL: https://jira.jboss.org/jira/browse/JBAS-8013 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8646) Provide inital OSGi coverage in demos

by Thomas Diesler (JIRA)

Provide inital OSGi coverage in demos -------------------------------------- Key: JBAS-8646 URL: https://jira.jboss.org/browse/JBAS-8646 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8647) Enhance the classloader leak unit tests to use the Eclipse Memory Analyzer Tool (MAT) api

by Scott Marlow (JIRA)

Enhance the classloader leak unit tests to use the Eclipse Memory Analyzer Tool (MAT) api ------------------------------------------------------------------------------------------ Key: JBAS-8647 URL: https://jira.jboss.org/browse/JBAS-8647 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Scott Marlow Assignee: Scott Marlow I like using the Eclipse MAT for finding memory problems and would like to explore using the MAT api for automating finding memory issues. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8033) Can not deploy JAXWS war file to Jboss 5.1 and 6.0.0.M2

by jay ZHAO (JIRA)

Can not deploy JAXWS war file to Jboss 5.1 and 6.0.0.M2 ------------------------------------------------------- Key: JBAS-8033 URL: https://jira.jboss.org/browse/JBAS-8033 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.M2, JBossAS-5.1.0.GA Environment: RHEL 2.6.18-194.el5 Reporter: jay ZHAO Assignee: Ales Justin Priority: Critical We have a JAXWS war file which has been successfully deployed to GlassFish and WebLogic, but cannot be deployed to JBoss AS 5.1 and 6.0.0.M2. On AS 5.1 there is no detailed log info, here is the error log on 5.1: DEPLOYMENTS IN ERROR: Deployment "vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/opt/jboss-5.1.0.GA/server/default/tmp/4sge1w-qbnvnk-g9bavwnj-1-g9d3hmos-4t8/JAXWSDiscoveryService.war/ deployment failed at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305) ... 16 more 2010-05-18 15:06:31,508 INFO [org.jboss.profileservice.management.upload.remoting.DeployHandler] (ResourceContainer.invoker.nonDaemon-15) Remove, [vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/] 2010-05-18 15:06:31,523 WARN [org.rhq.core.pc.inventory.CreateResourceRunner] (ResourceFactory.executor-1) Throwable was found in creation report for request [1]: java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/opt/jboss-5.1.0.GA/configurations/discovery/deploy/JAXWSDiscoveryService.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/opt/jboss-5.1.0.GA/server/default/tmp/4sge1w-qbnvnk-g9bavwnj-1-g9d3hmos-4t8/JAXWSDiscoveryService.war/ deployment failed The errors we got when we deployed the same war file to 6.0.0.M2 are: Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.derby.jdbc.EmbedXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, org/apache/derby/jdbc/EmbedXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethods(Class.java:1791) at org.jboss.deployment.AnnotatedClassFilter.hasAnnotations(AnnotatedClassFilter.java:194) at org.jboss.deployment.AnnotatedClassFilter.accepts(AnnotatedClassFilter.java:122) at org.jboss.deployment.AnnotatedClassFilter.visit(AnnotatedClassFilter.java:102) at org.jboss.virtual.plugins.vfs.helpers.WrappingVirtualFileHandlerVisitor.visit(WrappingVirtualFileHandlerVisitor.java:62) at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:362) at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374) at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374) at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374) at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:374) at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:307) at org.jboss.virtual.VFS.visit(VFS.java:438) at org.jboss.virtual.VirtualFile.visit(VirtualFile.java:448) at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.getClasses(WarAnnotationMetaDataDeployer.java:180) at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.processMetaData(WarAnnotationMetaDataDeployer.java:153) at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.deploy(WarAnnotationMetaDataDeployer.java:127) at org.jboss.web.deployers.WarAnnotationMetaDataDeployer.deploy(WarAnnotationMetaDataDeployer.java:80) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) ... 39 more 2010-05-18 10:45:15,790 INFO [org.jboss.profileservice.management.upload.remoting.DeployHandler] (ResourceContainer.invoker.nonDaemon-2) Failed to complete command: [start] for deployment: names=[vfszip:/opt/jboss-6.0.0.20100216-M2/server/default/deploy/JAXWSDiscoveryService.war/]: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS) We have not seen the same problem in other major AS platforms. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

5
9
0 / 0

[JBoss JIRA] Created: (JBAS-8651) Typo in ClusteringDefaultsDeployer make the global passivationMaxIdleTime prop not being picked up

by Jean Deruelle (JIRA)

Typo in ClusteringDefaultsDeployer make the global passivationMaxIdleTime prop not being picked up -------------------------------------------------------------------------------------------------- Key: JBAS-8651 URL: https://jira.jboss.org/browse/JBAS-8651 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.1.0.GA Reporter: Jean Deruelle Assignee: Remy Maucherat Priority: Minor in addPassivationConfigDefaults method of ClusteringDefaultsDeployer line 246 contains a bad copy paste if (passCfg.getPassivationMinIdleTime() == null) passCfg.setPassivationMaxIdleTime(new Integer(this.passivationMaxIdleTime)); it should be if (passCfg.getPassivationMaxIdleTime() == null) passCfg.setPassivationMaxIdleTime(new Integer(this.passivationMaxIdleTime)); It affects EAP 5 version as well -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8381) Widen the range of raw SNMP types permitted by RequestHandlerImpl

by Kenny MacLeod (JIRA)

Widen the range of raw SNMP types permitted by RequestHandlerImpl ----------------------------------------------------------------- Key: JBAS-8381 URL: https://jira.jboss.org/browse/JBAS-8381 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: SNMP adapter Affects Versions: JBossAS-5.1.0.GA Reporter: Kenny MacLeod Assignee: Dimitris Andreadis Priority: Minor RequestHandlerImpl.getValue() for includes logic for determining how to express a JMX attribute in terms of an SNMP type. It supports Long, Integer, and String, as well as values of the raw SnmpTimeTicks and SnmpObjectId types. I think this should be widened, by removing the check for SnmpTimeTicks and SnmpObjectId, and replacing it with a single check for the SnmpSyntax interface. This would allow beans to return the full range of SNMP types. Also, an explicit check for null should be performed, and represented by the SnmpNull type. Note that setValueFor() is already more restrictive than getValueFor(), so we wouldn't be introducing any new asymmetry. Patch for RequestHandlerImpl.java to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-7884) javax.transaction.TransactionManager not found after OSGi integration

by Thomas Diesler (JIRA)

javax.transaction.TransactionManager not found after OSGi integration --------------------------------------------------------------------- Key: JBAS-7884 URL: https://jira.jboss.org/jira/browse/JBAS-7884 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossAS-6.0.0.M3 18:36:17,250 WARN [org.jboss.deployment.MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossas/trunk/testsuite/output/lib/simple-session.jar: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "vfs:///home/tdiesler/svn/jbossas/trunk/testsuite/output/lib/simple-session.jar" is missing the following dependencies: Dependency "interface javax.transaction.TransactionManager" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'interface javax.transaction.TransactionManager' **") Dependency "interface javax.transaction.TransactionManager" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'interface javax.transaction.TransactionManager' **") DEPLOYMENTS IN ERROR: Deployment "interface javax.transaction.TransactionManager" is in error due to the following reason(s): ** NOT FOUND Depends on 'interface javax.transaction.TransactionManager' ** -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib

by Paul Ferraro (JIRA)

Move jboss-ha-server-* jars from common/lib to server/all/lib ------------------------------------------------------------- Key: JBAS-8164 URL: https://jira.jboss.org/browse/JBAS-8164 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 6.0.0.M3 Reporter: Paul Ferraro Assignee: Scott Marlow Fix For: 6.0.0.Final Currently, the build puts the following jars into common/lib: jboss-ha-server-api.jar jboss-ha-server-cache-jbc.jar jboss-ha-server-cache-spi.jar jboss-ha-server-core.jar This will likely cause classloader issues, especially for classes that extend/implement jbosscache or jgroups classes (e.g. CacheManager, ChannelFactory), since these jars reside in server/all/lib -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8773) Log configuration errors are hard to debug

by David Lloyd (JIRA)

Log configuration errors are hard to debug ------------------------------------------ Key: JBAS-8773 URL: https://issues.jboss.org/browse/JBAS-8773 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: TBD-6.x Because of the way the log services are coordinated, some log configuration problems and runtime errors do not occur until after the bootstrap log handlers have already been removed. It would be better to not remove these handlers until the new ones are known to be good. Maybe by using replaceHandlers() in the logger service. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
1
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 January 2011