[JBoss Seam] - Deployment Error
by merajcal
While deploying icefaces example on oc4j server, facing following errror
2007-02-05 12:20:22.921 ERROR J2EE EJB3027 [seam-icefaces] An error occured deploying EJB module: com.evermind.server.ejb.deployment.InvalidEJBAssemblyException: Unknown assembly-descriptor subtag: interceptor-binding, see section 22.5 of the EJB specification
2007-02-05 12:20:22.921 NOTIFICATION application : seam-icefaces is in failed state
Feb 5, 2007 12:20:22 PM com.evermind.server.Application setConfig
WARNING: Application: seam-icefaces is in failed state as initialization failedjava.lang.InstantiationException: Error initializing ejb-modules: Unknown assembly-descriptor subtag: interceptor-binding, see section 22.5 of the EJB specification
07/02/05 12:20:22 oracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: Error initializing ejb-modules: Unknown assembly-descriptor subtag: interceptor-binding, see section 22.5 of the EJB specification
07/02/05 12:20:22 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:510)
07/02/05 12:20:22 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:191)
07/02/05 12:20:22 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
07/02/05 12:20:22 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
07/02/05 12:20:22 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
07/02/05 12:20:22 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819)
07/02/05 12:20:22 at java.lang.Thread.run(Thread.java:595)
07/02/05 12:20:22 Caused by: java.lang.InstantiationException: Error initializing ejb-modules: Unknown assembly-descriptor subtag: interceptor-binding, see section 22.5 of the EJB specification
07/02/05 12:20:22 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1056)
07/02/05 12:20:22 at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:210)
07/02/05 12:20:22 at com.evermind.server.Application.setConfig(Application.java:391)
07/02/05 12:20:22 at com.evermind.server.Application.setConfig(Application.java:308)
07/02/05 12:20:22 at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1771)
07/02/05 12:20:22 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:507)
07/02/05 12:20:22 ... 6 more
07/02/05 12:20:22 Caused by: com.evermind.server.ejb.deployment.InvalidEJBAssemblyException: Unknown assembly-descriptor subtag: interceptor-binding, see section 22.5 of the EJB specification
07/02/05 12:20:22 at com.evermind.server.ejb.deployment.EJBPackage.parseAssemblyDescriptor(EJBPackage.java:665)
07/02/05 12:20:22 at com.evermind.server.ejb.deployment.EJBPackage.parseEJBModule(EJBPackage.java:481)
07/02/05 12:20:22 at com.evermind.server.ejb.EJBPackageDeployment.parseMetaData(EJBPackageDeployment.java:973)
07/02/05 12:20:22 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:831)
07/02/05 12:20:22 ... 11 more
2007-02-05 12:20:22.984 NOTIFICATION Application Deployer for seam-icefaces FAILED.
2007-02-05 12:20:22.984 NOTIFICATION Application UnDeployer for seam-icefaces STARTS.
2007-02-05 12:20:23.046 NOTIFICATION Removing all web binding(s) for application seam-icefaces from all web site(s)
2007-02-05 12:20:23.250 ERROR java.lang.InstantiationException: Error initializing ejb-modules: Unknown assembly-descriptor subtag: interceptor-binding, see section 22.5 of the EJB specification
2007-02-05 12:20:23.281 NOTIFICATION Application UnDeployer for seam-icefaces COMPLETES.
2007-02-05 12:20:23.281 WARNING java.lang.InstantiationException: Error initializing ejb-modules: Unknown assembly-descriptor subtag: interceptor-binding, see section 22.5 of the EJB specification
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011164#4011164
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011164
19Â years, 2Â months
[Tomcat, HTTPD, Servlets & JSP] - Re: Major problem using error-page element in web.xml
by flarosa
Here's some more information about my issue -
I've determined that the problem occurs when a request for a document in a non-existent directory is received, and replaced with /default.jsp.
Default.jsp contains relative references to a CSS file and some image files. When the browser tries to get these, it tries to get them out of the non-existent directory specified in the original URL; this is when the exceptions occur in the log.
I would guess that what is happening is this:
(a) The browser tries to retrieve the image from the bad URL;
(b) The server starts serving up the default.jsp page instead;
(c) The browser sees that it's getting HTML instead of an image, and closes its socket;
(d) The server gets an exception while trying to write to the socket, and in doing so, fails to release some resource.
Changing the references in default.jsp to absolute references does prevent the problem from occuring regularly. Still, if this is really what is happening, it's very troubling. There are lots of other ways sockets can close early, not to mention the potential for someone to write a program specifically to exploit the problem.
In fact, a check of my logs shows that I'm still getting the exception but in much smaller numbers. Probably because web pages unknown to me are linking to bad images (there was an old web site at the same domain name for many years, hence the need for the 404 redirect).
Frank
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011157#4011157
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011157
19Â years, 2Â months
[JBossCache] - Re: Jboss Caching issue
by bhavranjan
| Thanks for ur reply
|
| I have already checked that , here is my confi.xml files
|
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!-- ===================================================================== -->
| <!-- -->
| <!-- Sample TreeCache Service Configuration -->
| <!-- -->
| <!-- ===================================================================== -->
|
| <server>
|
| <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar"/>
|
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
|
| <mbean code="org.jboss.cache.TreeCache"
| name="jboss.cache:service=TreeCache">
|
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
|
| <!--
| Configure the TransactionManager
| -->
| <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
|
| <!--
| Node locking level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
|
| <!--
| Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| INVALIDATION_ASYNC
| INVALIDATION_SYNC
| -->
|
|
| <attribute name="CacheMode">LOCAL</attribute>
|
| <!-- New 1.3.x cache loader config block -->
| <attribute name="CacheLoaderConfiguration">
| <config>
| <!-- if passivation is true, only the first cache loader is used; the rest are ignored -->
| <passivation>false</passivation>
| <preload>/demo</preload>
| <shared>false</shared>
|
| <!-- we can now have multiple cache loaders, which get chained -->
| <cacheloader>
| <class>org.jboss.cache.loader.FileCacheLoader</class>
| <!-- same as the old CacheLoaderConfig attribute -->
| <properties>
| location=/tmp/bhavFileStore
| </properties>
|
| <!-- only one cache loader in the chain may set fetchPersistentState to true.
| An exception is thrown if more than one cache loader sets this to true. -->
| <fetchPersistentState>true</fetchPersistentState>
| <!-- determines whether this cache loader ignores writes - defaults to false. -->
| <ignoreModifications>false</ignoreModifications>
| <!-- if set to true, purges the contents of this cache loader when the cache starts up.
| Defaults to false. -->
| <purgeOnStartup>false</purgeOnStartup>
| </cacheloader>
|
|
|
| </config>
|
| </attribute>
| <!--
| The max amount of time (in milliseconds) we wait until the
| initial state (ie. the contents of the cache) are retrieved from
| existing members in a clustered environment
| -->
| <attribute name="InitialStateRetrievalTimeout">20000</attribute>
|
| <!--
| Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <attribute name="SyncReplTimeout">15000</attribute>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <attribute name="LockAcquisitionTimeout">10000</attribute>
|
|
| <!-- Name of the eviction policy class. Not supported now. -->
| <attribute name="EvictionPolicyClass"></attribute>
| </mbean>
|
| <mbean
| code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
| name="jboss:service=proxyFactory,type=jrmp,target=factory">
| <attribute
| name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
| <attribute
| name="TargetName">jboss.cache:service=TreeCache</attribute>
| <attribute name="JndiName">TreeCache</attribute> <attribute
| name="InvokeTargetMethod">true</attribute> <attribute
| name="ExportedInterface">org.jboss.cache.TreeCacheMBean</attribute>
| <attribute name="ClientInterceptors"> <iterceptors>
| <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
| <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
| <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
| </iterceptors> </attribute>
| <depends>jboss:service=invoker,type=jrmp</depends>
| <depends>jboss.cache:service=TreeCache</depends>
| </mbean>
| </server>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011156#4011156
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011156
19Â years, 2Â months
[JBoss Seam] - Error in deployment
by merajcal
Whaen I am trying to deploy Icefaces example I am facing foloowing error
2007-02-05 12:00:48.687 ERROR J2EE EJB3027 [seam-icefaces] An error occured deploying EJB module: javax.ejb.EJBException: @PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.; nested exception is: java.lang.InstantiationException: @PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.
2007-02-05 12:00:48.718 NOTIFICATION application : seam-icefaces is in failed state
Feb 5, 2007 12:00:48 PM com.evermind.server.Application setConfig
WARNING: Application: seam-icefaces is in failed state as initialization failedjava.lang.InstantiationException: Error initializing ejb-modules: @PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.; nested exception is: java.lang.InstantiationException: @PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.
07/02/05 12:00:48 oracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: Error initializing ejb-modules: @PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.; nested exception is: java.lang.InstantiationException: @PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.
07/02/05 12:00:48 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:510)
07/02/05 12:00:48 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:191)
07/02/05 12:00:48 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
07/02/05 12:00:48 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
07/02/05 12:00:48 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
07/02/05 12:00:48 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819)
07/02/05 12:00:48 at java.lang.Thread.run(Thread.java:595)
07/02/05 12:00:48 Caused by: java.lang.InstantiationException: Error initializing ejb-modules: @PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.; nested exception is: java.lang.InstantiationException: @PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.
07/02/05 12:00:48 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1056)
07/02/05 12:00:48 at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:210)
07/02/05 12:00:48 at com.evermind.server.Application.setConfig(Application.java:391)
07/02/05 12:00:48 at com.evermind.server.Application.setConfig(Application.java:308)
07/02/05 12:00:48 at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1771)
07/02/05 12:00:48 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:507)
07/02/05 12:00:48 ... 6 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011155#4011155
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011155
19Â years, 2Â months
[JBossWS] - Re: Problems with Jboss and Sun's 1.6 JDK
by akirainoue
Can you share how to implement web service client stub as an EJB, generated by sun jwsdp (wscompile) in jboss?
My EJB is calling web service to 3rd party provider. The client stub is generated through Sun's jwsdp. However I encountered the following exception:
java.lang.ClassCastException: org.jboss.ws.soap.SOAPMessageImpl
at com.sun.xml.rpc.client.StubBase._postSendingHook(StubBase.java:231)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:324)
I added the following jar from jwsdp to the lib dir:
FastInfoset.jar
jaxrpc-impl.jar
jaxrpc-spi.jar
jsr173_api.jar
saaj-impl.jar
I am running jboss-4.0.5.GA.
How can I resolve the problem? Can the stub generated by jwsdp be used in JBoss or any application other the Sun?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011153#4011153
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011153
19Â years, 2Â months