February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6619) Management API for Datasources subsystem is missing some properties

by Zbyněk Roubalík (JIRA)

Zbyněk Roubalík created AS7-6619: ------------------------------------ Summary: Management API for Datasources subsystem is missing some properties Key: AS7-6619 URL: https://issues.jboss.org/browse/AS7-6619 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.2.0.Alpha1 Reporter: Zbyněk Roubalík Assignee: Stefano Maestri Some properties which were present in previous versions of AS7 are missing in current release: Parameter driver-name for operation 'get-installed-driver' is no longer available. These value-type for 'reply-properties' for operation 'get-installed-driver' are no longer available: [jdbc-compliant, module-slot, driver-class-name, driver-module-name] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6617) Struts actions are not getting linked to modules

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6617?page=com.atlassian.jira.plugin.s... ] David Lloyd closed AS7-6617. ---------------------------- Resolution: Rejected This is a user question, not a bug. Please direct questions to the user forums. Thank you. > Struts actions are not getting linked to modules > ------------------------------------------------ > > Key: AS7-6617 > URL: https://issues.jboss.org/browse/AS7-6617 > Project: Application Server 7 > Issue Type: Clarification > Environment: Windows XP > Reporter: lalithambigai sigaamani > > Failed to define class *action.java in Module "deployment.XXX.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link *action.java(Module "deployment.XXX.war:main" from Service Module Loader) > Caused by: java.lang.NoClassDefFoundError: IllegalName: *action.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4844) Extremely slow response times in Remote EJB invocation on cluster membership change

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4844?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4844: ---------------------------------------------- Jitka Kudrnacova <jkudrnac(a)redhat.com> made a comment on [bug 900480|https://bugzilla.redhat.com/show_bug.cgi?id=900480] Still present in 6.1.0.DR4 build: http://hudson.qa.jboss.com/hudson/job/eap-6x-failover-ejb-ejbremote-shutd... > Extremely slow response times in Remote EJB invocation on cluster membership change > ----------------------------------------------------------------------------------- > > Key: AS7-4844 > URL: https://issues.jboss.org/browse/AS7-4844 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 7.1.2.Final (EAP) > Reporter: Radoslav Husar > Assignee: jaikiran pai > Labels: failover_testing > Fix For: 7.2.0.CR1 > > > In failover scenarios [1], the response times of remote EJB client are sometimes extremely large. > On *graceful* shutdown, response times reach up to one minute [2]. Graceful failover is a positive test, no such exceptions are anticipated. > On server crash in a cluster, RTs reach up to 1 minute as well [3]. > [1] https://docspace.corp.redhat.com/docs/DOC-92019#Failover_Tests > [2] http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x... > [3] http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6618) Upgrade Infinispan to 5.2.2.Final

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-6618: ----------------------------------- Summary: Upgrade Infinispan to 5.2.2.Final Key: AS7-6618 URL: https://issues.jboss.org/browse/AS7-6618 Project: Application Server 7 Issue Type: Bug Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 8.0.0.Alpha1 Tag: https://github.com/infinispan/infinispan/tree/5.2.2.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4268) Add JMS bridge to Messaging subsystem

by Shameer Kunjumohamed (JIRA)

[ https://issues.jboss.org/browse/AS7-4268?page=com.atlassian.jira.plugin.s... ] Shameer Kunjumohamed commented on AS7-4268: ------------------------------------------- Yes, thanks Jeff. > Add JMS bridge to Messaging subsystem > ------------------------------------- > > Key: AS7-4268 > URL: https://issues.jboss.org/browse/AS7-4268 > Project: Application Server 7 > Issue Type: Task > Components: JMS > Affects Versions: 7.1.1.Final > Reporter: Justin Bertram > Assignee: Jeff Mesnil > Fix For: 7.2.0.Alpha1 > > > Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7. In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it. The bridge is a nice feature so we need a way to deploy it. > > It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server. It really needs its own subsystem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5562) Log message too cryptic when deployment references a non-existent configuration in profile config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5562?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5562: ---------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 900892|https://bugzilla.redhat.com/show_bug.cgi?id=900892] If this should be included in EAP 6.1.0, jboss-eap-6.1.0 flag must be selected to enter 3-ACK process. Please set pm, dev, qa acks to '?' too. > Log message too cryptic when deployment references a non-existent configuration in profile config > ------------------------------------------------------------------------------------------------- > > Key: AS7-5562 > URL: https://issues.jboss.org/browse/AS7-5562 > Project: Application Server 7 > Issue Type: Enhancement > Components: Server > Affects Versions: 7.1.2.Final (EAP) > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: Open To Community > > Attachments: helloWorld.ear, helloWorld.ear-source.zip > > > When a jboss-ejb-client.xml inside of a deployment that references an outbound-socket that does not exist in the standalone.xml, it logs a cryptic message and does not explain where the issue is. Note when a deployment contains more sub deployements, the log message is much larger and the issue if you know what to look for is hidden in the middle. > 15:41:01,189 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.dd-based-ejb-client-context.\"helloWorld.ear\" Missing[jboss.remoting.endpoint.subsystem.outbound-connection.part101node01-connection]","jboss.deployment.subunit.\"helloWorld.ear\".\"helloWorld.war\".INSTALL Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"helloWorld.ear\".INSTALL Missing[JBAS014861: <one or more transitive dependencies>]"]}}} > The error message should be translated to say something to the extent of > "Your deployment helloWorld.ear contains a jboss-ejb-client.xml which references an outbound-socket named part101node01 which is not defined in your JBoss profile's remoting subsystem configuration" > jboss.ejb3.dd-based-ejb-client-context.\"helloWorld.ear - this shows that helloWorld.ear is the deployment, jboss.ejb3.dd-based-ejb-client-context seems to the jboss-ejb-client.xml > jboss.remoting.endpoint.subsystem.outbound-connection.part101node01-connection - this shows that the subsystem that is missing the outbound-configuration is the remoting subsystem and that the reference name missing is part101node01 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6070) Domain mode: kill an unresponsive JVM

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6070?page=com.atlassian.jira.plugin.s... ] Heiko Braun reassigned AS7-6070: -------------------------------- Assignee: Brian Stansberry (was: Heiko Braun) > Domain mode: kill an unresponsive JVM > ------------------------------------- > > Key: AS7-6070 > URL: https://issues.jboss.org/browse/AS7-6070 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Dennis Reed > Assignee: Brian Stansberry > > If an AS instance gets into a state where it cannot be controlled normally by the host controller, local OS commands must be used to kill it. > It would be helpful to be able to kill an unresponsive JVM through the management interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1600) Deadlock in Infinispan with TCP and use_send_queues=true

by Bela Ban (JIRA)

Bela Ban created JGRP-1600: ------------------------------ Summary: Deadlock in Infinispan with TCP and use_send_queues=true Key: JGRP-1600 URL: https://issues.jboss.org/browse/JGRP-1600 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.3 https://issues.jboss.org/browse/ISPN-2836 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-53) buildDialectConfigurationMap BUG

by kevin hu (JIRA)

kevin hu created DROOLS-53: ------------------------------ Summary: buildDialectConfigurationMap BUG Key: DROOLS-53 URL: https://issues.jboss.org/browse/DROOLS-53 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.5 Environment: drools5.5 jbmp4.3 Reporter: kevin hu Assignee: Mark Proctor When I use jbmp4.3 completed a process,Once again the execution Drools, will get the following error: java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.lang.String at java.util.Properties.enumerate(Properties.java:1060) at java.util.Properties.propertyNames(Properties.java:971) at org.drools.util.ChainedProperties.mapStartsWith(ChainedProperties.java:206) at org.drools.util.ChainedProperties.mapStartsWith(ChainedProperties.java:188) at org.drools.compiler.PackageBuilderConfiguration.buildDialectConfigurationMap(PackageBuilderConfiguration.java:297) at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:192) at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170) at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:300) at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:228) at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilder(KnowledgeBuilderFactoryServiceImpl.java:34) at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilder(KnowledgeBuilderFactory.java:46) The content of is as follows: -------------------------------------------------------------------------------- (java.util.Properties) {java.runtime.name=Java(TM) SE Runtime Environment, [100001, WebappClassLoader context: /mit delegate: false repositories: /WEB-INF/classes/ ----------> Parent Classloader: org.apache.catalina.loader.StandardClassLoader@ec6b00 ]=org.jbpm.pvm.internal.repository.DeploymentClassLoader@77576b, sun.boot.library.path=C:\Program Files (x86)\Java\jdk1.6.0_37\jre\bin, java.vm.version=20.12-b01, shared.loader=, 100001={WorkNoBom=process(WorkNoBom)}, java.vm.vendor=Sun Microsystems Inc., java.vendor.url=http://java.sun.com/, path.separator=;, tomcat.util.buf.StringCache.byte.enabled=true, java.vm.name=Java HotSpot(TM) Client VM, file.encoding.pkg=sun.io, sun.java.launcher=SUN_STANDARD, user.country=CN, sun.os.patch.level=Service Pack 1, java.vm.specification.name=Java Virtual Machine Specification, user.dir=D:\apache-tomcat-6.0.36\bin, java.runtime.version=1.6.0_37-b06, java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment, java.endorsed.dirs=D:\apache-tomcat-6.0.36/common/endorsed, os.arch=x86, webapp.root=E:\Workspaces\mdb_web\WebRoot\, java.io.tmpdir=D:\apache-tomcat-6.0.36\temp, line.separator= , java.vm.specification.vendor=Sun Microsystems Inc., java.naming.factory.url.pkgs=org.apache.naming, user.variant=, os.name=Windows 7, sun.jnu.encoding=GBK, java.library.path=C:\Program Files (x86)\Java\jdk1.6.0_37\bin;D:\apache-tomcat-6.0.36\bin, java.specification.name=Java Platform API Specification, java.class.version=50.0, sun.management.compiler=HotSpot Client Compiler, sun.io.useCanonCaches=false, os.version=6.1, user.home=C:\Users\kevin.hu, catalina.useNaming=true, user.timezone=Asia/Shanghai, java.awt.printerjob=sun.awt.windows.WPrinterJob, file.encoding=GBK, java.specification.version=1.6, catalina.home=D:\apache-tomcat-6.0.36, java.class.path=D:\apache-tomcat-6.0.36/bin/bootstrap.jar;C:\Program Files (x86)\Java\jdk1.6.0_37/lib/tools.jar, user.name=kevin.hu, java.naming.factory.initial=org.apache.naming.java.javaURLContextFactory, package.definition=sun.,java.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper., java.vm.specification.version=1.0, sun.java.command=org.apache.catalina.startup.Bootstrap start, java.home=C:\Program Files (x86)\Java\jdk1.6.0_37\jre, sun.arch.data.model=32, user.language=zh, java.specification.vendor=Sun Microsystems Inc., awt.toolkit=sun.awt.windows.WToolkit, java.vm.info=mixed mode, java.version=1.6.0_37, java.ext.dirs=C:\Program Files (x86)\Java\jdk1.6.0_37\jre\lib\ext;C:\Windows\Sun\Java\lib\ext, sun.boot.class.path=C:\Program Files (x86)\Java\jdk1.6.0_37\jre\lib\resources.jar;C:\Program Files (x86)\Java\jdk1.6.0_37\jre\lib\rt.jar;C:\Program Files (x86)\Java\jdk1.6.0_37\jre\lib\sunrsasign.jar;C:\Program Files (x86)\Java\jdk1.6.0_37\jre\lib\jsse.jar;C:\Program Files (x86)\Java\jdk1.6.0_37\jre\lib\jce.jar;C:\Program Files (x86)\Java\jdk1.6.0_37\jre\lib\charsets.jar;C:\Program Files (x86)\Java\jdk1.6.0_37\jre\lib\modules\jdk.boot.jar;C:\Program Files (x86)\Java\jdk1.6.0_37\jre\classes, server.loader=, java.vendor=Sun Microsystems Inc., catalina.base=D:\apache-tomcat-6.0.36, file.separator=\, java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi, common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar, sun.io.unicode.encoding=UnicodeLittle, sun.cpu.endian=little, package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.,sun.beans., sun.desktop=windows, sun.cpu.isalist=pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86} ------------------------------------------------------------ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-263) Remove WeakHash map from BeanELResolver and depend on proper callback to remove bean properties

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/JBWEB-263?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski commented on JBWEB-263: ------------------------------------------ Well, porting class would require a lot of changes(3.x branch code is quite different) which I dont think are acceptable for 2.x branch? I just switched key class in map(that seems to be the difference between 3.x and 2.x in this department). Test run seems to be fine. Im trying to profile now just to double check. > Remove WeakHash map from BeanELResolver and depend on proper callback to remove bean properties > ----------------------------------------------------------------------------------------------- > > Key: JBWEB-263 > URL: https://issues.jboss.org/browse/JBWEB-263 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Bartosz Baranowski > Assignee: Remy Maucherat > Attachments: JBWEB-263.patch, JBWEB-263.patch > > > As in subject. Even though its a weakhashmap( and current source has the ConcurrentCache. > Affected version: 2.1.12.GA - http://svn.jboss.org/repos/jbossweb/branches/2.1.x/ > Fix version: next( EAP depends on 2.1.13.GA-patch01 or JBOSSWEB_2_1_12_GA_patch03 ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
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 February 2013