[JBoss JIRA] (AS7-3786) Some TestCases are run against hard-coded 127.0.0.1
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/AS7-3786?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan resolved AS7-3786.
---------------------------------
Resolution: Duplicate Issue
see AS7-3696
> Some TestCases are run against hard-coded 127.0.0.1
> ---------------------------------------------------
>
> Key: AS7-3786
> URL: https://issues.jboss.org/browse/AS7-3786
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
> Assignee: Shelly McGowan
> Priority: Critical
>
> Some TestCases are hard bound to *127.0.0.1* IP address. I think, it is useless - especially testing in IPv6 environment is impossible in this case for a such TestCase(-s).
> These classes aren't in integration testsuite part, it is in other places.
> Some of them are (maybe I've overlooked some others):
> - org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase
> - org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase
> - org.jboss.as.controller.test.RemoteProxyControllerProtocolTestCase
> - org.jboss.as.controller.ModelControllerClientTestCase
> - org.jboss.as.jmx.JMXSubsystemTestCase
> - org.jboss.as.jmx.ModelControllerMBeanTestCase
> Otherwise these tests are run *before* IP address transformation (usually used node0 variable and tranforms AS7 config file standalone-*.xml), so maybe there isn't present now any mechanism how to get/propagate proper (and wanted) IP address.
> Also note - some of them are hardcoded to IP name alias *localhost* - see JBPAPP-8132 for localhost vs. localhost6.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3790) TS: Unable to pass tests in integration smoke test part of testsuite in IPv6 environment
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3790?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek moved JBPAPP-8137 to AS7-3790:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-3790 (was: JBPAPP-8137)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.0.Final
(was: EAP 6.0.0 DR 13)
Component/s: Test Suite
(was: Testsuite)
Security: (was: JBoss Internal)
Docs QE Status: (was: NEW)
> TS: Unable to pass tests in integration smoke test part of testsuite in IPv6 environment
> ----------------------------------------------------------------------------------------
>
> Key: AS7-3790
> URL: https://issues.jboss.org/browse/AS7-3790
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
> Assignee: Shelly McGowan
> Priority: Blocker
>
> I've tried to build AS7 and run default part of testsuite (including integration smoke tests) in IPv6 environment like:{code}./build.sh clean install -Dnode0=::1 -Dipv6{code}
> My lookpack network interface was configured as:{code}[root@fedora15-vrt1 Documents]# ifconfig lo
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:60156 errors:0 dropped:0 overruns:0 frame:0
> TX packets:60156 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:37911245 (36.1 MiB) TX bytes:37911245 (36.1 MiB)
> [root@fedora15-vrt1 Documents]#
> {code}
> The result is failure because timeout:
> {code}
> <snip>
> main:
> build-smoke:
> [INFO] Executed tasks
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-ts-integ-smoke ---
> [INFO] Compiling 110 source files to /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/target/test-classes
> [WARNING] /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/surefire/servermodule/AbstractServerInModuleTestCase.java:[54,62] [deprecation] getModulesDir() in org.jboss.as.server.ServerEnvironment has been deprecated
> [INFO]
> [INFO] --- maven-surefire-plugin:2.10:test (smoke-full.surefire) @ jboss-as-ts-integ-smoke ---
> [INFO] Surefire report directory: /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.952s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [1.435s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.276s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [1.525s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [11.337s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [5.599s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [21.175s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [3.940s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [2.620s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [2.615s]
> [INFO] JBoss Application Server: Embedded ................ SUCCESS [4.239s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [5.673s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [6.888s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [3.532s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [8.944s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [4.899s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [11.049s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [5.775s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [9.914s]
> [INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [8.926s]
> [INFO] JBoss Application Server: EE ...................... SUCCESS [13.024s]
> [INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [7.015s]
> [INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [0.184s]
> [INFO] JBoss Application Server: Common code for clustering subsystems SUCCESS [5.332s]
> [INFO] JBoss Application Server: JGroups Subsystem ....... SUCCESS [8.036s]
> [INFO] JBoss Application Server: Infinispan Subsystem .... SUCCESS [23.168s]
> [INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [11.052s]
> [INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [19.138s]
> [INFO] JBoss Application Server: Clustering Server API ... SUCCESS [13.274s]
> [INFO] JBoss Application Server: Clustered registry service SUCCESS [2.203s]
> [INFO] JBoss Application Server: JacORB Subsystem ........ SUCCESS [16.268s]
> [INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [35.557s]
> [INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [5.422s]
> [INFO] JBoss Application Server: Clustering Server API implementation SUCCESS [5.224s]
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SUCCESS [7.409s]
> [INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [19.789s]
> [INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.183s]
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SUCCESS [9.624s]
> [INFO] JBoss Application Server: Application Client Bootstrap SUCCESS [7.014s]
> [INFO] JBoss Application Server: Command line interface .. SUCCESS [12.399s]
> [INFO] JBoss Application Server: EJB Client BOM .......... SUCCESS [0.226s]
> [INFO] JBoss Application Server: JMS Client BOM .......... SUCCESS [0.213s]
> [INFO] JBoss Application Server: EJB and JMS client combined jar SUCCESS [4.948s]
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SUCCESS [3.795s]
> [INFO] JBoss Application Server: Clustered service provider registry services SUCCESS [4.434s]
> [INFO] JBoss Application Server: Clustered singleton services SUCCESS [5.016s]
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SUCCESS [24.135s]
> [INFO] JBoss Application Server: Config Admin ............ SUCCESS [5.690s]
> [INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [7.514s]
> [INFO] JBoss Application Server: EE Deployment ........... SUCCESS [4.195s]
> [INFO] JBoss Application Server: JAXR Client ............. SUCCESS [4.562s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [0.231s]
> [INFO] JBoss Application Server: JPA SPI ................. SUCCESS [4.460s]
> [INFO] JBoss Application Server: JPA UTIL ................ SUCCESS [1.698s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [7.273s]
> [INFO] JBoss Application Server: Weld Integration ........ SUCCESS [8.499s]
> [INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [8.492s]
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SUCCESS [0.158s]
> [INFO] JBoss Application Server: JDR ..................... SUCCESS [6.291s]
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SUCCESS [5.485s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [3.706s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [18.260s]
> [INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [13.138s]
> [INFO] JBoss Application Server: Mail subsystem .......... SUCCESS [7.227s]
> [INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [18.398s]
> [INFO] JBoss Application Server: ModCluster Subsystem .... SUCCESS [7.415s]
> [INFO] JBoss Application Server: OSGi .................... SUCCESS [0.148s]
> [INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [9.388s]
> [INFO] JBoss Application Server: OSGi ConfigurationAdmin . SUCCESS [4.866s]
> [INFO] JBoss Application Server: POJO Subsystem .......... SUCCESS [7.217s]
> [INFO] JBoss Application Server: sosreport scripts ....... SUCCESS [2.259s]
> [INFO] JBoss Application Server: Service Archive Subsystem SUCCESS [6.041s]
> [INFO] JBoss Application Server: XTS Subsystem ........... SUCCESS [7.902s]
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SUCCESS [3.552s]
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SUCCESS [4.524s]
> [INFO] JBoss Application Server: Infinispan Hibernate 2nd level cache provider SUCCESS [1.783s]
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SUCCESS [3.333s]
> [INFO] JBoss Application Server: Build ................... SUCCESS [21.975s]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.190s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [1.574s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [3.888s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [2.520s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [18.181s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [3.492s]
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SUCCESS [0.261s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration SUCCESS [15.898s]
> [INFO] JBoss Application Server: Demos: Aggregator ....... SUCCESS [2.748s]
> [INFO] JBoss Application Server: Demos: Spec ............. SUCCESS [4.056s]
> [INFO] JBoss Application Server: Demos: Legacy TO BE MOVED SUCCESS [10.657s]
> [INFO] JBoss Application Server: Distribution ............ SUCCESS [1.035s]
> [INFO] JBoss Application Server: Remoting Subsystem Test . SUCCESS [2.981s]
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SUCCESS [2.360s]
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SUCCESS [1.969s]
> [INFO] JBoss Application Server Test Suite: Shared ....... SUCCESS [7.605s]
> [INFO] JBoss Application Server Test Suite: Aggregator ... SUCCESS [6.152s]
> [INFO] JBoss Application Server Test Suite: Integration .. SUCCESS [2.203s]
> [INFO] JBoss Application Server Test Suite: Integration - Smoke FAILURE [15:07.181s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 26:31.461s
> [INFO] Finished at: Thu Feb 16 11:51:51 CET 2012
> [INFO] Final Memory: 341M/494M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (smoke-full.surefire) on project jboss-as-ts-integ-smoke: Failure or timeout -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jboss-as-ts-integ-smoke
> [pjanouse@fedora15-vrt1 jboss-as]$
> {code}
> Unfortunately org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase.txt and org.jboss.as.test.smoke.embedded.demo~essaging.MessagingTestCase-output.txt files in jboss-as/testsuite/integration/smoke/target/surefire-reports are created, but leaved empty only. Nor work-around mentioned in [ARQ-696|https://issues.jboss.org/browse/ARQ-696?focusedCommentId=12667010...] comment doesn't help.
> BTW I've checked standalone-full.xml and basic things are correctly assigned to ::1 (especially _management_ and _public_ interface)
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3729) Admin console login fails on latest Chrome
by Nicklas Karlsson (JIRA)
Nicklas Karlsson created AS7-3729:
-------------------------------------
Summary: Admin console login fails on latest Chrome
Key: AS7-3729
URL: https://issues.jboss.org/browse/AS7-3729
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b, 7.1.0.Final
Environment: Windows 7 Enterprise (SP1), Chrome 19.0.1036.7 dev-m
Reporter: Nicklas Karlsson
Assignee: Heiko Braun
The application hangs at the GWT "Loading..." but never gives the password prompt dialog. Login OK on IE9. Issues remains even if caches/passwords as cleared. From the log:
{code}
Refused to set unsafe header "Connection"
Failed to load resource: the server responded with a status of 401 (Unauthorized)
680FEF40512BAC70B21AD8530EA085D0.cache.html:6772012-02-13 13:05:36,982 [ERROR] Authentication required. Could not execute {
"operation" => "read-attribute",
"name" => "process-type",
"address" => []
}
{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
14 years, 2 months
[JBoss JIRA] (AS7-3786) Some TestCases are run against hard-coded 127.0.0.1
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3786?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek moved JBPAPP-8135 to AS7-3786:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-3786 (was: JBPAPP-8135)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.0.Final
(was: EAP 6.0.0 DR 13)
Component/s: Test Suite
(was: Testsuite)
Security: (was: JBoss Internal)
Docs QE Status: (was: NEW)
> Some TestCases are run against hard-coded 127.0.0.1
> ---------------------------------------------------
>
> Key: AS7-3786
> URL: https://issues.jboss.org/browse/AS7-3786
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
> Assignee: Shelly McGowan
> Priority: Critical
>
> Some TestCases are hard bound to *127.0.0.1* IP address. I think, it is useless - especially testing in IPv6 environment is impossible in this case for a such TestCase(-s).
> These classes aren't in integration testsuite part, it is in other places.
> Some of them are (maybe I've overlooked some others):
> - org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase
> - org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase
> - org.jboss.as.controller.test.RemoteProxyControllerProtocolTestCase
> - org.jboss.as.controller.ModelControllerClientTestCase
> - org.jboss.as.jmx.JMXSubsystemTestCase
> - org.jboss.as.jmx.ModelControllerMBeanTestCase
> Otherwise these tests are run *before* IP address transformation (usually used node0 variable and tranforms AS7 config file standalone-*.xml), so maybe there isn't present now any mechanism how to get/propagate proper (and wanted) IP address.
> Also note - some of them are hardcoded to IP name alias *localhost* - see JBPAPP-8132 for localhost vs. localhost6.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3722) org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011093: Could not load component class org.springframework.social.facebook.web.FacebookInitTag for spring-social-facebook 1.0.1
by Hendy Irawan (JIRA)
Hendy Irawan created AS7-3722:
---------------------------------
Summary: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011093: Could not load component class org.springframework.social.facebook.web.FacebookInitTag for spring-social-facebook 1.0.1
Key: AS7-3722
URL: https://issues.jboss.org/browse/AS7-3722
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Affects Versions: 7.1.0.CR1b
Environment: spring-social-facebook 1.0.1.RELEASE
Reporter: Hendy Irawan
Assignee: David Lloyd
Loading only spring-social-facebook 1.0.1.RELEASE :
{code}
<dependency>
<groupId>org.springframework.social</groupId>
<artifactId>spring-social-facebook</artifactId>
<version>1.0.1.RELEASE</version>
</dependency>
{code}
throws:
{code}
16:44:45,857 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-16) MSC00001: Failed to start service jboss.deployment.unit."satukancinta-web.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."satukancinta-web.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "satukancinta-web.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_147-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_147-icedtea]
at java.lang.Thread.run(Thread.java:722) [:1.7.0_147-icedtea]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011093: Could not load component class org.springframework.social.facebook.web.FacebookInitTag
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:113)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:54)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
Caused by: java.lang.ClassNotFoundException: org.springframework.social.facebook.web.FacebookInitTag from [Module "deployment.satukancinta-web.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.0.CR6]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.0.CR6]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.0.CR6]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.0.CR6]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.0.CR6]
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:111)
... 7 more
{code}
The workaround is to add:
{code}
<dependency>
<groupId>org.springframework.social</groupId>
<artifactId>spring-social-facebook-web</artifactId>
<version>1.0.1.RELEASE</version>
</dependency>
{code}
However in my opinion this should not be needed if the web application does not use the web resources provided by spring-social-facebook-web artifact.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3709) Annotation @DependsOn does not understand definition of jar file like "name.jar#singletonBeanName"
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created AS7-3709:
-------------------------------------
Summary: Annotation @DependsOn does not understand definition of jar file like "name.jar#singletonBeanName"
Key: AS7-3709
URL: https://issues.jboss.org/browse/AS7-3709
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.CR1b
Reporter: Ondřej Chaloupka
Assignee: Stuart Douglas
In case that you define dependson annotation on singleton which is bundled in jar in ear and you want to use definition of jar with hash sign like: @DependsOn("one.jar#SingletonOne") exception is thrown during deployment.
When you use only the singleton bean name it works.
(EJB3.1 4.8.1)
{code}
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."dependson-test.ear"."two.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."dependson-test.ear"."two.jar".INSTALL: Failed to process phase INSTALL of subdeployment "two.jar" of deployment "dependson-test.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014402: Could not merge data for SingletonTwo
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.deploy(AbstractMergingProcessor.java:75)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014406: Could not find EJB one.jar#SingletonOne referenced by @DependsOn annotation in org.jboss.as.test.integration.ejb.singleton.dependson.SingletonTwo
at org.jboss.as.ejb3.deployment.processors.merging.EjbDependsOnMergingProcessor.setupDependencies(EjbDependsOnMergingProcessor.java:97)
at org.jboss.as.ejb3.deployment.processors.merging.EjbDependsOnMergingProcessor.handleAnnotations(EjbDependsOnMergingProcessor.java:71)
at org.jboss.as.ejb3.deployment.processors.merging.EjbDependsOnMergingProcessor.handleAnnotations(EjbDependsOnMergingProcessor.java:50)
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.processComponentConfig(AbstractMergingProcessor.java:91)
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.deploy(AbstractMergingProcessor.java:73)
... 6 more
{code}
Please, check my test code: https://github.com/ochaloup/jboss-as/blob/JBQA-5268-tests-singleton/tests...
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3756) RESTEasy: Deployment fails if there is more than one EJB-JAR in the EAR
by Frank Schwarz (JIRA)
Frank Schwarz created AS7-3756:
----------------------------------
Summary: RESTEasy: Deployment fails if there is more than one EJB-JAR in the EAR
Key: AS7-3756
URL: https://issues.jboss.org/browse/AS7-3756
Project: Application Server 7
Issue Type: Bug
Components: REST
Affects Versions: 7.1.0.CR1b
Reporter: Frank Schwarz
Assignee: Stuart Douglas
If there is more than one EJB-JAR in the EAR, deployment of Restful webservice fails:
{code}
22:01:53,351 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.subunit."profiles.ear"."profiles.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."profiles.ear"."profiles.war".INSTALL: Failed to process phase INSTALL of subdeployment "profiles.war" of deployment "profiles.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_30]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011231: More than one Application class found in deployment class com.buschmais.hr.profiles.rest.service.RestService and class com.buschmais.hr.profiles.rest.service.RestService
at org.jboss.as.jaxrs.deployment.ResteasyDeploymentData.merge(ResteasyDeploymentData.java:38)
at org.jboss.as.jaxrs.deployment.JaxrsIntegrationProcessor.deploy(JaxrsIntegrationProcessor.java:93)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
{code}
Please note, that there is only one class "com.buschmais.hr.profiles.rest.service.RestService" in the deployment unit. Please don't bother me to check if the class is both in the EAR and the WAR. Be assured that it is not!
This is also not RESTEASY-650.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3654) Handling of slot attribute is not done correctly
by Facundo Contrera (JIRA)
Facundo Contrera created AS7-3654:
-------------------------------------
Summary: Handling of slot attribute is not done correctly
Key: AS7-3654
URL: https://issues.jboss.org/browse/AS7-3654
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Affects Versions: 7.1.0.CR1b
Reporter: Facundo Contrera
Assignee: David Lloyd
Fix For: 7.1.0.Final
I use SLOT attribute in the driver element to reference an speficic version instead of using main (default one), but when I start up the JBoss the attribute is erased and it uses always the .jar file inside the main folder.
I tested deleting the main folder, so as to be sure the JBoss was using my .jar inside the slot folder, but it doesn't work.
>From looking into code, functionality is partly there but it does not work as it should.
--
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
14 years, 2 months