[Installation, Configuration & DEPLOYMENT] - Exploded Deployment and persistence unit references - imposs
by espinosa_cz
Everything works when packed to appropriate archives but I wanted to try exploded development to improve redeployment time.
vod-ear-2.0.0.ear is exploded EAR (huge!)
metadata-import-ejb-2.0.0.jar is exploded EJB JAR archive, it contain simple persistence.xml just referring ../cmm-ejb-2.0.0.jar entities.
cmm-ejb-2.0.0.jar is exploded EJB JAR archive, it contains entities referenced by metadata-import-ejb-2.0.0.jar
All other WAR, EJB JARs are exploded as well.
This configuration gives me this deploy error:
ObjectName: persistence.units:ear=vod-ear-2.0.0.ear,jar=metadata-import-ejb-2.0.0.jar,unitName=metadataimport-unit
| State: FAILED
| Reason: java.lang.RuntimeException: error trying to scan <jar-file>: file:/C:/jboss/jboss-4.0.5.GA/server/vod/deploy/vod-ear-2.0.0.ear/metadata-import-ejb-2.0.0.jar/cmm-ejb-2.0.0.jar
| I Depend On:
| jboss.jca:service=DataSourceBinding,name=jdbc/ContentDS
| Depends On Me:
| jboss.j2ee:ear=vod-ear-2.0.0.ear,jar=metadata-import-ejb-2.0.0.jar,name=ImportProductSession,service=EJB3
| jboss.j2ee:ear=vod-ear-2.0.0.ear,jar=metadata-import-ejb-2.0.0.jar,name=ImportTaskSession,service=EJB3
Persistence unit configurer - unlike deployer - cannot cope with exploded EJB JARs!??!.
Thank you for any clarifications or hints
Espinosa
P.S.
JBossAS 4.0.5.GA
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108960#4108960
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108960
18 years, 5 months
[Messaging, JMS & JBossMQ] - Exception in thread
by GunterR
Hello,
I am using JBoss4.0.3SP1 with Java 1.5.0.0.12 on a Windows 2003 Server. I have created a topic on the server where the clients can subscribe to via http.
I have adapted the jboss-service.xml in deploy/jms/jbossmq-httpil.sar/META-INF as follows:
<?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE server>
| <server>
| <mbean code="org.jboss.mq.il.http.HTTPServerILService"
| name="jboss.mq:service=InvocationLayer,type=HTTP">
| <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
| <depends>jboss.web:service=WebServer</depends>
| <attribute name="ConnectionFactoryJNDIRef">HTTPConnectionFactory</attribute>
| <attribute name="XAConnectionFactoryJNDIRef">HTTPXAConnectionFactory</attribute>
| <attribute name="PingPeriod">10000</attribute>
| <attribute name="TimeOut">60</attribute>
| <attribute name="RestInterval">0</attribute>
| </mbean>
| </server>
In order to detect if a client did not unsubscribe, I have added a ClientMonitorInterceptor in the deploy/jms/jbossmq-service.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!-- $Id: jbossmq-service.xml,v 1.24.2.1 2005/06/01 05:56:44 starksm Exp $ -->
|
| <server>
|
| <!-- ==================================================================== -->
| <!-- JBossMQ -->
| <!-- ==================================================================== -->
|
|
| <!-- ==================================================================== -->
| <!-- JBossMQ Interceptor chain configuration -->
| <!-- ==================================================================== -->
| <!-- To tune performance, you can have the Invoker skip over the TracingInterceptor -->
| <!-- and/or the SecurityManager, but then you loose the ability to trace and/or enforce security. -->
| <mbean code="org.jboss.mq.server.jmx.Invoker" name="jboss.mq:service=Invoker">
| <depends optional-attribute-name="NextInterceptor">jboss.mq:service=TracingInterceptor</depends>
| <depends>jboss:service=Naming</depends>
| </mbean>
|
| <mbean code="org.jboss.mq.server.jmx.InterceptorLoader" name="jboss.mq:service=TracingInterceptor">
| <attribute name="InterceptorClass">org.jboss.mq.server.TracingInterceptor</attribute>
| <depends optional-attribute-name="NextInterceptor">jboss.mq:service=SecurityManager</depends>
| </mbean>
|
| <mbean code="org.jboss.mq.security.SecurityManager" name="jboss.mq:service=SecurityManager">
| <attribute name="DefaultSecurityConfig">
| <security>
| <role name="guest" read="true" write="true" create="true"/>
| </security>
| </attribute>
| <attribute name="SecurityDomain">java:/jaas/jbossmq</attribute>
| <depends optional-attribute-name="NextInterceptor">jboss.mq:service=ClientMonitorInterceptor</depends>
| </mbean>
|
| <!--
| | The ClientMonitorInterceptor disconnects clients that have been idle for to long.
| | This interceptor is not enabled by default since the server might disconnect clients
| | when the it is under high load.
| -->
|
| <mbean code="org.jboss.mq.server.jmx.ClientMonitorInterceptor" name="jboss.mq:service=ClientMonitorInterceptor">
| <attribute name="ClientTimeout">80000</attribute>
| <depends optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager</depends>
| </mbean>
|
| <!--
| | The ClientReconnectInterceptor is used to allow a client to connect to the server even
| | if it's clientID is allready being used by another client. This interceptor will disconnect
| | the previously connected client to allow the new connection to succeed. This is not enabled
| | by default since the JMS spec states that the 2nd client connecting to the server with the same
| | id should get an exception.
| -->
| <!--
| <mbean code="org.jboss.mq.server.jmx.InterceptorLoader" name="jboss.mq:service=ClientReconnectInterceptor">
| <attribute name="InterceptorClass">org.jboss.mq.server.ClientReconnectInterceptor</attribute>
| <depends optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager</depends>
| </mbean>
| -->
| <!-- ==================================================================== -->
| <!-- System Destinations -->
| <!-- ==================================================================== -->
|
| <!-- Dead Letter Queue -->
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=DLQ">
| <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
| </mbean>
|
| </server>
|
I tested this succesfully on our developing machine. I let the client crash and after a few seconds, the server noticed this and removed the subscription from the nondurable subscriptions list.
I made the same configuration on the customer's site and it worked well for two days. After that, I found the following exception in our server logs:
| 2007-11-28 11:23:31,718 INFO STDOUT : Exception in thread "ClientMonitor Service Thread"
| 2007-11-28 11:23:31,718 INFO STDOUT : java.lang.NullPointerException
| 2007-11-28 11:23:31,718 INFO STDOUT : at org.jboss.mq.server.ClientMonitorInterceptor.disconnectInactiveClients(ClientMonitorInterceptor.java:55)
| 2007-11-28 11:23:31,718 INFO STDOUT : at org.jboss.mq.server.jmx.ClientMonitorInterceptor$1.run(ClientMonitorInterceptor.java:64)
| 2007-11-28 11:23:31,718 INFO STDOUT : at java.lang.Thread.run(Thread.java:595)
|
| After this, inactive subscriptions aren't detected anymore on the server.
|
| I searched the forums, jira bug list, faqs, but couldn't find anything pointing to this particular problem.
|
| thanks in advance for anyone who can answer my question.
| Gunter
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108959#4108959
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108959
18 years, 5 months
[JBossWS] - Re: Java Client Application using Stub with WS-Security
by method_ben
I did not find an exception in my server log file and my code (web service)doesnt contain an try/catch(WSSecurityException e) clause like you said.
I think that the exception is thrown by a referenced lib. In my classpath of my Eclipse projects (my client project and my web service project), I include all libs of jboss_folder/client and jboss_folder/lib/endorsed.
My web service class :
| import javax.jws.WebMethod;
| import javax.jws.WebParam;
| import javax.jws.WebResult;
| import javax.jws.WebService;
| import javax.jws.soap.SOAPBinding;
| import org.jboss.ws.annotation.EndpointConfig;
|
| @WebService(targetNamespace = "rrr",serviceName = "TestService", wsdlLocation="WEB-INF/wsdl/TestService.wsdl")
| @SOAPBinding(parameterStyle=SOAPBinding.ParameterStyle.WRAPPED, use=SOAPBinding.Use.LITERAL, style=SOAPBinding.Style.DOCUMENT)
| @EndpointConfig(configName = "Standard WSSecurity Endpoint")
| public class Test
| {
| @WebMethod
| @WebResult(name="result",targetNamespace="rrr")
| public String allo(@WebParam(name="name", targetNamespace="rrr")String name)
| {
| System.out.println("Allo " + name);
| return name;
| }
|
| @WebMethod
| @WebResult(name="result",targetNamespace="rrr")
| public String hello(@WebParam(name="name", targetNamespace="rrr")String name)
| {
| System.out.println("Hello " + name);
| return name;
| }
| }
|
Contains of my war file :
META-INF\MANIFEST.MF
WEB-INF\jboss-wsse-client.xml
WEB-INF\jboss-wsse-server.xml
WEB-INF\web.xml
WEB-INF\wsse.keystore
WEB-INF\wsse.truststore
WEB-INF\classes\com\Test.Class
WEB-INF\wsdl\TestService.wsdl
I have no idea where the exception is logged !
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108954#4108954
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108954
18 years, 5 months