[JBoss Messaging] New message: "User JBM.SUCKER is NOT authenticated"
by Leonid Batizhevsky
User development,
A new message was posted in the thread "User JBM.SUCKER is NOT authenticated":
http://community.jboss.org/message/524686#524686
Author : Leonid Batizhevsky
Profile : http://community.jboss.org/people/leonko
Message:
--------------------------------------------------------------
Hello, I have this eror message then all nodes connect to cluster:
6:02:22,065 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
16:02:22,065 ERROR [ExceptionUtil] ConnectionFactoryEndpoint[jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory] createFailoverConnectionDelegate [ya-9acfxa5g-1-fu42xa5g-ilu04i-vao4c5]
javax.jms.JMSSecurityException: User JBM.SUCKER is NOT authenticated
at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223)
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 com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at javax.management.StandardMBean.invoke(StandardMBean.java:391)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy217.authenticate(Unknown Source)
at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233)
at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171)
at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108)
at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java)
at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
16:02:22,483 ERROR [ClusterConnectionManager] Failed to start connection info
javax.jms.JMSSecurityException: User JBM.SUCKER is NOT authenticated
at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223)
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 com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at javax.management.StandardMBean.invoke(StandardMBean.java:391)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy217.authenticate(Unknown Source)
at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233)
at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171)
at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108)
at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java)
at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:211)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:171)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_31353833.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_31353833.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87)
at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo.start(ClusterConnectionManager.java:646)
at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.ensureAllConnectionsCreated(ClusterConnectionManager.java:409)
at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.notify(ClusterConnectionManager.java:230)
at org.jboss.messaging.core.impl.DefaultClusterNotifier.sendNotification(DefaultClusterNotifier.java:72)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.putReplicantLocally(MessagingPostOffice.java:1187)
at org.jboss.messaging.core.impl.postoffice.PutReplicantRequest.execute(PutReplicantRequest.java:94)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlRequestHandler.handle(GroupMember.java:622)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:616)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:637)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:944)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:619)
JBOSS 5.1.0.GA out of box config (I chenge only cluster settings ) and default password changed in config
+messaging/messaging-service.xml:+
<attribute name="SuckerPassword">mypass</attribute>
+messaging/messaging-jboss-beans.xml+:<property name="suckerPassword">mypass</property>
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524686#524686
16 years, 5 months
[jBPM] New message: "Re: Unable to login to jbpm-console"
by Raji n
User development,
A new message was posted in the thread "Unable to login to jbpm-console":
http://community.jboss.org/message/524680#524680
Author : Raji n
Profile : http://community.jboss.org/people/raji_126
Message:
--------------------------------------------------------------
I faced a similar issue with jbpm 3.2 version. Though this is an older post, found this unanswered. So thought of sharing my solution, so that it helps someone.
The security constraint web.xml under <jboss_root>\default\deploy\jbpm\jsf-console.war is configured
for the role "user" only. So it throws a 403 error if the new user created in the database does not belong to the group "user".
Change it to point to the group that you created.
<security-constraint>
<web-resource-collection>
<web-resource-name>Secure Area</web-resource-name>
<url-pattern>/app/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>*user*</role-name>
</auth-constraint>
</security-constraint>
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524680#524680
16 years, 5 months
[JBoss Messaging] New message: "Re: Failed Attempt to integrate JBOSS AS with Websphere MQ"
by Ben Cotton
User development,
A new message was posted in the thread "Failed Attempt to integrate JBOSS AS with Websphere MQ":
http://community.jboss.org/message/524679#524679
Author : Ben Cotton
Profile : http://community.jboss.org/people/ben.cotton@rutgers.edu
Message:
--------------------------------------------------------------
I was able to sucessfully deploy your WMQTestMDB.java MDB to my JBoss AS 5.1 instance and confirm that this MDB executed immediately upon my sending a test message to my WSMQ destination 'TEST.QUEUE'.
I did this by doing the following
1. Modify your WMQTestMDB.java source to indicate my WSMQ instance ('hostName' and 'queueManager' property values changed)
2. Build a .jar (file name = JBossMessagingForum.jar) to deploy to my JBoss AS 5.1 instance (this .jar is attached to this post)
3. cp JBossMessagingForum.jar $JBOSS_HOME/server/default/deploy/
4. confirm from the JBoss server log file that the deploy had no errors/exceptions and that EJB 'WMQTestMDB' started
5. From the IBM Websphere MQ Explorer application, right clicked on the 'TEST.QUEUE' object and selected the 'Put Test Message' menu item
6. Sent a "Hello World" text message to TEST.QUEUE
7. Confirmed from the JBoss server log file that the MDB consumed the 'Hello World' message
All this worked without error, I am not exactly sure why your MDB deployment did not work for you.
As a possible test, maybe you can take the attached .jar and re-try steps 1 through 7 above?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524679#524679
16 years, 5 months
[jBPM] New message: "jBPM 4.3 - possible problems with the jPDL Eclipse editor?"
by Patricia B
User development,
A new message was posted in the thread "jBPM 4.3 - possible problems with the jPDL Eclipse editor?":
http://community.jboss.org/message/524671#524671
Author : Patricia B
Profile : http://community.jboss.org/people/patriciab
Message:
--------------------------------------------------------------
I am working on an application which currently uses jBPM 3.3.1. I intend to migrate to jBPM 4.3. For this, I used the migration tool, which translated the jpdl xml file to the new format. One problem that I found during migration was that the decision element was not completely migrated - namely, the handler element was missing from the migrated definition, and I added it manually afterwards. I attached the new jPDL xml that resulted after the migration.
Apart from that, the main problem that I ran into is related to the visual editor. Using the Eclipse plugin provided by JBPM 4.3, whenever I edit the process definition using the *Diagram* view, all the *<java/>* elements nested within *<transition/>* elements are removed. If I edit it using the *Source* view of the jPDL editor, whithout touching the *Diagram* view, all the <*java/>* elements are preserved. The process definition having the *java* elements for transitions seems to be executed ok. I am using Eclipse - Galileo (Build id: 20090920-1017), and Ubuntu 9.10.
I got the same result using the examples that comes with jBPM 4.3. If I manually add the <*java/>* element to a transition using the *Source* view, it works fine, but as soon as I modify the process definition using the *Diagram* view, all the *<java/>* elements are removed. I also noticed that there is somewhat of a disconnect between the behaviour of the *Diagram* view and the *Source* view for the jPDL editor. For example, there is no way to specify java tasks for transitions on the *diagram* view, whereas on the *Source* view, one can edit the xml file, to add *<java/>* elements for transitions, or any other activities i.e. event listener, etc.
My main question is whether removing java elements for transitions, whenever using the Eclipse jPDL editor, *Diagram* view is a simple issue, or is it intentional - i.e. transitions containing java tasks will not be supported moving forward. The latter does not seem very intuitive to me, since the migration tool produces exactly this type of structure. If that is correct though, then how should the process definition look like? Any feedback/comment is very welcome.
Thanks!
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524671#524671
16 years, 5 months
[JBoss Messaging] New message: "Re: Failed Attempt to integrate JBOSS AS with Websphere MQ"
by Jeremy O'Donohue
User development,
A new message was posted in the thread "Failed Attempt to integrate JBOSS AS with Websphere MQ":
http://community.jboss.org/message/524658#524658
Author : Jeremy O'Donohue
Profile : http://community.jboss.org/people/jeremyojeremy
Message:
--------------------------------------------------------------
Good Morning Ben,
Back at work today, had a look at your code snippets, but still run into issues we have seen before:
Most of the properties you are using in your MDB are rejected on deployment by our JBOSS server:
Heres the Error:
Failed to create Resource wmp-mdb-test-v1.jar - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS IN ERROR: Deployment "jboss.j2ee:jar=wmp-mdb-test-v1.jar,name=WMQMDBTest,service=EJB3" is in error due to the following reason(s): java.beans.IntrospectionException: No property found for: transportType on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@9d87a0(ra=null destination=TEST.QUEUE destinationType=null tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS IN ERROR: Deployment "jboss.j2ee:jar=wmp-mdb-test-v1.jar,name=WMQMDBTest,service=EJB3" is in error due to the following reason(s): java.beans.IntrospectionException: No property found for: transportType on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@9d87a0(ra=null destination=TEST.QUEUE destinationType=null tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
I've had a look into this in the past and is seems to happen because there are no getters / setters for some of the properties defined in the MDB ie. hostName in the org.jboss.resource.adapter.jms.inflow.JmsActivationSpec class (http://docs.huihoo.com/javadoc/jboss/4.0.2/org/jboss/resource/adapter/jms...).
Did you have to extend this class to have a successful deployment?
FYI setting : @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), allows you to reference the QUEUE by it's WSMQ Name as it tells the MDB to bypass JNDI lookup and go straight to WS.
My New Test MDB code:
package au.com.loftusit.mqtest;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
import org.jboss.annotation.ejb.ResourceAdapter;
@MessageDriven(activationConfig =
{
@ActivationConfigProperty(propertyName="messagingType",propertyValue="javax.jms.MessageListener"),
@ActivationConfigProperty(propertyName = "destinationType",propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "TEST.QUEUE"),
@ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"),
@ActivationConfigProperty(propertyName = "channel", propertyValue = "SYSTEM.DEF.SVRCONN"),
@ActivationConfigProperty(propertyName = "hostName", propertyValue = "172.19.1.14"),
@ActivationConfigProperty(propertyName = "queueManager", propertyValue = "ExampleQM"),
@ActivationConfigProperty(propertyName = "port", propertyValue = "1414"),
@ActivationConfigProperty(propertyName = "transportType", propertyValue = "CLIENT")
})
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
@ResourceAdapter(value = "wmq.jmsra.rar")
class WMQMDBTest implements MessageListener {
public void onMessage(Message message) {
System.out.println(message.toString());
}
}
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524658#524658
16 years, 5 months