[JCA/JBoss] - JCA close/destroy
by chavali
We have a requirement to maintain the session with the legacy system and the client. We want to persist the same connection for multiple requests from client. Upon clients logoff the legacy system to be notified may be by calling destroy instead of close. Upon the notification to (EIS)legacy system, the legacy system will processing and do some cleanup.
I donot know with the connection pooling will the destroy close the physical connection with the EIS legacy system.
Calling the destroy() instead of close() in JCA will the physical connection gets closed with the legacy system?
Will the EIS (legacy system) socket desc gets closed by calling the destroy().
Can some body help in this regard.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132121#4132121
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132121
16 years, 8 months
[JBoss Messaging] - Re: Error running in performance messaging benchmark framewo
by singhal_ashwani
In the statck trace , it is trying to connect "localhost:7777/local-messaging"
[java] java.rmi.NotBoundException: localhost:7777/local-messaging
The perf.xml is below
<!-- benchmark configuration -->
<db-url>jdbc:hsqldb:./output/db/perfdb</db-url>
<report-directory>./output/results</report-directory>
<color-step>15</color-step>
<!-- benchmark-wide test defaults -->
<default-executor-name>REMOTE</default-executor-name>
/queue/testQueue
<connection-factory>/ConnectionFactory</connection-factory>
<acknowledgment-mode>AUTO_ACKNOWLEDGE</acknowledgment-mode>
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-factory-class>org.jboss.jms.perf.framework.factories.MessageMessageFactory</message-factory-class>
<message-size>0</message-size>
<!-- safeguard for receive jobs that block waiting messages will never arrive -->
600000
org.jnp.interfaces.NamingContextFactory
jnp://localhost:1099
org.jboss.naming:org.jnp.interfaces
<!--
-->
255,0,0
org.jnp.interfaces.NamingContextFactory
jnp://localhost:1199
org.jboss.naming:org.jnp.interfaces
0,0, 255
org.apache.activemq.jndi.ActiveMQInitialContextFactory
tcp://localhost:61616
<jndi-property name="queue./queue/testQueue">TEST_QUEUE</jndi-property>
<jndi-property name="queue./queue/simpleQueue">SIMPLE_QUEUE</jndi-property>
<jndi-property name="connectionFactoryNames">/ConnectionFactory</jndi-property>
0, 255, 255
org.apache.qpid.jndi.PropertiesFileInitialContextFactory
<jndi-property name="connectionfactory./ConnectionFactory">amqp://guest:guest@/test?brokerlist='localhost'</jndi-property>
<jndi-property name="queue./queue/testQueue">testQueue</jndi-property>
<jndi-property name="queue./queue/simpleQueue">simpleQueue</jndi-property>
255, 0, 255
<performance-tests>
<!-- just makes sure the executors are deployed and ready -->
<!-- -->
<performance-test name="Ping" loops="1">
<!--
-->
<!--
-->
<!-- -->
</performance-test>
<!-- -->
<!-- -->
<performance-test name="Ping Remote Only" loops="1">
</performance-test>
<!-- -->
<!--
<performance-test name="Single Burst" loops="10">
/queue/simpleQueue
<message-size>0</message-size>
30000
</performance-test>
-->
<!--
<performance-test name="Throughput O KB Message Non-Persistent Non-Transactional, 1 sender, 1 receiver">
<message-size>0</message-size>
10000
</performance-test>
-->
<!--
<performance-test name="Throughput-Remote">
/queue/simpleQueue
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-size>0</message-size>
30000
</performance-test>
-->
<!--
<performance-test name="Throughput-INVM">
/queue/simpleQueue
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-size>0</message-size>
30000
</performance-test>
-->
<!--
<performance-test name="Measured Send Rate vs. Intended Send Rate INVM">
/queue/simpleQueue
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-size>0</message-size>
50000
</performance-test>
-->
<!--
<performance-test name="Measured Send Rate vs. Intended Send Rate Remote">
/queue/simpleQueue
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-size>0</message-size>
50000
</performance-test>
-->
<!--
<performance-test name="Send 50000 Non-Persistent Non-Transactional 0 KB Local">
/queue/simpleQueue
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-size>0</message-size>
50000
</performance-test>
-->
<!--
<performance-test name="Send 20000 Non-Persistent Non-Transactional 1 KB Text Local" loops="3">
/queue/simpleQueue
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-factory-class>org.jboss.jms.perf.framework.factories.TextMessageFactory</message-factory-class>
<message-size>1024</message-size>
30000
</performance-test>
-->
<!--
<performance-test name="Send 30000 Non-Persistent Non-Transactional 0 KB Remote">
/queue/simpleQueue
<delivery-mode>NON_PERSISTENT</delivery-mode>
<message-size>0</message-size>
30000
</performance-test>
-->
<!--
<performance-test name="Send 30000 Persistent Non-Transactional 0 KB Local">
/queue/simpleQueue
<delivery-mode>PERSISTENT</delivery-mode>
<message-size>0</message-size>
30000
</performance-test>
-->
<!--
<performance-test name="Send 30000 Persistent Non-Transactional 1 KB Text Remote">
/queue/simpleQueue
<delivery-mode>PERSISTENT</delivery-mode>
<message-factory-class>org.jboss.jms.perf.framework.factories.TextMessageFactory</message-factory-class>
<message-size>1024</message-size>
30000
</performance-test>
-->
</performance-tests>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132114#4132114
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132114
16 years, 8 months
[Security & JAAS/JBoss] - JAAS Authentification with wrong role
by forfaro
Hi,
I have build a JBoss authentification, using FORM based Login, in version 4.0.4GA.
The login works great, when wrong login data is entered I am lead to the error page, when logging in with the right user, I come to the right page. The only thing is, when I login with an user with correct login data, but with the wrong role, I get the system error message saying "Access to the requested resource has been denied" and am not lead to the error page.
Is this a known problem ? At the moment I use
| <login-config>
| <auth-method>FORM</auth-method>
| <form-login-config>
| <form-login-page>/login.html</form-login-page>
| <form-error-page>/error.html</form-error-page>
| </form-login-config>
| </login-config>
|
Am I missing a third page or how can I catch a user with wrong role to show a correct error page ?
Greets
Sascha
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132104#4132104
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132104
16 years, 8 months