Service Assemblies don't show up!!!

[learnopenesb]

Hi,

We are using openesb 20080515 build and for some reason after the server restart the service assemblies don't show up at all. We have checked the jbi-registry.xml and it does not have any assemblies in there!

We are not sure what could have caused this issue? Any pointers?Copy+of+server_Log+063008.zip

server.log is attached for reference.


Thanks
Neel

[Nikita Sawant]

Hi Neel,

The server.log does not have any information regarding service
assemblies being deployed/ to the runtime, the attached log seems to
have the later half of your setup.

Did you deploy service assemblies and then restart the server
immediately ? What exact sequence of steps did you follow ?

~ Nikita

learnopenesb wrote:

> Hi,
>
> We are using openesb 20080515 build and for some reason after the server
> restart the service assemblies don't show up at all. We have checked the
> jbi-registry.xml and it does not have any assemblies in there!
>
> We are not sure what could have caused this issue? Any pointers?
> http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
> Copy+of+server_Log+063008.zip
>
> server.log is attached for reference.
>
>
> Thanks
> Neel
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[learnopenesb]

Nikita,

We already had assemblies deployed onto the server and were working fine. The server log has entries starting yesterday and we know for sure things were working fine till today AM.

As with the sequence of events that happened,
1) we had deployed few composite apps today AM (the composite apps is that they were generated/built using netbeans build 200806161120).
2) At around 1pm today we noticed that one of our already deployed service (ejb web service) was not responding due to connection pool max. out errors. We fixed that service and redeployed it and restarted the server. The service then started functioning as desired.
3) Later-on we observed that all our service assemblies are missing!

We really are not sure what could have caused this and were hoping the log would provide more details.
One suspect is the deployment of CA from netbeans build 200806161120 to Glassfish server 20080515 but we are not sure.

Let me know if you need any further information.

Thanks
Neel

Nikita Sawant wrote:

Hi Neel,

The server.log does not have any information regarding service
assemblies being deployed/ to the runtime, the attached log seems to
have the later half of your setup.

Did you deploy service assemblies and then restart the server
immediately ? What exact sequence of steps did you follow ?

~ Nikita

learnopenesb wrote:
> Hi,
>
> We are using openesb 20080515 build and for some reason after the server
> restart the service assemblies don't show up at all. We have checked the
> jbi-registry.xml and it does not have any assemblies in there!
>
> We are not sure what could have caused this issue? Any pointers?
> http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
> Copy+of+server_Log+063008.zip
>
> server.log is attached for reference.
>
>
> Thanks
> Neel
>  


---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[Nikita Sawant]

Hi Neel,

Can you send me a listing of the contents of the service assembly folder : ${DOMAIN}/jbi/service-assemblies and attach the jbi-registry.xml too.

Do you have a cluster setup or are you deploying to a single server instance ?

Regards,
Nikita

learnopenesb wrote:

Nikita,

We already had assemblies deployed onto the server and were working fine.
The server log has entries starting yesterday and we know for sure things
were working fine till today AM.

As with the sequence of events that happened, 
1) we had deployed few composite apps today AM (the composite apps is that
they were generated/built using netbeans build 200806161120). 
2) At around 1pm today we noticed that one of our already deployed service
(ejb web service) was not responding due to connection pool max. out errors.
We fixed that service and redeployed it and restarted the server. The
service then started functioning as desired.
3) Later-on we observed that all our service assemblies are missing!

We really are not sure what could have caused this and were hoping the log
would provide more details. 
One suspect is the deployment of CA from netbeans build 200806161120 to
Glassfish server 20080515 but we are not sure.

Let me know if you need any further information.

Thanks
Neel


Nikita Sawant wrote:
  

Hi Neel,

The server.log does not have any information regarding service 
assemblies being deployed/ to the runtime, the attached log seems to 
have the later half of your setup. 

Did you deploy service assemblies and then restart the server 
immediately ? What exact sequence of steps did you follow ?

~ Nikita

learnopenesb wrote:
    

Hi,

We are using openesb 20080515 build and for some reason after the server
restart the service assemblies don't show up at all. We have checked the
jbi-registry.xml and it does not have any assemblies in there!

We are not sure what could have caused this issue? Any pointers?
http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
Copy+of+server_Log+063008.zip 

server.log is attached for reference.


Thanks
Neel
  
      

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...



    

[learnopenesb]

Nikita,

The servcies assemblies folder is empty and that is really surprising!. I have attached the jbi-registry.xml
We do NOT have a cluster setup.

The other question though is how do we get back on track?

Thanks
Neel
jbi-registry.xml

Nikita Sawant wrote:

Hi Neel,

Can you send me a listing of the contents of the service assembly folder
: ${DOMAIN}/jbi/service-assemblies and attach the jbi-registry.xml too.

Do you have a cluster setup or are you deploying to a single server
instance ?

Regards,
Nikita

learnopenesb wrote:
> Nikita,
>
> We already had assemblies deployed onto the server and were working fine.
> The server log has entries starting yesterday and we know for sure things
> were working fine till today AM.
>
> As with the sequence of events that happened,
> 1) we had deployed few composite apps today AM (the composite apps is that
> they were generated/built using netbeans build 200806161120).
> 2) At around 1pm today we noticed that one of our already deployed service
> (ejb web service) was not responding due to connection pool max. out errors.
> We fixed that service and redeployed it and restarted the server. The
> service then started functioning as desired.
> 3) Later-on we observed that all our service assemblies are missing!
>
> We really are not sure what could have caused this and were hoping the log
> would provide more details.
> One suspect is the deployment of CA from netbeans build 200806161120 to
> Glassfish server 20080515 but we are not sure.
>
> Let me know if you need any further information.
>
> Thanks
> Neel
>
>
> Nikita Sawant wrote:
>  
>> Hi Neel,
>>
>> The server.log does not have any information regarding service
>> assemblies being deployed/ to the runtime, the attached log seems to
>> have the later half of your setup.
>>
>> Did you deploy service assemblies and then restart the server
>> immediately ? What exact sequence of steps did you follow ?
>>
>> ~ Nikita
>>
>> learnopenesb wrote:
>>    
>>> Hi,
>>>
>>> We are using openesb 20080515 build and for some reason after the server
>>> restart the service assemblies don't show up at all. We have checked the
>>> jbi-registry.xml and it does not have any assemblies in there!
>>>
>>> We are not sure what could have caused this issue? Any pointers?
>>> http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
>>> Copy+of+server_Log+063008.zip
>>>
>>> server.log is attached for reference.
>>>
>>>
>>> Thanks
>>> Neel
>>>  
>>>      
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [e-mail]
>> For additional commands, e-mail: [e-mail]
>>
>>
>>
>>    
>
>  

[Nikita Sawant]

Hi Neel,

The empty contents of the service-assemblies folder and the empty jbi-registry.xml indicate that the service assembly has either been undeployed or removed.

A service assembly is removed from both the registry and repository ( the service-assemblies folder ) when :

1. You undeploy it
2. You accidentally delete it from one of the two, then the other is cleaned up by the runtime automatically. i.e. if you accidentlly deleted the contents of the service-assemblies folder then the service-assembly is deleted from the registry and vice versa.

If the case were (2) then there is a message in the server.log indicating so, which I do not see.

So I don't know what went wrong in your case. Could you zip the  ${DOMAIN}/jbi/config folder, I want to see if there were any issues with persisting information to the registry.

To get back on track you need to deploy the composite applications again.

Regards,
Nikita

learnopenesb wrote:

Nikita,

The servcies assemblies folder is empty and that is really surprising!. I
have attached the jbi-registry.xml
We do NOT have a cluster setup.

The other question though is how do we get back on track?

Thanks
Neel
http://www.nabble.com/file/p18214355/jbi-registry.xml jbi-registry.xml 


Nikita Sawant wrote:
  

Hi Neel,

Can you send me a listing of the contents of the service assembly folder 
: ${DOMAIN}/jbi/service-assemblies and attach the jbi-registry.xml too.

Do you have a cluster setup or are you deploying to a single server 
instance ?

Regards,
Nikita

learnopenesb wrote:
    

Nikita,

We already had assemblies deployed onto the server and were working fine.
The server log has entries starting yesterday and we know for sure things
were working fine till today AM.

As with the sequence of events that happened, 
1) we had deployed few composite apps today AM (the composite apps is
that
they were generated/built using netbeans build 200806161120). 
2) At around 1pm today we noticed that one of our already deployed
service
(ejb web service) was not responding due to connection pool max. out
errors.
We fixed that service and redeployed it and restarted the server. The
service then started functioning as desired.
3) Later-on we observed that all our service assemblies are missing!

We really are not sure what could have caused this and were hoping the
log
would provide more details. 
One suspect is the deployment of CA from netbeans build 200806161120 to
Glassfish server 20080515 but we are not sure.

Let me know if you need any further information.

Thanks
Neel


Nikita Sawant wrote:
  
      

Hi Neel,

The server.log does not have any information regarding service 
assemblies being deployed/ to the runtime, the attached log seems to 
have the later half of your setup. 

Did you deploy service assemblies and then restart the server 
immediately ? What exact sequence of steps did you follow ?

~ Nikita

learnopenesb wrote:
    
        

Hi,

We are using openesb 20080515 build and for some reason after the
server
restart the service assemblies don't show up at all. We have checked
the
jbi-registry.xml and it does not have any assemblies in there!

We are not sure what could have caused this issue? Any pointers?
http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
Copy+of+server_Log+063008.zip 

server.log is attached for reference.


Thanks
Neel
  
      
          

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...



    
        

[learnopenesb]

Nikita,

Attached is the zip of the ${DOMAIN}/jbi/config folder.config.zip

Nikita Sawant wrote:

Hi Neel,

The empty contents of the service-assemblies folder and the empty
jbi-registry.xml indicate that the service assembly has either been
undeployed or removed.

A service assembly is removed from both the registry and repository (
the service-assemblies folder ) when :

   1. You undeploy it
   2. You accidentally delete it from one of the two, then the other is
      cleaned up by the runtime automatically. i.e. if you accidentlly
      deleted the contents of the service-assemblies folder then the
      service-assembly is deleted from the registry and vice versa.

If the case were (2) then there is a message in the server.log
indicating so, which I do not see.

So I don't know what went wrong in your case. Could you zip the  
${DOMAIN}/jbi/config folder, I want to see if there were any issues with
persisting information to the registry.

To get back on track you need to deploy the composite applications again.

Regards,
Nikita

learnopenesb wrote:
> Nikita,
>
> The servcies assemblies folder is empty and that is really surprising!. I
> have attached the jbi-registry.xml
> We do NOT have a cluster setup.
>
> The other question though is how do we get back on track?
>
> Thanks
> Neel
> http://www.nabble.com/file/p18214355/jbi-registry.xml jbi-registry.xml
>
>
> Nikita Sawant wrote:
>  
>> Hi Neel,
>>
>> Can you send me a listing of the contents of the service assembly folder
>> : ${DOMAIN}/jbi/service-assemblies and attach the jbi-registry.xml too.
>>
>> Do you have a cluster setup or are you deploying to a single server
>> instance ?
>>
>> Regards,
>> Nikita
>>
>> learnopenesb wrote:
>>    
>>> Nikita,
>>>
>>> We already had assemblies deployed onto the server and were working fine.
>>> The server log has entries starting yesterday and we know for sure things
>>> were working fine till today AM.
>>>
>>> As with the sequence of events that happened,
>>> 1) we had deployed few composite apps today AM (the composite apps is
>>> that
>>> they were generated/built using netbeans build 200806161120).
>>> 2) At around 1pm today we noticed that one of our already deployed
>>> service
>>> (ejb web service) was not responding due to connection pool max. out
>>> errors.
>>> We fixed that service and redeployed it and restarted the server. The
>>> service then started functioning as desired.
>>> 3) Later-on we observed that all our service assemblies are missing!
>>>
>>> We really are not sure what could have caused this and were hoping the
>>> log
>>> would provide more details.
>>> One suspect is the deployment of CA from netbeans build 200806161120 to
>>> Glassfish server 20080515 but we are not sure.
>>>
>>> Let me know if you need any further information.
>>>
>>> Thanks
>>> Neel
>>>
>>>
>>> Nikita Sawant wrote:
>>>  
>>>      
>>>> Hi Neel,
>>>>
>>>> The server.log does not have any information regarding service
>>>> assemblies being deployed/ to the runtime, the attached log seems to
>>>> have the later half of your setup.
>>>>
>>>> Did you deploy service assemblies and then restart the server
>>>> immediately ? What exact sequence of steps did you follow ?
>>>>
>>>> ~ Nikita
>>>>
>>>> learnopenesb wrote:
>>>>    
>>>>        
>>>>> Hi,
>>>>>
>>>>> We are using openesb 20080515 build and for some reason after the
>>>>> server
>>>>> restart the service assemblies don't show up at all. We have checked
>>>>> the
>>>>> jbi-registry.xml and it does not have any assemblies in there!
>>>>>
>>>>> We are not sure what could have caused this issue? Any pointers?
>>>>> http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
>>>>> Copy+of+server_Log+063008.zip
>>>>>
>>>>> server.log is attached for reference.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Neel
>>>>>  
>>>>>      
>>>>>          
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [e-mail]
>>>> For additional commands, e-mail: [e-mail]
>>>>
>>>>
>>>>
>>>>    
>>>>        
>>>  
>>>      
>>
>>    
>
>  

[Nikita Sawant]

Hi Neel,

The jbi-registry.xml  in the jbi/config folder you provided is different than the one you provided earlier ( http://www.nabble.com/file/p18214355/jbi-registry.xml ).

The one in jbi/config shows a service assembly "XDSBDocumentRetrieveCA" deployed to the HTTP BC and BPEL SE on the server instance. While the one you provided earlier does not have any service assemblies.

Which one is the correct one ?

~ Nikita

learnopenesb wrote:

Nikita,

Attached is the zip of the ${DOMAIN}/jbi/config folder.
http://www.nabble.com/file/p18222381/config.zip config.zip 



Nikita Sawant wrote:
  

Hi Neel,

The empty contents of the service-assemblies folder and the empty 
jbi-registry.xml indicate that the service assembly has either been 
undeployed or removed.

A service assembly is removed from both the registry and repository ( 
the service-assemblies folder ) when :

   1. You undeploy it
   2. You accidentally delete it from one of the two, then the other is
      cleaned up by the runtime automatically. i.e. if you accidentlly
      deleted the contents of the service-assemblies folder then the
      service-assembly is deleted from the registry and vice versa.

If the case were (2) then there is a message in the server.log 
indicating so, which I do not see.

So I don't know what went wrong in your case. Could you zip the  
${DOMAIN}/jbi/config folder, I want to see if there were any issues with 
persisting information to the registry.

To get back on track you need to deploy the composite applications again.

Regards,
Nikita

learnopenesb wrote:
    

Nikita,

The servcies assemblies folder is empty and that is really surprising!. I
have attached the jbi-registry.xml
We do NOT have a cluster setup.

The other question though is how do we get back on track?

Thanks
Neel
http://www.nabble.com/file/p18214355/jbi-registry.xml jbi-registry.xml 


Nikita Sawant wrote:
  
      

Hi Neel,

Can you send me a listing of the contents of the service assembly folder 
: ${DOMAIN}/jbi/service-assemblies and attach the jbi-registry.xml too.

Do you have a cluster setup or are you deploying to a single server 
instance ?

Regards,
Nikita

learnopenesb wrote:
    
        

Nikita,

We already had assemblies deployed onto the server and were working
fine.
The server log has entries starting yesterday and we know for sure
things
were working fine till today AM.

As with the sequence of events that happened, 
1) we had deployed few composite apps today AM (the composite apps is
that
they were generated/built using netbeans build 200806161120). 
2) At around 1pm today we noticed that one of our already deployed
service
(ejb web service) was not responding due to connection pool max. out
errors.
We fixed that service and redeployed it and restarted the server. The
service then started functioning as desired.
3) Later-on we observed that all our service assemblies are missing!

We really are not sure what could have caused this and were hoping the
log
would provide more details. 
One suspect is the deployment of CA from netbeans build 200806161120 to
Glassfish server 20080515 but we are not sure.

Let me know if you need any further information.

Thanks
Neel


Nikita Sawant wrote:
  
      
          

Hi Neel,

The server.log does not have any information regarding service 
assemblies being deployed/ to the runtime, the attached log seems to 
have the later half of your setup. 

Did you deploy service assemblies and then restart the server 
immediately ? What exact sequence of steps did you follow ?

~ Nikita

learnopenesb wrote:
    
        
            

Hi,

We are using openesb 20080515 build and for some reason after the
server
restart the service assemblies don't show up at all. We have checked
the
jbi-registry.xml and it does not have any assemblies in there!

We are not sure what could have caused this issue? Any pointers?
http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
Copy+of+server_Log+063008.zip 

server.log is attached for reference.


Thanks
Neel
  
      
          
              

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...



    
        
            

[learnopenesb]

Nikita,

I am sorry, I forgot to mention that we had deployed one composite app today morning. So, the jbi file is the correct file, just that it shows the assembly that we deployed today.

Thanks
Neel

Nikita Sawant wrote:

Hi Neel,

The jbi-registry.xml  in the jbi/config folder you provided is different
than the one you provided earlier (
http://www.nabble.com/file/p18214355/jbi-registry.xml ).

The one in jbi/config shows a service assembly "XDSBDocumentRetrieveCA"
deployed to the HTTP BC and BPEL SE on the server instance. While the
one you provided earlier does not have any service assemblies.

Which one is the correct one ?

~ Nikita

learnopenesb wrote:
> Nikita,
>
> Attached is the zip of the ${DOMAIN}/jbi/config folder.
> http://www.nabble.com/file/p18222381/config.zip config.zip
>
>
>
> Nikita Sawant wrote:
>  
>> Hi Neel,
>>
>> The empty contents of the service-assemblies folder and the empty
>> jbi-registry.xml indicate that the service assembly has either been
>> undeployed or removed.
>>
>> A service assembly is removed from both the registry and repository (
>> the service-assemblies folder ) when :
>>
>>    1. You undeploy it
>>    2. You accidentally delete it from one of the two, then the other is
>>       cleaned up by the runtime automatically. i.e. if you accidentlly
>>       deleted the contents of the service-assemblies folder then the
>>       service-assembly is deleted from the registry and vice versa.
>>
>> If the case were (2) then there is a message in the server.log
>> indicating so, which I do not see.
>>
>> So I don't know what went wrong in your case. Could you zip the  
>> ${DOMAIN}/jbi/config folder, I want to see if there were any issues with
>> persisting information to the registry.
>>
>> To get back on track you need to deploy the composite applications again.
>>
>> Regards,
>> Nikita
>>
>> learnopenesb wrote:
>>    
>>> Nikita,
>>>
>>> The servcies assemblies folder is empty and that is really surprising!. I
>>> have attached the jbi-registry.xml
>>> We do NOT have a cluster setup.
>>>
>>> The other question though is how do we get back on track?
>>>
>>> Thanks
>>> Neel
>>> http://www.nabble.com/file/p18214355/jbi-registry.xml jbi-registry.xml
>>>
>>>
>>> Nikita Sawant wrote:
>>>  
>>>      
>>>> Hi Neel,
>>>>
>>>> Can you send me a listing of the contents of the service assembly folder
>>>> : ${DOMAIN}/jbi/service-assemblies and attach the jbi-registry.xml too.
>>>>
>>>> Do you have a cluster setup or are you deploying to a single server
>>>> instance ?
>>>>
>>>> Regards,
>>>> Nikita
>>>>
>>>> learnopenesb wrote:
>>>>    
>>>>        
>>>>> Nikita,
>>>>>
>>>>> We already had assemblies deployed onto the server and were working
>>>>> fine.
>>>>> The server log has entries starting yesterday and we know for sure
>>>>> things
>>>>> were working fine till today AM.
>>>>>
>>>>> As with the sequence of events that happened,
>>>>> 1) we had deployed few composite apps today AM (the composite apps is
>>>>> that
>>>>> they were generated/built using netbeans build 200806161120).
>>>>> 2) At around 1pm today we noticed that one of our already deployed
>>>>> service
>>>>> (ejb web service) was not responding due to connection pool max. out
>>>>> errors.
>>>>> We fixed that service and redeployed it and restarted the server. The
>>>>> service then started functioning as desired.
>>>>> 3) Later-on we observed that all our service assemblies are missing!
>>>>>
>>>>> We really are not sure what could have caused this and were hoping the
>>>>> log
>>>>> would provide more details.
>>>>> One suspect is the deployment of CA from netbeans build 200806161120 to
>>>>> Glassfish server 20080515 but we are not sure.
>>>>>
>>>>> Let me know if you need any further information.
>>>>>
>>>>> Thanks
>>>>> Neel
>>>>>
>>>>>
>>>>> Nikita Sawant wrote:
>>>>>  
>>>>>      
>>>>>          
>>>>>> Hi Neel,
>>>>>>
>>>>>> The server.log does not have any information regarding service
>>>>>> assemblies being deployed/ to the runtime, the attached log seems to
>>>>>> have the later half of your setup.
>>>>>>
>>>>>> Did you deploy service assemblies and then restart the server
>>>>>> immediately ? What exact sequence of steps did you follow ?
>>>>>>
>>>>>> ~ Nikita
>>>>>>
>>>>>> learnopenesb wrote:
>>>>>>    
>>>>>>        
>>>>>>            
>>>>>>> Hi,
>>>>>>>
>>>>>>> We are using openesb 20080515 build and for some reason after the
>>>>>>> server
>>>>>>> restart the service assemblies don't show up at all. We have checked
>>>>>>> the
>>>>>>> jbi-registry.xml and it does not have any assemblies in there!
>>>>>>>
>>>>>>> We are not sure what could have caused this issue? Any pointers?
>>>>>>> http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
>>>>>>> Copy+of+server_Log+063008.zip
>>>>>>>
>>>>>>> server.log is attached for reference.
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>> Neel
>>>>>>>  
>>>>>>>      
>>>>>>>          
>>>>>>>              
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [e-mail]
>>>>>> For additional commands, e-mail: [e-mail]
>>>>>>
>>>>>>
>>>>>>
>>>>>>    
>>>>>>        
>>>>>>            
>>>>>  
>>>>>      
>>>>>          
>>>>    
>>>>        
>>>  
>>>      
>>
>>    
>
>  

[Nikita Sawant]

Hi Neel,

I don't have any leads to work on right now.

Have you tried deploying the service assemblies which were deleted ? Did the vanishing service assemblies behavior recur ?

Regards,
Nikita

learnopenesb wrote:

Nikita,

I am sorry, I forgot to mention that we had deployed one composite app today
morning. So, the jbi file is the correct file, just that it shows the
assembly that we deployed today.

Thanks
Neel

Nikita Sawant wrote:
  

Hi Neel,

The jbi-registry.xml  in the jbi/config folder you provided is different 
than the one you provided earlier ( 
http://www.nabble.com/file/p18214355/jbi-registry.xml ).

The one in jbi/config shows a service assembly "XDSBDocumentRetrieveCA" 
deployed to the HTTP BC and BPEL SE on the server instance. While the 
one you provided earlier does not have any service assemblies.

Which one is the correct one ?

~ Nikita

learnopenesb wrote:
    

Nikita,

Attached is the zip of the ${DOMAIN}/jbi/config folder.
http://www.nabble.com/file/p18222381/config.zip config.zip 



Nikita Sawant wrote:
  
      

Hi Neel,

The empty contents of the service-assemblies folder and the empty 
jbi-registry.xml indicate that the service assembly has either been 
undeployed or removed.

A service assembly is removed from both the registry and repository ( 
the service-assemblies folder ) when :

   1. You undeploy it
   2. You accidentally delete it from one of the two, then the other is
      cleaned up by the runtime automatically. i.e. if you accidentlly
      deleted the contents of the service-assemblies folder then the
      service-assembly is deleted from the registry and vice versa.

If the case were (2) then there is a message in the server.log 
indicating so, which I do not see.

So I don't know what went wrong in your case. Could you zip the  
${DOMAIN}/jbi/config folder, I want to see if there were any issues with 
persisting information to the registry.

To get back on track you need to deploy the composite applications
again.

Regards,
Nikita

learnopenesb wrote:
    
        

Nikita,

The servcies assemblies folder is empty and that is really surprising!.
I
have attached the jbi-registry.xml
We do NOT have a cluster setup.

The other question though is how do we get back on track?

Thanks
Neel
http://www.nabble.com/file/p18214355/jbi-registry.xml jbi-registry.xml 


Nikita Sawant wrote:
  
      
          

Hi Neel,

Can you send me a listing of the contents of the service assembly
folder 
: ${DOMAIN}/jbi/service-assemblies and attach the jbi-registry.xml
too.

Do you have a cluster setup or are you deploying to a single server 
instance ?

Regards,
Nikita

learnopenesb wrote:
    
        
            

Nikita,

We already had assemblies deployed onto the server and were working
fine.
The server log has entries starting yesterday and we know for sure
things
were working fine till today AM.

As with the sequence of events that happened, 
1) we had deployed few composite apps today AM (the composite apps is
that
they were generated/built using netbeans build 200806161120). 
2) At around 1pm today we noticed that one of our already deployed
service
(ejb web service) was not responding due to connection pool max. out
errors.
We fixed that service and redeployed it and restarted the server. The
service then started functioning as desired.
3) Later-on we observed that all our service assemblies are missing!

We really are not sure what could have caused this and were hoping
the
log
would provide more details. 
One suspect is the deployment of CA from netbeans build 200806161120
to
Glassfish server 20080515 but we are not sure.

Let me know if you need any further information.

Thanks
Neel


Nikita Sawant wrote:
  
      
          
              

Hi Neel,

The server.log does not have any information regarding service 
assemblies being deployed/ to the runtime, the attached log seems to 
have the later half of your setup. 

Did you deploy service assemblies and then restart the server 
immediately ? What exact sequence of steps did you follow ?

~ Nikita

learnopenesb wrote:
    
        
            
                

Hi,

We are using openesb 20080515 build and for some reason after the
server
restart the service assemblies don't show up at all. We have
checked
the
jbi-registry.xml and it does not have any assemblies in there!

We are not sure what could have caused this issue? Any pointers?
http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
Copy+of+server_Log+063008.zip 

server.log is attached for reference.


Thanks
Neel
  
      
          
              
                  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...



    
        
            
                

[learnopenesb]

Yes we have deployed the service assemblies again and we haven't seen them vanishing.

Is there anything that we can setup that can help us to do the root cause analysis if the behavior recurs?

Thanks
Neel

Nikita Sawant wrote:

Hi Neel,

I don't have any leads to work on right now.

Have you tried deploying the service assemblies which were deleted ? Did
the vanishing service assemblies behavior recur ?

Regards,
Nikita

learnopenesb wrote:
> Nikita,
>
> I am sorry, I forgot to mention that we had deployed one composite app today
> morning. So, the jbi file is the correct file, just that it shows the
> assembly that we deployed today.
>
> Thanks
> Neel
>
> Nikita Sawant wrote:
>  
>> Hi Neel,
>>
>> The jbi-registry.xml  in the jbi/config folder you provided is different
>> than the one you provided earlier (
>> http://www.nabble.com/file/p18214355/jbi-registry.xml ).
>>
>> The one in jbi/config shows a service assembly "XDSBDocumentRetrieveCA"
>> deployed to the HTTP BC and BPEL SE on the server instance. While the
>> one you provided earlier does not have any service assemblies.
>>
>> Which one is the correct one ?
>>
>> ~ Nikita
>>
>> learnopenesb wrote:
>>    
>>> Nikita,
>>>
>>> Attached is the zip of the ${DOMAIN}/jbi/config folder.
>>> http://www.nabble.com/file/p18222381/config.zip config.zip
>>>
>>>
>>>
>>> Nikita Sawant wrote:
>>>  
>>>      
>>>> Hi Neel,
>>>>
>>>> The empty contents of the service-assemblies folder and the empty
>>>> jbi-registry.xml indicate that the service assembly has either been
>>>> undeployed or removed.
>>>>
>>>> A service assembly is removed from both the registry and repository (
>>>> the service-assemblies folder ) when :
>>>>
>>>>    1. You undeploy it
>>>>    2. You accidentally delete it from one of the two, then the other is
>>>>       cleaned up by the runtime automatically. i.e. if you accidentlly
>>>>       deleted the contents of the service-assemblies folder then the
>>>>       service-assembly is deleted from the registry and vice versa.
>>>>
>>>> If the case were (2) then there is a message in the server.log
>>>> indicating so, which I do not see.
>>>>
>>>> So I don't know what went wrong in your case. Could you zip the  
>>>> ${DOMAIN}/jbi/config folder, I want to see if there were any issues with
>>>> persisting information to the registry.
>>>>
>>>> To get back on track you need to deploy the composite applications
>>>> again.
>>>>
>>>> Regards,
>>>> Nikita
>>>>
>>>> learnopenesb wrote:
>>>>    
>>>>        
>>>>> Nikita,
>>>>>
>>>>> The servcies assemblies folder is empty and that is really surprising!.
>>>>> I
>>>>> have attached the jbi-registry.xml
>>>>> We do NOT have a cluster setup.
>>>>>
>>>>> The other question though is how do we get back on track?
>>>>>
>>>>> Thanks
>>>>> Neel
>>>>> http://www.nabble.com/file/p18214355/jbi-registry.xml jbi-registry.xml
>>>>>
>>>>>
>>>>> Nikita Sawant wrote:
>>>>>  
>>>>>      
>>>>>          
>>>>>> Hi Neel,
>>>>>>
>>>>>> Can you send me a listing of the contents of the service assembly
>>>>>> folder
>>>>>> : ${DOMAIN}/jbi/service-assemblies and attach the jbi-registry.xml
>>>>>> too.
>>>>>>
>>>>>> Do you have a cluster setup or are you deploying to a single server
>>>>>> instance ?
>>>>>>
>>>>>> Regards,
>>>>>> Nikita
>>>>>>
>>>>>> learnopenesb wrote:
>>>>>>    
>>>>>>        
>>>>>>            
>>>>>>> Nikita,
>>>>>>>
>>>>>>> We already had assemblies deployed onto the server and were working
>>>>>>> fine.
>>>>>>> The server log has entries starting yesterday and we know for sure
>>>>>>> things
>>>>>>> were working fine till today AM.
>>>>>>>
>>>>>>> As with the sequence of events that happened,
>>>>>>> 1) we had deployed few composite apps today AM (the composite apps is
>>>>>>> that
>>>>>>> they were generated/built using netbeans build 200806161120).
>>>>>>> 2) At around 1pm today we noticed that one of our already deployed
>>>>>>> service
>>>>>>> (ejb web service) was not responding due to connection pool max. out
>>>>>>> errors.
>>>>>>> We fixed that service and redeployed it and restarted the server. The
>>>>>>> service then started functioning as desired.
>>>>>>> 3) Later-on we observed that all our service assemblies are missing!
>>>>>>>
>>>>>>> We really are not sure what could have caused this and were hoping
>>>>>>> the
>>>>>>> log
>>>>>>> would provide more details.
>>>>>>> One suspect is the deployment of CA from netbeans build 200806161120
>>>>>>> to
>>>>>>> Glassfish server 20080515 but we are not sure.
>>>>>>>
>>>>>>> Let me know if you need any further information.
>>>>>>>
>>>>>>> Thanks
>>>>>>> Neel
>>>>>>>
>>>>>>>
>>>>>>> Nikita Sawant wrote:
>>>>>>>  
>>>>>>>      
>>>>>>>          
>>>>>>>              
>>>>>>>> Hi Neel,
>>>>>>>>
>>>>>>>> The server.log does not have any information regarding service
>>>>>>>> assemblies being deployed/ to the runtime, the attached log seems to
>>>>>>>> have the later half of your setup.
>>>>>>>>
>>>>>>>> Did you deploy service assemblies and then restart the server
>>>>>>>> immediately ? What exact sequence of steps did you follow ?
>>>>>>>>
>>>>>>>> ~ Nikita
>>>>>>>>
>>>>>>>> learnopenesb wrote:
>>>>>>>>    
>>>>>>>>        
>>>>>>>>            
>>>>>>>>                
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> We are using openesb 20080515 build and for some reason after the
>>>>>>>>> server
>>>>>>>>> restart the service assemblies don't show up at all. We have
>>>>>>>>> checked
>>>>>>>>> the
>>>>>>>>> jbi-registry.xml and it does not have any assemblies in there!
>>>>>>>>>
>>>>>>>>> We are not sure what could have caused this issue? Any pointers?
>>>>>>>>> http://www.nabble.com/file/p18205851/Copy%2Bof%2Bserver_Log%2B063008.zip
>>>>>>>>> Copy+of+server_Log+063008.zip
>>>>>>>>>
>>>>>>>>> server.log is attached for reference.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Neel
>>>>>>>>>  
>>>>>>>>>      
>>>>>>>>>          
>>>>>>>>>              
>>>>>>>>>                  
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: [e-mail]
>>>>>>>> For additional commands, e-mail: [e-mail]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>    
>>>>>>>>        
>>>>>>>>            
>>>>>>>>                
>>>>>>>  
>>>>>>>      
>>>>>>>          
>>>>>>>              
>>>>>>    
>>>>>>        
>>>>>>            
>>>>>  
>>>>>      
>>>>>          
>>>>    
>>>>        
>>>  
>>>      
>>
>>    
>
>  

[learnopenesb]

Nikita,

It issue just resurfaced. All I did was I deployed one CA onto the glassfish server and it somehow made all existing CAs vanish.

We had to redeploy our CAs back in there but I have attached my CA (testAdhocQueryCA), the config directory and  the server.log.

This should be helpful for the root cause analysis.

Note that my netbeans IDE version is Build 200806161120 and my glassfish version is glassfish-v2-ur2-b04-patch-20080515.


server.log

config.zip

testAdhocQueryCA.zip

Please let me know if you need any further information. I believe it has got something to do with compatibility of netbeans / glassfish versions but I am not totally convinced.


Thanks
Neel



Yes we have deployed the service assemblies again and we haven't seen them vanishing.

Is there anything that we can setup that can help us to do the root cause analysis if the behavior recurs?

Thanks
Neel

Nikita Sawant wrote:

Hi Neel,

I don't have any leads to work on right now.

Have you tried deploying the service assemblies which were deleted ? Did
the vanishing service assemblies behavior recur ?

Regards,
Nikita

learnopenesb wrote:
> Nikita,
>
> I am sorry, I forgot to mention that we had deployed one composite app today
> morning. So, the jbi file is the correct file, just that it shows the
> assembly that we deployed today.
>
> Thanks
> Neel
>
> Nikita Sawant wrote:
>  
>> Hi Neel,
>>
>> The jbi-registry.xml  in the jbi/config folder you provided is different
>> than the one you provided earlier (
>> http://www.nabble.com/file/p18214355/jbi-registry.xml ).
>>
>> The one in jbi/config shows a service assembly "XDSBDocumentRetrieveCA"
>> deployed to the HTTP BC and BPEL SE on the server instance. While the
>> one you provided earlier does not have any service assemblies.
>>
>> Which one is the correct one ?
>>
>> ~ Nikita
>>
>> learnopenesb wrote:
>>    
>>> Nikita,
>>>
>>> Attached is the zip of the ${DOMAIN}/jbi/config folder.
>>> http://www.nabble.com/file/p18222381/config.zip config.zip
>>>
>>>
>>>
>>> Nikita Sawant wrote:
>>>  
>>>      
>>>> Hi Neel,
>>>>
>>>> The empty contents of the service-assemblies folder and the empty
>>>> jbi-registry.xml indicate that the service assembly has either been
>>>> undeployed or removed.
>>>>
>>>> A service assembly is removed from both the registry and repository (
>>>> the service-assemblies folder ) when :
>>>>
>>>>    1. You undeploy it
>>>>    2. You accidentally delete it from one of the two, then the other is
>>>>       cleaned up by the runtime automatically. i.e. if you accidentl