I'm trying do deploy a java spring project on ec2 but the deployment fails.
On Jenkins I get this message:
"Failed to connect to the host via ssh: Shared connection to *ip* closed.", "unreachable": true
checking the server logs, I found this error:
ERROR [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0022:
Deploy of deployment "*.war" was rolled back with no failure message
Related
I'm actually trying to develop an hyperledger network composed by 11 peers belongs to the same organization (the only org in the network). For the deploy I'm following the hyperledger tutorial skeleton (v2.2) rewriting scripts from the fabric-samples repository for our purposes.
Deploy is essentially completed except for the chaincode (I'm using java version of basic-transfer chaincode for testing), scripts passes every of the following steps:
Packaging chaincode
Installing chaincode for each peer
Query installed chaincode (succesfull for each peer)
ApproveForMyOrg by authorized peer
Check commit readiness (succesfull for each peer)
Commit chaincode
Query Commited Chaincode (succesfull for each peer)
At the end of these steps are supposed to be some containers representing chaincode deployed for eache peer. Containers are created but I found each of them exited with status 1.
Inspecting logs inside crashed containers I've found the following error:
Thread[main,5,main] 12:58:44:717 SEVERE org.hyperledger.fabric.contract.ContractRouter startRouting Unable to start routing
org.hyperledger.fabric.contract.ContractRuntimeException: Unable to start routing
at org.hyperledger.fabric.contract.ContractRouter.startRouting(ContractRouter.java:99)
at org.hyperledger.fabric.contract.ContractRouter.main(ContractRouter.java:174)
Exception in thread "main" org.hyperledger.fabric.contract.ContractRuntimeException: Unable to start routing
at org.hyperledger.fabric.contract.ContractRouter.startRouting(ContractRouter.java:99)
at org.hyperledger.fabric.contract.ContractRouter.main(ContractRouter.java:174)
furthermore inspecting log inside the commiter peer container I've found this warning:
2022-07-19 12:58:44.924 UTC [lifecycle] Work -> WARN 07b could not launch chaincode 'basic_1.0:bbab0f02e28d4564deb06801011c79a705a33755dc6f25d6e2ae8dd39b51a09f': chaincode registration failed: container exited with 1
At this point I cannot invoke deployed chaincode for this reason.
I'm facing an error while trying to deploy my applications, when trying to start WildFly 10.1.0 in debug mode through eclipse's plugin.
I have 4 applications been deploying directly through wildfly's folder, with its .war files, and 3 applications on my workspace, being deployed on eclipse's plugin.
The error is this one.
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.server.DeployerChainAddHandler$FinalRuntimeStepHandler#12ac20df for operation {"operation" => "add-deployer-chains","address" => []} at address [] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException
ERROR [org.jboss.as.controller.client] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.domain.management.security.SecurityRealmAddHandler$ServiceInstallStepHandler#2b4e1dec for operation {"address" => [("core-service" => "management"),("security-realm" => "ApplicationRealm")],"operation" => "add","map-groups-to-roles" => undefined} at address [
("core-service" => "management"),
("security-realm" => "ApplicationRealm")
] failed handling operation rollback --
java.util.concurrent.TimeoutException
Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final]
at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final]
at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final]
at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124)
at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138)
at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final]
ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment ".....-.war" was rolled back with no failure message
ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment ".....-.war" was rolled back with no failure message
ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment ".....-.war" was rolled back with no failure message
ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment ".....-.war" was rolled back with no failure message
ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment ".....-.war" was rolled back with no failure message
ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment ".....-.war" was rolled back with no failure message
ERROR [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0022: Deploy of deployment ".....-.war" was rolled back with no failure message
I know its a timeout, but i dont know why and what should i do to solve this.
When i start the server without the debug mode, this doesn't happen.
It starts much faster and i can access my application normally.
I'm the only one on company that have this issue, and no one figure out whats going on.
I'm using a Linux Ubuntu 64-bit.
I leveled up my Wildfly's VM arguments configuration to this:
-Xms256m -Xmx1536m
I'm using a custom standalone.xml, used for everyone on my company.
This is taking so long and i'm missing most of the time, trying to startup on debug mode.
(Yes, sometimes and somehow it works and i have like 10 minutes developing while wildfly helps me).
I trully need help cause this is unableling me from work...may anyone help me?
Obs.: I changed the war file names, just to be safe.
You should check for method breakpoints. If you have breakpoints on methods, just remove it.
I am able to run a JBOSS project without debugging.
However, when I try to run the project in debug mode I get the following message in the event log:
5:02:17 PM All files are up-to-date
5:02:21 PM All files are up-to-date
5:02:21 PM Error running ProjectConfiguration
Invalid arguments : Already listening
[timeout, port, localAddress]
I have killed all the java.exe processes on my machine. Any ideas?
Update
I setup a fresh project completely. I am now getting the following:
6:06:56 PM Error running JBOSS Local: Unable to open debugger port (127.0.0.1:9157): java.net.SocketException "socket closed"
6:06:56 PM Application Server was not connected before run configuration stop, reason:
Unable to ping server at localhost:8080
AND this:
ERROR: transport error 202: failed to attach to shared memory connection: The system cannot find the file specified
ERROR: JDWP Transport dt_shmem failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Disconnected from server
Perhaps you could try remote debugging by starting JBoss with this uncommented in bin/standalone.conf.bat:
-Xrunjdwp:transport=dt_socket,address=8888,server=y,suspend=n
Then in IntelliJ, start a remote debug session against localhost:8888.
I have a Gradle project that I'm trying to deploy locally with gradlew stopServers deploy startServers but it fails with this error:
:components/verification-ear:stopServers
Stopping server: localhost/server-three
Failed to get the list of the operation properties: "JBAS014883: No resource definition is registered for address [
("host" => "localhost"),
("server-config" => "server-three")
]"
:components/verification-ear:stopServers FAILED
FAILURE: Build failed with an exception.
I don't understand why this is throwing an error. I have servers 1 & 2 shut off while 3 is running full-ha. My JBOSS_HOME variable is correct and I'm running in domain mode from the JBoss Home bin.
I'm trying to move some Web Service stubs from Metro to Axis2, however after generating my stubs using wsdl2java I'm constently getting 404 errors whenever I try and make a service call.
16/12/2010 11:14:57 AM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing-1.5.3-jar - file:/C:/Users/xxx/.m2/repository/org/apache/axis2/axis2/1.5.3/axis2-1.5.3-jar.jar
16/12/2010 11:14:57 AM org.apache.axis2.transport.http.HTTPSender sendViaPost
INFO: Unable to sendViaPost to url[xxxx]
org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:307)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:200)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:438)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at au.com.jpaterso.betcalc.axis2.tab.LoginStub.getKey(LoginStub.java:184)
at au.com.jpaterso.betcalc.axis2.tab.Test.main(Test.java:13)
Exception in thread "main" org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:307)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:200)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:438)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at au.com.jpaterso.betcalc.axis2.tab.LoginStub.getKey(LoginStub.java:184)
at au.com.jpaterso.betcalc.axis2.tab.Test.main(Test.java:13)
The URL that it's trying to connect to is definitely correct as I can access it via my browser/SoapUI.
Any help would be greatly appreciated!
Thanks, Joseph.
You didn't provide much information about the environment in which you try to deploy your WS. E.g. is this a webapp running under Tomcat/JBoss or maybe the standalone server deployed with Axis2?
From the trace that you have posted I suppose that there is a connection with your server but your WS is not successfully deployed. I assume that you may use the standalone server for your tests and I suggest:
Go to your WS repository. On my test machine this would be something like ~/axis2-x.x.x/repository/services and make sure that your service is there (either the .aar file or the unpacked version).
Start the server and check if your service is really deployed. On my installation, for example the server will generate the following output (not complete):
me#melinuxpc:~/axis2-1.5.1/bin> ./axis2server.sh
Using AXIS2_HOME: xxx
Using JAVA_HOME: xxx
Using JAVA_OPTS: -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
Listening for transport dt_socket at address: 8000
[INFO] [SimpleAxisServer] Starting
[INFO] [SimpleAxisServer] Using the Axis2 Repository xxx
[SimpleAxisServer] Using the Axis2 Repository xxx
[SimpleAxisServer] Using the Axis2 Configuration File xxx
[INFO] Clustering has been disabled
[INFO] Deploying module: xxx
[INFO] Deploying Web service: MyTestService - file: ~/axis2-1.5.1/repository/services/MyTestService/
Check if your web service is deployed and there are no errors. You may check if the WSDL of the service is available "in the browser". On my test machine the URL will be:
http://localhost:8080/axis2/services/MyTestService?wsdl
While a list with all deployed services may be seen at:
http://localhost:8080/axis2/services/
And do not be too quick in abandoning Axis2 ;)
Good luck!
I also see this error when use "axis2-wsdl2code-maven-plugin" to generate stub for a .NET webservice (.asmx).
I fixed by disable "chunked" of _serviceClient. Only add below code in method Constructor of file stub.
_serviceClient.getOptions().setProperty(HTTPConstants.CHUNKED, "false");