[JCA/JBoss] - Re: Setting up JBoss 4.2.2 so MDBs can subscribe to Topic on
by gortman
We now have the WebLogic topic messages being sent to a secured queue (one of the default queues, queue/A) on our JBoss server. However, we haven't been able to configure our EJB3 MDBs to listen to the local queue. It should be an easy thing but has turned out to be anything but. We are getting a "not bound" exception when JBoss tries to deploy the MDB to listen to queue/A.
Any tips on what the solution might be? Here are the activation configs we are using in our MDB:
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/A"),
@ActivationConfigProperty(propertyName="userName",
propertyValue="uname"),
@ActivationConfigProperty(propertyName="password",
propertyValue="psswd"),
@ActivationConfigProperty(propertyName="providerUrl",
propertyValue="jnp://localhost:1299"),
@ActivationConfigProperty(propertyName="JmsProviderAdapterJNDI",
propertyValue="DefaultJMSProvider")
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179440#4179440
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179440
17 years, 6 months
[JBossMQ] - problem while Getting reply message... in Request / reply pa
by rahb
I am using JMS Request / Reply pattern, I can send message to the consumer...consumer process it and again sends back to the producer...
but withhen that I get the following error message....Tell me where it could be the wrong...
15:15:58,640 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] XAResourceRecord.prepare - prepare failed with exception XAException.XAER_RMERR
15:15:58,640 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_50] - Prepare phase of action a010668:e33:48e128e4:a4 received heuristic decision: TwoPhaseOutcome.HEURISTIC_HAZARD
15:15:58,640 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_36] - BasicAction.End() - prepare phase of action-id a010668:e33:48e128e4:a4 failed.
15:15:58,640 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_37] - Received heuristic: TwoPhaseOutcome.HEURISTIC_HAZARD .
15:15:58,640 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_38] - Action Aborting
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179438#4179438
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179438
17 years, 6 months
[JBoss Portal] - Re: change portlet titlebar style
by PeterJ
The title bar is created in:
org.jboss.portal.theme.impl.render.div.DivDecorationRenderer.render()
which calls
org.jboss.portal.theme.impl.render.div.DivDecorationRenderer.renderTriggerableActions()
which in turn places an icon for every valid action. The valid actions are maintained by the class
org.jboss.portal.theme.page.WindowContext
which in turn is initialized by this statement in the *-object.xml file:
<supported-window-states>
| <window-state>normal</window-state>
| <window-state>minimized</window-state>
| <window-state>maximized</window-state>
| </supported-window-states>
So the first step would appear to be adding to the supported states, and updating the css to reference the icons (example: the "help" state creates an anchor with class "portlet-mode-help", and in the css this class references image images/help.gif ).
If you look at the code I mentioned, you will notice that the states are divided into "mode" and "windowstate" states. I have not dug deep enough to determine how to get a new state mapped to one of these.
Hopefully this will get you far enough to at least know where to look.
Disclaimer: I have not tried this so I do not know if it will even work.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179434#4179434
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179434
17 years, 6 months
[JBoss Tools (users)] - 3.0.0 alpha, and seam tutorial problem
by jjfraney
I don't know the root of the problem, may not be jboss tool, but its a place to start.
I run the tutorial at http://docs.jboss.com/seam/latest/reference/en-US/html/gettingstartedwith....
I finish the 'add action' section. There are two failures at this point. I'm not sure what these mean. I'm not expecting these kinds of errors in a tutorial. The tutorial hasn't given enough information, I think, to figgure out how to proceed.
1) clicking the 'ping!' button in the web view causes a null pointer exception (like the injection of log and facesMessages did not happen). Seam gives me the error page.
Here is the relevant part of stack trace (I left off ejb transaction rollback stack traces, but if you want to see them, I'll post 'em)
org.domain.seamhello.session.PingBean.ping(PingBean.java:21)
| sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| java.lang.reflect.Method.invoke(Method.java:597)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
| org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
|
2) The testng unit test fails for the ping method. A little red x appears next to the test named: 'org.domain.seamhello.test.PingTest.init' and the following shows up in the 'Failure Exception' window:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| SARDeployer -> java.lang.ClassNotFoundException: [Ljava.lang.Class;
|
| ServiceDeploymentDeployer -> java.lang.ClassNotFoundException: [Ljava.lang.Class;
|
| ServiceClassLoaderDeployer -> java.lang.ClassNotFoundException: [Ljava.lang.Class;
|
| BeanDeployer -> java.lang.ClassNotFoundException: [Ljava.lang.Class;
|
| ServiceDeployer -> java.lang.ClassNotFoundException: [Ljava.lang.Class;
|
| BeanMetaDataDeployer -> java.lang.ClassNotFoundException: [Ljava.lang.Class;
|
| KernelDeploymentDeployer -> java.lang.ClassNotFoundException: [Ljava.lang.Class;
|
|
| at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:576)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:559)
| at org.jboss.embedded.Bootstrap.bootstrapURL(Bootstrap.java:149)
| at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:183)
| at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:195)
| at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:11)
| at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1041)
| at org.jboss.seam.mock.BaseSeamTest.startSeam(BaseSeamTest.java:935)
| at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:923)
| at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580)
| at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398)
| at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145)
| at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82)
| at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:167)
| at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:104)
| at org.testng.TestRunner.runWorkers(TestRunner.java:712)
| at org.testng.TestRunner.privateRun(TestRunner.java:582)
| at org.testng.TestRunner.run(TestRunner.java:477)
| at org.testng.SuiteRunner.runTest(SuiteRunner.java:324)
| at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:319)
| at org.testng.SuiteRunner.privateRun(SuiteRunner.java:292)
| at org.testng.SuiteRunner.run(SuiteRunner.java:198)
| at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:823)
| at org.testng.TestNG.runSuitesLocally(TestNG.java:790)
| at org.testng.TestNG.run(TestNG.java:708)
| at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)
| at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179432#4179432
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179432
17 years, 6 months
[Beginners Corner] - Re: PermGen space
by PeterJ
In a typical application, the permgen will grow to a certain size and then stay at that size for the rest of the app run. Some of the reasons that the pergen size will increase are:
* Deploying a new application
* Redeploying an application
* Accessing new functionality within an application
If you find that you are redeploying applications often, then you will need to periodically restart the app server.
The JVM will remove unneeded class definitions from the permgen during a garbage collection, but sometimes classes in an old version of an application still hang around even after a new version has been deployed, hence the increase in permgen size.
If you are not redeploying applications, then you need to monitor the permgen size (use JConsole or a similar tool) and when you see a permgen increase you need to figure out what was going on at that time.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179429#4179429
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179429
17 years, 6 months
[JCA/JBoss] - Re: Problems changing DefaultDS
by PeterJ
Someone set up this wiki page to describe the steps to convert DefaultDS to use MySQL:
http://wiki.jboss.org/wiki/SetUpMysqlAsDefaultDS
The steps for Oracle should be the same, though the details will change. (I haven't reviewed those steps in detail, and lately all of my work has been done with 5.0 where the steps to replace hsqldb with another database are somewhat different. In addition, I work with MySQL and PostgreSQL.)
Essentially, the steps you outlined are correct. The catch is the DDL statements used by the various services. The wiki page you referenced details getting the messaging service DDL statements converted. But there are also tables for timers, hi-lo sequence tables, and transactions - you have run into issues with the first two, and looking at the last one I don't think that will be a problem. The issue is, of course, that different databases do not accept the same data types. But once you have corrected all of the tables, then you are done.
By the way, one way to view all of the tables is to use the hsqldb-ds.xml file, and start and then stop the app server. The tables can be view in the file server/xxx/data/hypersonic/localDB.script.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179428#4179428
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179428
17 years, 6 months
Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
buhg@localhost
17 years, 6 months
