[JBoss JIRA] (AS7-6234) WAB deployment showing as successful, but not responding
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6234?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler resolved AS7-6234.
---------------------------------
Resolution: Cannot Reproduce Bug
With PR [#3727|https://github.com/jbossas/jboss-as/pull/3727] I see
{code}
15:00:09,803 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war"
15:00:10,198 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011006: OSGi Framework - 2.1.0.CR7
15:00:10,287 INFO [org.jboss.osgi.framework] (MSC service thread 1-8) JBOSGI011001: Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
15:00:10,287 INFO [org.jboss.osgi.framework] (MSC service thread 1-7) JBOSGI011001: Bundle installed: jboss-osgi-logging:1.0.0
15:00:10,287 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: org.apache.felix.log:1.0.0
15:00:10,287 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011001: Bundle installed: org.apache.felix.configadmin:1.2.8
15:00:10,368 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011011: Starting bundles for start level: 1
15:00:10,370 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: jboss-as-osgi-http:7.2.0.Alpha1-SNAPSHOT
15:00:10,379 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: org.apache.felix.log:1.0.0
15:00:10,383 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: jboss-osgi-logging:1.0.0
15:00:10,394 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: org.apache.felix.configadmin:1.2.8
15:00:10,397 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011002: Bundle started: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
15:00:10,398 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011000: OSGi Framework started
15:00:10,402 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011001: Bundle installed: spring-app:1.0.0.SNAPSHOT
15:00:10,685 INFO [org.jboss.web] (ServerService Thread Pool -- 60) JBAS018210: Register web context: /spring-app
15:00:10,686 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011002: Bundle started: spring-app:1.0.0.SNAPSHOT
15:00:11,294 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war"
{code}
> WAB deployment showing as successful, but not responding
> --------------------------------------------------------
>
> Key: AS7-6234
> URL: https://issues.jboss.org/browse/AS7-6234
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: jboss-7.2.0-server-output-deployment-showing-as-successful.txt, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-source-codes.zip
>
>
> Simple Spring WAB file, that I think should work, doesn't seem to. Deployment goes seemingly without issues - no errors are reported - but servlet does not respond to requests. Both OSGi panel and deployment management panel in admin console show the deployment as successful.
> Attached server output and .war file, that should respond to /spring-app request.
--
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
[JBoss JIRA] (AS7-6063) Deadlock in Module FallbackClassLoader
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6063?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-6063:
--------------------------------
Fix Version/s: 7.2.0.CR1
(was: 7.2.0.Alpha1)
Priority: Critical (was: Major)
Marked critical - needs to be looked at early next year
> Deadlock in Module FallbackClassLoader
> --------------------------------------
>
> Key: AS7-6063
> URL: https://issues.jboss.org/browse/AS7-6063
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Steve Reed
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: 7.2.0.CR1
>
> Attachments: jboss-dead-lock.txt, ThreadDump-2.txt
>
>
> Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar
> Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8...
> During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started.
> The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible.
> I will attach the thread dump to this issue as supporting evidence.
--
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
[JBoss JIRA] (AS7-6233) System properties referencing each other in domain mode do not work
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/AS7-6233?page=com.atlassian.jira.plugin.s... ]
Kabir Khan updated AS7-6233:
----------------------------
Assignee: Kabir Khan
Fix Version/s: 7.2.0.Alpha1
7.1.4.Final (EAP)
Affects Version/s: 7.1.3.Final (EAP)
7.1.2.Final (EAP)
Component/s: Domain Management
> System properties referencing each other in domain mode do not work
> -------------------------------------------------------------------
>
> Key: AS7-6233
> URL: https://issues.jboss.org/browse/AS7-6233
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Kabir Khan
> Assignee: Kabir Khan
> Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> The following set up:
> {code}
> <system-properties>
> <property name="one" value="one1"/>
> <property name="two" value="${one}"/>
> </system-properties>
> {code}
> works in standalone, so
> {code}
> [standalone@localhost:9999 /] :resolve-expression(expression="${two}")
> {
> "outcome" => "success",
> "result" => "one1"
> }
> {code}
> However, in domain mode the properties get passed in in the wrong order so
> {code}
> [domain@localhost:9999 /] /host=master/server=server-one:resolve-expression(expression="${two}")
> {
> "outcome" => "success",
> "result" => "${one}"
> }
> {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
[JBoss JIRA] (AS7-6234) WAB deployment showing as successful, but not responding
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6234?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler commented on AS7-6234:
-------------------------------------
What does the DEBUG log say? A successfully deployed bundle means that it is installed with the framework. It may not have been resolved let alone started.
> WAB deployment showing as successful, but not responding
> --------------------------------------------------------
>
> Key: AS7-6234
> URL: https://issues.jboss.org/browse/AS7-6234
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: jboss-7.2.0-server-output-deployment-showing-as-successful.txt, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-source-codes.zip
>
>
> Simple Spring WAB file, that I think should work, doesn't seem to. Deployment goes seemingly without issues - no errors are reported - but servlet does not respond to requests. Both OSGi panel and deployment management panel in admin console show the deployment as successful.
> Attached server output and .war file, that should respond to /spring-app request.
--
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
[JBoss JIRA] (AS7-6234) WAB deployment showing as successful, but not responding
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6234?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori updated AS7-6234:
-----------------------------------
Attachment: spring-app-source-codes.zip
> WAB deployment showing as successful, but not responding
> --------------------------------------------------------
>
> Key: AS7-6234
> URL: https://issues.jboss.org/browse/AS7-6234
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: jboss-7.2.0-server-output-deployment-showing-as-successful.txt, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-source-codes.zip
>
>
> Simple Spring WAB file, that I think should work, doesn't seem to. Deployment goes seemingly without issues - no errors are reported - but servlet does not respond to requests. Both OSGi panel and deployment management panel in admin console show the deployment as successful.
> Attached server output and .war file, that should respond to /spring-app request.
--
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
[JBoss JIRA] (AS7-6219) Whitespace on Bundle-Classpath manifest header should not fail WAB deployment
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6219?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-6219:
--------------------------------
Issue Type: Bug (was: Enhancement)
> Whitespace on Bundle-Classpath manifest header should not fail WAB deployment
> -----------------------------------------------------------------------------
>
> Key: AS7-6219
> URL: https://issues.jboss.org/browse/AS7-6219
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Fix For: 7.2.0.Alpha1
>
> Attachments: bundle-classpath.txt
>
>
> Indentation of values works for Import-Package header, but if used with Bundle-Classpath header, it doesn't work and classes are not found. See attachment for details.
> This can lead to subtle, hard-to-analyze failures in the deployment. Manifest is often configured in maven pom, where indentation is common.
--
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
[JBoss JIRA] (AS7-5951) Cannot reliably deploy OSGi host and fragment bundles on server restart
by Paul Illingworth (JIRA)
[ https://issues.jboss.org/browse/AS7-5951?page=com.atlassian.jira.plugin.s... ]
Paul Illingworth commented on AS7-5951:
---------------------------------------
I'll give this a go as soon as I can. It'll probably early next year I'm afraid.
(I am currently avoiding the problem by using a single bundle that combines all the guice host and fragment bundles)
> Cannot reliably deploy OSGi host and fragment bundles on server restart
> -----------------------------------------------------------------------
>
> Key: AS7-5951
> URL: https://issues.jboss.org/browse/AS7-5951
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows XP SP3
> Reporter: Paul Illingworth
> Assignee: Thomas Diesler
> Labels: OSGI
> Fix For: 7.2.0.Alpha1
>
> Attachments: this_one_failed.txt, this_one_worked.txt
>
>
> If I deploy guice-3.0.0 (host bundle), guice-servlet (fragment) and guice-persist (fragment) into the "deployments" folder then the there is no guarantee the fragments will be installed before the host and so they may not be attached to the host when it resolves.
> This happens on starting the application server. Sometimes the fragments are attached, sometimes they aren't.
> If I install the bundles into the "bundles" folder structure and add capability entries to the standalone.xml file then it works as expected.
> I am using 7.2.0-Alpha1 built from cb72a7cd1669131b28a552f1dbf3c2582ad19813.
--
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
[JBoss JIRA] (AS7-6235) Reconsider expressions for model reference attributes in server-group and server-config
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6235:
-------------------------------------
Summary: Reconsider expressions for model reference attributes in server-group and server-config
Key: AS7-6235
URL: https://issues.jboss.org/browse/AS7-6235
Project: Application Server 7
Issue Type: Sub-task
Components: Domain Management
Reporter: Brian Stansberry
Priority: Critical
Fix For: 7.2.0.Alpha1
There are some attributes in the server-group and server-config resources that represent references to other resources that support expressions. For example the "group" attribute in a server-config and the "profile" attribute in a server-group. Supporting expressions on such attributes is problematic because it precludes accurately validating that the reference is valid during operation execution Stage.MODEL. This is because expression resolution sources may not be fully populated until Stage.RUNTIME.
I wanted to remove expression support from these attributes but was unwilling to do so because of concerns about breaking compatibility. But some recent testing showed me that on *master* for at least some of these, setting an expression would not work -- the HC could not launch servers. If these expressions didn't work *in previous releases* as well, we can remove support for them without breaking compatibility.
The task here is to test setting these attributes to expressions in 7.1.2 and 7.1.3. For any attribute like this where expression support didn't actually work, we should remove the support in 7.2.
Testing can be done by simply taking the current xml attribute value, e.g. "foo" and using it as the default in an expression, e.g. "${exp-test:foo}" and then starting the HC. There is no need to mess with setting system property "exp-test".
--
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
[JBoss JIRA] (AS7-6234) WAB deployment showing as successful, but not responding
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6234?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori updated AS7-6234:
-----------------------------------
Attachment: jboss-7.2.0-server-output-deployment-showing-as-successful.txt
spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war
> WAB deployment showing as successful, but not responding
> --------------------------------------------------------
>
> Key: AS7-6234
> URL: https://issues.jboss.org/browse/AS7-6234
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: jboss-7.2.0-server-output-deployment-showing-as-successful.txt, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war
>
>
> Simple Spring WAB file, that I think should work, doesn't seem to. Deployment goes seemingly without issues - no errors are reported - but servlet does not respond to requests. Both OSGi panel and deployment management panel in admin console show the deployment as successful.
> Attached server output and .war file, that should respond to /spring-app request.
--
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
[JBoss JIRA] (JBRULES-3693) Pull Request to update smooks to 1.5.1
by Nick Cross (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3693?page=com.atlassian.jira.plug... ]
Nick Cross updated JBRULES-3693:
--------------------------------
Fix Version/s: 6.0.0.Alpha1
> Pull Request to update smooks to 1.5.1
> --------------------------------------
>
> Key: JBRULES-3693
> URL: https://issues.jboss.org/browse/JBRULES-3693
> Project: JBRULES
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.Alpha1
> Reporter: George Varsamis
> Assignee: Mark Proctor
> Fix For: 6.0.0.Alpha1
>
>
> Switchyard requires Smooks v 1.5.1 . I have updated drools parent to use smooks 1.5.1 and also updated the source code in droolsjbpm-integration/drools-pipeline to reflect this. The change is trivial. I have run the tests and the change had no adverse effect on the codebase.
> I will attach the pull requests to this ticket.
--
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