[jboss-user] [JCA] - Re: ClassNotFoundException when moving JCA adaptor from 4.2.

2009-10-25 Thread pwnell
Not really since I share that RAR across many different ears.  The RAR provides 
a global logging and auditing framework shared by up to 7 different ears 
deployed in the same JBoss instance.  Surely the domain names would be 
different then?

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262042#4262042

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262042
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss Web Services Users] - XOM fails in production but works in dev

2009-10-16 Thread pwnell
I really need urgent help please.  I have implemented a web service using XOM 
to transfer large files from the client to the web service.  In dev this works 
fine, however in production I see no errors in the log file, yet the 
inputstream yields 0 bytes when reading the file.

I am using jbossws-3.0.1-native-2.0.4.GA (build=200803312044) on JBoss 4.2.3 
GA.  Here are the log files:


  | 2009-10-17 00:12:44,525 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] 
doPost: /LicensingWSBeanService/WSServerLargeFileTransferBean
  | 2009-10-17 00:12:44,525 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] 
handleRequest: 
jboss.ws:context=LicensingWSBeanService,endpoint=WSServerLargeFileTransferBean
  | 2009-10-17 00:12:44,525 DEBUG 
[org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: 
org.jboss.ws.core.jaxws.handler.soapmessagecontextja...@4964f4eb (Thread 
http-0.0.0.0-8080-1)
  | 2009-10-17 00:12:44,525 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] 
BEGIN handleRequest: 
jboss.ws:context=LicensingWSBeanService,endpoint=WSServerLargeFileTransferBean
  | 2009-10-17 00:12:44,525 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] 
createMessage: [contentType=multipart/related; type="application/xop+xml"; 
  | boundary="uuid:604b4c1b-9578-4a57-897e-fa68d07da32e"; 
  | start-info="text/xml"]
  | 2009-10-17 00:12:44,541 DEBUG 
[org.jboss.ws.core.soap.attachment.SwapableMemoryDataSource] Using memory 
buffer, size = 325
  | 2009-10-17 00:12:44,556 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] 
setRepository, 
repository=org.jboss.mx.loading.heirarchicalloaderreposito...@2f57d162, 
cl=org.jboss.mx.loading.heirarchicalloaderrepository3$cacheclassloa...@7b04eff0{
 url=null ,addedOrder=0}
  | 2009-10-17 00:12:44,583 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: 
POST
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: PRE
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] addHandler: 
  | HandlerMetaDataJAXWS:
  |  type=PRE
  |  name=Recording Handler
  |  class=class org.jboss.wsf.framework.invocation.RecordingServerHandler
  |  params=[]
  |  protocols=##SOAP11_HTTP
  |  services=null
  |  ports=null
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: ENDPOINT
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: POST
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: 
[type=POST,info=[service={http://webservice.licensing.sarad.co.za/}WSServerLargeFileTransferBeanService,port={http://webservice.licensing.sarad.co.za/}WSServerLargeFileTransferBeanPort,binding=http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true]]
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler 
executor: []
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.soap.SOAPMessageDispatcher] getDispatchDestination: 
{http://webservice.licensing.sarad.co.za/}uploadApplicationUpdates
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] unbindRequestMessage: 
{http://webservice.licensing.sarad.co.za/}uploadApplicationUpdates
  | 2009-10-17 00:12:44,584 DEBUG [org.jboss.ws.core.EndpointInvocation] 
setRequestParamValue: 
[name={http://webservice.licensing.sarad.co.za/}uploadApplicationUpdates,value=org.jboss.ws.core.soap.SOAPBodyElementDoc]
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: 
ENDPOINT
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: 
[type=ENDPOINT,info=[service={http://webservice.licensing.sarad.co.za/}WSServerLargeFileTransferBeanService,port={http://webservice.licensing.sarad.co.za/}WSServerLargeFileTransferBeanPort,binding=http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true]]
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler 
executor: []
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: 
PRE
  | 2009-10-17 00:12:44,584 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: 
[type=PRE,info=[service={http://webservice.licensing.sarad.co.za/}WSServerLargeFileTransferBeanService,port={http://webservice.licensing.sarad.co.za/}WSServerLargeFileTransferBeanPort,binding=http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true]]
  | 2009-10-17 00:12:44,585 DEBUG 
[org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler 
executor: []
  | 2009-10-17 00:12:44,585 DEBUG [org.jboss.ws.core.EndpointInvocation] 
getRequestPayload
  | 2009-10-17 00:12:44,585 DEBUG [org.jboss.ws.core.EndpointInvocation] 
getRequestParamValue: 
{http://webservice.licensing.

[jboss-user] [JBoss Web Services Users] - Re: XOM fails in production but works in dev

2009-10-16 Thread pwnell
PS: vTestFile in the client is a byte[] of the file content.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260850#4260850

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260850
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss Web Services Users] - Re: XOM fails in production but works in dev

2009-10-16 Thread pwnell
Sorry, that should read XOP/MTOM, not XOM. Typo.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260851#4260851

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260851
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBoss Web Services Users] - Re: XOM fails in production but works in dev

2009-10-16 Thread pwnell
Additional info that might help - the SOAP message sent from the client to the 
server to upload the test file for the local dev scenario (working):


  | POST./LicensingWSBeanService/WSServerLargeFileTransferBean.HTTP/1.1
  | Soapaction:.""
  | 
Accept:.text/xml,.multipart/related,.text/html,.image/gif,.image/jpeg,.*;.q=.2,.*/*;.q=.2
  | 
Content-type:.multipart/related;start="";type="application/xop+xml";boundary="uuid:480a4f5f-b9ea-4c31-b857-3d36f5dca84e";start-info="text/xml"
  | User-Agent:.JAX-WS.RI.2.1.6.in.JDK.6
  | Host:.DEV:8080
  | Connection:.keep-alive
  | Content-Length:.955
  | 
  | --uuid:480a4f5f-b9ea-4c31-b857-3d36f5dca84e
  | 
Content-Id:.
  | Content-Type:.application/xop+xml;charset=utf-8;type="text/xml"
  | Content-Transfer-Encoding:.binary
  | 
  | 
  |   http://schemas.xmlsoap.org/soap/envelope/";>
  | 
  |   
http://webservice.licensing.sarad.co.za/";>
  | 70923672990106339906486742558683167563297568954954
  | 2100
  | 
  |   
http://www.w3.org/2004/08/xop/include".href="cid:d477c76d-d33f-46d6-92a8-701e2a8d1901@example.jaxws.sun.com";>
  | 
  |   
  | 
  |
  | --uuid:480a4f5f-b9ea-4c31-b857-3d36f5dca84e
  | Content-Id:.
  | Content-Type:.application/octet-stream
  | Content-Transfer-Encoding:.binary
  | 
  | ..
  | --uuid:480a4f5f-b9ea-4c31-b857-3d36f5dca84e--
  | 
  | 
  | And for the production scenario (not working):
  | 
  | 
  |   | POST./LicensingWSBeanService/WSServerLargeFileTransferBean.HTTP/1.1
  |   | SOAPAction:.""
  |   | 
Accept:.text/xml,.multipart/related,.text/html,.image/gif,.image/jpeg,.*;.q=.2,.*/*;.q=.2
  |   | 
Content-Type:.multipart/related;type="application/xop+xml";boundary="uuid:78c1dc43-5c49-43c5-af8b-1f06fd985e58";start-info="text/xml"
  |   | User-Agent:.Java/1.6.0_10
  |   | Host:.PROD:8080
  |   | Connection:.keep-alive
  |   | Content-Length:.517
  |   | 
  |   | --uuid:78c1dc43-5c49-43c5-af8b-1f06fd985e58
  |   | Content-Type:.application/xop+xml;charset=utf-8;type="text/xml"
  |   | Content-Transfer-Encoding:.binary
  |   | 
  |   | 
  |   |   http://schemas.xmlsoap.org/soap/envelope/";>
  |   | 
  |   |   
http://webservice.licensing.sarad.co.za/";>
  |   | 01475913245426691815944254703234806328018572161348
  |   | 2100
  |   | 
  |   |   
  |   | 
  |   |
  |   | --uuid:78c1dc43-5c49-43c5-af8b-1f06fd985e58--
  |   | 
  | 
  | It is interesting to see the User-Agent differ even though both client 
machines run JDK6. Ignore the periods - most of them represent spaces.
  | 
  | Ideas?

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260856#4260856

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260856
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JCA] - ClassNotFoundException when moving JCA adaptor from 4.2.3 ->

2009-10-18 Thread pwnell
I have written a JCA adaptor some years ago on JCA 1.5, for JBoss 3.x.  I later 
moved it to JBoss 4.x without problems.  However when I tried to deploy it 
under JBoss 5.1.0 GA it fails.  I managed to fix most of the issues but I 
cannot seem to get around this one:


  | 17:06:26,781 ERROR [[/LogMon]] StandardWrapper.Throwable
  | java.lang.NoClassDefFoundError: 
net/za/pwnconsulting/logmon/rar/cci/data/client/LogMessage
  | at 
net.za.pwnconsulting.logmon.clientapi.LogMonClientAPIFactory.getCCILogMonAPI(LogMonClientAPIFactory.java:30)
  | at net.za.pwnconsulting.javaconfig.core.LMS.(LMS.java:28)
  | at 
net.za.pwnconsulting.javaconfig.core.BasicConfiguration.initConfig(BasicConfiguration.java:144)
  | at 
net.za.pwnconsulting.javaconfig.core.AbstractConfiguration.init(AbstractConfiguration.java:189)
  | at 
net.za.pwnconsulting.webmvc.config.WebConfiguration.(WebConfiguration.java:85)
  | at 
net.za.pwnconsulting.webmvc.servlet.BootstrapServlet.initServlet(BootstrapServlet.java:75)
  | at 
net.za.pwnconsulting.webmvc.servlet.AbstractBootstrapServlet.init(AbstractBootstrapServlet.java:105)
  | at javax.servlet.GenericServlet.init(GenericServlet.java:212)
  | at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
  | at 
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:950)
  | at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4122)
  | at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4421)
  | 
  | 
  | Now the class in question 
(net/za/pwnconsulting/logmon/rar/cci/data/client/LogMessage) is deployed inside 
the LogMonJCA.rar file in the deploy directory.  The code trying to access it 
resides in a LogMonConsole.ear package also in the deploy directory.
  | 
  | Why would this work previously on JBoss 4.x and 3.x, but not in JBoss 5.x?  
Somewhere the classloader behaviour changed and is not loading classes from the 
RAR file.
  | 
  | So either my deployment is incorrect, or I need to change the classloader 
behaviour in JBoss.  When I bundled this class with the .ear file, I got 
another error where the InteractionSpec the client code sent via .execute() is 
not compatible with the InteractionSpec used in the RAR file.  This makes sense 
as they are loaded by two different class loaders - hence even though they are 
binary compatible they are still distinct classes.
  | 
  | Any help would be much appreciated.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260970#4260970

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260970
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JCA] - Re: ClassNotFoundException when moving JCA adaptor from 4.2.

2009-10-19 Thread pwnell
I get this:


  | net.za.pwnconsulting.logmon.rar.cci.data.client.LogMessage Information
  | Not loaded in repository cache
  | 

I know my RAR is loaded:

  | name='LogMonJCA.rar',service=RARDeployment
  | 

and as you can see LogMessage is indeed inside the RAR archive:


  | r...@waldopc:/opt/jboss-5.1.0.GA/bin# jar -tf 
../server/default/deploy/LogMonJCA.rar | grep LogMessage
  | net/za/pwnconsulting/logmon/rar/cci/data/client/LogMessage.class
  | 

Some additional info:

java2ClassLoadingCompliance = false
WarClassLoaderDeployer not commented out
I do not have WEB-INF/jboss-classloading.xml files. 
I *do* make use of jboss-app.xml files - in the RAR and in the ear.  In the RAR 
file:


  | 
  |
  |dot.com:loader=LogMonJCA
  |  
  |  java2ParentDelegation=false
  | 
  |
  | 
  | 

In the ear file:

  | 
  |
  |dot.com:loader=LogMonConsole
  |
  |  java2ParentDelegation=false
  | 
  |
  | 
  | 

Not sure if these are the cause of the problem but I have always used it like 
this and it used to work just fine.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261107#4261107

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261107
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JCA] - Re: ClassNotFoundException when moving JCA adaptor from 4.2.

2009-10-19 Thread pwnell
It *seems* like my code works in the standard configuration, not in the 
default.  Does this help shed some light?

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261146#4261146

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261146
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB/JBoss] - Re: NullPointerException restoring EJB state

2009-06-18 Thread pwnell
Sorry, I meant to say EOFException

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238564#4238564

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238564
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB/JBoss] - NullPointerException restoring EJB state

2009-06-18 Thread pwnell
Why do I get this error randomly?  This is on a Stateful session bean:

2009-06-18 18:57:46,939 INFO  [STDOUT] 
(ContainerBackgroundProcessor[StandardEngine[jboss.web]]) In destroy...

2009-06-18 18:57:46,951 WARN  [org.jboss.seam.Component] 
(ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Exception calling 
component @Destroy method: search

javax.ejb.EJBException: Could not activate; failed to restore state
at 
org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.activateSession(StatefulSessionFilePersistenceManager.java:318)
at 
org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:476)
at 
org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:430)
at 
org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:59)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at 
org.jboss.ejb3.stateful.StatefulRemoveInterceptor.invoke(StatefulRemoveInterceptor.java:100)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
at 
org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at 
org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at 
org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at 
org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at 
org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at 
org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at 
org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at 
org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:154)
at 
org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
at 
org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
at $Proxy1164.destroy(Unknown Source)
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.seam.util.Reflections.invoke(Reflections.java:22)
at 
org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
at 
org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76)
at 
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
at 
org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:43)
at 
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at 
org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32)
at 
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at 
org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
at 
org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54)
at 
org.javassist.tmp.java.lang.Object_$$_javassist_8.destroy(Object_$$_javassist_8.java)
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.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.util.Reflections.invoke