Konfiguracja środowiska. Pomoc.

0

Witam wszystkich :)
Jako, że to mój pierwszy post więc parę słów o mnie. Jestem studentem informatyki, skończyłem VI semestrów i czas wziąć się za pisanie pracy inżynierskiej. Moim tematem jest System wspomagający sprzedaż produktów bankowych. Chcę to napisać w Javie w przy użyciu EJB oraz JPA. Za serwer chciałbym użyć JBoss, jednak nie jest to mi narzucone i jeśli ktoś twierdzi, że inny jest lepszy, to chętnie zapoznam się z jego zdaniem. Mój problem polega na konfiguracji środowiska żeby to w ogóle ruszyło. Jestem całkiem zielony jeśli chodzi o to i byłbym bardzo wdzięczny za wszelkie wskazówki. Póki co tworzę aplikację w netbeansie, robię klasę Encji i już w tym momencie nie startuje wysypując następujące komunikaty:

ant -f C:\Users\Dammy\Documents\EJBModule2 -Dnb.internal.action.name=run -Ddirectory.deployment.supported=false -DforceRedeploy=false -Dnb.wait.for.caches=true run
init:
deps-jar:
compile:
library-inclusion-in-archive:
Building jar: C:\Users\Dammy\Documents\EJBModule2\dist\EJBModule2.jar
dist-directory-deploy:
pre-run-deploy:
Starting JBoss Application Server
JBoss Application Server Started
Distributing C:\Users\Dammy\Documents\EJBModule2\dist\EJBModule2.jar to [org.jboss.as.ee.deployment.spi.DeploymentManagerTarget@57f94841]
Deploying C:\Users\Dammy\Documents\EJBModule2\dist\EJBModule2.jar
{"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit."EJBModule2.jar#EJBModule2PU" is missing [jboss.naming.context.java.jboss.datasources."ExampleDS [jdbcmem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE]"]"]}}}
C:\Users\Dammy\Documents\EJBModule2\nbproject\build-impl.xml The module has not been deployed.
See the server log for details.
BUILD FAILED (total time: 22 seconds)

A poniżej logi serwera:

Calling "C:\Users\Dammy\Downloads\jboss-eap-6.4.0\jboss-eap-6.4\bin\standalone.conf.bat"
"JAVA_OPTS already set in environment; overriding default settings with values: -Xms128m -Xmx512m -XX:MaxPermSize=256m"
Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_25\bin\java"

JBoss Bootstrap Environment

JBOSS_HOME: "C:\Users\Dammy\Downloads\jboss-eap-6.4.0\jboss-eap-6.4"

JAVA: "C:\Program Files\Java\jdk1.8.0_25\bin\java"

JAVA_OPTS: "-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m"

===============================================================================

1611,316 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1
1611,677 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
1611,769 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) starting
1614,573 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment EJBModule1.jar
1614,577 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment EJBModule2.jar
1614,652 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.13.GA-redhat-1
1614,657 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
1614,660 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.13.GA-redhat-1
1614,798 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
1614,899 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem
1614,919 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
1614,897 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 37) JBAS012615: Activated the following JSF Implementations: [main, 1.2]
1614,888 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
1614,940 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.31.Final-redhat-1)
1614,972 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.3.4.Final-redhat-1
1614,953 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013371: Activating Security Subsystem
1615,091 INFO [org.jboss.as.security] (MSC service thread 1-5) JBAS013370: Current PicketBox version=4.1.1.Final-redhat-1
1615,459 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
1615,502 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
1615,505 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
1617,242 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.0.0.1:8080
1617,265 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.0.0.1:8080
1618,565 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
1621,018 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.4.Final-redhat-1
1621,025 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on 127.0.0.1:9999
1621,025 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:4447
1621,029 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\Dammy\Downloads\jboss-eap-6.4.0\jboss-eap-6.4\standalone\deployments
1621,060 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "EJBModule2.jar" (runtime-name: "EJBModule2.jar")
1621,060 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "EJBModule1.jar" (runtime-name: "EJBModule1.jar")
1622,459 INFO [org.jboss.as.jpa] (MSC service thread 1-4) JBAS011401: Read persistence.xml for EJBModule2PU
1622,459 INFO [org.jboss.as.jpa] (MSC service thread 1-7) JBAS011401: Read persistence.xml for EJBModule1PU
1622,611 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."EJBModule1.jar".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."EJBModule1.jar".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "EJBModule1.jar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011434: Persistence provider module load error org.eclipse.persistence (class org.eclipse.persistence.jpa.PersistenceProvider)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.lookupProvider(PersistenceUnitServiceHandler.java:613)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnit(PersistenceUnitServiceHandler.java:317)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:279)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleJarDeployment(PersistenceUnitServiceHandler.java:147)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:119)
at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:48)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
... 5 more
Caused by: org.jboss.modules.ModuleNotFoundException: org.eclipse.persistence:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.as.jpa.persistenceprovider.PersistenceProviderLoader.loadProviderModuleByName(PersistenceProviderLoader.java:60)
at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.lookupProvider(PersistenceUnitServiceHandler.java:610)
... 11 more

1622,621 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment EJBModule2.jar
1622,864 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting Services for CDI deployment: EJBModule2.jar
1623,336 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900 1.1.28 (redhat)
1623,411 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016008: Starting weld service for deployment EJBModule2.jar
1624,192 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "EJBModule1.jar")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit."EJBModule1.jar".FIRST_MODULE_USE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit."EJBModule1.jar".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "EJBModule1.jar"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011434: Persistence provider module load error org.eclipse.persistence (class org.eclipse.persistence.jpa.PersistenceProvider)
Caused by: org.jboss.modules.ModuleNotFoundException: org.eclipse.persistence:main"}}
1624,199 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "EJBModule2.jar")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit."EJBModule2.jar#EJBModule2PU" is missing [jboss.naming.context.java.jboss.datasources."ExampleDS [jdbcmem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE]"]"]}
1624,224 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS015859: Deployed "EJBModule2.jar" (runtime-name : "EJBModule2.jar")
1624,225 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS015859: Deployed "EJBModule1.jar" (runtime-name : "EJBModule1.jar")
1624,226 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.jboss.datasources."ExampleDS [jdbcmem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE]" (missing) dependents: [service jboss.persistenceunit."EJBModule2.jar#EJBModule2PU"]
JBAS014777: Services which failed to start: service jboss.deployment.unit."EJBModule1.jar".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."EJBModule1.jar".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "EJBModule1.jar"

1624,437 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
1624,438 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
1624,439 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started (with errors) in 14085ms - Started 201 of 242 services (4 services failed or missing dependencies, 61 services are lazy, passive or on-demand)
1624,506 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment EJBModule2.jar
1624,520 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment EJBModule1.jar (runtime-name: EJBModule1.jar) in 15ms
1625,073 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment EJBModule2.jar (runtime-name: EJBModule2.jar) in 573ms
1625,368 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "EJBModule1.jar" (runtime-name: "EJBModule1.jar")
1625,369 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "EJBModule2.jar" (runtime-name: "EJBModule2.jar")
1625,370 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.deployment.unit."EJBModule2.jar".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."EJBModule2.jar".WeldStartService]
service jboss.deployment.unit."EJBModule2.jar".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."EJBModule2.jar".WeldStartService]
service jboss.persistenceunit."EJBModule2.jar#EJBModule2PU" (missing) dependents: [service jboss.deployment.unit."EJBModule2.jar".WeldStartService, service jboss.deployment.unit."EJBModule2.jar".deploymentCompleteService]
JBAS014777: Services which failed to start: service jboss.deployment.unit."EJBModule1.jar".FIRST_MODULE_USE

1629,329 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "EJBModule2.jar" (runtime-name: "EJBModule2.jar")
1629,361 INFO [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011401: Read persistence.xml for EJBModule2PU
1629,369 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment EJBModule2.jar
1629,371 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016005: Starting Services for CDI deployment: EJBModule2.jar
1629,373 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment EJBModule2.jar
1629,377 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "EJBModule2.jar")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit."EJBModule2.jar#EJBModule2PU" is missing [jboss.naming.context.java.jboss.datasources."ExampleDS [jdbcmem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE]"]"]}
1629,378 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "EJBModule2.jar" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit."EJBModule2.jar#EJBModule2PU" is missing [jboss.naming.context.java.jboss.datasources."ExampleDS [jdbcmem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE]"]"]}
1629,381 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment EJBModule2.jar
1629,389 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment EJBModule2.jar (runtime-name: EJBModule2.jar) in 10ms

Bardzo proszę o cierpliwość i pomoc :D

0

Jeśli nie potrzebujesz kobyły jBossa (95% projektów studencko-hobbystycznych nie potrzebuje), a jedyne co chcesz osiągnąć jego używaniem to przekazywanie tego co masz w bazie i Javie to możesz użyć osadzonego serwera Jetty. Używam go w domowym dłubaniu bez, pardon, pieprzenia się z konfigurowaniem tych rzeczy. Masz do niego też framework Spark. Opisałem go tutaj - prosty set-up i wyświetlanie Hello World: http://blog.kornakiewicz.pl/spark-framework/

A ten log sugeruje, że jBoss nie ma wszystkich zależności dostępnych, ale nie znam się na tym.

0

Caused by: org.jboss.modules.ModuleNotFoundException: org.eclipse.persistence:main"
I nie dziwota, JBoss to jest standardowo Hibernate a nie EclipseLink. Widać że próbujesz odpalić jakiś randomowy kod z internetów a tutorial był pod Glassfisha...

Rada starszego kolegi: nie wypuszczaj się z motyką na słońce. Chcesz klepać na inż. system w dziedzinie na której sie nie znasz w technologii której nie umiesz. To się skończy bardzo słabo i w terminie to ty sie nie obronisz.

0

Skoro jest to projekt na studia, to nie wolisz go pisać w JEE7 i używać najnowszej wersji JBossa (Wildfly9)?
Pokaż persistence.xml, bo coś mi się wydaje że ustawiłeś jako providera JPA eclipselinka, a w JBoss jest Hibernate. Możesz w ogóle wywalić sekcję provider, to zostanie wybrany domyślny dla serwera aplikacyjnego.

0

Ogólnie miałem na 6 semestrze przedmiot na którym właśnie miałem EJB i JPA, wydało mi się to ciekawe i dla kogoś zielonego dobre na start. Kupiłem książkę do nauki i tam właśnie było opisane na JBossie, więc dlatego mój wybór padł na JBossa. Spróbuje waszych propozycji (JBossa (Wildfly9) i/lub Jetty).

Shalom:
Wiem, że czeka mnie trudne zadanie, ale chcę przy okazji się czegoś nauczyć, mam dużą motywację i mam nadzieję, że uda mi się osiągnąć cel. W Swingu napisałem już cały interfejs, zostaje "tylko" baza.

1 użytkowników online, w tym zalogowanych: 0, gości: 1