[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 reopened AS7-6234:
---------------------------------
Yes, this is a bug. The webcontext gets registered but root access gives 404
> 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, server.springapp.log, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-1.0.0-BUILD-SNAPSHOT-no-manifest-works.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
11 years, 8 months
[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 commented on AS7-6234:
----------------------------------------
I attached the very same .war without the manifest creation (just the default manifest), and that works without issues. Having a proper OSGi manifest should not cause the app to not work - it should either work or complain about something. As far as I know and what I have tested with other apps, in 7.2, that is expected to work.
> 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, server.springapp.log, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-1.0.0-BUILD-SNAPSHOT-no-manifest-works.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
11 years, 8 months
[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-1.0.0-BUILD-SNAPSHOT-no-manifest-works.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, server.springapp.log, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-1.0.0-BUILD-SNAPSHOT-no-manifest-works.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
11 years, 8 months
[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:
----------------------------
Description:
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}
ManagedServerOperationsFactory.getAllSystemProperties() should use a LinkedHashMap to preserve the order of the system properties, since at the moment in the server 'two' gets added before 'one'
was:
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}
> 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}
> ManagedServerOperationsFactory.getAllSystemProperties() should use a LinkedHashMap to preserve the order of the system properties, since at the moment in the server 'two' gets added before 'one'
--
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, 8 months
[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 edited comment on AS7-6234 at 12/20/12 9:26 AM:
------------------------------------------------------------------
this was changed to cannot reproduce - so is the servlet responding for you? all the logs claim that it should be, but there's still 404 when trying to access.
This same app was working and responding fine without the OSGi manifest, but when changed to use OSGi manifest, it has stopped working.
was (Author: jrantav):
this was changed to cannot reproduce - so is the servlet responding for you? all the logs claim that it should be, but there's still 404 when trying to access.
> 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, server.springapp.log, 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
11 years, 8 months
[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 commented on AS7-6234:
----------------------------------------
this was changed to cannot reproduce - so is the servlet responding for you? all the logs claim that it should be, but there's still 404 when trying to access.
> 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, server.springapp.log, 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
11 years, 8 months
[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: server.springapp.log
> 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, server.springapp.log, 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
11 years, 8 months
[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 commented on AS7-6234:
----------------------------------------
Yes, but there should be a mention of the problem somewhere I think.
I changed the two INFOs at standalone/configuration/logging.properties to DEBUG, but didn't get anything that would clarify the problem for me. I'll attach the full log in case it helps.
> 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
11 years, 8 months
[JBoss JIRA] (AS7-6222) JCA workmanager and bootstrap-context "name" attributes should not support expressions
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6222?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6222:
----------------------------------
Summary: JCA workmanager and bootstrap-context "name" attributes should not support expressions (was: JCA workmanager "name" attribute should not support expressions)
> JCA workmanager and bootstrap-context "name" attributes should not support expressions
> --------------------------------------------------------------------------------------
>
> Key: AS7-6222
> URL: https://issues.jboss.org/browse/AS7-6222
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Domain Management, JCA
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> These "name" attributes represent part of the address of a resource. Resource address elements cannot support expressions, because their value needs to be resolvable
> 1) before all system property values are known
> 2) on the master host controller, which may have different resolution sources from other HCs or the servers.
--
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, 8 months
[JBoss JIRA] (AS7-6222) JCA workmanager and bootstrap-context "name" attributes should not support expressions
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6222?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6222:
----------------------------------
Comment: was deleted
(was: Edited title to remove bootstrap-context, which does not have this problem.)
> JCA workmanager and bootstrap-context "name" attributes should not support expressions
> --------------------------------------------------------------------------------------
>
> Key: AS7-6222
> URL: https://issues.jboss.org/browse/AS7-6222
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Domain Management, JCA
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> These "name" attributes represent part of the address of a resource. Resource address elements cannot support expressions, because their value needs to be resolvable
> 1) before all system property values are known
> 2) on the master host controller, which may have different resolution sources from other HCs or the servers.
--
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, 8 months