[JBoss Messaging] - Re: Getting javax.jms.InvalidClientIDException when using 1.
by sathish_06
Hi,
The jboss application server that we use is Jboss-4.0.4.GA AS.
We use 'perusworld' as a client ID. But, while posting to this forum, I had replaced with 'defaultclient' for ease of understanding for everyone.
Here is the correct one:
02:08:31,248 INFO [JMSContainerInvoker] Waiting for reconnect internal 10000ms for TransactionCategorisationMDB
| 02:08:31,279 ERROR [ExceptionUtil] org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint@b4dcd9 createConnectionDelega
| te [5c4o5s4p-gy8nr8-eyddak01-1-eyddfey7-1n]
| javax.jms.InvalidClientIDException: Client ID 'defaultclient' already used by ConnectionEndpoint[-2147483632]
| at org.jboss.jms.server.ServerPeer.checkClientID(ServerPeer.java:651)
| at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpo
| int.java:129)
| at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFact
| oryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:64)
| 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:585)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| at org.jboss.jms.server.container.InjectionAspect.handleCreateConnectionDelegate(InjectionAspect.java:69)
| at org.jboss.aop.advice.org.jboss.jms.server.container.InjectionAspect0.invoke(InjectionAspect0.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aop.Advisor.dynamicInvoke(Advisor.java:723)
| at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:101)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:127)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:715)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:552)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
| 02:08:31,279 ERROR [ServerThread] SocketServerInvoker[0.0.0.0:4457].invoke() call failed: Client ID 'defaultclient' already used
| by ConnectionEndpoint[-2147483632]
| 02:08:31,295 WARN [JMSContainerInvoker] JMS provider failure detected for DataPointManagementMDB
| javax.jms.InvalidClientIDException: Client ID 'defaultclient' already used by ConnectionEndpoint[-2147483632]
| at org.jboss.jms.server.ServerPeer.checkClientID(ServerPeer.java:651)
| at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpo
| int.java:129)
| at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFact
| oryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:64)
| 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:585)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| at org.jboss.jms.server.container.InjectionAspect.handleCreateConnectionDelegate(InjectionAspect.java:69)
| at org.jboss.aop.advice.org.jboss.jms.server.container.InjectionAspect0.invoke(InjectionAspect0.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aop.Advisor.dynamicInvoke(Advisor.java:723)
| at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:101
Thx, Sathish
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019475#4019475
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019475
19Â years, 2Â months
[JBoss jBPM] - Re: jpdl-3.2.Beta2: how to access variable from task form in
by avbentem
...solved!
This may be caused by using a more recent version of the Hibernate libraries (though I doubt the older version would not create an empty List), or maybe is simply a bug that everyone would suffer. I did not yet investigate; I will submit a bug report later, if I did not cause this myself...
http://fisheye.jboss.com/browse/JBPM/jbpm.3/jpdl/jar/src/main/java/org/jb...
48 List decisionConditions = null;
| :
| 105 } else if (decisionConditions!=null) {
| 106 // backwards compatible mode based on separate DecisionCondition
In my setup, database table JBPM_DECISIONCONDITION is empty, but for this Hibernate still creates an empty List. Changing into:
105 } else if (decisionConditions!=null && !decisionConditions.isEmpty()) {
solved my problems. Now both
<decision name="Large quantity?">
| <!-- First transition is also the default ("otherwise") branch -->
| <transition name="No" to="ship item"/>
| <transition name="Yes" to="Make appointment">
| <condition><![CDATA[#{quantity > 2}]]></condition>
| </transition>
| </decision>
and
<condition><![CDATA[#{contextInstance.variables['quantity'] > 2}]]></condition>
work as expected (as noted earlier in this thread, using the 'expression' attribute somehow does not get the condition into the database to start with).
Arjan.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019474#4019474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019474
19Â years, 2Â months
[JBoss Messaging] - Re: Xa - Memory Leak ?
by jeanbobby
I just use the a spring JtaTransactionManager which acts as a TM wrapper that looks up JBoss UserTx and TM in jndi, and allow consistent syntax when switching to a spring-specific TM.
I dont know the spring code base by heart but it has to properly call commit on the jboss resources as I do have consitent distributed tx behaviour for my commits and rollbacks between JBM and Hibernate.
Anyway, I did setup a one class test bootstraped as a sar and using a thread pool executor for the multithreading and I can see the same ever groging ServerConsumerEndpoint count with JHat (with both TransactionManager and UserTransaction).
Would you have a few minutes to look into it ?
I can send it to you if you're interested.
Thanks,
Best regards
Olivier
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019473#4019473
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019473
19Â years, 2Â months
[JBossWS] - Problems ejb call and jaxrpc / principal
by penguine
Hallo Thomas,
The HelloBean in my/your example:
String urlstr = "http://localhost:8080/ws/RoleSecured?wsdl";
String argument = "testmich";
System.out.println("Contacting webservice at " + urlstr);
URL url = new URL(urlstr);
QName qname = new QName("http://hello.ws.jboss.org/", "HelloService");
ServiceFactory factory = ServiceFactory.newInstance();
Service service = factory.createService(url, qname);
Hello hello = (Hello) service.getPort(Hello.class);
Stub stub = (Stub) hello;
stub._setProperty(Stub.USERNAME_PROPERTY, "kermit");
stub._setProperty(Stub.PASSWORD_PROPERTY, "thefrog");
System.out.println("hello.hello(" + argument + ")");
System.out.println("output:" + hello.hello(argument)); <-- here the exception occurs
I become the following error:
Contacting webservice at http://localhost:8080/ws/RoleSecured?wsdl
hello.hello(testmich)
java.rmi.RemoteException: Call invocation failed with code [Client] because of: java.rmi.AccessException: SecurityException; nested exception is:
java.lang.SecurityException: Insufficient method permissions, principal=null, ejbName=HelloBean, method=hello, interface=SERVICE_ENDPOINT, requiredRoles=[friend], principalRoles=[]; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: java.rmi.AccessException: SecurityException; nested exception is:
java.lang.SecurityException: Insufficient method permissions, principal=null, ejbName=HelloBean, method=hello, interface=SERVICE_ENDPOINT, requiredRoles=[friend], principalRoles=[]
at org.jboss.ws.common.CommonClient.invoke(CommonClient.java:331)
at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:560)
at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:338)
at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:148)
at $Proxy0.hello(Unknown Source)
at de.mycompany.it.webservice.test.TestHelloClientII.main(TestHelloClientII.java:67)
Caused by: javax.xml.rpc.soap.SOAPFaultException: java.rmi.AccessException: SecurityException; nested exception is:
java.lang.SecurityException: Insufficient method permissions, principal=null, ejbName=HelloBean, method=hello, interface=SERVICE_ENDPOINT, requiredRoles=[friend], principalRoles=[]
at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.getSOAPFaultException(SOAPFaultExceptionHelper.java:100)
at org.jboss.ws.common.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:574)
at org.jboss.ws.common.CommonClient.invoke(CommonClient.java:319)
... 5 more
Exception in thread "main"
If I do a normal lookup to my bean as you do it in your examples it works.
But if I try to use the webserver to access the wsdl like my example above I don´t have a valid principal setting.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019457#4019457
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019457
19Â years, 2Â months