[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
13 years, 4 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
13 years, 4 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
13 years, 4 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
13 years, 4 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
13 years, 4 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
13 years, 4 months
[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
13 years, 4 months
[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
13 years, 4 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:
----------------------------
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
13 years, 4 months
[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
13 years, 4 months