I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.


[** jboss.xml starts here **]

<?xml version="1.0" encoding="UTF-8"?>
<!--
We want to confirm that these session beans are removed before
session beans under them are removed.
-->

<enterprise-beans>

<ejb-name>Robocop/repository/RepositoryManagement</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>


<ejb-name>Robocop/repository/Repository</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>

</enterprise-beans>

<container-configurations>
<container-configuration extends = "Standard Stateless SessionBean">
<container-name>Shortlived Stateless SessionBean</container-name>
<container-cache-conf>
<cache-policy-conf>
<overager-period>120</overager-period>
<max-bean-age>120</max-bean-age>
</cache-policy-conf>
</container-cache-conf>
</container-configuration>
</container-configurations>

I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.


[** jboss.xml starts here **]

<?xml version="1.0" encoding="UTF-8"?>
<!--
We want to confirm that these session beans are removed before
session beans under them are removed.
-->

<enterprise-beans>

<ejb-name>Robocop/repository/RepositoryManagement</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>


<ejb-name>Robocop/repository/Repository</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>

</enterprise-beans>

<container-configurations>
<container-configuration extends = "Standard Stateless SessionBean">
<container-name>Shortlived Stateless SessionBean</container-name>
<container-cache-conf>
<cache-policy-conf>
<overager-period>120</overager-period>
<max-bean-age>120</max-bean-age>
</cache-policy-conf>
</container-cache-conf>
</container-configuration>
</container-configurations>

I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.


[** jboss.xml starts here **]

<?xml version="1.0" encoding="UTF-8"?>
<!--
We want to confirm that these session beans are removed before
session beans under them are removed.
-->

<enterprise-beans>

<ejb-name>Robocop/repository/RepositoryManagement</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>


<ejb-name>Robocop/repository/Repository</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>

</enterprise-beans>

<container-configurations>
<container-configuration extends = "Standard Stateless SessionBean">
<container-name>Shortlived Stateless SessionBean</container-name>
<container-cache-conf>
<cache-policy-conf>
<overager-period>120</overager-period>
<max-bean-age>120</max-bean-age>
</cache-policy-conf>
</container-cache-conf>
</container-configuration>
</container-configurations>

I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.


[** jboss.xml starts here **]

<?xml version="1.0" encoding="UTF-8"?>
<!--
We want to confirm that these session beans are removed before
session beans under them are removed.
-->

<enterprise-beans>

<ejb-name>Robocop/repository/RepositoryManagement</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>


<ejb-name>Robocop/repository/Repository</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>

</enterprise-beans>

<container-configurations>
<container-configuration extends = "Standard Stateless SessionBean">
<container-name>Shortlived Stateless SessionBean</container-name>
<container-cache-conf>
<cache-policy-conf>
<overager-period>120</overager-period>
<max-bean-age>120</max-bean-age>
</cache-policy-conf>
</container-cache-conf>
</container-configuration>
</container-configurations>

I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.


[** jboss.xml starts here **]

<?xml version="1.0" encoding="UTF-8"?>
<!--
We want to confirm that these session beans are removed before
session beans under them are removed.
-->

<enterprise-beans>

<ejb-name>Robocop/repository/RepositoryManagement</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>


<ejb-name>Robocop/repository/Repository</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>

</enterprise-beans>

<container-configurations>
<container-configuration extends = "Standard Stateless SessionBean">
<container-name>Shortlived Stateless SessionBean</container-name>
<container-cache-conf>
<cache-policy-conf>
<overager-period>120</overager-period>
<max-bean-age>120</max-bean-age>
</cache-policy-conf>
</container-cache-conf>
</container-configuration>
</container-configurations>

I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.

I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.


[** jboss.xml starts here **]

<?xml version="1.0" encoding="UTF-8"?>
<!--
We want to confirm that these session beans are removed before
session beans under them are removed.
-->

<enterprise-beans>

<ejb-name>Robocop/repository/RepositoryManagement</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>


<ejb-name>Robocop/repository/Repository</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>

</enterprise-beans>

<container-configurations>
<container-configuration extends = "Standard Stateless SessionBean">
<container-name>Shortlived Stateless SessionBean</container-name>
<container-cache-conf>
<cache-policy-conf>
<overager-period>120</overager-period>
<max-bean-age>120</max-bean-age>
</cache-policy-conf>
</container-cache-conf>
</container-configuration>
</container-configurations>

I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.


[** jboss.xml starts here **]

<?xml version="1.0" encoding="UTF-8"?>
<!--
We want to confirm that these session beans are removed before
session beans under them are removed.
-->

<enterprise-beans>

<ejb-name>Robocop/repository/RepositoryManagement</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>


<ejb-name>Robocop/repository/Repository</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>

</enterprise-beans>

<container-configurations>
<container-configuration extends = "Standard Stateless SessionBean">
<container-name>Shortlived Stateless SessionBean</container-name>
<container-cache-conf>
<cache-policy-conf>
<overager-period>120</overager-period>
<max-bean-age>120</max-bean-age>
</cache-policy-conf>
</container-cache-conf>
</container-configuration>
</container-configurations>

I can't make attach work so I just paste jboss.xml to end of this message.

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.


[** jboss.xml starts here **]

<?xml version="1.0" encoding="UTF-8"?>
<!--
We want to confirm that these session beans are removed before
session beans under them are removed.
-->

<enterprise-beans>

<ejb-name>Robocop/repository/RepositoryManagement</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>


<ejb-name>Robocop/repository/Repository</ejb-name>
<configuration-name>Shortlived Stateless SessionBean</configuration-name>

</enterprise-beans>

<container-configurations>
<container-configuration extends = "Standard Stateless SessionBean">
<container-name>Shortlived Stateless SessionBean</container-name>
<container-cache-conf>
<cache-policy-conf>
<overager-period>120</overager-period>
<max-bean-age>120</max-bean-age>
</cache-policy-conf>
</container-cache-conf>
</container-configuration>
</container-configurations>

Case is that I have session bean that is used to save/load data. In create you give selection rule that is used to filter what is shown.

New stateless session bean is done because access to our repository is done through webservices and so they do not need their own state.

But because I don't want to redo everything I just get that old stateful bean and use it with correct selection rule (same for all in current system).

Problem is that when no-one calls our webservices stateful beans are first moved to disk and then finally removed, and stateless beans above them are not removed. So when next time someone calls our webservices we have stateless bean without underlying data connection because cached bean was removed from disk.

I tried to set max-bean-age to stateless beans so they would be removed in shorter time it takes stateful beans to be totally removed. Looking from "JBoss 3.0 Deployment and Administration Handbook" it would seem that you can set that data for stateless beans, max-bean-life and remover-period are mentioned as stateful only.

Perhaps I could set stateful beans max-bean-life to new value so they would never be removed, but I think it is not that good idea.

It seems that I can't reply to this forum ...well testing once more with shorter post :)