[JBoss JIRA] (AS7-5527) add-user utility reports "No java.io.Console available to interact with user." when used silently with su and piped to a file.
by Tom Jenkinson (JIRA)
Tom Jenkinson created AS7-5527:
----------------------------------
Summary: add-user utility reports "No java.io.Console available to interact with user." when used silently with su and piped to a file.
Key: AS7-5527
URL: https://issues.jboss.org/browse/AS7-5527
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.2.0.Alpha1
Reporter: Tom Jenkinson
./add-user.sh from a script does not work anymore. In previous versions it worked. It has to do with the "theConsole" object being null.
In the same breadth, the --silent=true option in add-user.sh does not work anymore. Again has to do with the need for "theConsole" object being null.
The --silent=true option was added because in some environments, System.console() returns null[for example when the Izpack installer calls that script] and the add-user.sh script breaks because of its dependence on System.console() object to print stuff.
This is using a build (jboss-as-7.2.0.Alpha1-SNAPSHOT) of master from today:
[tom@tomsfc16 bin]$ sudo ./add-user.sh --silent=true foo bar > /tmp/capture.log 2>&1
[tom@tomsfc16 bin]$ cat /tmp/capture.log
Exception in thread "main" java.lang.IllegalStateException: JBAS015232: No java.io.Console available to interact with user.
at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:97)
at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.modules.Module.run(Module.java:270)
at org.jboss.modules.Main.main(Main.java:294)
--
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, 8 months
[JBoss JIRA] (AS7-5061) CLONE - add-user script broken
by Samuel Doyle (JIRA)
Samuel Doyle created AS7-5061:
---------------------------------
Summary: CLONE - add-user script broken
Key: AS7-5061
URL: https://issues.jboss.org/browse/AS7-5061
Project: Application Server 7
Issue Type: Bug
Reporter: Samuel Doyle
Assignee: Darran Lofthouse
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
./add-user.sh dustin dustin1 does not work anymore. In previous versions it worked. It has to do with the "theConsole" object being null.
In the same breadth, the --silent=true option in add-user.sh does not work anymore. Again has to do with the need for "theConsole" object being null.
The --silent=true option was added because in some environments, System.console() returns null[for example when the Izpack installer calls that script] and the add-user.sh script breaks because of its dependence on System.console() object to print stuff.
[the "theConsole" object calls the System.console() object]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5485) Exploded mount relies on deployment extension
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5485:
-----------------------------------
Summary: Exploded mount relies on deployment extension
Key: AS7-5485
URL: https://issues.jboss.org/browse/AS7-5485
Project: Application Server 7
Issue Type: Feature Request
Components: OSGi, Server
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
The web subsystem relies on exploded mounts. Currently we mark the deployment as exploded for *.war and *.wab
As a result OSGi webapps with *.jar extension do not get exploded and resources cannot be accessed via the associated web context.
--
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, 8 months
[JBoss JIRA] (AS7-5357) Read-Only Property Without Value - Initial Message Package Size
by Stefan Negrea (JIRA)
Stefan Negrea created AS7-5357:
----------------------------------
Summary: Read-Only Property Without Value - Initial Message Package Size
Key: AS7-5357
URL: https://issues.jboss.org/browse/AS7-5357
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.2.Final (EAP)
Reporter: Stefan Negrea
Initial-message-packet-size property of a connection-factory does not have a value for profiles even though it is read-only. The expectation is that server returns the default value. The example below uses the full profile but the issue is applicable to all other profiles that have the messaging subsystem.
Property: initial-message-packet-size
Path: /profile=full/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory
Sample CLI output:
[domain@localhost:9999 /] cd profile=full/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory
[domain@localhost:9999 connection-factory=RemoteConnectionFactory] :read-resource-description
{
"outcome" => "success",
"result" => {
......
"initial-message-packet-size" => {
"description" => "The initial size of messages created through this factory.",
"type" => INT,
"nillable" => false,
"unit" => "BYTES",
"access-type" => "read-only",
"storage" => "configuration"
}
"operations" => undefined,
"children" => {}
}
}
[domain@localhost:9999 connection-factory=RemoteConnectionFactory] :read-resource(include-runtime=true,include-defaults=true)
{
"outcome" => "success",
"result" => {
"auto-group" => false,
"block-on-acknowledge" => false,
"block-on-durable-send" => true,
"block-on-non-durable-send" => false,
"cache-large-message-client" => false,
"call-timeout" => 30000L,
"client-failure-check-period" => 30000,
"client-id" => undefined,
"compress-large-messages" => false,
"confirmation-window-size" => -1,
"connection-load-balancing-policy-class-name" => "org.hornetq.api.core.client.loadbalance.RoundRobinConnectionLoadBalancingPolicy",
"connection-ttl" => "60000",
"connector" => {"netty" => undefined},
"consumer-max-rate" => -1,
"consumer-window-size" => 1048576,
"discovery-group-name" => undefined,
"discovery-initial-wait-timeout" => undefined,
"dups-ok-batch-size" => 1048576,
"entries" => ["java:jboss/exported/jms/RemoteConnectionFactory"],
"factory-type" => undefined,
"failover-on-initial-connection" => false,
"failover-on-server-shutdown" => undefined,
"group-id" => undefined,
"ha" => false,
"max-retry-interval" => "2000",
"min-large-message-size" => 102400,
"pre-acknowledge" => false,
"producer-max-rate" => -1,
"producer-window-size" => 65536,
"reconnect-attempts" => 0,
"retry-interval" => 2000L,
"retry-interval-multiplier" => "1.0",
"scheduled-thread-pool-max-size" => 5,
"thread-pool-max-size" => 30,
"transaction-batch-size" => 1048576,
"use-global-pools" => true
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5529) Webserver Not Responding
by GUNASEKHAR YALAMURI (JIRA)
GUNASEKHAR YALAMURI created AS7-5529:
----------------------------------------
Summary: Webserver Not Responding
Key: AS7-5529
URL: https://issues.jboss.org/browse/AS7-5529
Project: Application Server 7
Issue Type: Clarification
Environment: Production
Reporter: GUNASEKHAR YALAMURI
Priority: Blocker
My Application Server is not Responding, Attaching are the GCC Logs generated.
--
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, 8 months
[JBoss JIRA] (AS7-5396) Persistent resolve before the complete set is installed
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5396:
-----------------------------------
Summary: Persistent resolve before the complete set is installed
Key: AS7-5396
URL: https://issues.jboss.org/browse/AS7-5396
Project: Application Server 7
Issue Type: Bug
Reporter: Thomas Diesler
Priority: Critical
On server restart we process initial deployments in parallel. For a large set, deploymentA could race many phases ahead of deploymentB with no particular order in which these deployments are processed.
With osgi deployments we may see a resolve problem because there is a central entity (i.e. the resolver) which works on the complete set of metadata of the installed deployments, which implies some sort of processing order. The minimum requirement would be that all deployments in a given set get processed by one phase before any deployment moves on to the next phase.
{code}
07:09:46,473 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011006: OSGi Framework - 2.0.0.CR20
07:09:46,884 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: jboss-osgi-logging:1.0.0
07:09:46,900 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.apache.felix.log:1.0.0
07:09:46,924 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
07:09:46,929 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.apache.felix.configadmin:1.2.8
07:09:47,440 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.apache.geronimo.specs.geronimo-annotation_1.0_spec:1.1.1
07:09:47,450 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.apache.servicemix.specs.saaj-api-1.3:1.9.0
07:09:47,446 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.apache.ws.xmlschema.core:2.0.1
07:09:47,451 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.springframework.expression:3.0.6.RELEASE
07:09:47,464 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: com.springsource.org.apache.commons.logging:1.1.1
07:09:47,468 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.springframework.asm:3.0.6.RELEASE
07:09:47,465 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.apache.geronimo.specs.geronimo-activation_1.1_spec:1.1.0
07:09:47,479 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.apache.geronimo.specs.geronimo-servlet_3.0_spec:1.0.0
07:09:47,485 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: stax2-api:3.1.1
07:09:47,500 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.apache.servicemix.bundles.asm:3.3.0.2
07:09:47,510 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.springframework.osgi.core:1.2.1
07:09:47,520 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.apache.servicemix.specs.stax-api-1.0:1.9.0
07:09:47,522 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: com.springsource.org.aopalliance:1.0.0
07:09:47,529 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.apache.geronimo.specs.geronimo-ws-metadata_2.0_spec:1.1.3
07:09:47,551 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.springframework.beans:3.0.6.RELEASE
07:09:47,552 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.apache.servicemix.bundles.joda-time:1.5.2.4
07:09:47,554 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.eclipse.jetty.aggregate.jetty-all-server:7.4.2.v20110526
07:09:47,565 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.ops4j.pax.web.pax-web-runtime:1.0.3
07:09:47,570 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.apache.servicemix.bundles.commons-pool:1.5.4.1
07:09:47,567 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.apache.servicemix.bundles.wsdl4j:1.6.2.5
07:09:47,589 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.apache.servicemix.specs.jsr311-api-1.1.1:1.9.0
07:09:47,602 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.apache.servicemix.bundles.xmlsec:1.4.5.1
07:09:47,604 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.ops4j.pax.web.pax-web-spi:1.0.3
07:09:47,608 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.apache.servicemix.specs.jaxb-api-2.1:1.9.0
07:09:47,612 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.springframework.aop:3.0.6.RELEASE
07:09:47,633 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.springframework.osgi.extender:1.2.1
07:09:47,634 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: cxf-dosgi-ri-topology-manager:1.4.0.SNAPSHOT
07:09:47,655 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.apache.geronimo.specs.geronimo-javamail_1.4_spec:1.2.0
07:09:47,638 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: com.springsource.org.jdom:1.1.0
07:09:47,661 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.apache.neethi:3.0.1
07:09:47,673 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.springframework.core:3.0.6.RELEASE
07:09:47,696 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: cxf-dosgi-ri-dsw-cxf:1.4.0.SNAPSHOT
07:09:47,699 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.apache.servicemix.bundles.xmlresolver:1.2.0.4
07:09:47,701 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: com.springsource.slf4j.jcl:1.5.10
07:09:47,697 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: woodstox-core-asl:4.1.1
07:09:47,719 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: com.springsource.slf4j.api:1.5.10
07:09:47,737 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: osgi.enterprise:4.2.0.201003190513
07:09:47,754 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.apache.servicemix.bundles.jaxb-impl:2.1.13.2
07:09:47,740 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: cxf-dosgi-ri-discovery-local:1.4.0.SNAPSHOT
07:09:47,776 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.apache.servicemix.specs.jaxws-api-2.1:1.9.0
07:09:47,779 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.springframework.osgi.io:1.2.1
07:09:47,809 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001: Bundle installed: org.ops4j.pax.web.pax-web-jetty:1.0.3
07:09:47,833 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.springframework.context:3.0.6.RELEASE
07:09:47,882 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.springframework.context.ApplicationContext,org.springframework.beans.BeansException' for service type 'org.apache.cxf.bus.factory'
07:09:47,912 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: spring-expression-3.0.6.RELEASE.jar
07:09:47,915 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: com.springsource.org.apache.commons.logging-1.1.1.jar
07:09:47,916 INFO [org.jboss.as.osgi] (MSC service thread 1-4) Resolve: xmlschema-core-2.0.1.jar
07:09:47,932 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: org.apache.servicemix.bundles.opensaml:2.4.1.1
07:09:47,938 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: geronimo-activation_1.1_spec-1.1.jar
07:09:48,223 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: spring-asm-3.0.6.RELEASE.jar
07:09:48,233 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: geronimo-servlet_3.0_spec-1.0.jar
07:09:48,290 INFO [org.jboss.as.osgi] (MSC service thread 1-4) Resolve: stax2-api-3.1.1.jar
07:09:48,321 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: geronimo-annotation_1.0_spec-1.1.1.jar
07:09:48,328 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: spring-osgi-core-1.2.1.jar
07:09:48,337 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: org.apache.servicemix.specs.saaj-api-1.3-1.9.0.jar
07:09:48,392 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: spring-beans-3.0.6.RELEASE.jar
07:09:48,399 INFO [org.jboss.as.osgi] (MSC service thread 1-4) Resolve: org.apache.servicemix.bundles.joda-time-1.5.2_4.jar
07:09:48,662 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: org.apache.servicemix.bundles.asm-3.3_2.jar
07:09:48,667 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: com.springsource.org.aopalliance-1.0.0.jar
07:09:48,680 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: jetty-all-server-7.4.2.v20110526.jar
07:09:48,758 INFO [org.jboss.as.osgi] (MSC service thread 1-4) Resolve: geronimo-ws-metadata_2.0_spec-1.1.3.jar
07:09:48,764 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: org.apache.servicemix.bundles.commons-pool-1.5.4_1.jar
07:09:48,767 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: org.apache.servicemix.bundles.wsdl4j-1.6.2_5.jar
07:09:48,899 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: org.apache.servicemix.specs.jsr311-api-1.1.1-1.9.0.jar
07:09:48,900 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: org.apache.servicemix.specs.jaxb-api-2.1-1.9.0.jar
07:09:48,907 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: spring-aop-3.0.6.RELEASE.jar
07:09:48,900 INFO [org.jboss.as.osgi] (MSC service thread 1-4) Resolve: org.apache.servicemix.specs.stax-api-1.0-1.9.0.jar
07:09:48,928 INFO [org.jboss.as.osgi] (MSC service thread 1-4) Resolve: spring-osgi-extender-1.2.1.jar
07:09:48,929 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: cxf-dosgi-ri-topology-manager-1.4-SNAPSHOT.jar
07:09:48,939 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: com.springsource.org.jdom-1.1.0.jar
07:09:48,941 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: spring-core-3.0.6.RELEASE.jar
07:09:48,987 INFO [org.jboss.as.osgi] (MSC service thread 1-4) Resolve: org.apache.servicemix.bundles.xmlresolver-1.2_4.jar
07:09:48,997 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: woodstox-core-asl-4.1.1.jar
07:09:49,003 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: geronimo-javamail_1.4_spec-1.2.jar
07:09:49,007 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: cxf-dosgi-ri-discovery-local-1.4-SNAPSHOT.jar
07:09:49,019 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: neethi-3.0.1.jar
07:09:49,028 INFO [org.jboss.as.osgi] (MSC service thread 1-4) Resolve: org.osgi.enterprise-4.2.0.jar
07:09:49,031 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Resolve: org.apache.servicemix.specs.jaxws-api-2.1-1.9.0.jar
07:09:49,047 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: spring-osgi-io-1.2.1.jar
07:09:49,059 INFO [org.jboss.as.osgi] (MSC service thread 1-1) Resolve: spring-context-3.0.6.RELEASE.jar
07:09:49,104 INFO [org.jboss.as.osgi] (MSC service thread 1-2) Resolve: org.apache.servicemix.bundles.opensaml-2.4.1_1.jar
07:09:49,271 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.apache.cxf.bundle-minimal:2.5.4
07:09:49,285 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015967: Cannot install reflection index for unresolved bundle: cxf-dosgi-ri-dsw-cxf-1.4-SNAPSHOT.jar
07:09:49,306 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015967: Cannot install reflection index for unresolved bundle: com.springsource.slf4j.jcl-1.5.10.jar
07:09:49,311 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015967: Cannot install reflection index for unresolved bundle: org.apache.servicemix.bundles.jaxb-impl-2.1.13_2.jar
07:09:49,320 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015967: Cannot install reflection index for unresolved bundle: pax-web-runtime-1.0.3.jar
07:09:49,310 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015967: Cannot install reflection index for unresolved bundle: com.springsource.slf4j.api-1.5.10.jar
07:09:49,351 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015967: Cannot install reflection index for unresolved bundle: pax-web-spi-1.0.3.jar
07:09:49,359 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015967: Cannot install reflection index for unresolved bundle: pax-web-jetty-1.0.3.jar
07:09:49,355 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015967: Cannot install reflection index for unresolved bundle: org.apache.servicemix.bundles.xmlsec-1.4.5_1.jar
07:09:49,733 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015967: Cannot install reflection index for unresolved bundle: cxf-bundle-minimal-2.5.4.jar
07:09:49,956 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011011: Starting bundles for start level: 1
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5495) DuplicateServiceException when redeploying a rar multiple times
by Flavia Rainone (JIRA)
Flavia Rainone created AS7-5495:
-----------------------------------
Summary: DuplicateServiceException when redeploying a rar multiple times
Key: AS7-5495
URL: https://issues.jboss.org/browse/AS7-5495
Project: Application Server 7
Issue Type: Bug
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: 7.2.0.Alpha1
Start up a JBoss AS instance and run org.jboss.as.test.smoke.deployment.rar.tests.redeployment.ReDeploymentTestCase twice. At the second time the test runs, it will fail with a DuplicateServiceException.
The cause of this failure is in ResourceAdapterService, that does not remove itself from the resource adapters service list on stop. Notice that the same service adds itself to that list on start.
So, when a new rar is deployed, that list is reread and the resource adapter service gets redeployed along with the service being deployed. If the service being deployed is the same as before, we will get a duplicate deployment of the same components, resulting in a DuplicateServiceException.
--
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, 8 months