[JBoss JIRA] (AS7-5969) WebDeploymentService does blocking tasks in a MSC thread
by jaikiran pai (JIRA)
jaikiran pai created AS7-5969:
---------------------------------
Summary: WebDeploymentService does blocking tasks in a MSC thread
Key: AS7-5969
URL: https://issues.jboss.org/browse/AS7-5969
Project: Application Server 7
Issue Type: Bug
Components: Web
Reporter: jaikiran pai
Assignee: jaikiran pai
The WebDeploymentService in its start/stop lifecycle methods triggers the web application context initialization which can internally trigger various component initialization tasks like startup servlet initializations and servlet context initializations. This currently happens in a MSC thread but instead should be happening via a server executor which is already available for such blocking tasks.
--
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
11 years, 10 months
[JBoss JIRA] (AS7-5963) Provide ability to detect server shutdown
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5963:
-----------------------------------
Summary: Provide ability to detect server shutdown
Key: AS7-5963
URL: https://issues.jboss.org/browse/AS7-5963
Project: Application Server 7
Issue Type: Feature Request
Components: Server
Reporter: Thomas Diesler
Assignee: Jason Greene
Fix For: 7.2.0.Alpha1
The general use case is that a subsystem maintains state (on behalf of a deployment) that should be removed on explicit user interaction (i.e. mgmt op) but not on subsystem/server shutdown. This should also work in the domain case. Perhaps the ApplicationServerService (or similar) could be queried about whether it is currently shutting down.
--
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
11 years, 10 months
[JBoss JIRA] (AS7-2792) CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping
by Rostislav Svoboda (Created) (JIRA)
CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping
-----------------------------------------------------------------------------------------------------------
Key: AS7-2792
URL: https://issues.jboss.org/browse/AS7-2792
Project: Application Server 7
Issue Type: Bug
Components: CLI, Domain Management
Affects Versions: 7.1.0.Beta1
Reporter: Rostislav Svoboda
Assignee: Alexey Loubyansky
Fix For: 7.1.0.CR1
Hi Alexey.
CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping. I would expect to see 'resolved-multicast-address' or something similar to 'resolved-address' for interface definition.
I hope management model can provide such information. If not please reassign to Brian.
{code}
$ bin/standalone.sh -c standalone-ha.xml -u 224.34.3.154
$ bin/jboss-admin.sh -c
[standalone@localhost:9999 /] cd /socket-binding-group=standard-sockets/socket-binding=jgroups-udp
[standalone@localhost:9999 socket-binding=jgroups-udp] :read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"bound" => false,
"bound-address" => undefined,
"bound-port" => undefined,
"fixed-port" => false,
"interface" => undefined,
"multicast-address" => expression "${jboss.default.multicast.address:230.0.0.4}",
"multicast-port" => 45688,
"name" => "jgroups-udp",
"port" => 55200
}
}
{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
11 years, 10 months
[JBoss JIRA] (AS7-5966) Installed library not recognized as CDI bean archive
by Martin Kouba (JIRA)
Martin Kouba created AS7-5966:
---------------------------------
Summary: Installed library not recognized as CDI bean archive
Key: AS7-5966
URL: https://issues.jboss.org/browse/AS7-5966
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.2.Final (EAP)
Reporter: Martin Kouba
Assignee: Stuart Douglas
The CDI 1.0 spec states in 12.1. "Bean archives":
{quote}
* In an application deployed as an ear, the container searches every bean archive bundled with or *referenced by* the ear, including bean archives bundled with or referenced by wars and EJB jars contained in the ear. The bean archives might be library jars, EJB jars, rars or war WEB-INF/classes directories.
* In an application deployed as a war, the container searches every bean archive bundled with or *referenced by* the war. The bean archives might be library jars or the WEB-INF/classes directory.
* In an application deployed as an EJB jar, the container searches the EJB jar, if it is a bean archive, and every bean archive referenced by the EJB jar.
* ...
{quote}
Java EE 6 allows to reference installed libraries - see EE.8.2.2 "Installed Libraries".
However it seems installed libraries are not recognized as bean archives.
--
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
11 years, 10 months
[JBoss JIRA] (AS7-5948) Bundle undeploy does not remove storage state
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5948:
-----------------------------------
Summary: Bundle undeploy does not remove storage state
Key: AS7-5948
URL: https://issues.jboss.org/browse/AS7-5948
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.CR1
{code}
08:44:19,541 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=53,rev=0,startlevel=1,started=true,location=test-bundle]
08:44:19,542 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=45,rev=0,startlevel=1,started=true,location=auto-start]
08:44:19,543 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=15,rev=0,startlevel=1,started=true,location=test-bundle]
08:44:19,544 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=59,rev=0,startlevel=1,started=true,location=static-logservice]
08:44:19,545 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=76,rev=0,startlevel=1,started=true,location=osgi-ws-test]
08:44:19,545 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=42,rev=0,startlevel=1,started=true,location=bundle-c.wab]
08:44:19,546 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=111,rev=0,startlevel=1,started=true,location=deferred-bundle-a.jar]
08:44:19,546 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=105,rev=0,startlevel=1,started=true,location=deferred-bundle-b.jar]
08:44:19,549 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=73,rev=0,startlevel=1,started=false,location=org.jboss.netty:main]
08:44:19,549 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=32,rev=0,startlevel=1,started=true,location=complex-cdi.jar]
08:44:19,550 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=63,rev=0,startlevel=1,started=true,location=nested-bundle.jar]
08:44:19,550 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=39,rev=0,startlevel=1,started=true,location=osgi-rest-test]
08:44:19,551 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=79,rev=0,startlevel=1,started=true,location=bundle-c.wab]
08:44:19,551 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=93,rev=0,startlevel=1,started=true,location=bundle-d.wab]
08:44:19,552 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=94,rev=0,startlevel=1,started=true,location=bundle-e.jar]
08:44:19,552 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=12,rev=3,startlevel=1,started=true,location=org.jboss.osgi.logging]
08:44:19,553 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=104,rev=0,startlevel=1,started=true,location=deferred-bundle-a.jar]
08:44:19,553 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=50,rev=0,startlevel=1,started=true,location=ejb3-osgi.jar]
08:44:19,554 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=121,rev=0,startlevel=1,started=false,location=version-range-a]
08:44:19,554 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=23,rev=0,startlevel=1,started=true,location=optional-import-a]
08:44:19,555 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=116,rev=0,startlevel=1,started=true,location=startlevel-testcase]
08:44:19,555 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=80,rev=0,startlevel=1,started=true,location=bundle-c.wab]
08:44:19,556 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=83,rev=0,startlevel=1,started=true,location=osgi-ear-test]
08:44:19,556 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=127,rev=0,startlevel=1,started=true,location=osgi-configadmin-tests]
08:44:19,557 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=30,rev=0,startlevel=1,started=true,location=osgi-cdi-test]
08:44:19,558 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=57,rev=0,startlevel=1,started=true,location=deploymentmarker-bundle-b]
08:44:19,559 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=36,rev=0,startlevel=1,started=true,location=ejb3-bundle-a.jar]
08:44:19,559 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=66,rev=0,startlevel=1,started=false,location=test-bundle]
08:44:19,560 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=129,rev=0,startlevel=1,started=true,location=config-admin-pid-b]
08:44:19,560 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=86,rev=0,startlevel=1,started=true,location=xpath-test.jar]
08:44:19,561 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=51,rev=0,startlevel=1,started=true,location=legacy-bundle]
08:44:19,561 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=71,rev=0,startlevel=1,started=true,location=org.apache.felix.eventadmin]
08:44:19,562 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=88,rev=0,startlevel=1,started=true,location=osgi-webapp-test]
08:44:19,562 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=34,rev=0,startlevel=1,started=true,location=visa-bundle.jar]
08:44:19,563 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=108,rev=0,startlevel=1,started=true,location=deferred-bundle-a.jar]
08:44:19,564 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=97,rev=0,startlevel=1,started=true,location=good-bundle.jar]
08:44:19,564 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=13,rev=3,startlevel=1,started=true,location=org.apache.felix.configadmin]
08:44:19,565 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=46,rev=0,startlevel=1,started=true,location=redeploy]
08:44:19,565 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=14,rev=3,startlevel=1,started=true,location=org.jboss.as.osgi.configadmin]
08:44:19,566 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=92,rev=0,startlevel=1,started=true,location=bundle-c.wab]
08:44:19,566 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=112,rev=0,startlevel=1,started=true,location=deferred-bundle-b.jar]
08:44:19,566 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=135,rev=0,startlevel=1,started=true,location=bundle-deployment-casetwo]
08:44:19,567 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=77,rev=0,startlevel=1,started=true,location=bundle-a.war]
08:44:19,567 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=123,rev=0,startlevel=1,started=true,location=example-bundle]
08:44:19,568 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=122,rev=0,startlevel=1,started=true,location=version-range-c]
08:44:19,568 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=16,rev=0,startlevel=1,started=false,location=test-fragment]
08:44:19,568 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=40,rev=0,startlevel=1,started=true,location=bundle-a.war]
08:44:19,569 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=140,rev=0,startlevel=1,started=true,location=simple-bundle.wab]
08:44:19,569 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=28,rev=0,startlevel=1,started=false,location=arquillian-deployer-test-bundle]
08:44:19,570 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=27,rev=0,startlevel=1,started=true,location=example-arquillian-deployer]
08:44:19,570 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=126,rev=0,startlevel=1,started=true,location=example-xservice-bam-client-bundle]
08:44:19,571 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=37,rev=0,startlevel=1,started=true,location=ejb3-bundle-a.jar]
08:44:19,571 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=98,rev=0,startlevel=2,started=true,location=good-bundle.jar]
08:44:19,572 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=141,rev=0,startlevel=1,started=true,location=updated-bundle.wab]
08:44:19,572 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=68,rev=0,startlevel=1,started=true,location=persistence-bundle-a.jar]
08:44:19,573 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=87,rev=0,startlevel=1,started=true,location=example-jaxb]
08:44:19,573 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=113,rev=0,startlevel=1,started=true,location=dynamic-logservice]
08:44:19,574 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=136,rev=0,startlevel=1,started=false,location=test-bundle-two]
08:44:19,574 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=74,rev=0,startlevel=1,started=true,location=org.projectodd.stilts:main]
08:44:19,574 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=38,rev=0,startlevel=1,started=true,location=bundle-a.wab]
08:44:19,575 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=107,rev=0,startlevel=1,started=true,location=deferred-bundle-b.jar]
08:44:19,575 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=41,rev=0,startlevel=1,started=true,location=bundle-b.war]
08:44:19,576 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=47,rev=0,startlevel=1,started=true,location=redeploy]
08:44:19,576 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=25,rev=0,startlevel=1,started=true,location=optional-import-a]
08:44:19,577 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=55,rev=0,startlevel=2,started=true,location=deploymentmarker-bundle-c]
08:44:19,577 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=70,rev=0,startlevel=1,started=true,location=osgi-repository-bundle]
08:44:19,578 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=33,rev=0,startlevel=1,started=true,location=paypal-bundle.jar]
08:44:19,578 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=43,rev=0,startlevel=1,started=true,location=bundle-c.wab]
08:44:19,579 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=103,rev=0,startlevel=1,started=true,location=bad-bundle.jar]
08:44:19,579 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=110,rev=0,startlevel=1,started=true,location=good-bundle.jar]
08:44:19,580 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=133,rev=0,startlevel=1,started=true,location=example-xservice-mab-target-bundle]
08:44:19,580 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=137,rev=0,startlevel=1,started=true,location=osgi-bundlecontext-test]
08:44:19,581 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=62,rev=0,startlevel=1,started=true,location=example-jta]
08:44:19,581 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=72,rev=0,startlevel=1,started=true,location=stomplet-server-provider]
08:44:19,582 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=22,rev=0,startlevel=1,started=true,location=optional-import-a]
08:44:19,582 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=75,rev=0,startlevel=1,started=true,location=simple-stomplet]
08:44:19,583 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=95,rev=0,startlevel=1,started=true,location=sax-parser.jar]
08:44:19,584 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=20,rev=0,startlevel=1,started=true,location=optional-import-a]
08:44:19,584 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=65,rev=0,startlevel=1,started=true,location=bundle-deployment-case-one]
08:44:19,585 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=128,rev=0,startlevel=1,started=true,location=config-admin-pid-a]
08:44:19,585 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=102,rev=0,startlevel=2,started=true,location=bad-bundle.jar]
08:44:19,586 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=106,rev=0,startlevel=1,started=true,location=deferred-bundle-a.jar]
08:44:19,586 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=35,rev=0,startlevel=1,started=true,location=osgi-ejb3-test]
08:44:19,587 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=100,rev=0,startlevel=1,started=true,location=bad-bundle.jar]
08:44:19,588 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=96,rev=0,startlevel=1,started=true,location=deferred-resolve-tests]
08:44:19,588 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=60,rev=0,startlevel=1,started=true,location=bundleA]
08:44:19,589 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=90,rev=0,startlevel=1,started=true,location=bundle-a.war]
08:44:19,589 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=21,rev=0,startlevel=1,started=true,location=optional-import-b]
08:44:19,590 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=58,rev=0,startlevel=1,started=true,location=example-jndi]
08:44:19,591 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=85,rev=0,startlevel=1,started=true,location=war-structure-bundle.war]
08:44:19,591 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=24,rev=0,startlevel=1,started=false,location=optional-import-b]
08:44:19,592 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=132,rev=0,startlevel=1,started=true,location=xservice-module-access]
08:44:19,592 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=131,rev=0,startlevel=1,started=true,location=config-admin-bundle-b]
08:44:19,593 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=119,rev=0,startlevel=1,started=false,location=version-range-a]
08:44:19,593 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=11,rev=3,startlevel=1,started=true,location=org.apache.felix.log]
08:44:19,594 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=48,rev=0,startlevel=1,started=true,location=simple-client.jar]
08:44:19,594 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=81,rev=0,startlevel=1,started=false,location=resource-injection.jar]
08:44:19,595 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=52,rev=0,startlevel=1,started=true,location=http-service-example]
08:44:19,596 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=64,rev=0,startlevel=1,started=true,location=arq466-bundle]
08:44:19,596 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=117,rev=0,startlevel=3,started=true,location=osgi-startlevel-a]
08:44:19,597 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=101,rev=0,startlevel=1,started=true,location=bad-bundle.jar]
08:44:19,598 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=0,rev=0,startlevel=0,started=false,location=System Bundle]
08:44:19,598 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=69,rev=0,startlevel=1,started=true,location=persistence-bundle-a.jar]
08:44:19,599 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=99,rev=0,startlevel=1,started=true,location=good-bundle.jar]
08:44:19,599 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=89,rev=0,startlevel=1,started=true,location=bundle-c.wab]
08:44:19,600 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=115,rev=0,startlevel=1,started=true,location=ejb-client-descriptor-bundle.jar]
08:44:19,601 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=114,rev=0,startlevel=1,started=true,location=bundleA]
08:44:19,601 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=124,rev=0,startlevel=1,started=true,location=xservice-module-access]
08:44:19,602 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=49,rev=0,startlevel=1,started=true,location=ejb3-osgi-target]
08:44:19,603 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=84,rev=0,startlevel=1,started=true,location=echo-bundle.jar]
08:44:19,603 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=67,rev=0,startlevel=1,started=true,location=osgi-jpa-test]
08:44:19,604 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=78,rev=0,startlevel=1,started=true,location=bundle-b.war]
08:44:19,604 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=120,rev=0,startlevel=1,started=true,location=version-range-b]
08:44:19,605 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=130,rev=0,startlevel=1,started=true,location=config-admin-pid-c]
08:44:19,605 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=44,rev=0,startlevel=1,started=true,location=example-bundle]
08:44:19,606 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=61,rev=0,startlevel=1,started=true,location=osgi-configadmin]
08:44:19,607 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=29,rev=0,startlevel=1,started=true,location=dom-parser.jar]
08:44:19,607 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=56,rev=0,startlevel=1,started=true,location=deploymentmarker-bundle-a]
08:44:19,608 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=91,rev=0,startlevel=1,started=true,location=bundle-b.war]
08:44:19,608 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=17,rev=0,startlevel=1,started=true,location=test-bundle2]
08:44:19,609 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=109,rev=0,startlevel=1,started=true,location=deferred-bundle-b.jar]
08:44:19,610 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=54,rev=0,startlevel=1,started=true,location=deploymentmarker-tests]
{code}
--
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
11 years, 10 months
[JBoss JIRA] (JGRP-1541) Discovery: persist discovery responses
by Bela Ban (JIRA)
Bela Ban created JGRP-1541:
------------------------------
Summary: Discovery: persist discovery responses
Key: JGRP-1541
URL: https://issues.jboss.org/browse/JGRP-1541
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.3
When we use TCPPING.initial_hosts=A, and have nodes A, B and C, then the following can happen:
- A is started. The view is {A}
- B is started, finds A and joins the cluster. The view is {A,B}
- C is started, finds A and joins the cluster. The view is now {A,B,C}
- A is killed. The view is now {B,C}
- C is restarted
--> C won't find A therefore cannot ask B to join it (C doesn't know about B)
SOLUTION:
- If every member persisted its discovery results on disk, C would still know about A and B, and could therefore discover B
- This could be implemented directly in TCPPING, or as a generic, separate, protocol (possibly useful for other discovery protocols such as S3_PING, TCPGOSSIP (when the GossipRouter is down) as well)
- The disk cache would have to include an expiry mechanism, so that the file doesn't grow forever, and also stale results aren't returned forever
- This mechanism would not work though if C came up the first time (no file on disk yet) and A wasn't running.
--
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
11 years, 10 months
[JBoss JIRA] Created: (AS7-1264) Add schema references to standalone.xml, domain.xml, host.xml
by Gerry Matte (JIRA)
Add schema references to standalone.xml, domain.xml, host.xml
-------------------------------------------------------------
Key: AS7-1264
URL: https://issues.jboss.org/browse/AS7-1264
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Affects Versions: 7.0.0.CR1
Reporter: Gerry Matte
Assignee: Brian Stansberry
It appears that users of Jboss 7 will be often modifying these configuration files as they fine tune their server and when they discover how to implement new features.
It seems quite surprising to me that these files do not have the schema references identified in the file header. Any good XML editor would use those references to validate changes and new entries and thereby avoid a great deal of frustration for users and those who provide support for forum issues.
I realise that if jboss validated each xml file when starting up there would be performance penalty that may be unacceptable to many users. A command-line switch could be used to either turn on xml validation (if the default were that no validation is performed) or conversely to turn off xml validation if the default state was that xml validation was on.
Personally I favor having a switch that turns off validation - to be used on production servers only.
If the schema/dtd files were published online and referenced within the configuration xml files, future changes to the schema structure would be "enforced" upon the user community as they attemted to use an out-of-date version when upgrading to a new version of Jboss 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (JBASM-40) JBPAPP-366 still persistent in JBoss 4.2.3 GA
by Nagaraju Roddam (JIRA)
Nagaraju Roddam created JBASM-40:
------------------------------------
Summary: JBPAPP-366 still persistent in JBoss 4.2.3 GA
Key: JBASM-40
URL: https://issues.jboss.org/browse/JBASM-40
Project: JBoss AS Server Manager
Issue Type: Release
Environment: GNU Linux 2.6.18-308; JDK 1.6.0.31; JBoss 4.2.3 GA
Reporter: Nagaraju Roddam
Assignee: Shelly McGowan
The 'AJP Connector Threads in CLOSE_WAIT Status' issue mentioned in ticket JBPAPP-366 is observed in JBoss 4.2.3 GA. As per the ticket (JBPAPP-366), the resolution is available in JBoss-4.2.0.GA-CP02.
Does it imply that we've to upgrade to JBoss 5.0.0 to get this issue resolved?
Please advice.
--
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
11 years, 10 months