[EJB 3.0] - MDB w/Tibco Queue only Works with ActivationConfig Settings
by ptfromseismic
I hope someone has figured this out. We are running JBoss 4.2.2. We have a simple MDB being driven off a Tibco EMS Queue. I got this to work (after many failed attempts) by configuring an ExternalContext and a JMSProviderLoader. This works only if I have all of the connection info (user, password, URL, etc.) in the Properties for the ExternalContext (no problem) AND ALSO in the ActivationConfig annotations for the MDB (problem!).
Basically, we need this info to be configurable at deployment time so we have to find a way to take it out of the MDB annotations (or override them).
We tried putting the same info (user, password, maxSession, DLQ settings, etc.) into an ejb-jar.xml, jboss.xml, properties for the JMSProviderLoader. But the only place it seems to have any effect is when set as ActivationConfig annotations in the MDB which is not acceptable for our situation.
It appears this info gets set on a JMSActivationSpec object when the ear gets deployed. How can I get these values set without using MDB annotations?
Any help would be very much appreciated!
-ptFromSeismic
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172285#4172285
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172285
18 years
[Javassist user questions] - Drools Exception
by bindhu
Hi All,
I'm facing a problem when i have both *.drl and *.dsl. The following is the exception i'm facing.
java.lang.IllegalArgumentException: Unable to use expander. Make sure a expander or dsl config is being passed to the parser. [ExpanderResolver was not set].
at org.drools.lang.RuleParser.expander(Unknown Source)
at org.drools.lang.RuleParser.prolog(Unknown Source)
at org.drools.lang.RuleParser.compilation_unit(Unknown Source)
at org.drools.compiler.DrlParser.compile(Unknown Source)
at org.drools.compiler.DrlParser.parse(Unknown Source)
at org.drools.compiler.DrlParser.parse(Unknown Source)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(Unknown Source)
at com.livetrial.CreditExample.main(CreditExample.java:24)
Exception in thread "main"
In the main java class, i have the below codes:
builder.addPackageFromDrl( new InputStreamReader(CreditExample.class.getResourceAsStream("/credit.drl" )) );
builder.addPackageFromDrl( new InputStreamReader(CreditExample.class.getResourceAsStream("/credit.dsl" )) );
Please guide me on how to resolve this problem.
Thanks
Bindhu
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172282#4172282
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172282
18 years
[JBossWS] - Can't get a dependency on jboss.ws:service=EndpointRegistry
by viniciuscarvalho
Hello there! I've created MBeans several times on jboss, and I can't find what am I missing here.
I'm developing a DatabaseRecordProcessor, it's start method looks like this:
| public void start() throws Exception{
| try
| {
| MBeanServer server = MBeanServerLocator.locate();
| ManagedEndpointRegistryMBean registry = (ManagedEndpointRegistryMBean)MBeanProxyExt.create(ManagedEndpointRegistryMBean.class, "jboss.ws:service=EndpointRegistry");
|
| Set<ObjectName> names = registry.getEndpoints();
| for(ObjectName o : names){
| ((ManagedEndpointMBean)MBeanProxyExt.create(ManagedEndpointMBean.class, o)).addRecordProcessor(this);
| }
| }
| catch (Exception e)
| {
| e.printStackTrace();
| }
|
| }
|
and the jboss-service:
| <?xml version="1.0" encoding="UTF-8"?>
| <server>
| <mbean name="bobsam:service=DatabaseRecordProcessor" code="com.furiousbob.management.DatabaseRecordProcessor">
| <depends>jboss.ws:service=EndpointRegistry</depends>
| </mbean>
|
| </server>
|
Well, it all seems ok. But it never gets installed, the jmx-core complains about jboss.ws:service=EndpointRegistry is NOTINSTALLED.
What's funny is that: if I remove the dependency and put my sar on the deploy.last it works fine. What I can't understand is why the dependency mechanism is not working for jboss.ws mbeans?
Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172276#4172276
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172276
18 years
[Installation, Configuration & DEPLOYMENT] - Cannot undeploy package after timeout
by scubie
Hi All
I have searched but do not seem to be able to find similar symptoms to this one...
We are using JBOSS 4.0.3 SP1 on Solaris in our development and in the production environments by the customer. The following ONLY happens at the customer site. We have tried similating it in our development even with the customer's data, no luck, it just does not happen by us.
We have a query which is submitted to Oracle (10.2.0.4) which normally returns within 2 - 3 seconds. Even if it scans all 1 million records it still returns fairly fast. However occassionally the query does not return and we eventually get a timeout in JBOSS after 300 seconds. I have raised that to 1200 seconds already but still no go.
When JBOSS times out like this, we cannot even undeploy the package and re-deploy it again. Other packages running under JBOSS still continue, but this one does not respond anymore, does not process any further transactions and cannot be un-deployed. We need to stop JBOSS as a whole and rerstart it then all carries on as if nothing happened.
We can then even request the exact same set of data (query) and then all will work for some time. We have not been able to identify a pattern at all.
Any ideas please?
Thank you
Carlo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172273#4172273
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172273
18 years
[Installation, Configuration & DEPLOYMENT] - Multiple jvmRoute possible?
by rajeshchande
Hello,
I have a clustered environment with 2 JBoss instances (node1 & node2) in the cluster up and running fine with applications deployed on the same.
I have Apache ----> JBoss (Apache forwarding requests to JBoss using Mod_jk.
Apache - 2.0.55
JBoss - 4.2.2GA
mod_jk - 1.2.20
Now I have a new application which needs to be deployed on a "standalone" JBoss instance.
Can I use node1 from the cluster also as a standalone configuration by deploying the WAR file in the "deploy" folder instead of "farm" folder?
For sending requests from Apache to JBoss 1, can i have the following configuration in server.xml as follows
#################
| <!-- Define an AJP 1.3 Connector on port 8009 -->
| <Connector port="53041" address="${jboss.bind.address}" protocol="AJP/1.3"
| emptySessionPath="true" enableLookups="false" redirectPort="8443"
| maxThreads="200" connectionTimeout="600000" />
| <Engine name="jboss.web" defaultHost="localhost" jvmRoute="hubudweb-devl-01,worker1">
| #################
This configuration works fine for me i.e. Jboss node1 works fine both as a clustered instance and a stand alone instance.
So can I have multiple jvmRoute in use? Will this effect Session replication or Load Balancing in any ways?
At times I get following error in Apache mod_jk logs:
#####################
| [Mon Aug 25 10:57:31 2008]hubudweb-devl-cluster-01 0.006362
| [Mon Aug 25 10:57:31 2008]hubudweb-devl-cluster-01 0.010887
| [Mon Aug 25 10:57:31 2008]hubudweb-devl-cluster-01 0.010962
| [Mon Aug 25 10:57:32 2008][25100:0019] [error] get_most_suitable_worker::jk_lb_worker.c (719): locking failed with errno=45
| [Mon Aug 25 10:57:32 2008]hubudweb-devl-cluster-01 0.011048
| [Mon Aug 25 10:57:32 2008]hubudweb-devl-cluster-01 0.011544
| [Mon Aug 25 10:57:32 2008]hubudweb-devl-cluster-01 0.011031
| [Mon Aug 25 10:57:33 2008]hubudweb-devl-cluster-01 0.011322
| #####################
Is multiple jvmRoute th culprit for this error? What could be the reason for above error?
Regards,
Rajesh.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172271#4172271
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172271
18 years
[Remoting] - Re: Compression marshalling
by robert.geisler
hello again...
i did a step back: removed "dataType=serializable" and configured my EJB3 Remoting Connector like this:
<attribute name="InvokerLocator">socket://${jboss.bind.address}:3873/
| ?marshaller=org.jboss.remoting.marshal.compress.CompressingMarshaller
| &unmarshaller=org.jboss.remoting.marshal.compress.CompressingUnMarshaller</attribute>
|
and yes, it works (reduced amount of data being transferred) -at least for a very, very simple EJB 3.0
(just one Remote Method that returns a String like "successful").
now i got a new issue:
| 2008-08-25 12:54:38,755 ERROR [org.jboss.remoting.transport.socket.ServerThread] failed
| java.io.IOException: Can not read data for version 154. Supported versions: 1,2,22
| at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:674)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:534)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
|
first i checked the Remoting Version i am using for client and server: both JBossRemoting Version 2.2.2.SP1 (Bluto).
because the version being read differs very often (154, 77,...) i guess that someone else (maybe another Remoting Connector?) tries to read the invocation, dont expect an compressed input and finally reads a wrong version number...?
my EJB (Remote Business Interface) just talks to a second EJB (Local Business Interface) that talks to a third EJB (Local Business Interface, reads and returns an Entity). all EJBs are EJB 3.0 and in debug modus a noticed that the above exception is thrown after my first EJB already got the data form my Entity and before my client recieves the answer from my first EJB.
finally i am kind of surprised, because the answer my client recieves is good: from the client side of view everything just seem to work -on the server side there is the exception shown above :- \
any ideas and hints what i am doing wrong?
thanks in advance
robert
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172263#4172263
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172263
18 years