[JBoss JIRA] Created: (AS7-1964) AbstractDataSourceService#stop() doesn't stop anything
by Bob McWhirter (JIRA)
AbstractDataSourceService#stop() doesn't stop anything
------------------------------------------------------
Key: AS7-1964
URL: https://issues.jboss.org/browse/AS7-1964
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.0.Alpha1
Reporter: Bob McWhirter
Assignee: Jesper Pedersen
The Service<T> for DataSources has a stop() method which simply nulls out its value, but doesn't stop/shutdown/destroy/clean-up anything else.
{noformat}
public synchronized void stop(StopContext stopContext) {
sqlDataSource = null;
}
{noformat}
In IRC, Jesper referenced JBJCA-672, resolved for IronJacamar 1.0.5
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (AS7-1447) data-source connection-url is not writable
by Nicklas Karlsson (JIRA)
data-source connection-url is not writable
------------------------------------------
Key: AS7-1447
URL: https://issues.jboss.org/browse/AS7-1447
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Final
Reporter: Nicklas Karlsson
Assignee: Jesper Pedersen
Trying to edit the JDBC URL of a datasource gives
22:51:00,148 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 1)
Operation ("write-attribute") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "java:jboss/datasources/ExampleDS")
]) - failure description: "Attribute connection-url is not writeable"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (AS7-1881) Some property in resource-adapters are duplicated in wrong positions
by Stefano Maestri (JIRA)
Some property in resource-adapters are duplicated in wrong positions
--------------------------------------------------------------------
Key: AS7-1881
URL: https://issues.jboss.org/browse/AS7-1881
Project: Application Server 7
Issue Type: Clarification
Components: JCA
Reporter: Stefano Maestri
Assignee: Stefano Maestri
Fix For: 7.1.0.Beta1
{noformat}
[standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=xmpp-ra.rar:read-resource
{
"outcome" => "success",
"result" => {
"archive" => "xmpp-ra.rar",
"background-validation" => undefined,
"background-validation-millis" => undefined,
"blocking-timeout-wait-millis" => undefined,
"config-properties" => {"host" => "talk.google.om"},
"connection-definitions" => [{
"class-name" => "com.ramphastos.xmpp.XmppConnectionFactory",
"jndi-name" => "xmpp",
"pool-name" => "xmpp-ra_rar-Pool",
"min-pool-size" => 10,
"max-pool-size" => 100
}],
"flush-strategy" => undefined,
"idle-timeout-minutes" => undefined,
"max-pool-size" => undefined,
"min-pool-size" => undefined,
"pool-prefill" => undefined,
"pool-use-strict-min" => undefined,
"transaction-support" => "NoTransaction"
}
}
{noformat}
why two times min/max-pool-size? which one to rely on?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (AS7-1665) Problem with JBoss 7
by Peter Penzov (JIRA)
Problem with JBoss 7
--------------------
Key: AS7-1665
URL: https://issues.jboss.org/browse/AS7-1665
Project: Application Server 7
Issue Type: Enhancement
Reporter: Peter Penzov
Priority: Minor
rcbandit@rcbandit-laptop:~/Desktop/jboss-as-7.0.1.Final/bin$ ./domain.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/rcbandit/Desktop/jboss-as-7.0.1.Final
JAVA: 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
=========================================================================
12:17:36,671 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
12:17:38,033 INFO [org.jboss.as.process.Host Controller.status] (main) Starting process 'Host Controller'
[Host Controller] 12:17:38,606 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
[Host Controller] 12:17:39,953 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
[Host Controller] 12:17:41,139 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2
[Host Controller] 12:17:41,287 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3
[Host Controller] 12:17:41,457 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3
[Host Controller] 12:17:46,885 WARN [org.jboss.as] (Controller Boot Thread) No security realm defined for native management service, all access will be unrestricted.
[Host Controller] 12:17:46,892 INFO [org.jboss.as] (Controller Boot Thread) creating http management service using network interface (management) port (9990)
[Host Controller] 12:17:46,926 WARN [org.jboss.as] (Controller Boot Thread) No security realm defined for http management service, all access will be unrestricted.
[Host Controller] 12:17:47,502 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /127.0.0.1:9999
[Host Controller] 12:17:47,629 INFO [org.jboss.as.host.controller] (Controller Boot Thread) Starting server server-one
12:17:47,693 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) Starting process 'Server:server-one'
[Host Controller] 12:17:48,044 INFO [org.jboss.as.host.controller] (Controller Boot Thread) Starting server server-two
12:17:48,115 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) Starting process 'Server:server-two'
[Server:server-one] 12:17:49,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
[Server:server-two] 12:17:49,087 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
[Server:server-two] 12:17:50,023 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
[Server:server-one] 12:17:50,044 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
[Server:server-two] 12:17:50,197 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.1.Final "Zap" starting
[Server:server-one] 12:17:50,250 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.1.Final "Zap" starting
[Server:server-one] 12:17:52,015 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-4) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/lib/jvm/java-6-openjdk/jre/lib/i386/server:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/i386-linux-gnu/jni:/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/usr/lib/jni:/lib:/usr/lib
[Server:server-two] 12:17:52,018 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-3) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/lib/jvm/java-6-openjdk/jre/lib/i386/server:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/i386-linux-gnu/jni:/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/usr/lib/jni:/lib:/usr/lib
[Server:server-one] 12:17:52,341 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
[Server:server-two] 12:17:52,344 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8230
[Server:server-two] 12:17:52,677 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32010: JBossTS Recovery Service (tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
[Server:server-one] 12:17:52,695 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA32010: JBossTS Recovery Service (tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
[Server:server-one] 12:17:52,702 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
[Server:server-two] 12:17:52,716 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA12324: Start RecoveryActivators
[Server:server-two] 12:17:52,778 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
[Server:server-one] 12:17:52,815 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-2) ARJUNA12324: Start RecoveryActivators
[Server:server-two] 12:17:52,826 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA12296: ExpiredEntryMonitor running at Mon, 29 Aug 2011 12:17:52
[Server:server-one] 12:17:52,865 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA12296: ExpiredEntryMonitor running at Mon, 29 Aug 2011 12:17:52
[Server:server-two] 12:17:52,881 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA12343: RecoveryManagerImple is ready. Socket listener is turned off.
[Server:server-two] 12:17:52,881 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32013: Starting transaction recovery manager
[Server:server-one] 12:17:52,967 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-2) ARJUNA12343: RecoveryManagerImple is ready. Socket listener is turned off.
[Server:server-one] 12:17:52,967 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA32013: Starting transaction recovery manager
[Server:server-two] 12:17:52,984 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
[Server:server-one] 12:17:53,021 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA32017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
[Server:server-two] 12:17:53,052 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
[Server:server-one] 12:17:53,050 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
[Server:server-one] 12:17:53,080 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
[Server:server-two] 12:17:53,087 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
[Server:server-one] 12:17:53,222 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
[Server:server-two] 12:17:53,222 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
[Server:server-two] 12:17:53,282 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
[Server:server-one] 12:17:53,319 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
[Server:server-one] 12:17:53,323 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
[Server:server-two] 12:17:53,458 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
[Server:server-one] 12:17:53,501 INFO [org.jboss.as.naming] (MSC service thread 1-1) Starting Naming Service
[Server:server-two] 12:17:53,636 INFO [org.jboss.as.naming] (MSC service thread 1-4) Starting Naming Service
[Server:server-two] 12:17:53,881 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-4) Starting remote JMX connector
[Server:server-one] 12:17:53,881 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector
[Server:server-one] 12:17:54,237 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
[Server:server-one] 12:17:54,278 INFO [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
[Server:server-two] 12:17:54,288 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
[Server:server-two] 12:17:54,455 INFO [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
[Host Controller] 12:17:55,350 INFO [org.jboss.as.host.controller.mgmt] (pool-3-thread-1) Server [Server:server-one] registered using connection [org.jboss.as.protocol.mgmt.ManagementChannel@5facbd]
[Host Controller] 12:17:55,375 INFO [org.jboss.as.host.controller.mgmt] (pool-3-thread-2) Server [Server:server-two] registered using connection [org.jboss.as.protocol.mgmt.ManagementChannel@b124fa]
[Host Controller] 12:17:55,405 INFO [org.jboss.host.controller] (pool-3-thread-2) Registering server server-two
[Host Controller] 12:17:55,406 INFO [org.jboss.host.controller] (pool-3-thread-1) Registering server server-one
[Server:server-two] 12:17:55,656 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
[Server:server-one] 12:17:55,656 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
[Server:server-one] 12:17:55,711 INFO [org.jboss.as.logging] (MSC service thread 1-4) Removing bootstrap log handlers
[Server:server-two] 12:17:55,758 INFO [org.jboss.as.logging] (MSC service thread 1-4) Removing bootstrap log handlers
[Server:server-one] 12:17:55,831 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/ExampleDS]
[Server:server-two] 12:17:55,835 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) Bound data source [java:jboss/datasources/ExampleDS]
[Server:server-one] 12:17:56,972 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-two] 12:17:56,972 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-one] 12:17:57,035 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 8915ms - Started 87 of 138 services (51 services are passive or on-demand)
[Server:server-two] 12:17:57,043 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 8758ms - Started 87 of 138 services (51 services are passive or on-demand)
[Host Controller] 12:20:06,708 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
[Host Controller] 12:20:12,786 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (LOGTOOL-27) Extended interfaces should find translations for the interface that was extended
by James Perkins (JIRA)
Extended interfaces should find translations for the interface that was extended
--------------------------------------------------------------------------------
Key: LOGTOOL-27
URL: https://issues.jboss.org/browse/LOGTOOL-27
Project: Log Tool
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: James Perkins
Assignee: James Perkins
Currently if an interface is extended both the super interface needs translation files and the sub-interface needs the same messages translated. Either the messages need to be discovered and generated into the subtype or the subtype needs to extend the supertypes implementation.
Extending the supertypes implementation does leave the generated code more simple, but would require that any extended interfaces be annotated with @MessageLogger or @MessageBundle.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (LOGTOOL-31) Allow exception methods to set fields on the exception object
by David Lloyd (JIRA)
Allow exception methods to set fields on the exception object
-------------------------------------------------------------
Key: LOGTOOL-31
URL: https://issues.jboss.org/browse/LOGTOOL-31
Project: Log Tool
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 1.0.0.Beta9
Create a new annotation called @Field which accepts a single string parameter. For methods which return an exception, the values of these parameters will be assigned to fields on the exception object with the corresponding name.
For example:
{code}
@Message(id = 1000, "The transaction failed because blah blah %s")
XAException transactionFailedBlah(String blah, @Field("errorCode") int errorCode);
// should also continue to work with @Cause in conjunction with exceptions which don't have a cause param:
@Message(id = 1001, "The operation was interrupted unexpectedly by %s")
InterruptedIOException surprise(String reason, @Cause Throwable someCause, @Field("bytesTransferred") int bytesTransferred);
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months