[JBoss JIRA] (AS7-5854) JBOSGI011210: Bundle already uninstalled when a bundle is undeployed, then redeployed in same session
by Ed Roberts (JIRA)
Ed Roberts created AS7-5854:
-------------------------------
Summary: JBOSGI011210: Bundle already uninstalled when a bundle is undeployed, then redeployed in same session
Key: AS7-5854
URL: https://issues.jboss.org/browse/AS7-5854
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.2.0.Alpha1
Environment: Windows XP Professional
Oracle JDK 1.6.0_32
JBoss AS 7.2.0.Alpha1 build from master 24/10/2012
Reporter: Ed Roberts
Assignee: Thomas Diesler
I start up JBoss AS with some bundles. I stop one of them by deleting the corresponding .deployed file. I then restart it by deleting the corresponding .undeployed file. If I was using the Felix Web Console at all times to look at the meta-typed configuration for the service in this bundle, when the bundle is finally redeployed, a refresh of the configuration page caused an exception
{code}
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) java.lang.IllegalStateException: JBOSGI011210: Bundle already uninstalled: vcs-configuration-jboss-svc:1.0.0.SNAPSHOT
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.jboss.osgi.framework.internal.AbstractBundleState.assertNotUninstalled(AbstractBundleState.java:649)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.jboss.osgi.framework.internal.UserBundleRevision.getEntry(UserBundleRevision.java:138)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.jboss.osgi.framework.internal.AbstractBundleState.getEntry(AbstractBundleState.java:463)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.metatype.internal.l10n.BundleResources.loadProperties(BundleResources.java:166)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.metatype.internal.l10n.BundleResources.getResources(BundleResources.java:144)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.metatype.internal.l10n.BundleResources.getResources(BundleResources.java:84)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.metatype.DefaultMetaTypeProvider.getObjectClassDefinition(DefaultMetaTypeProvider.java:172)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.metatype.internal.MetaTypeInformationImpl.getObjectClassDefinition(MetaTypeInformationImpl.java:125)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.webconsole.internal.compendium.ConfigManagerBase.getObjectClassDefinition(ConfigManagerBase.java:208)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.webconsole.internal.compendium.ConfigManager.getServices(ConfigManager.java:487)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(ConfigManager.java:379)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.webconsole.internal.compendium.ConfigManager.renderContent(ConfigManager.java:295)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:147)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.webconsole.internal.compendium.ConfigManager.doGet(ConfigManager.java:239)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:437)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:384)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
2012-10-30 13:19:32,133 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2012-10-30 13:19:32,258 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at java.lang.reflect.Method.invoke(Method.java:597)
2012-10-30 13:19:32,258 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.ops4j.pax.web.service.internal.HttpServiceStarted$2.invoke(HttpServiceStarted.java:209)
2012-10-30 13:19:32,258 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.ops4j.pax.web.service.internal.$Proxy35.service(Unknown Source)
2012-10-30 13:19:32,258 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
2012-10-30 13:19:32,258 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
2012-10-30 13:19:32,258 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)
2012-10-30 13:19:32,258 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
2012-10-30 13:19:32,258 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:117)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:74)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.Server.handle(Server.java:345)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:919)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:582)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:51)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
2012-10-30 13:19:32,274 ERROR [stderr](qtp31185487-155 - /system/console/configMgr) at java.lang.Thread.run(Thread.java:662)
{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
12 years, 11 months
[JBoss JIRA] (JBAS-9521) WSDLFilePublisher only deploying schemas with the same name once even if there are more in different subdirectories under a WAR
by Adam Kovari (JIRA)
Adam Kovari created JBAS-9521:
---------------------------------
Summary: WSDLFilePublisher only deploying schemas with the same name once even if there are more in different subdirectories under a WAR
Key: JBAS-9521
URL: https://issues.jboss.org/browse/JBAS-9521
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: JBossAS-5.1.0.GA
Environment: - JBoss AS 5.1.0GA
- JBoss EAP 5.1.{1,2}
- JBoss SOA-P 5.{2,3}
- jbossws-native-3.1.2.SP9
Reporter: Adam Kovari
Assignee: Alessio Soldano
Priority: Minor
Attachments: temp.war
JBoss when deploying WSDLs copies the schemas into <profile>/data/wsdl/... directory. If the original WAR file contains 2 subdirectories which contain 2 XSD schemas with the same name, it will only deploy the schemas from the first directory.
--
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
12 years, 11 months
[JBoss JIRA] (AS7-5896) jboss-admin.sh accepts crazy values for :add-proxy()
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-5896?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar moved MODCLUSTER-264 to AS7-5896:
------------------------------------------------
Project: Application Server 7 (was: mod_cluster)
Key: AS7-5896 (was: MODCLUSTER-264)
Workflow: GIT Pull Request workflow (was: jira)
> jboss-admin.sh accepts crazy values for :add-proxy()
> ----------------------------------------------------
>
> Key: AS7-5896
> URL: https://issues.jboss.org/browse/AS7-5896
> Project: Application Server 7
> Issue Type: Bug
> Environment: modcluster subsystem of AS 7.1 trunk
> Reporter: Misty Stanley-Jones
> Assignee: Radoslav Husar
> Priority: Minor
>
> I am allowed to use all of these kinds of syntax with :add-proxy():
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=abc.com,port=123)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "port" => 123,
> "host" => "abc.com",
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=def.com)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "host" => "def.com",
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(port=999)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "port" => 999,
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> I think only the first one should be valid.
--
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
12 years, 11 months
[JBoss JIRA] (AS7-5896) jboss-admin.sh accepts crazy values for :add-proxy()
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-5896?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated AS7-5896:
--------------------------------
Fix Version/s: 7.2.0.Alpha1
Component/s: Clustering
This is actually an AS7 issue. I will take it.
> jboss-admin.sh accepts crazy values for :add-proxy()
> ----------------------------------------------------
>
> Key: AS7-5896
> URL: https://issues.jboss.org/browse/AS7-5896
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Environment: modcluster subsystem of AS 7.1 trunk
> Reporter: Misty Stanley-Jones
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 7.2.0.Alpha1
>
>
> I am allowed to use all of these kinds of syntax with :add-proxy():
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=abc.com,port=123)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "port" => 123,
> "host" => "abc.com",
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=def.com)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "host" => "def.com",
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> [domain@localhost:9999 subsystem=modcluster] :add-proxy(port=999)
> {
> "outcome" => "success",
> "result" => {
> "domain-results" => {"step-1" => undefined},
> "server-operations" => [{
> "servers" => [],
> "operation" => {
> "address" => [("subsystem" => "modcluster")],
> "operation" => "add-proxy",
> "port" => 999,
> "operation-headers" => {"execute-for-coordinator" => true}
> }
> }]
> }
> }
> I think only the first one should be valid.
--
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
12 years, 11 months
[JBoss JIRA] (AS7-5894) jboss-ejb3-ext-api is not marked a jboss api module
by Carlo de Wolf (JIRA)
Carlo de Wolf created AS7-5894:
----------------------------------
Summary: jboss-ejb3-ext-api is not marked a jboss api module
Key: AS7-5894
URL: https://issues.jboss.org/browse/AS7-5894
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.3.Final (EAP)
Reporter: Carlo de Wolf
Assignee: jaikiran pai
jboss-ejb3-ext-api-2.0.0-redhat-2.jar does into org.jboss.ejb3 module which is marked as private.
All classes in jboss-ejb3-ext-api should really be public instead.
--
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
12 years, 11 months
[JBoss JIRA] (AS7-5762) Allow multiple quoted strings within a CLI command
by James Perkins (JIRA)
James Perkins created AS7-5762:
----------------------------------
Summary: Allow multiple quoted strings within a CLI command
Key: AS7-5762
URL: https://issues.jboss.org/browse/AS7-5762
Project: Application Server 7
Issue Type: Bug
Components: CLI
Reporter: James Perkins
Assignee: Alexey Loubyansky
CLI commands with multiple quotes are not properly parsed.
{code}
/subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter, value="all(match(\"pattern1\"),not(match(\"pattern2\")))")
{code}
I would expect the above command to return the following to the OSH.
{code}
all(match("pattern"),not(match("pattern2")))
{code}
What actually gets passed to the OSH is
{code}
all(match(
{code}
Note this filter syntax relies on PR https://github.com/jbossas/jboss-as/pull/3251
--
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
12 years, 11 months
[JBoss JIRA] (AS7-5893) CLONE - Empty messaging subsystem can not be persisted
by Tom Fonteyne (JIRA)
Tom Fonteyne created AS7-5893:
---------------------------------
Summary: CLONE - Empty messaging subsystem can not be persisted
Key: AS7-5893
URL: https://issues.jboss.org/browse/AS7-5893
Project: Application Server 7
Issue Type: Feature Request
Components: JMS
Affects Versions: 7.1.3.Final (EAP)
Reporter: Tom Fonteyne
Assignee: Jeff Mesnil
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
When the messaging subsystem is persisted, it requires to have defined hornetq-server nodes but that's not correct.
E.g. when the messaging subsystem is added through the CLI, it should be marshalled even though there is no hornetq-server
The XSD for the messaging subsystem is correct: minOccurs for hornetq-server element is 0.
--
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
12 years, 11 months