@Wibowit generalnie często coś źle skonfiguruje i potem uruchamiając projekt nie śmiga, serwer również często rzuci jakimś dziwnym wyjątkiem, do którego kompletnie nie wiem jak się zabrać
rozumiem, że błędy leżą często po mojej stronie - coś źle skonfiguruje albo dodam kolidujące ze sobą dependencies w pomie. Tylko, że w innych technologiach się z tym nie spotkałem, ani nie słyszałem od znajomych czy gdzieś tam w internecie, żeby takie pokręcone problemy były
I dlatego ten temat :P próbuje rozwikłać czy ja jakoś źle do tego podchodze, czy to po prostu tak wygląda pisanie w javie (a może i każda technologia tak ma jak się ją bliżej posmyra)
edit
szybki przykład: zrobilem świeży projekt o nazwie ABC, wrzuciłem JBossa jako serwer, zrobilem artifact .war odpalam i mam:
C:\Users\Maciek\workspace\jboss-eap-6.2\bin\standalone.bat
[2014-06-03 05:10:19,351] Artifact unnamed: Server is not connected. Deploy is not available.
Detected server admin port: 9999
Detected server http port: 8080
Calling "C:\Users\Maciek\workspace\jboss-eap-6.2\bin\standalone.conf.bat"
Setting JAVA property to "C:\Program Files\Java\jdk1.7.0_45\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "C:\Users\Maciek\workspace\jboss-eap-6.2"
JAVA: "C:\Program Files\Java\jdk1.7.0_45\bin\java"
JAVA_OPTS: "-XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman"
===============================================================================
17:10:20,311 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
17:10:20,461 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
17:10:20,523 INFO [org.jboss.as] (MSC service thread 1-8) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
17:10:21,233 INFO [org.xnio] (MSC service thread 1-9) XNIO Version 3.0.7.GA-redhat-1
17:10:21,234 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
17:10:21,237 INFO [org.xnio.nio] (MSC service thread 1-9) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
17:10:21,243 INFO [org.jboss.remoting] (MSC service thread 1-9) JBoss Remoting version 3.2.18.GA-redhat-1
17:10:21,262 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.
17:10:21,277 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem
17:10:21,280 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
17:10:21,284 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
17:10:21,291 INFO [org.jboss.as.security] (MSC service thread 1-14) JBAS013170: Current PicketBox version=4.0.19.SP2-redhat-1
17:10:21,302 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
17:10:21,304 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
17:10:21,308 INFO [org.jboss.as.connector.logging] (MSC service thread 1-16) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.23.Final-redhat-1)
17:10:21,316 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
17:10:21,345 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
17:10:21,462 INFO [org.apache.coyote.http11] (MSC service thread 1-14) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.0.0.1:8080
17:10:21,468 INFO [org.apache.coyote.http11] (MSC service thread 1-14) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.0.0.1:8080
17:10:21,552 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
17:10:21,567 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.3.Final-redhat-1
17:10:21,596 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-12) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\Maciek\workspace\jboss-eap-6.2\standalone\deployments
17:10:21,597 INFO [org.jboss.as.remoting] (MSC service thread 1-9) JBAS017100: Listening on 127.0.0.1:4447
17:10:21,597 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:9999
17:10:21,600 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-16) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:224) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_45]
at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_45]
at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_45]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_45]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_45]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:162) [jboss-as-domain-http-interface-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:190) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
... 5 more
17:10:21,840 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
17:10:21,850 INFO [org.jboss.as] (Controller Boot Thread) JBAS015964: Http management interface is not enabled
17:10:21,850 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
17:10:21,850 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) started (with errors) in 1814ms - Started 127 of 186 services (2 services failed or missing dependencies, 56 services are passive or on-demand)
Connected to server
[2014-06-03 05:10:22,241] Artifact unnamed: Artifact is being deployed, please wait...
17:10:22,307 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015876: Starting deployment of "unnamed.war" (runtime-name: "unnamed.war")
17:10:22,313 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."unnamed.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."unnamed.war".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "unnamed.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018740: Failed to mount deployment content
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:97) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
... 5 more
Caused by: java.io.FileNotFoundException: C:\Users\Maciek\IdeaProjects\ABC\out\artifacts\unnamed\unnamed.war (System nie może odnaleźć określonej ścieżki)
at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_45]
at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_45]
at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:55)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:258)
at org.jboss.vfs.VFS.mountZipExpanded(VFS.java:533)
at org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.mountDeploymentContent(DeploymentMountProvider.java:98) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:93) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
... 6 more
17:10:22,317 ERROR [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "unnamed.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"unnamed.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"unnamed.war\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"unnamed.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018740: Failed to mount deployment content
Caused by: java.io.FileNotFoundException: C:\\Users\\Maciek\\IdeaProjects\\ABC\\out\\artifacts\\unnamed\\unnamed.war (System nie może odnaleźć określonej ścieżki)"}}
17:10:22,319 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment unnamed.war (runtime-name: unnamed.war) in 2ms
[2014-06-03 05:10:22,349] Artifact unnamed: Error during artifact deployment. See server log for details.
[2014-06-03 05:10:22,377] Artifact unnamed: java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"unnamed.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"unnamed.war\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"unnamed.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018740: Failed to mount deployment content
Caused by: java.io.FileNotFoundException: C:\\Users\\Maciek\\IdeaProjects\\ABC\\out\\artifacts\\unnamed\\unnamed.war (System nie może odnaleźć określonej ścieżki)"}}
Nie mówie, że sie nie da rozwiązać bo nie próbowałem póki co, ale chodzi mi o sam fakt wystąpienia.