July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3128) Create a JON/RHQ plugin for Drools

by Edson Tirelli (JIRA)

Create a JON/RHQ plugin for Drools ---------------------------------- Key: JBRULES-3128 URL: https://issues.jboss.org/browse/JBRULES-3128 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assignee: Edson Tirelli Create a fully functional JON/RHQ plugin for Drools based on the POC developed a few years ago. Use latest Drools and RHQ versions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-9417) Upgrade to jboss-bootstrap 2.1.0-alpha-6

by Andrew Rubinger (JIRA)

Upgrade to jboss-bootstrap 2.1.0-alpha-6 ---------------------------------------- Key: JBAS-9417 URL: https://issues.jboss.org/browse/JBAS-9417 Project: Legacy JBoss Application Server 6 Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: 6.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-137) Release 2.1.0-alpha-6

by Andrew Rubinger (JIRA)

Release 2.1.0-alpha-6 --------------------- Key: JBBOOT-137 URL: https://issues.jboss.org/browse/JBBOOT-137 Project: JBoss Bootstrap Issue Type: Task Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: 2.1.0-alpha-6 Track commits to release 2.1.0-alpha-6 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-134) Add ClassPool support

by Andrew Lee Rubinger (JIRA)

Add ClassPool support --------------------- Key: JBBOOT-134 URL: https://jira.jboss.org/jira/browse/JBBOOT-134 Project: JBoss Bootstrap Issue Type: Feature Request Components: impl-base Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 2.1.0-alpha-6 Apply Kabir's work on optimization to reflection within MC/AS. -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3141) Replace BinaryHeapPriorityQueue Implementation with

by Brad Davis (JIRA)

Replace BinaryHeapPriorityQueue Implementation with ---------------------------------------------------- Key: JBRULES-3141 URL: https://issues.jboss.org/browse/JBRULES-3141 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brad Davis Assignee: Mark Proctor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (AS7-1295) interceptors are ignored when they are in <ear>/lib

by Oved O (JIRA)

interceptors are ignored when they are in <ear>/lib --------------------------------------------------- Key: AS7-1295 URL: https://issues.jboss.org/browse/AS7-1295 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.Final Environment: fedora 14 Reporter: Oved O Assignee: John Bailey Attachments: reproduction.tar.gz When an ejb have interceptor classes from jars in <ear>/lib, those interceptors are ignored. For example (this example is attached), assuming you have a jar in the lib directory, with MyInterceptor class, and a deployed jar with two ejbs (MyRegularUser and CallingRegularUser) and a local interceptor (MyLocalInterceptor). The CallingRegularUser depends on MyRegularUser ejb, and on the post process method it calls a method of MyRegularUser. When called, both MyLocalInterceptor and MyInterceptor should run, but only MyLocalInterceptor runs. The log: [oourfali@dhcp-1-30 bin]$ ./standalone.sh --server-config=standalone-preview.xml ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/tlv/oourfali/jboss-7.0.0.CR1 JAVA: /usr/java/jdk1.6.0_24/bin/java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Xrunjdwp:transport=dt_socket,address=7766,server=y,suspend=n ========================================================================= Listening for transport dt_socket at address: 7766 12:46:21,780 INFO [org.jboss.modules] JBoss Modules version 1.0.0.CR4 12:46:22,027 INFO [org.jboss.msc] JBoss MSC version 1.0.0.CR2 12:46:22,083 INFO [org.jboss.as] JBoss AS 7.0.0.CR1 "White Rabbit" starting 12:46:23,065 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1) 12:46:23,077 INFO [org.jboss.as.logging] Removing bootstrap log handlers 12:46:23,095 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2) 12:46:23,101 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0) 12:46:23,187 INFO [org.jboss.as.jacorb] (Controller Boot Thread) Activating JacORB Subsystem 12:46:23,319 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem 12:46:23,333 INFO [org.jboss.as.naming] (MSC service thread 1-1) Starting Naming Service 12:46:23,344 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem 12:46:23,364 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem 12:46:23,372 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 3.2.0.Beta2 12:46:23,388 INFO [org.xnio] (MSC service thread 1-5) XNIO Version 3.0.0.Beta3 12:46:23,405 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.0.0.Beta3 12:46:23,522 INFO [org.jboss.as.webservices] (Controller Boot Thread) Activating WebServices Extension 12:46:23,527 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-8) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/jdk1.6.0_24/jre/lib/amd64/server:/usr/java/jdk1.6.0_24/jre/lib/amd64:/usr/java/jdk1.6.0_24/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib 12:46:23,605 INFO [org.jboss.as.remoting] (MSC service thread 1-8) Listening on /10.35.203.35:9999 12:46:23,607 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-6) Starting remote JMX connector 12:46:23,628 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem 12:46:23,659 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-5) Unable to set the URLStreamHandlerFactory 12:46:23,667 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-5) Unable to set the ContentHandlerFactory 12:46:23,821 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-7) JBoss Web Services - Stack CXF Server 4.0.0.Beta2 12:46:23,829 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-vpn-203-35.tlv.redhat.com-10.35.203.35-8080 12:46:23,856 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/tlv/oourfali/jboss-7.0.0.CR1/standalone/data/messagingjournal,bindingsDirectory=/home/tlv/oourfali/jboss-7.0.0.CR1/standalone/data/messagingbindings,largeMessagesDirectory=/home/tlv/oourfali/jboss-7.0.0.CR1/standalone/data/messaginglargemessages,pagingDirectory=/home/tlv/oourfali/jboss-7.0.0.CR1/standalone/data/messagingpaging) 12:46:24,001 INFO [org.jboss.as.connector] (MSC service thread 1-3) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2) 12:46:24,099 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/datasources/ExampleDS] 12:46:24,140 INFO [org.jboss.as.jacorb] (MSC service thread 1-4) CORBA ORB Service Started 12:46:24,143 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) Bound data source [java:/RHEVMDataSource] 12:46:24,176 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) Registered connection factory java:/JmsXA on mdr 12:46:24,197 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-8) HornetQ resource adaptor started 12:46:24,197 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file://RaActivatorhornetq-ra 12:46:24,350 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-7) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} vpn-203-35.tlv.redhat.com:5455 for CORE protocol 12:46:24,365 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-7) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} vpn-203-35.tlv.redhat.com:5445 for CORE protocol 12:46:24,381 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) Server is now live 12:46:24,381 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) HornetQ Server version 2.2.6.Final (HQ_2_2_6_FINAL_AS7, 121) [81345b0c-a929-11e0-850e-001a4aebfff4] started 12:46:24,384 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) trying to deploy queue jms.queue.testQueue 12:46:24,402 INFO [org.jboss.as.jacorb] (MSC service thread 1-1) CORBA Naming Service Started 12:46:24,543 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) trying to deploy queue jms.topic.testTopic 12:46:24,806 INFO [org.jboss.as.deployment] (MSC service thread 1-2) Started FileSystemDeploymentService for directory /home/tlv/oourfali/jboss-7.0.0.CR1/standalone/deployments 12:46:24,812 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found reproduction.ear in deployment directory. To trigger deployment create a file called reproduction.ear.dodeploy 12:46:24,812 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found rhevm-genericapi.war in deployment directory. To trigger deployment create a file called rhevm-genericapi.war.dodeploy 12:46:24,812 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found rhevm-genericapi.jar in deployment directory. To trigger deployment create a file called rhevm-genericapi.jar.dodeploy 12:46:24,813 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found rhevm.ear in deployment directory. To trigger deployment create a file called rhevm.ear.dodeploy 12:46:24,824 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.CR1 "White Rabbit" started in 3253ms - Started 125 of 184 services (59 services are passive or on-demand) 12:46:24,842 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "reproduction.ear" 12:46:24,885 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "test_reg.jar" 12:46:24,973 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named CallingRegularUser in deployment unit subdeployment "test_reg.jar" of deployment "reproduction.ear" are as follows: java:global/reproduction/test_reg/CallingRegularUser!reproduction.regular_user.CallingRegularUser java:app/test_reg/CallingRegularUser!reproduction.regular_user.CallingRegularUser java:module/CallingRegularUser!reproduction.regular_user.CallingRegularUser java:global/reproduction/test_reg/CallingRegularUser java:app/test_reg/CallingRegularUser java:module/CallingRegularUser 12:46:24,973 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named MyRegularUser in deployment unit subdeployment "test_reg.jar" of deployment "reproduction.ear" are as follows: java:global/reproduction/test_reg/MyRegularUser!reproduction.regular_user.MyRegularUser java:app/test_reg/MyRegularUser!reproduction.regular_user.MyRegularUser java:module/MyRegularUser!reproduction.regular_user.MyRegularUser java:global/reproduction/test_reg/MyRegularUser java:app/test_reg/MyRegularUser java:module/MyRegularUser 12:46:25,069 INFO [org.jboss.as.ejb3.deployment.processors.EjbDependsOnAnnotationProcessor] (MSC service thread 1-1) CallingRegularUser bean has @DependsOn 12:46:25,120 INFO [stdout] (MSC service thread 1-6) My Regular User - initialized 12:46:25,122 INFO [stdout] (MSC service thread 1-2) CallingRegularUser - calling initialized 12:46:25,129 WARN [org.jboss.as.ejb3.component.EJBComponent] (MSC service thread 1-2) EJBTHREE-2120: deprecated getTransactionAttributeType method called (dev problem) 12:46:25,132 INFO [stdout] (MSC service thread 1-2) local interceptor - testing 12:46:25,132 INFO [stdout] (MSC service thread 1-2) MyRegularUser - doSomething 12:46:25,214 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "reproduction.ear" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1888) MessageProxy contains a field that is not serializable (added since JBMESSAGING-1878)

by Yong Hao Gao (JIRA)

MessageProxy contains a field that is not serializable (added since JBMESSAGING-1878) ------------------------------------------------------------------------------------- Key: JBMESSAGING-1888 URL: https://issues.jboss.org/browse/JBMESSAGING-1888 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.4.8.SP1, 1.4.0.SP3.CP13 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP14, 1.4.8.SP2 MessageProxy is a serializable class, therefore all its fields (non-transient) need to be serializable too. The field (source) is an instance of CallbackManager, which is a non-serializable class. Make it transient should solve the problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-1345) JDBC_PING fails to initialize table in mysql

by Raúl Raja Martínez (JIRA)

JDBC_PING fails to initialize table in mysql -------------------------------------------- Key: JGRP-1345 URL: https://issues.jboss.org/browse/JGRP-1345 Project: JGroups Issue Type: Bug Affects Versions: 2.12 Reporter: Raúl Raja Martínez Assignee: Bela Ban JDBC_PING fails to initialize DB table for discover when executing the following SQL: CREATE TABLE JGROUPSPING (own_addr varchar(200) NOT NULL, cluster_name varchar(200) NOT NULL, ping_data varbinary(5000) DEFAULT NULL, PRIMARY KEY (own_addr, cluster_name) ) The statement results in "Specified key was too long; max key length is 1000 bytes" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (AS7-1272) Infinispan subsystem configures its transport with invalid timeout values.

by Trustin Lee (JIRA)

Infinispan subsystem configures its transport with invalid timeout values. -------------------------------------------------------------------------- Key: AS7-1272 URL: https://issues.jboss.org/browse/AS7-1272 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.Final Reporter: Trustin Lee Assignee: Paul Ferraro Whenever I start the Infinispan subsystem, I see the following warning: {code} 13:20:23,854 WARN [org.infinispan.config.TimeoutConfigurationValidatingVisitor] (MSC service thread 1-4) ISPN00148: Invalid <transport>: distributedSyncTimout value of 240000. It can not be higher than <stateRetrieval>:timeout which is 10000 {code} The current subsystem configuration looks like the following: {code} <subsystem xmlns="urn:jboss:domain:infinispan:1.0" default-cache-container="default"> <cache-container name="default" default-cache="default" listener-executor="infinispan-listener" eviction-executor="infinispan-eviction" replication-queue-executor="infinispan-repl-queue"> <transport executor="infinispan-transport" lock-timeout="240000"/> <distributed-cache name="default" start="EAGER" mode="SYNC" virtual-nodes="1" owners="2" batching="false" indexing="NONE" l1-lifespan="0" remote-timeout="30000"> <locking isolation="REPEATABLE_READ" acquire-timeout="30000" concurrency-level="1000" striping="false" /> <rehashing enabled="true" timeout="600000" /> </distributed-cache> </cache-container> </subsystem> {code} It seems like there are not all attribute that correspond to all transport timeout properties. If that's intended, as least the subsystem should feed the sensible defaults to Infinispan. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1259) remove add/modify/remove-[xa-]data-source commands

by Alexey Loubyansky (JIRA)

remove add/modify/remove-[xa-]data-source commands -------------------------------------------------- Key: AS7-1259 URL: https://issues.jboss.org/browse/AS7-1259 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky These commands should be removed in favour of the generic type commands data-source and xa-data-source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011