-
1. Re: JBAS015052 trying to deploy applications on AIX
jasipher Apr 2, 2013 10:05 AM (in response to jasipher)I built the jboss-as-ejb-in-ear quickstart project and deployed it to the plain vanilla standalone server. That also fails with "JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [180 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment" on AIX. The server logs are attached.
-
server.log.zip 1.6 KB
-
boot.log.zip 2.5 KB
-
-
2. Re: JBAS015052 trying to deploy applications on AIX
ctomc Apr 2, 2013 10:21 AM (in response to jasipher)Hi,
can you try with jboss 7.2.0.final (=EAP6.1.Alpha)
as there ware few bugs fixed in networking library that effected AIX.
--
tomaz
-
3. Re: JBAS015052 trying to deploy applications on AIX
jasipher Apr 2, 2013 2:01 PM (in response to ctomc)I get the same result with eap-6.1.0.Alpha. The only difference is that the JBAS015052 message is not written to the log. It is written to jboss-as-ejb-in-ear-ear.failed. Both the log and the .failed file are attached.
-
jboss-as-ejb-in-ear-ear.ear.failed.zip 336 bytes
-
server.log.zip 3.6 KB
-
-
4. Re: JBAS015052 trying to deploy applications on AIX
lafr Apr 2, 2013 2:00 PM (in response to ctomc)FYI: according to https://community.jboss.org/message/758708#758708#758708 a downgrade of your JDK from SR10 to SR7 (as far as available on AXI 7.1) helps to some extend, but other problems remain as far as I understood.
-
5. Re: JBAS015052 trying to deploy applications on AIX
jasipher Apr 4, 2013 11:55 AM (in response to lafr)Unfortunately SR7 is no longer available for download so I don't think that's going to work. And, after reading about the other problems with SR7 I'm not sure that's really a workable solution even if we're able to get a copy of it.
-
6. Re: JBAS015052 trying to deploy applications on AIX
jasipher Apr 4, 2013 12:19 PM (in response to jasipher)I can't really pretend that I know what's going on in this code, but it looks to me as if the issue is in this method from the BootTimeScannerDeployment class in org.jboss.as.server.deployment.scanner.DeploymentScannerAdd.
{code}
@Override
public Future<ModelNode> deploy(final ModelNode operation, final ScheduledExecutorService scheduledExecutor) {
try {
deploymentOperation.set(operation);
final FutureTask<ModelNode> task = new FutureTask<ModelNode>(new Callable<ModelNode>() {
@Override
public ModelNode call() throws Exception {
deploymentDoneLatch.await();
return deploymentResults.get();
}
});
scheduledExecutor.submit(task);
return task;
} finally {
scanDoneLatch.countDown();
}
}
{code}
The problem is that all it does is wait for deploymentDoneLatch to be counted down without ever executing the operation. I'm really not clear on how this works on the other platforms, but it seems like this method needs an instance of ModelControllerClient that it can use to execute the operation.
I must be missing something because it obviously works everywhere but AIX. I *think* what's going on is that this gets invoked during the oneOffScan (this is what I see in debug), and it just waits for something that never happens. On the non-AIX platforms, I think a second instance of FileSystemDeploymentService is started by the DeploymentScannerService, and that scanner actually does the deployment and somehow counts down deploymentDoneLatch.
This stuff is a bit over my head, and I'd really appreciate it if someone could straighten me out on how it's supposed to work.
-
7. Re: JBAS015052 trying to deploy applications on AIX
nickarls Apr 5, 2013 1:22 AM (in response to jasipher)I don't think that's the actual deployment code, I think it's just code for adding stuff to the deployment queue. Perhaps the scanner collects stuff that needs to be deployed then sorts out the dependencies and finally deploys them in the specific order at the end.
In any case, if you would be correct I don't think anything would deploy on any platform
-
8. Re: JBAS015052 trying to deploy applications on AIX
jasipher Jun 13, 2013 10:51 AM (in response to jasipher)The problem is resolved with SR13.