June 2009 - jboss-user - Jboss List Archives

[JCA/JBoss] - Re: Changinh connection state in CMP EJB

by vickyk

The required changes are attached here https://jira.jboss.org/jira/browse/JBAS-1429 The reauthenitication mechanism with jdbc ra will work when 1) <reauthentication-support> tag is enabled in ra.xml at jboss-local-jdbc.rar/META-INF/ra.xml AND jboss-xa-jdbc.rar/META-INF/ra.xml AND 2) The -ds.xml corresponding to the local-tx-datasource AND xa-datasource would have <reauthentication-mechanism> pointing to the appropriate reauthentication mechanism implementation. Missing of any of the configuration would cause *misbehavior* of the JCA pooling mechanism. We should have a way to pass the reatuthentication details to the MCF e.g mcf.setReauthenticationTrue(true); Should we not have reauthentication related API as a part of the MCF ? For other RA's to support re-authentication what they need is 1) Enable the <reauthentication-support> in the vendor-specificRA.rar/META-INF/ra.xml AND 2) provide connection-property for CF which will tell the MCF to use the reauthentication. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237580#4237580 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237580

17 years, 1 month

1
0
0 / 0

[JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

by kennardconsulting

destinations-service.xml: <?xml version="1.0" encoding="UTF-8"?> | |  | | <server> | |  | | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=DLQ" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | |  | | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=ExpiryQueue" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=emails" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <attribute name="JNDIName">avant-ss/emails</attribute> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=imports1" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <attribute name="JNDIName">avant-ss/imports1</attribute> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=imports2" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <attribute name="JNDIName">avant-ss/imports2</attribute> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=reports1" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <attribute name="JNDIName">avant-ss/reports1</attribute> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=reports2" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <attribute name="JNDIName">avant-ss/reports2</attribute> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | </mbean> | </server> Stack trace (for one of the queues): 18:31:23,437 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=avant-ss-app.ear,jar=avant-ss-ejb.jar,name=ReportBean,service=EJB3 | 18:31:23,437 INFO [EJBContainer] STARTED EJB: com.avant.ss.ejb.session.report.ReportBean ejbName: ReportBean | 18:31:23,437 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI: | | | 18:31:23,437 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1030063(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)e0863a destination=queue/avant-ss/imports1 destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=3 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) | javax.naming.NameNotFoundException: avant-ss not bound | at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) | at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) | at org.jnp.server.NamingServer.getObject(NamingServer.java:785) | at org.jnp.server.NamingServer.lookup(NamingServer.java:396) | at org.jnp.server.NamingServer.lookup(NamingServer.java:399) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) | at javax.naming.InitialContext.lookup(InitialContext.java:392) | at org.jboss.util.naming.Util.lookup(Util.java:222) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352) | at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) | at java.lang.Thread.run(Thread.java:619) | 18:31:23,437 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=avant-ss-app.ear,jar=avant-ss-ejb.jar,name=CalculationVariablesBean,service=EJB3 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237579#4237579 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237579

17 years, 1 month

1
0
0 / 0

[JNDI/Naming/Network] - Re: Migrating 4.2.3.GA to 5.1.0.GA - JNDI missing?

by kennardconsulting

It is not present anywhere else, or reference in any MANIFEST files, sorry. But note it is not a JAR file either: it is an exploded folder named '.jar'. This is okay in 4.2.3.GA - is it still okay in 5.1.0.GA? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237577#4237577 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237577

17 years, 1 month

1
0
0 / 0

[JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

by jaikiran

Can you please post the entire configuration file which gives this error and also the entire exception stacktrace? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237574#4237574 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237574

17 years, 1 month

1
0
0 / 0

[JNDI/Naming/Network] - Re: Migrating 4.2.3.GA to 5.1.0.GA - JNDI missing?

by jaikiran

Everything looks right. This log is suspicious though: anonymous wrote : 2009-06-15 13:03:31,687 WARN [org.jboss.ejb3.Ejb3AnnotationHandler] (main) JBMETA-4: did not find any bean meta data for annotation bean DocumentBean, will create some | This usually happens when the EJB (jar) is being picked up from some lib folder of the deployment or the MANIFEST.MF of the jars and is considered as an "library" instead of a "deployment". Can you just double check that this jar file is not present in any other location within your AS? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237571#4237571 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237571

17 years, 1 month

1
0
0 / 0

[JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

by kennardconsulting

gaohoward, Thank you for your quick reply. Unfortunately using JNDIName gives the same error ('app' not bound). It's probably fair to say that app isn't bound, but I was kind of hoping JBoss Messaging would create it automatically (like JBoss MQ did). Regards, Richard. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237568#4237568 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237568

17 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: beginner question for the jbpm evalutaion (performance a

by jbarrez

Adding more executor threads will only help when there is a bottleneck in the asynchronous continuations, not in regular business process execution. But tweaking Hibernate for your needs is generally an excellent idea. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237567#4237567 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237567

17 years, 1 month

1
0
0 / 0

[JNDI/Naming/Network] - Re: Migrating 4.2.3.GA to 5.1.0.GA - JNDI missing?

by kennardconsulting

jaikiran, Apologies. My deployment is exploded, so avant-ss-ejb.jar is a folder at: N:\jboss-5.1.0.GA\server\all\deploy\avant-ss-app.ear\avant-ss-ejb.jar\ No, avant-ss-ejb.jar is not mentioned in any MANIFEST.MF. Only in application.xml: <?xml version="1.0" encoding="UTF-8"?> | <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"> | | <display-name>Avant SS</display-name> | | <module id="avant-ss-ejb.jar"> | <ejb>avant-ss-ejb.jar</ejb> | </module> | | <module id="avant-ss-web.war"> | <web> | <web-uri>avant-ss-web.war</web-uri> | <context-root>/avant-ss</context-root> | </web> | </module> | | </application> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237566#4237566 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237566

17 years, 1 month

1
0
0 / 0

[JNDI/Naming/Network] - Re: Migrating 4.2.3.GA to 5.1.0.GA - JNDI missing?

by jaikiran

The important part: "jaikiran" wrote : | | Where is the avant-ss-ejb.jar located in the avant-ss-app.ear? Also do you list avant-ss-ejb.jar in any MANIFEST.MF files of the jars? If yes, remove it from those MANIFEST.MF files View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237564#4237564 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237564

17 years, 1 month

1
0
0 / 0

[JNDI/Naming/Network] - Re: Migrating 4.2.3.GA to 5.1.0.GA - JNDI missing?

by kennardconsulting

jaikiran, Thanks again for being so helpful. Again there is rather a lot of code involved. I will try to post the relevant bits: package com.avant.ss.ejb.session; | | import java.io.File; | | import javax.ejb.Stateful; | | import com.avant.ss.ejb.entity.Document; | import com.kennardconsulting.core.ejb.session.DiskFileBean; | import com.kennardconsulting.core.ejb.session.isession.IDiskFileBean; | import com.kennardconsulting.core.util.EjbUtils; | | @Stateful | public class DocumentBean | extends DiskFileBean<Document> | implements IDiskFileBean<Document> | { | ...lots of code... | package com.kennardconsulting.core.ejb.session.isession; | | import java.io.InputStream; | import java.util.List; | | import com.kennardconsulting.core.ejb.entity.DiskFile; | import com.kennardconsulting.core.simpletype.ListState; | | public interface IDiskFileBean<DF extends DiskFile> | extends IBaseSessionBean | { | ...code... | There is nothing related to DocumentBean in either jboss.xml or ejb-jar.xml. Regards, Richard. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237563#4237563 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237563

17 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2009