Fail to deploy vdb by Admin API sometimes.
Sometimes I failed to deploy vdb by Admin API.
The teiid version is 7.2.
And the option -c used when starting jbossas refers to a symbolic link.
The teiid-server is a symbolic link.
The whole log file "deployError.log" was attached. You can search the key word "/StreamingDeploymentTarget" in the log file.
The test case is that deploying a given VDB continuously. There are two fail of hundreds deployments.
11:07:53,132 INFO  [RUNTIME] Data Source DFS_CORE not accessible.
11:07:53,133 INFO  [RUNTIME] Data Source workspace_23Connection not accessible.
11:07:53,134 INFO  [RUNTIME] Data Source workspace_23Connection not accessible.
11:07:53,134 INFO  [RUNTIME] VDB "W23.1[DR_dfs[dfs/teiid/DFS_CORE, localdb/oracle/workspace_23Connection], ext[ext/oracle/workspace_23Connection], workspaceInstance]" deployed in inactive state.
BTW, I found that there was an issue of Jboss-soa that has similar exception.
1. Fail to deploy vdb by Admin API sometimes.
Did the VDB actually deployed, and NPE was saying that the deployment already done or actual error in deploying. I am trying to figure out if I can ignore the NPE or not.
2. Re: Fail to deploy vdb by Admin API sometimes.
When we use option "-c path" to start jboss, if this path is a link as description of this topic. we met a issue about deploy VDB in Teiid 7.2 ( or 7.1) sometimes.
If this path is real path, it will be ok.
Now we have used 7.4 beta1 for Teiid. We use "link" to start Jboss. it looks OK.
So I want to know whether this is known bug which has been fix from 7.1 or 7.2 to now.
3. Re: Fail to deploy vdb by Admin API sometimes.
-c <profile> = points to what profile you want to start like 'default', 'all' etc. I did not understand the link part here. Either way, I do not know of any fix we put in for this issue.
4. Re: Fail to deploy vdb by Admin API sometimes.
I am testing this case. Follow is my test code.
I am testing for Teiid 7.4 beta1. I also find same issue. When I start jboss use "-c teiid-server". This issue will be happened. The attchement is log of this issue.
In my environment , we create a link which is below our $JBOSS_HOME/server.
We can have 2 difference ways to start jboss. Thay are "-c teiid-server" and "-c /var/mwm/jboss/server/teiid-server".
When using "-c teiid-server", it will throw an exception as you have saw.
When using "-c /var/mwm/jboss/server/teiid-server", I have not found this issue by now.
I am testing way 2. At this time it has run over 900 times. It is OK now.
Could you give me any advice to avoid this issue ?
5. Re: Fail to deploy vdb by Admin API sometimes.
An update follow previous message.
It is running over 1800 times use way 2. It is ok now.
6. Re: Fail to deploy vdb by Admin API sometimes.
By now, My test has been running over 10700 times in way 2.
7. Fail to deploy vdb by Admin API sometimes.
My test has been running all day. It has been run over 14000 times in way 2. It looks OK.
It fail under 1000 times in way 1.
So Maybe it is a bug for teiid I think. Or shall I configure something to avoid it?
8. Fail to deploy vdb by Admin API sometimes.
and the releated JBoss Remoting JIRA, try to apply the patch from that issue and rebuild the jboss-remoting.jar, this will remove the remote deployer to local in VM deployer. That may improve the above deployment situation.