[JBoss-dev] [ jboss-Bugs-1472788 ] java.lang.NoSuchMethodError: javax.servlet.http.HttpServletR

2006-04-19 Thread SourceForge.net
Bugs item #1472788, was opened at 2006-04-19 12:23
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1472788group_id=22866

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Nishant Saini (nishantsaini)
Assigned to: Nobody/Anonymous (nobody)
Summary: java.lang.NoSuchMethodError: javax.servlet.http.HttpServletR

Initial Comment:
I am using HttpNamingContextFactory for looking up an
EJB Home deployed on server. I am using JBoss 4.0.4-RC1
and I get the following error:


java.lang.NoSuchMethodError:
javax.servlet.http.HttpServletResponse.resetBuffer()V
at
org.jboss.invocation.http.servlet.InvokerServlet.processRequest(InvokerServlet.java:193)
at
org.jboss.invocation.http.servlet.InvokerServlet.doGet(InvokerServlet.java:214)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:54)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:174)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)




Can you please suggest the solution ? I think there is
some incompatible jar from which HttpServletResponse
class is being loaded and the method resetBuffer() must
have been present at compile time.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1472788group_id=22866


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1402221 ] DLQueue no ExceptionListener

2006-01-10 Thread SourceForge.net
Bugs item #1402221, was opened at 2006-01-10 23:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1402221group_id=22866

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: JBossMQ
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: RE (emberson)
Assigned to: Nobody/Anonymous (nobody)
Summary: DLQueue no ExceptionListener

Initial Comment:
After the DLQHandler creates a Connection it does 
not register an ExceptionListener for that 
Connection. As a result, if the Connection fails,
1) the Connection is not re-established and 2)
the logfile fills up with the reports in the
asynchFailure Connection method.

Fix is something like:

DLQHandler implements ExceptionListener.
After creating Connection, register this.

onException(...) {
   try {
  kill Connection
   } catch (...) { ... }
   try {
  create Connection
  register this as ExceptionListener
   } catch (...) {...}
}

Please put fix into 3.2.8 and next 4.x release.
Thanks.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1402221group_id=22866


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1232189 ] Error creating a new config using the Server Navigatior

2005-07-04 Thread SourceForge.net
Bugs item #1232189, was opened at 2005-07-04 12:45
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1232189group_id=22866

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: JBoss-IDE
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andreas Piater (ikeapiat)
Assigned to: Nobody/Anonymous (nobody)
Summary: Error creating a new config using the Server Navigatior

Initial Comment:
Environment:
java 1.5.0_04
eclipse-SDK-3.1-win32.zip
jboss-ide 1.4.1.e31-jre15

When I want to create a new Jboss Server configuration
the following error occurs:

An error has occurred. See error log for more details.

I the log file there is the following stack trace:

!SESSION 2005-07-04 13:41:21.500
---
eclipse.buildId=I20050627-1435
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32,
NL=de_DE
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.jface 4 2 2005-07-04 13:41:48.531
!MESSAGE Problems occurred when invoking code from
plug-in: org.eclipse.jface.
!STACK 0
java.lang.NoSuchMethodError:
org.eclipse.jdt.internal.debug.ui.launcher.LauncherMessages.getString(Ljava/lang/String;)Ljava/lang/String;
at
org.jboss.ide.eclipse.launcher.ui.configuration.ServerLaunchArgumentsTab.createControl(ServerLaunchArgumentsTab.java:86)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showTabsFor(LaunchConfigurationTabGroupViewer.java:720)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:639)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:519)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$5.run(LaunchConfigurationTabGroupViewer.java:471)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:488)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:452)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:789)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:601)
at
org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:763)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
at
org.eclipse.core.runtime.Platform.run(Platform.java:783)
at
org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
at
org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148)
at
org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:761)
at
org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1453)
at
org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:379)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.handleConfigurationAdded(LaunchConfigurationView.java:270)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.launchConfigurationAdded(LaunchConfigurationView.java:251)
at
org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.run(LaunchManager.java:1581)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
at
org.eclipse.core.runtime.Platform.run(Platform.java:783)
at
org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.notify(LaunchManager.java:1605)
at
org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:806)
at
org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.writeNewFile(LaunchConfigurationWorkingCopy.java:278)
at
org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave0(LaunchConfigurationWorkingCopy.java:233)
at
org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave(LaunchConfigurationWorkingCopy.java:174)
at
org.eclipse.debug.internal.ui.launchConfigurations.CreateLaunchConfigurationAction.performAction(CreateLaunchConfigurationAction.java:75)
at
org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction$1.run

[JBoss-dev] [ jboss-Feature Requests-1189817 ] JBossJCache

2005-04-26 Thread SourceForge.net
Feature Requests item #1189817, was opened at 2005-04-25 14:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376688aid=1189817group_id=22866

Category: Other
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Joe Ryan (joeryan)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBossJCache

Initial Comment:
Need  a way to figure out what extra memory each vm 
instance should have for the TreeCache. Maybe 
methods on the TreeCache could report stats 
dynamically.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376688aid=1189817group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1176717 ] UsersRolesLoginModule has limited configurations in sar

2005-04-04 Thread SourceForge.net
Bugs item #1176717, was opened at 2005-04-04 19:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1176717group_id=22866

Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: rwag (rollin368)
Assigned to: Nobody/Anonymous (nobody)
Summary: UsersRolesLoginModule has limited configurations in sar

Initial Comment:
I have an EJB application, headless without the web, that uses 
UsersRolesLoginModule for JAAS security.  Originally I defined 
my application-policy in the server's conf/login-config.xml.  I 
defined the usersProperties and rolesProperties that were 
contained in the EJB. 
 
Later on I decided to move that configuration to a sar file.  I 
found that the sar's META-INF/login-config.xml did not appear 
to accept my usersProperties or rolesProperties 
configurations.  As a result I had to comment out those 
module-options and use the default roles.properties and 
users.properties files. 
 
It is a relatively minor bug but took time.  Also I started to 
wonder how much can be defined in a sar versus the 
server-config. 

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1176717group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Feature Requests-1163269 ] run.* startup scripts

2005-03-14 Thread SourceForge.net
Feature Requests item #1163269, was opened at 2005-03-14 21:49
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376688aid=1163269group_id=22866

Category: JBossServer
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Lars Kral (lkral)
Assigned to: Nobody/Anonymous (nobody)
Summary: run.* startup scripts

Initial Comment:
How about adding a %JBOSS_OPTS% variable to the list of
JVM args? Using the %JAVA_ARGS% is not flexible enough
to pass -Xmx or -Xms (or something similar) because it
also affects the tomcat startup script for example.


Cheers,
Lars

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376688aid=1163269group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Feature Requests-1163272 ] DO NOT POST HERE: Use http://jira.jboss.com

2005-03-14 Thread SourceForge.net
Feature Requests item #1163272, was opened at 2005-03-14 20:57
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376688aid=1163272group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to: Nobody/Anonymous (nobody)
Summary: DO NOT POST HERE: Use http://jira.jboss.com

Initial Comment:
Use http://jira.jboss.com

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376688aid=1163272group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1161789 ] SerializableResultSetMetaData.getColumnCount

2005-03-11 Thread SourceForge.net
Bugs item #1161789, was opened at 2005-03-12 02:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1161789group_id=22866

Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Evgeniy (evgen_ii)
Assigned to: Nobody/Anonymous (nobody)
Summary: SerializableResultSetMetaData.getColumnCount

Initial Comment:
Method getColumnCount of 
SerializableResultSetMetaData class returns wrong 
number of columns in resultset. It is as great as actual 
count + 1 constantly. The problem is obvious - in 
constructor internal array is created with the actual size 
+ 1 

int count = metaData.getColumnCount();
  columnData = new ColumnData[count+1];


and than the lenght of this array is returned as column 
count:

public int getColumnCount() throws SQLException
   {
  return columnData.length;
   }

And we get wrong count of columns in resulset.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1161789group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1151858 ] Cannot type characters '}' and ']'

2005-02-25 Thread SourceForge.net
Bugs item #1151858, was opened at 2005-02-25 16:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1151858group_id=22866

Category: JBoss-IDE
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Phaiax (phaiax)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot type characters '}' and ']'

Initial Comment:
I'm running Eclipse 3.0.1 and JBoss-IDE 1.4.1-e30. As 
soon as JBoss-IDE plugin and features folders are 
installed, I cannot type the characters '}' and ']' (AltGr+0 
and AltGr+9 on a german keyboard) in any Eclipse 
editor. All other characters work fine. After uninstalling 
JBoss-IDE, the problem's gone. I tried it also with a 
perfectly new eclipse installation.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1151858group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1146303 ] error in MdbEjb.jsp page

2005-02-22 Thread SourceForge.net
Bugs item #1146303, was opened at 2005-02-22 15:57
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146303group_id=22866

Category: JBossWeb
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: matrat jean-michel (jmmatrat)
Assigned to: Nobody/Anonymous (nobody)
Summary: error in MdbEjb.jsp page

Initial Comment:
When I click on the link to get infos about a mdb I've
got this

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error ()
that prevented it from fulfilling this request.

exception

org.apache.jasper.JasperException: Impossible de
compiler la classe pour la JSP

Une erreur s'est produite à la ligne: 95 dans le
fichier jsp: /MdbEjb.jsp
Erreur de servlet générée:
D:\java\plateforme\jboss-4.0.1sp1\server\default\work\jboss.web\localhost\web-console\org\apache\jsp\MdbEjb_jsp.java:189:
cannot resolve symbol
symbol  : method isStatisticsProvider ()
location: interface
org.jboss.management.j2ee.MessageDrivenBeanMBean
if (ejb.isStatisticsProvider())
   ^


Une erreur s'est produite à la ligne: 127 dans le
fichier jsp: /MdbEjb.jsp
Erreur de servlet générée:
D:\java\plateforme\jboss-4.0.1sp1\server\default\work\jboss.web\localhost\web-console\org\apache\jsp\MdbEjb_jsp.java:223:
cannot resolve symbol
symbol  : method getStats ()
location: interface
org.jboss.management.j2ee.MessageDrivenBeanMBean
javax.management.j2ee.statistics.MessageDrivenBeanStats
stats =
(javax.management.j2ee.statistics.MessageDrivenBeanStats)ejb.getStats
();
  
  
  ^


Une erreur s'est produite à la ligne: 127 dans le
fichier jsp: /MdbEjb.jsp
Erreur de servlet générée:
Note:
D:\java\plateforme\jboss-4.0.1sp1\server\default\work\jboss.web\localhost\web-console\org\apache\jsp\MdbEjb_jsp.java
uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
2 errors




org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)

org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332)
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:412)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:472)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)

org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)

note The full stack trace of the root cause is
available in the Apache Tomcat/5.0.28 logs.
Apache Tomcat/5.0.28

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146303group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1146382 ] USE JIRA TO POST BUG REPORTS

2005-02-22 Thread SourceForge.net
Bugs item #1146382, was opened at 2005-02-22 16:39
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146382group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to: Nobody/Anonymous (nobody)
Summary: USE JIRA TO POST BUG REPORTS

Initial Comment:
http://jira.jboss.com

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146382group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1146384 ] POST BUG REPORTS ON JIRA

2005-02-22 Thread SourceForge.net
Bugs item #1146384, was opened at 2005-02-22 16:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146384group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to: Nobody/Anonymous (nobody)
Summary: POST BUG REPORTS ON JIRA

Initial Comment:
http://jira.jboss.com

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146384group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1146385 ] USE JIRA

2005-02-22 Thread SourceForge.net
Bugs item #1146385, was opened at 2005-02-22 16:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146385group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to: Nobody/Anonymous (nobody)
Summary: USE JIRA

Initial Comment:
http://jira.jboss.com

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146385group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1146386 ] GO HERE: http://jira.jboss.com

2005-02-22 Thread SourceForge.net
Bugs item #1146386, was opened at 2005-02-22 16:41
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146386group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to: Nobody/Anonymous (nobody)
Summary: GO HERE: http://jira.jboss.com

Initial Comment:
.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1146386group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1144070 ] NullPointerException during creation of debug configuration

2005-02-18 Thread SourceForge.net
Bugs item #1144070, was opened at 2005-02-18 22:32
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1144070group_id=22866

Category: JBoss-IDE
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: MiNe (kopv)
Assigned to: Nobody/Anonymous (nobody)
Summary: NullPointerException during creation of debug configuration 

Initial Comment:
In the debug configuration dialog occures a dialog box: 
?An error has occurred. See error log for more details? 
(Log file details at 
the bottom of this description). If I do not change the 
Name of the 
configuration the error occurs when I try to select it. 
The error immediately 
occurs, when I change the name of the configuration. I 
am using a gentoo box 
with amd64 and the standard emerged packages: 

blackdown-jdk-1.4.2.01 
Jboss-ide 1.4.1-e30 
eclipse-3.0.1-r2 
Code: 

!ENTRY org.eclipse.core.runtime 4 2 Feb 08, 2005 
23:26:49.608
!MESSAGE Problems occurred when invoking code from 
plug-
in: org.eclipse.core.runtime.
!STACK 0
java.lang.NullPointerException
at 
org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab.
updateServerConfigurati
ons(HomeTab.java:328)
at 
org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab.
access$1
(HomeTab.java:311)
at 
org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab
$1.modifyText
(HomeTab.java:138)
at 
org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:187)
at 
org.eclipse.swt.widgets.EventTable.sendEvent
(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent
(Widget.java:954)
at org.eclipse.swt.widgets.Widget.sendEvent
(Widget.java:978)
at org.eclipse.swt.widgets.Widget.sendEvent
(Widget.java:959)
at org.eclipse.swt.widgets.Text.setText
(Text.java:1563)
at 
org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab.
updateHomedirFromConfig
(HomeTab.java:286)
at 
org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab.
initializeFrom
(HomeTab.java:219)
at 
org.eclipse.debug.ui.AbstractLaunchConfigurationTabGro
up.initializeFrom
(AbstractLaunchConfigurationTabGroup.java:86)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Launc
hConfigurationTabGroupV
iewer.displayInstanceTabs
(LaunchConfigurationTabGroupViewer.java:540)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Launc
hConfigurationTabGroupV
iewer$5.run
(LaunchConfigurationTabGroupViewer.java:473)
at 
org.eclipse.swt.custom.BusyIndicator.showWhile
(BusyIndicator.java:69)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Launc
hConfigurationTabGroupV
iewer.inputChanged
(LaunchConfigurationTabGroupViewer.java:490)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Launc
hConfigurationTabGroupV
iewer.setInput
(LaunchConfigurationTabGroupViewer.java:454)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Launc
hConfigurationsDialog.h
andleLaunchConfigurationSelectionChanged
(LaunchConfigurationsDialog.java:775)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Launc
hConfigurationsDialog$2
.selectionChanged
(LaunchConfigurationsDialog.java:585)
at org.eclipse.jface.viewers.Viewer$2.run
(Viewer.java:159)
at 
org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:616)
at org.eclipse.core.runtime.Platform.run
(Platform.java:747)
at 
org.eclipse.jface.viewers.Viewer.fireSelectionChanged
(Viewer.java:157)
at 
org.eclipse.jface.viewers.StructuredViewer.updateSelecti
on
(StructuredViewer.java:1394)
at 
org.eclipse.jface.viewers.StructuredViewer.setSelection
(StructuredViewer.java:1093)
at org.eclipse.jface.viewers.Viewer.setSelection
(Viewer.java:356)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Launc
hConfigurationView.laun
chConfigurationRemoved
(LaunchConfigurationView.java:284)
at 
org.eclipse.debug.internal.core.LaunchManager$Configur
ationNotifier.run
(LaunchManager.java:1484)
at 
org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:616)
at org.eclipse.core.runtime.Platform.run
(Platform.java:747)
at 
org.eclipse.debug.internal.core.LaunchManager$Configur
ationNotifier.notify
(LaunchManager.java:1505)
at 
org.eclipse.debug.internal.core.LaunchManager.launchCo
nfigurationDeleted
(LaunchManager.java:736)
at 
org.eclipse.debug.internal.core.LaunchConfiguration.dele
te
(LaunchConfiguration.java:317)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Delet
eLaunchConfigurationAct
ion.performAction
(DeleteLaunchConfigurationAction.java:65)
at 
org.eclipse.debug.internal.ui.launchConfigurations.Abstr
actLaunchConfigurationA
ction$1.run
(AbstractLaunchConfigurationAction.java:103)
at 
org.eclipse.swt.custom.BusyIndicator.showWhile

[JBoss-dev] [ jboss-Bugs-1144212 ] Adding finally to constructor

2005-02-18 Thread SourceForge.net
Bugs item #1144212, was opened at 2005-02-19 11:58
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1144212group_id=22866

Category: Javassist
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: C. K. So (ckso)
Assigned to: Shigeru Chiba (chiba)
Summary: Adding finally to constructor

Initial Comment:
I have the similar problem with issue 997458.
I tried to insert code by ctconstructor.insertAfter(s,
true), when I run the program, it cause VerifyError,
and super() or this() must be the first call.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1144212group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1124805 ] java deadlock during starutp

2005-02-17 Thread SourceForge.net
Bugs item #1124805, was opened at 2005-02-17 15:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1124805group_id=22866

Category: None
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: David Boon (davidmboon)
Assigned to: Nobody/Anonymous (nobody)
Summary: java deadlock during starutp

Initial Comment:
Noticed very slow startup, did kill -3 and found
javadeadlock.  I've pasted the relevant dead lock, and
attached the entire thread dump.

Found one Java-level deadlock:
=
MessageDispatcher up processing thread:
  waiting to lock monitor 0xa4d393d4 (object
0xb9a6d310, a org.jboss.system.ServiceController),
  which is held by main
main:
  waiting to lock monitor 0x080d0854 (object
0xba632828, a java.util.HashMap),
  which is held by MessageDispatcher up processing thread

Java stack information for the threads listed above:
===
MessageDispatcher up processing thread:
at
org.jboss.system.ServiceController.install(ServiceController.java:199)
- waiting to lock 0xb9a6d310 (a
org.jboss.system.ServiceController)
at
sun.reflect.GeneratedMethodAccessor44.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at
org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at
org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at
org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.install(Unknown Source)
at
org.jboss.deployment.SARDeployer.create(SARDeployer.java:204)
at
org.jboss.deployment.MainDeployer.create(MainDeployer.java:783)
at
org.jboss.deployment.MainDeployer.create(MainDeployer.java:775)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:588)
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:324)
at
org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at
org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at
org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at
org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at
org.jboss.ha.singleton.HASingletonController.invokeSingletonMBeanMethod(HASingletonController.java:114)
at
org.jboss.ha.singleton.HASingletonController.startSingleton(HASingletonController.java:63)
at
org.jboss.ha.singleton.HASingletonSupport.makeThisNodeMaster(HASingletonSupport.java:141)
at
org.jboss.ha.singleton.HASingletonSupport.partitionTopologyChanged(HASingletonSupport.java:118)
at
org.jboss.ha.jmx.HAServiceMBeanSupport$1.replicantsChanged(HAServiceMBeanSupport.java:197)
at
org.jboss.ha.framework.server.DistributedReplicantManagerImpl.notifyKeyListeners(DistributedReplicantManagerImpl.java:699)
- locked 0xba632828 (a java.util.HashMap)
at
org.jboss.ha.framework.server.DistributedReplicantManagerImpl._remove(DistributedReplicantManagerImpl.java:509)
at
sun.reflect.GeneratedMethodAccessor64.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236)
at
org.jboss.ha.framework.server.HAPartitionImpl.handle(HAPartitionImpl.java:828)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615)
at
org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512)
at
org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326)
at
org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722)
at
org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554

[JBoss-dev] [ jboss-Bugs-1123074 ] impossible to auto create timer table

2005-02-15 Thread SourceForge.net
Bugs item #1123074, was opened at 2005-02-15 03:57
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1123074group_id=22866

Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Nathan Cheng (nathan_w_cheng)
Assigned to: Nobody/Anonymous (nobody)
Summary: impossible to auto create timer table

Initial Comment:
The method createTableIfNotExists() in

jboss-4.0.1-
src\server\src\main\org\jboss\ejb\txtimer\GeneralPurpose
DatabasePersistencePlugin.java

references an mbean attribute 
called TypeMappingMetaData; however, the class 
org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary
, which is expected to provide the value of this 
attribute, has no getter/setter methods for this 
attribute, and in fact there are no classes in the entire 
code base that has setter method 
for TypeMappingMetaData. This means that the 
getAttribute call at the beginning of 
createTableIfNotExists() will always return null, and so 
the method will always throw an IllegalStateException, 
and so the timer table will never get created. So if you 
don't manually create this table, or write your own 
persistence plugin, there is no way to have EJB timers 
persisted.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1123074group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1122305 ] finder type mapping for boolean datatype in MaxDB wrong

2005-02-14 Thread SourceForge.net
Bugs item #1122305, was opened at 2005-02-14 12:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1122305group_id=22866

Category: JBossCMP
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Ingo Brüll (ibruell)
Assigned to: Nobody/Anonymous (nobody)
Summary: finder type mapping for boolean datatype in MaxDB wrong

Initial Comment:
In one of my entity beans i have an attribute of type
boolean. Now i want to use this attribute in ejbQL to
select all entities set this attribute to 'true':

SELECT OBJECT(o) FROM Type AS o WHERE o.typeClass.type
= ?1 AND o.typeClass.internal = false

The EJBQL parser generates a select statement like:
SELECT a,b,c from table where booleanAttr = 0 [...].

The database supports real booleans so it requires a
select statement like:
SELECT a,b,c from table where booleanAttr = false [...].

I have not found a way to configure thos behavior and i
have not seen how the parsing works, now.

My environment:
- JBoss 4.0.1
- jdk1.5.0-update1
- debian sarge
- maxdb 7.5.00.23-1
- jdbc driver: sapdbc-7_6_00_00_3264.jar

I have tried that with jboss-3.2.7 also and had the
same error.

Here a snippet from the log:

2005-02-14 10:47:52,351 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Type#findNonInternalByTypeClass]
Executing SQL: SELECT t0_o.id FROM TYPE t0_o, TY
PE t1_o_typeClass WHERE (t1_o_typeClass.type = ? AND
t1_o_typeClass.xinternal = 1 AND
t0_o.TYPE_CLASS_ID=t1_o_typeClass.id)
2005-02-14 10:47:52,399 ERROR
[org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Type#findNonInternalByTypeClass]
Find failed
com.sap.dbtech.jdbc.exceptions.DatabaseException:
[-8006] (at 114): Data types must be compatible
at
com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:71)
at
com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:830)
at
com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:489)
at
com.sap.dbtech.jdbc.CallableStatementSapDB.sendCommand(CallableStatementSapDB.java:1646)
at
com.sap.dbtech.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:778)
at
com.sap.dbtech.jdbc.CallableStatementSapDB.doParse(CallableStatementSapDB.java:234)
at
com.sap.dbtech.jdbc.CallableStatementSapDB.constructor(CallableStatementSapDB.java:185)
at
com.sap.dbtech.jdbc.CallableStatementSapDB.init(CallableStatementSapDB.java:87)
at
com.sap.dbtech.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.java:722)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:355)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:205)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:190)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:128)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntitiesCommand.execute(JDBCFindEntitiesCommand.java:40)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntities(JDBCStoreManager.java:598)
at
org.jboss.ejb.plugins.CMPPersistenceManager.findEntities(CMPPersistenceManager.java:322)
at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntities(CachedConnectionInterceptor.java:321)
at
org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:649)
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.invocation.Invocation.performCall(Invocation.java:345)
at
org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1113)
at
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90)
at
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:192)
at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:212)
at
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90)
at
org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:117)
at
org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61)
at
org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28)
at
org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:41)
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:109

[JBoss-dev] [ jboss-Bugs-1120703 ] NullPointerException in MessageReference.init

2005-02-11 Thread SourceForge.net
Bugs item #1120703, was opened at 2005-02-11 12:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1120703group_id=22866

Category: JBossMQ
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Sergey Marchuk (smarchuk)
Assigned to: Nobody/Anonymous (nobody)
Summary: NullPointerException in MessageReference.init

Initial Comment:
On server startup JBoss tries to rebuild its JMS queue 
and fails if any JMS message is stored in the queue with
org.jboss.mq.SpyJMSException: Could not rebuild the 
queue from the queue's tranaction log.; - nested 
throwable: (java.lang.NullPointerException)

It happens both with File and Rolling Logged Persistence 
Managers. Full exceptions traces for both PMs are 
attached in the file.

Short investigation of source code shows that at 
org.jboss.mq.server.MessageCache.add
(MessageCache.java:115) null is passed as BasicQueue 
parameter to MessageCache.addInternal method. In 
MessageCache.addInternal this null is passed to newly 
crated instance of 
org.jboss.mq.server.MessageReference. So in 
org.jboss.mq.server.MessageReference.init
(MessageReference.java:100) there is direct access to 
BasicQueue queue parameter (which is null in our case) 
that causes NullPointerException. Here is a code 
snapshot:
...
  else if (queue.parameters.redeliveryDelay  0)
 this.redeliveryDelay = 
queue.parameters.redeliveryDelay;
...


I believe is should be fixed by additional null-checking, 
e.g. like that:
...
  else if (queue != null  
queue.parameters.redeliveryDelay  0)
 this.redeliveryDelay = 
queue.parameters.redeliveryDelay;
...
Some other ways might exist.


Versions used: JBoss 3.2.6, JDK1.4.2, WIN2000.


Thanks

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1120703group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1118578 ] NullPointerException getAttributes() in JBossCacheService

2005-02-08 Thread SourceForge.net
Bugs item #1118578, was opened at 2005-02-08 12:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1118578group_id=22866

Category: JBossCache
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: olivier martin (omartin_it)
Assigned to: Nobody/Anonymous (nobody)
Summary: NullPointerException getAttributes() in JBossCacheService

Initial Comment:
the method getAttributes use the method
getAttributesKeys which can return null if somthing
failed in the cache
but, referring to the code in jboss 3.2.6 or 3.2.7 line
236 in class
org.jboss.web.tomcat.tc5.session.JBossCacheService, 
the code above is called:
Set set = getAttributeKeys(id);
...
for (Iterator it = set.iterator(); it.hasNext();)
the NPE comes from set.iterator().

On the client side, when the page returns is blank and
we can see above stacktrace in the log.

the stack:
An exception or error occurred in the container during
the request processing
java.lang.NullPointerException
at
org.jboss.web.tomcat.tc5.session.JBossCacheService.getAttributes(JBossCacheService.java:236)
at
org.jboss.web.tomcat.tc5.session.AttributeBasedClusteredSession.populateAttributes(AttributeBasedClusteredSession.java:101)
at
org.jboss.web.tomcat.tc5.session.AttributeBasedClusteredSession.initAfterLoad(AttributeBasedClusteredSession.java:93)
at
org.jboss.web.tomcat.tc5.session.JBossCacheManager.loadSession(JBossCacheManager.java:364)
at
org.jboss.web.tomcat.tc5.session.JBossCacheManager.findSession(JBossCacheManager.java:273)
at
org.apache.coyote.tomcat5.CoyoteRequest.doGetSession(CoyoteRequest.java:2252)
at
org.apache.coyote.tomcat5.CoyoteRequest.getSession(CoyoteRequest.java:2116)
at
org.apache.coyote.tomcat5.CoyoteRequestFacade.getSession(CoyoteRequestFacade.java:526)
at
org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:86)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)



--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1118578group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1114376 ] JBoss-AOP v1.1 - NullPointerException in toString()

2005-02-01 Thread SourceForge.net
Bugs item #1114376, was opened at 2005-02-01 16:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1114376group_id=22866

Category: Aspects
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: PaulE (ut_paule)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBoss-AOP v1.1 - NullPointerException in toString()

Initial Comment:
In org.jboss.aop.introduction.InterfaceIntroduction
@version $Revision: 1.9 $

   public String toString()
   {
  return InterfaceIntroduction:{ name= + name + ; 
class= + classExpr.getClass().getName() + ; ast= + 
ast + ;interfaces= + interfaces + ;mixins= + mixins 
+ };
   }

Throws an NPE when classExpr is null. The following is 
an example where this can happen...


InterfaceIntroduction ii = new InterfaceIntroduction
(name, new TypeExpressionParser(new StringReader
(class(+className+))).Start() , INTRODUCTIONS);
AspectManager.instance().addInterfaceIntroduction(ii);
log.debug(PRE-bind(): Applied!  + ii );

the last line does an implicit ii.toString() and throws the 
NPE.



--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1114376group_id=22866


---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1112731 ] MEMBER OF Bug in SQL92 Compiler

2005-01-30 Thread SourceForge.net
Bugs item #1112731, was opened at 2005-01-30 20:00
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1112731group_id=22866

Category: JBossCMP
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Jens Bräuer (jensbr)
Assigned to: Nobody/Anonymous (nobody)
Summary: MEMBER OF Bug in SQL92 Compiler

Initial Comment:
Hi there !

I was experimenting with dynamic created
JBossQL-Queries, when i found what i expect to be a bug.
Ok, here some facts about the app i am writing:

2 (for this post relevant) Entity-Beans:

- Publication with a 1:M CMR to Author
- Author with fields firstName and lastName

Writing a method that creates queries on the fly, i
found that using the EJBToSQL92Compiler delivers
incorrect results.
I am searching a Publication written by 2 Authors i
know the firstName of. So i expected the query

SELECT p.id FROM Publication AS p, Author AS a1, Author
AS a2 WHERE (a1.firstName = 'Timo') AND (a1 MEMBER OF
p.author) AND ( a2.firstName = 'Jens' ) AND ( a2 MEMBER
OF p.author )

to deliver the id of this Publication.
This is true for the default compiler, but using the
SQL92 one also delivers another Publication in the
result. As i do only tests, there are only two entries
in the db. I double-checked the database and returning
only one Publication would definately be correct.

Ok: here is a test-run with the default EJBQL-Compiler:
---
[PublicationLocalHome] queryString: SELECT p.id FROM
Publication AS p, Author AS a1, Author AS a2 WHERE
(a1.firstName = 'Timo') AND (a1 MEMBER OF p.author) AND
( a2.firstName = 'Jens' ) AND ( a2 MEMBER OF p.author )

org.jboss.ejb.plugins.cmp.jdbc.JDBCDynamicQLQuery.Publication#ejbSelectGeneric
null - Executing SQL: 
SELECT t0_p.id FROM PUBLICATION t0_p, AUTHOR t1_a1,
AUTHOR t4_a2 WHERE ((t1_a1.firstName = 'Timo') AND
(EXISTS (SELECT t3_p_author_RELATION_TABLE.authorId
FROM PUBLICATIONAUTHORS t3_p_author_RELATION_TABLE
WHERE t0_p.id=t3_p_author_RELATION_TABLE.publicationId
AND t1_a1.id=t3_p_author_RELATION_TABLE.authorId)) AND
(t4_a2.firstName = 'Jens') AND (EXISTS (SELECT
t3_p_author_RELATION_TABLE.authorId FROM
PUBLICATIONAUTHORS t3_p_author_RELATION_TABLE WHERE
t0_p.id=t3_p_author_RELATION_TABLE.publicationId AND
t4_a2.id=t3_p_author_RELATION_TABLE.authorId)))

20:29:44,215 WARN  [PublicationLocalHome] result was : [1]
20:29:44,216 WARN  [PublicationLocalHome] result class:
java.util.ArrayList

And here a run using the EJBQLToSQL92Compiler:
--

[PublicationLocalHome] queryString: SELECT p.id FROM
Publication AS p, Author AS a1, Author AS a2 WHERE
(a1.firstName = 'Timo') AND (a1 MEMBER OF p.author) AND
( a2.firstName = 'Jens' ) AND ( a2 MEMBER OF p.author )

org.jboss.ejb.plugins.cmp.jdbc.JDBCDynamicQLQuery.Publication#ejbSelectGeneric
null - Executing SQL: SELECT t0_p.id FROM AUTHOR t5_a2,
AUTHOR t1_a1, PUBLICATION t0_p WHERE (t1_a1.firstName =
'Timo') AND (EXISTS (SELECT t2_p_local.id FROM
PUBLICATION t2_p_local INNER JOIN PUBLICATIONAUTHORS
t4_p_author_local_RELATION_TABLE ON
t2_p_local.id=t4_p_author_local_RELATION_TABLE.publicationId
INNER JOIN AUTHOR t3_p_author_local ON
t3_p_author_local.id=t4_p_author_local_RELATION_TABLE.authorId
WHERE t1_a1.id=t3_p_author_local.id)) AND
(t5_a2.firstName = 'Jens') AND (EXISTS (SELECT
t2_p_local.id FROM PUBLICATION t2_p_local INNER JOIN
PUBLICATIONAUTHORS t4_p_author_local_RELATION_TABLE ON
t2_p_local.id=t4_p_author_local_RELATION_TABLE.publicationId
INNER JOIN AUTHOR t3_p_author_local ON
t3_p_author_local.id=t4_p_author_local_RELATION_TABLE.authorId
WHERE t5_a2.id=t3_p_author_local.id))

20:35:44,763 WARN  [PublicationLocalHome] result was :
[1, 2]
20:35:44,766 WARN  [PublicationLocalHome] result class:
java.util.ArrayList

The query is exactly the same in both test-runs, but
the result is different. I will supply any
descriptors/source/etc needed.

Environment is:
- JBoss 4.0.1
- included Hypersonic
- Java 1.4.2 

regards, Jens Braeuer

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1112731group_id=22866


---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1109743 ] Typo in jbossstandard.xml Clustered Stateless SessionBean?

2005-01-26 Thread SourceForge.net
Bugs item #1109743, was opened at 2005-01-26 11:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1109743group_id=22866

Category: Clustering
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Jesper S. Knudsen (orwtech)
Assigned to: Nobody/Anonymous (nobody)
Summary: Typo in jbossstandard.xml Clustered Stateless SessionBean?

Initial Comment:
Hi

I have just tried to setup at clustered solution on my 
newly downloaded JBoss 4.0.1 using the document 
Clustering with JBoss

The clustering, loadbalancing and fail-over all work fine 
but when I deploy my .ear I keep getting the WARN: 
Could not load the org.jboss.ejb.plugins.
ServiceEndpointInterceptor interceptor message.

I searched the Clustering Forum an for something about 
removing the interceptor transaction=Container tag 
from the jbossstandard.xml file, so I had a look at it and I 
may have found a typo in the file.

The thing that caught my eyes is that the Clustered 
Stateless SessionBean container configuration uses the 
 org.jboss.ejb.plugins.ServiceEndpointInterceptor
where as the Clustered Stateful SessionBean
org.jboss.webservice.server.ServiceEndpointInterceptor

The only ServiceEndpointInterceptor.class to be found 
searching all .jars shipped with JBoss 4.0.1 is in the 
jboss-ws4ee.jar

Is this a typo for the Clustered Stateless SessionBean 
container configuration? Should it not be org.jboss.
webservice.server.ServiceEndpointInterceptor to be used 
by the Clustered Stateless SessionBean container 
configuration, too?

Best regards

Jesper
[EMAIL PROTECTED]


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1109743group_id=22866


---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1108530 ] XML file dtd errors

2005-01-24 Thread SourceForge.net
Bugs item #1108530, was opened at 2005-01-24 18:28
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1108530group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jeff Conrad (jconradmn)
Assigned to: Nobody/Anonymous (nobody)
Summary: XML file dtd errors

Initial Comment:
See full description at

http://www.jboss.org/index.html?
module=bbop=viewtopict=58853

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1108530group_id=22866


---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag--drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1108795 ] try to created existing tables when starting server

2005-01-24 Thread SourceForge.net
Bugs item #1108795, was opened at 2005-01-25 01:45
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1108795group_id=22866

Category: JBossCache
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: jl (jlzhang)
Assigned to: Nobody/Anonymous (nobody)
Summary: try to created existing tables when starting server

Initial Comment:
Here is bug information from the server log. It seems 
either Jboss need to check the existence before create 
or use a replacement or drop the tables during server 
shutdown.

2005-01-25 10:24:10,709 DEBUG 
[org.jboss.system.ServiceController] starting service 
jboss.mq:service=DestinationManager
2005-01-25 10:24:10,709 DEBUG 
[org.jboss.system.ServiceController] waiting in start 
jboss.mq:service=DestinationManager on 
jboss.mq:service=PersistenceManager
2005-01-25 10:24:10,709 DEBUG 
[org.jboss.system.ServiceController] starting service 
jboss.mq:service=PersistenceManager
2005-01-25 10:24:10,709 DEBUG 
[org.jboss.mq.pm.jdbc2.PersistenceManager] Starting 
jboss.mq:service=PersistenceManager
2005-01-25 10:24:10,709 DEBUG 
[org.jboss.mq.pm.jdbc2.PersistenceManager] Resolving 
uncommited TXS
2005-01-25 10:24:10,719 DEBUG 
[org.jboss.mq.pm.jdbc2.PersistenceManager] Could not 
create table with SQL: CREATE CACHED TABLE 
JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, 
DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, 
TXOP CHAR(1), MESSAGEBLOB OBJECT, PRIMARY KEY 
(MESSAGEID, DESTINATION) )
java.sql.SQLException: Table already exists: 
JMS_MESSAGES in statement [CREATE CACHED TABLE 
JMS_MESSAGES]
at org.hsqldb.jdbc.jdbcUtil.throwError(Unknown 
Source)
at 
org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate
(Unknown Source)
at 
org.jboss.resource.adapter.jdbc.WrappedPreparedStatem
ent.executeUpdate
(WrappedPreparedStatement.java:316)
at 
org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUnc
ommitedTXs(PersistenceManager.java:224)
at 
org.jboss.mq.pm.jdbc2.PersistenceManager.startService
(PersistenceManager.java:1422)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart
(ServiceMBeanSupport.java:272)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMBeanSupport.java:222)
at 
sun.reflect.GeneratedMethodAccessor2.invoke(Unknown 
Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:72)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:642)
at 
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:891)
at $Proxy0.start(Unknown Source)



2005-01-25 10:24:10,729 DEBUG 
[org.jboss.mq.pm.jdbc2.PersistenceManager] Could not 
create table with SQL: CREATE CACHED TABLE 
JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY 
(TXID) )
java.sql.SQLException: Table already exists: 
JMS_TRANSACTIONS in statement [CREATE CACHED 
TABLE JMS_TRANSACTIONS]
at org.hsqldb.jdbc.jdbcUtil.throwError(Unknown 
Source)
at 
org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate
(Unknown Source)
at 
org.jboss.resource.adapter.jdbc.WrappedPreparedStatem
ent.executeUpdate
(WrappedPreparedStatement.java:316)
at 
org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUnc
ommitedTXs(PersistenceManager.java:296)
at 
org.jboss.mq.pm.jdbc2.PersistenceManager.startService
(PersistenceManager.java:1422)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart
(ServiceMBeanSupport.java:272)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMBeanSupport.java:222)
at 
sun.reflect.GeneratedMethodAccessor2.invoke(Unknown 
Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:72)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:642)
at 
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:891)
at $Proxy0.start(Unknown Source)


--

You can respond by visiting: 
https

[JBoss-dev] [ jboss-Bugs-1104763 ] EJB-QL CMR traversal returns wrong interface type

2005-01-18 Thread SourceForge.net
Bugs item #1104763, was opened at 2005-01-18 19:57
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1104763group_id=22866

Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: wilsonpu (wilsonpu)
Assigned to: Nobody/Anonymous (nobody)
Summary: EJB-QL CMR traversal returns wrong interface type

Initial Comment:
Hello,
   JBOSS AS returns/contains wrong interface type with
CMR traversal using EJB-QL.
   We recreated the line item example from Mastering
EJB Appendix D on EJB-QL entity bean relationship
traversal (page 574).  

Test case below.  Codes are attached to ease table data
creatation.

   We created 3 tables:

Customer 
-
customerId (pk)
name

Order
-
orderId  (pk)
customerId  (fk)
date

LineItem
-
lineItemId  (pk)
orderId  (fk)
sku
quantity

On the CustomerBean, we defined a finder method using
Xdoclet.

 @ejb.finder
   signature=Collection
findCustomerLineItems(int customerId)
   unchcked=true
query=SELECT OBJECT(l) FROM Customer AS c,
IN(c.orders) o, IN (o.lineItems) l WHERE c.customerId=?1
   result-type-mapping=Local

We also defined CMR for getting the orders from the
customer bean and getting the lineitems from the order
bean.  (codes are attached)

Base on the finder method, we are expecting to return a
collection of LineItemLocal interface.  However, we got
CustomerLocal interface instead.

The codes are attached with DB data.  However, you will
have to separate the codes to different file.

Wilson Pu
[EMAIL PROTECTED]
Software Developer
Vision Solutions Inc.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1104763group_id=22866


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1099355 ] user data is shared between sessions

2005-01-10 Thread SourceForge.net
Bugs item #1099355, was opened at 2005-01-10 10:14
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1099355group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: mona_onsy (mona_onsy)
Assigned to: Nobody/Anonymous (nobody)
Summary: user data is shared between sessions

Initial Comment:
when running a web app on jboss app server using 
apache's tag libs, session variables are shared between 
different sessions of the application when the pages are 
refreshed. 
Meaning ... user A can see the data the user B 
entereded on page 1 if user A refreshed page 1 and user 
B was in page 2.  which is a security violation.

the same application using the same tag libs running on 
sun one app server doesn;t have this problem.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1099355group_id=22866


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1099365 ] session variables are shared between sessions

2005-01-10 Thread SourceForge.net
Bugs item #1099365, was opened at 2005-01-10 10:34
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1099365group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: mona_onsy (mona_onsy)
Assigned to: Nobody/Anonymous (nobody)
Summary: session variables are shared between sessions

Initial Comment:
When running a web application on jboss AS using 
apache's tag libs (standard 1.0), session variables are 
shared between different sessions, ie. user A can see 
the data that user B entered on page 1 by refreshing 
page 1 on his side when user B is in page 2.

The same application using the same tag libs running on 
sun one AS doesn't have that problem.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1099365group_id=22866


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1098948 ] Unimplemented spec requirement?

2005-01-09 Thread SourceForge.net
Bugs item #1098948, was opened at 2005-01-09 14:37
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1098948group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: padonak (padonak)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unimplemented spec requirement?

Initial Comment:
Hi !

We are moving from jboss323 to 326 and found the
following problem:

In one of our bmp in ejbCreate we call ctx.getEJBObject()
Spec (ejb20 10.5.5) states that container should thow
java.lang.IllegalStateException

Both versions of jboss doesn't throw it.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1098948group_id=22866


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1097916 ] ClassCastException in execution of EJB-QL finder

2005-01-07 Thread SourceForge.net
Bugs item #1097916, was opened at 2005-01-07 15:22
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1097916group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Nicolas (cnico)
Assigned to: Nobody/Anonymous (nobody)
Summary: ClassCastException in execution of EJB-QL finder

Initial Comment:
There is a ClassCastException at execution time on
Jboss since version 3.2.6 (it worked on 3.2.5 but
neither on 3.2.6 nor on 3.2.7RC1) when calling an EJB
finder query defined as follow with Xdoclet tags : 
@ejb.finder
 *view-type = local
 *signature=test.ProductLocal
findByRefToAndToLicense(java.lang.String refTo,
java.lang.String license)
 *result-type-mapping=Local
 *method-intf=LocalHome
 *query=SELECT DISTINCT pr.id FROM TourOperator
to, IN ( to.products ) AS pr WHERE to.licenseNumber =
?2 AND pr.refTo = ?1
 * 

The trace is given after when jboss is in trace log level.

I also tested the same query with a return of type
Collection and it worked well. So I think the Cast
problem is that I declared the result as ProductLocal
and not Collection but it should be working without
using a Collection since I known by construction that
the result of the search is either 0 or 1.

Here is the trace :

16:03:09,690 TRACE [Registry] lookup
491837535=jboss.j2ee:jndiName=ejb/ProductSearchHome,service=EJB
16:03:09,690 TRACE [StatelessSessionContainer] METHOD
HOME INVOKE 491837535||create||[Ljava.lang.Object;@1900f17
16:03:09,690 TRACE [LogInterceptor] Start method=create
16:03:09,690 TRACE [TxInterceptorCMT] Current
transaction in MI is null
16:03:09,690 TRACE [TxInterceptorCMT] TX_REQUIRED for
create timeout=0
16:03:09,690 TRACE [TxInterceptorCMT] Thread came in
with tx null
16:03:09,690 TRACE [TransactionImpl] Created new
instance for tx=TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//25, BranchQual=]
16:03:09,690 TRACE [TxInterceptorCMT] Starting new tx
TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//25, BranchQual=]
16:03:09,690 TRACE [TxInterceptorCMT] TxInterceptorCMT:
In finally
16:03:09,690 TRACE [TransactionImpl] Committing,
tx=TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//25, BranchQual=], status=STATUS_ACTIVE
16:03:09,690 TRACE [TransactionImpl] Before completion
done, tx=TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//25, BranchQual=], status=STATUS_ACTIVE
16:03:09,690 TRACE [TransactionImpl] Zero phase commit:
No resources.
16:03:09,690 TRACE [TransactionImpl] Committed OK,
tx=TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//25, BranchQual=]
16:03:09,690 TRACE [LogInterceptor] End method=create
16:03:09,752 TRACE [Registry] lookup
491837535=jboss.j2ee:jndiName=ejb/ProductSearchHome,service=EJB
16:03:09,752 TRACE [StatelessSessionContainer] METHOD
REMOTE INVOKE
491837535||searchProductIDByRefToAndLicenseNumber||
16:03:09,752 TRACE [LogInterceptor] Start
method=searchProductIDByRefToAndLicenseNumber
16:03:09,752 TRACE [TxInterceptorCMT] Current
transaction in MI is null
16:03:09,752 TRACE [TxInterceptorCMT] TX_REQUIRED for
searchProductIDByRefToAndLicenseNumber timeout=0
16:03:09,752 TRACE [TxInterceptorCMT] Thread came in
with tx null
16:03:09,752 TRACE [TransactionImpl] Created new
instance for tx=TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//26, BranchQual=]
16:03:09,752 TRACE [TxInterceptorCMT] Starting new tx
TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//26, BranchQual=]
16:03:09,752 TRACE [StatelessSessionInstancePool] Get
instance
[EMAIL PROTECTED]
test.ProductSearchSession
16:03:09,752 TRACE [CachedConnectionManager] new stack
for key: [EMAIL PROTECTED]
16:03:09,752 TRACE [ProxyFactoryFinderInterceptor]
invokerBInding is null in ProxyFactoryFinder
16:03:09,752 TRACE [LogInterceptor] Start
method=findByRefToAndToLicense
16:03:09,752 TRACE [TxInterceptorCMT] Current
transaction in MI is TransactionImpl:XidImpl
[FormatId=257, GlobalId=NICOLAS//26, BranchQual=]
16:03:09,752 TRACE [TxInterceptorCMT] TX_REQUIRED for
findByRefToAndToLicense timeout=0
16:03:09,752 TRACE [TxInterceptorCMT] Thread came in
with tx TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//26, BranchQual=]
16:03:09,752 TRACE [EntityInstancePool] Get instance
[EMAIL PROTECTED]
test.ProductCMP
16:03:09,752 TRACE [CachedConnectionManager] old stack
for key:
[EMAIL PROTECTED]
16:03:09,752 DEBUG [Product#findByRefToAndToLicense]
Executing SQL: SELECT DISTINCT t0_pr.ID FROM
tour_operator t1_to, product t0_pr WHERE
((t1_to.LICENSE = ? AND t0_pr.REF_TO = ?)) AND
t1_to.ID=t0_pr.TO_ID
16:03:09,752 TRACE [TransactionImpl] enlistResource():
Entered, tx=TransactionImpl:XidImpl [FormatId=257,
GlobalId=NICOLAS//26, BranchQual=] status=STATUS_ACTIVE
16:03:09,752 TRACE [TransactionImpl]
startResource(XidImpl [FormatId=257,
GlobalId=NICOLAS//26, BranchQual=1]) entered:
[EMAIL PROTECTED]
flags=0
16:03:09,752

[JBoss-dev] [ jboss-Feature Requests-1097446 ] Deployed Resources View

2005-01-06 Thread SourceForge.net
Feature Requests item #1097446, was opened at 2005-01-06 17:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376688aid=1097446group_id=22866

Category: JBoss-IDE
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Martín López (mmlopez)
Assigned to: Nobody/Anonymous (nobody)
Summary: Deployed Resources View

Initial Comment:
It would be very usefull to have a view that shows all 
deployed resources, so it would be unnecesary to 
search the projects tree for any resource to redeploy.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376688aid=1097446group_id=22866


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1097643 ] Alter Table not Working in MySQL

2005-01-06 Thread SourceForge.net
Bugs item #1097643, was opened at 2005-01-07 12:48
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1097643group_id=22866

Category: JBossCMP
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard C. L. Li (clli)
Assigned to: Nobody/Anonymous (nobody)
Summary: Alter Table not Working in MySQL

Initial Comment:
I tried to use the following options in CMP deployment:

  create-tabletrue/create-table
  alter-tabletrue/alter-table

The deployment is deployed to:

  JBoss 4.0.1 + MySQL 4.x + WindowsXP

I found that the app server generates an exception and
the CMP Entity Beans cannot be deployed.  The exception
is caused by the SQL that trying to add a column to an
existing column.

Finally I figure out in the docs that the alter table
feature compares column names in uppercases so that the
lower case column names in default mapping cause trouble.

I tried to dig into the source codes and figure the
comparison is made to DB column names and uppercased
column names.  I just wonder why not compare both names
in uppercase, but only one in uppercase and the other not?

I already make a patch for myself which make both names
to uppercase before comparison.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1097643group_id=22866


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1095637 ] Unable to download requested document (dtd or xsd file)

2005-01-04 Thread SourceForge.net
Bugs item #1095637, was opened at 2005-01-04 11:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1095637group_id=22866

Category: JBoss-IDE
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Damien (lyc1)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unable to download requested document (dtd or xsd file)

Initial Comment:
I am working with JBoss-IDE on xml files behind a proxy.

Xml plugin always wants to validate xml file (dtd or
xsd), but url to locate theses files are not available.

The plugin must provide an option to disable this
validation.

Here is the stacktrace

java.io.IOException: Server returned HTTP response
code: 503 for URL: http://an_url/2004/10/15/fichier.xsd
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:789)
at java.net.URL.openStream(URL.java:913)
at
org.jboss.ide.eclipse.jdt.xml.core.ns.LocalCache.fetchContent(LocalCache.java:169)
at
org.jboss.ide.eclipse.jdt.xml.core.ns.LocalCache.getLocation(LocalCache.java:73)
at
org.jboss.ide.eclipse.jdt.xml.core.ns.LocalCache$1.normalize(LocalCache.java:108)
at
org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createInputStream(URIConverterImpl.java:390)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:738)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:247)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:262)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:346)
at
org.jboss.ide.eclipse.jdt.xml.core.ns.LocalCache.getSchema(LocalCache.java:113)
at
org.jboss.ide.eclipse.jdt.xml.core.ns.Namespace.parseXSD(Namespace.java:557)
at
org.jboss.ide.eclipse.jdt.xml.core.ns.Namespace.readSchema(Namespace.java:208)
at
org.jboss.ide.eclipse.jdt.xml.ui.reconciler.NodeReconciler.fix(NodeReconciler.java:545)
at
org.jboss.ide.eclipse.jdt.xml.ui.reconciler.NodeReconciler.createTree(NodeReconciler.java:148)
at
org.jboss.ide.eclipse.jdt.xml.ui.editors.XMLDocumentProvider.createDocument(XMLDocumentProvider.java:59)
at
org.eclipse.ui.editors.text.FileDocumentProvider.createElementInfo(FileDocumentProvider.java:638)
at
org.eclipse.ui.texteditor.AbstractDocumentProvider.connect(AbstractDocumentProvider.java:397)
at
org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput(AbstractTextEditor.java:2869)
at
org.eclipse.ui.texteditor.StatusTextEditor.doSetInput(StatusTextEditor.java:173)
at
org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput(AbstractDecoratedTextEditor.java:1073)
at
org.eclipse.ui.editors.text.TextEditor.doSetInput(TextEditor.java:287)
at
org.eclipse.ui.texteditor.AbstractTextEditor$15.run(AbstractTextEditor.java:2233)
at
org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:303)
at
org.eclipse.jface.operation.ModalContext.run(ModalContext.java:253)
at
org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:588)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at
org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:585)
at
org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1653)
at
org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(AbstractTextEditor.java:2247)
at
org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTextEditor.java:2265)
at
org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:718)
at
org.eclipse.ui.internal.EditorManager.openInternalEditor(EditorManager.java:777)
at
org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:582)
at
org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:570)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2244)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2177)
at
org.eclipse.ui.internal.WorkbenchPage.access$6(WorkbenchPage.java:2169)
at
org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2156)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2151)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:299)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:137)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:110)
at
org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(OpenActionUtil.java:49

[JBoss-dev] [ jboss-Bugs-1096143 ] Default commit option for Clustered BMP EntityBean is A

2005-01-04 Thread SourceForge.net
Bugs item #1096143, was opened at 2005-01-05 00:10
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1096143group_id=22866

Category: Clustering
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Ole Husgaard (sparre)
Assigned to: Nobody/Anonymous (nobody)
Summary: Default commit option for Clustered BMP EntityBean is A

Initial Comment:
In 3.2.5 and 3.2.6 the default commit option for
Clustered BMP EntityBeans is A. I do not how it is in
other JBoss versions.

But just like Clustered CMP EntityBeans we need the
database to do the synchronization between cluster
nodes, so the default commit option for Clustered BMP
EntityBeans in standardjboss.xml should be B.

I hereby kindly ask that somebody with CVS R/W access
change this single character in standardjboss.xml in
the 3.2 branch.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1096143group_id=22866


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1093885 ] sitemesh deployment in war

2004-12-31 Thread SourceForge.net
Bugs item #1093885, was opened at 2004-12-31 15:23
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1093885group_id=22866

Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: V L (vipy)
Assigned to: Nobody/Anonymous (nobody)
Summary: sitemesh deployment in war

Initial Comment:
Running JBoss AS 4.0.1 final.
using sitemesh 2.2.1 final.

Theres an exception looking for the sitemesh.xml to
define the default filters in dir WEB-INF. When
sitemech.xml is placed in META-INF everything works.
sitemesh.xml is normally located in dir WEB-INF.

--EXCEPTION--
2004-12-31 15:20:49,021 ERROR
[org.jboss.web.localhost.Engine]
StandardContext[/]Exception starting filter sitemesh
com.opensymphony.module.sitemesh.factory.FactoryException:
Cannot construct Factory :
com.opensymphony.module.sitemesh.factory.DefaultFactory:
java.lang.reflect.InvocationTargetException
at
com.opensymphony.module.sitemesh.Factory.report(Factory.java:87)
at
com.opensymphony.module.sitemesh.Factory.getInstance(Factory.java:56)
at
com.opensymphony.module.sitemesh.filter.PageFilter.init(PageFilter.java:99)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308)
at
org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:79)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4349)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
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:324)
at
org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5441)
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:324)
at
org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at
org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:332)
at
org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:85)
at
org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:374)
at org.jboss.web.WebModule.startModule(WebModule.java:62)
at org.jboss.web.WebModule.startService(WebModule.java:40)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at
org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:416)
at
sun.reflect.GeneratedMethodAccessor10.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144

[JBoss-dev] [ jboss-Bugs-1090921 ] memory leak after 7 hours

2004-12-29 Thread SourceForge.net
Bugs item #1090921, was opened at 2004-12-24 20:18
Message generated for change (Comment added) made by atomrom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1090921group_id=22866

Category: JBossCMP
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Mormota (atomrom)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: memory leak after 7 hours

Initial Comment:
Hi,

I have experienced strange memory leaks under JBoss
4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5
hours running my application. (In the first 7 hours my
application consumes 100M of memory under 4.0.0,
however after 7 hours the memory consumption raises
lineraly). I used YourKit to detect the memory leak and
I found that the memory is chiefly occupied by HashMap
and entity bean proxies.

Unfortunately I cannot provide source code, but I can
give a short description of the component architecture
and functioning:
(a) objects are inserted into a messaging topic
(b) an MDB receives the objects and:
  (b.i) dispaches them to a resource adapter (the RA
sends the object over the network)
  (b.ii) creates a database entry using the String(s)
returned by the RA (a tuple looks like this: [String:
id, Date: date, String: st]; I'm using a CMP entity bean)

(c) a timer periodically removes the overaged database
entries (see date). ejbTimeout is implemented by a
stateless session bean, database entries are removed by
the corresponding CMP entity bean

(d) whenever the RA receives an object over the
network, it dispatches it to a stateless session bean,
which is registered as an endpoint at the RA
(e) the stateless session bean 
  (e.i) updates the database entry (using the ), or
more precisely, its st field
  (e.ii) inserts a new database entry
  (e.iii) if the st field statisfies certain
conditions, removes both the inserted and updated entries

Additional infos:
  * OS: RedHat AS (running on various hardware, e.g.
simple PC and a 4 processor Xeon server)
  * JDK: jdk1.4.5
  * I see lot of log messages regarding rolled back
transactions (because of timeouts); these exceptions
are thrown in the CMP entity bean in that method, which
removes the overaged entries. After a findByDate I
iterate over the resulting collection and when I want
to access id, an exception is thrown. Not always, but
strangely often.
  * the memory leak emerges after 7 (or 3.5) hours
regardless the load, and configuration. The load
influences only the gradient of the lineraly increasing
(and therefore deadly) period.

Merry Christmas,

Mormota

--

Comment By: Mormota (atomrom)
Date: 2004-12-29 19:45

Message:
Logged In: YES 
user_id=1184354

Some new details:
I simplified the application to the following (see new step
b.iii):
(a) objects are inserted into a messaging topic
(b) an MDB receives the objects and:
(b.i) dispaches them to a resource adapter (the RA
sends the object over the network)
(b.ii) creates a database entry using the String(s)
returned by the RA (a tuple looks like this: [String:
id, Date: date, String: st]; I'm using a CMP entity bean)
(b.iii) _removes the new entry_

Despite the database entries are removed instantly after
their creation (and therefore the database is empty), the
memory usade increases steadyly. 

In stable JBoss 4.0.1, there is no 3.5 (or 7) hours long
constant-memory-use period.

The pace of memory consumption growth can be reduced by
using C commit option (instead of the default B).

Memory leak still persist when using jdk 1.5.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1090921group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1090921 ] memory leak after 7 hours

2004-12-29 Thread SourceForge.net
Bugs item #1090921, was opened at 2004-12-24 11:18
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1090921group_id=22866

Category: JBossCMP
Group: v4.0
Status: Closed
Resolution: Duplicate
Priority: 5
Submitted By: Mormota (atomrom)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: memory leak after 7 hours

Initial Comment:
Hi,

I have experienced strange memory leaks under JBoss
4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5
hours running my application. (In the first 7 hours my
application consumes 100M of memory under 4.0.0,
however after 7 hours the memory consumption raises
lineraly). I used YourKit to detect the memory leak and
I found that the memory is chiefly occupied by HashMap
and entity bean proxies.

Unfortunately I cannot provide source code, but I can
give a short description of the component architecture
and functioning:
(a) objects are inserted into a messaging topic
(b) an MDB receives the objects and:
  (b.i) dispaches them to a resource adapter (the RA
sends the object over the network)
  (b.ii) creates a database entry using the String(s)
returned by the RA (a tuple looks like this: [String:
id, Date: date, String: st]; I'm using a CMP entity bean)

(c) a timer periodically removes the overaged database
entries (see date). ejbTimeout is implemented by a
stateless session bean, database entries are removed by
the corresponding CMP entity bean

(d) whenever the RA receives an object over the
network, it dispatches it to a stateless session bean,
which is registered as an endpoint at the RA
(e) the stateless session bean 
  (e.i) updates the database entry (using the ), or
more precisely, its st field
  (e.ii) inserts a new database entry
  (e.iii) if the st field statisfies certain
conditions, removes both the inserted and updated entries

Additional infos:
  * OS: RedHat AS (running on various hardware, e.g.
simple PC and a 4 processor Xeon server)
  * JDK: jdk1.4.5
  * I see lot of log messages regarding rolled back
transactions (because of timeouts); these exceptions
are thrown in the CMP entity bean in that method, which
removes the overaged entries. After a findByDate I
iterate over the resulting collection and when I want
to access id, an exception is thrown. Not always, but
strangely often.
  * the memory leak emerges after 7 (or 3.5) hours
regardless the load, and configuration. The load
influences only the gradient of the lineraly increasing
(and therefore deadly) period.

Merry Christmas,

Mormota

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:47

Message:
Logged In: YES 
user_id=175228

Please continue on the jira site:
http://jira.jboss.com/jira/browse/JBAS-1255

--

Comment By: Mormota (atomrom)
Date: 2004-12-29 10:45

Message:
Logged In: YES 
user_id=1184354

Some new details:
I simplified the application to the following (see new step
b.iii):
(a) objects are inserted into a messaging topic
(b) an MDB receives the objects and:
(b.i) dispaches them to a resource adapter (the RA
sends the object over the network)
(b.ii) creates a database entry using the String(s)
returned by the RA (a tuple looks like this: [String:
id, Date: date, String: st]; I'm using a CMP entity bean)
(b.iii) _removes the new entry_

Despite the database entries are removed instantly after
their creation (and therefore the database is empty), the
memory usade increases steadyly. 

In stable JBoss 4.0.1, there is no 3.5 (or 7) hours long
constant-memory-use period.

The pace of memory consumption growth can be reduced by
using C commit option (instead of the default B).

Memory leak still persist when using jdk 1.5.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1090921group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1089786 ] Missing org.w3c.dom.xpath.* in JBoss

2004-12-29 Thread SourceForge.net
Bugs item #1089786, was opened at 2004-12-22 07:15
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1089786group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: chen_comp (ychen123)
Assigned to: Nobody/Anonymous (nobody)
Summary: Missing org.w3c.dom.xpath.* in  JBoss

Initial Comment:
Checked JBoss's endorsed directory, no related classes 
have been packaged inside any jar which cause people 
can't use  org.apache.xpath.domapi.*


--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1089786group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1088495 ] Session replication fails on 2-node cluster

2004-12-29 Thread SourceForge.net
Bugs item #1088495, was opened at 2004-12-20 08:21
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1088495group_id=22866

Category: Clustering
Group: v4.0
Status: Closed
Resolution: None
Priority: 8
Submitted By: proudchief (proudchief)
Assigned to: Nobody/Anonymous (nobody)
Summary: Session replication fails on 2-node cluster

Initial Comment:
Operating System: Linux (Novell Linux Desktop, kernel
2.6.5-7.109.5-default)
JDK: Sun 1.4.2_06
2-node cluster using all configuration, with
unchanged settings. Both machines have identical OS,
JDK, and JBoss software.

  JBoss Bootstrap Environment

  JBOSS_HOME: /opt/jboss-4.0.1RC2

  JAVA: /opt/java/j2sdk1.4.2_06/bin/java

  JAVA_OPTS: -server -Xms128m -Xmx128m
-Dprogram.name=run.sh

  CLASSPATH:
/opt/jboss-4.0.1RC2/bin/run.jar:/opt/java/j2sdk1.4.2_06/lib/tools.jar

I deployed a very simple WAR with one servlet that
places several strings into the user's session. When
the servlet runs, a stack trace is produced (attached).
The session fails to replicate.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: proudchief (proudchief)
Date: 2004-12-20 08:24

Message:
Logged In: YES 
user_id=532979

Attaching the WAR file used to test.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1088495group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1089791 ] WSDLFilePublisher doesn't support remote XML schemas

2004-12-29 Thread SourceForge.net
Bugs item #1089791, was opened at 2004-12-22 07:24
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1089791group_id=22866

Category: JBossWS
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Bob Copeland (bobc)
Assigned to: Nobody/Anonymous (nobody)
Summary: WSDLFilePublisher doesn't support remote XML schemas

Initial Comment:
In JBoss 4.0.1RC2 - see attached wsdl and the forum post:
http://www.jboss.org/index.html?module=bbop=viewtopict=57914

WSDLFilePublisher only supports local XML schemas (and
poorly at that).  When deploying an ejb-jar containing
the attached WSDL, the following error is produced:

Caused by: java.lang.IllegalArgumentException: Cannot
find schema import in deployment:
META-INF/wsdl/http://localhost:8080/schemas/doc129.xsd

I suggest adding the following to publishSchemaImports
at line 199 as is done in publishWsdlImports:

   if (schemaLocation.startsWith(http://;))
   {
   continue;
   }


--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1089791group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1085726 ] Incorrect Handle implementation for CMP Entity beans

2004-12-29 Thread SourceForge.net
Bugs item #1085726, was opened at 2004-12-15 03:25
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1085726group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 9
Submitted By: Maxoid (maxoid)
Assigned to: Nobody/Anonymous (nobody)
Summary: Incorrect Handle implementation for CMP Entity beans

Initial Comment:
If an entity bean is a CMP bean with unknown 
primary key, then implementation of the javax.ejb.
Handle interface can't find home method 
findByPrimaryKey(java.lang.Object), but try with only 
 real PK class.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1085726group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1080095 ] ejb-link fails with linked tmp directory

2004-12-29 Thread SourceForge.net
Bugs item #1080095, was opened at 2004-12-06 10:03
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1080095group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Ralf Zimmermann (rz1911)
Assigned to: Nobody/Anonymous (nobody)
Summary: ejb-link fails with linked tmp directory

Initial Comment:
Hi, 

I have problems to deploy the attached EAR if the 
jboss/server/default/tmp directory is linked to another 
directoy using an symbolic link. I use JBoss 4.0.0, JDK 
1.4.2_06 and RedHat Linux. 

The EAR defins two (empty) session EJBs A and B. EJB A 
has an link to EJB B using th ejb-link syntax.

I get the following Exception:

2004-12-06 18:38:44,673 INFO  
[org.jboss.ejb.EjbModule] Deploying AEJB
2004-12-06 18:38:46,663 INFO  
[org.jboss.ejb.EjbModule] Deploying BEJB
2004-12-06 18:38:46,983 WARN  [org.jboss.ejb.EjbUtil] 
Can't locate deploymentInfo for target: 
file:/var/intelliform/tmp/deploy/tmp39034bug.ear-
contents/B.jar
2004-12-06 18:38:46,984 ERROR 
[org.jboss.ejb.StatelessSessionContainer] Starting
 failed jboss.j2ee:jndiName=AEJB,service=EJB
org.jboss.deployment.DeploymentException: Failed to 
resolve ejb-link: B.jar#BEJB
 make by ejb-name: ejb/BEJB
at org.jboss.ejb.Container.setupEnvironment
(Container.java:993)
at org.jboss.ejb.Container.startService
(Container.java:724)
at org.jboss.ejb.SessionContainer.startService
(SessionContainer.java:381
)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStar
t(ServiceMBeanS
upport.java:271)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMB
eanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor3.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown 
Source)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
...

The EAR deploys fine, if the mtp directory is an real 
directory.

I think this is due to the failure of 
EjbUtil.resolveRelativeLink.
The use of Strings.toURL calculates the URL for the 
DeploymentInfo class different than the MainDeployer 
class.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1080095group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1078485 ] Farm hot deploy of exploded archive fails

2004-12-29 Thread SourceForge.net
Bugs item #1078485, was opened at 2004-12-03 09:51
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1078485group_id=22866

Category: Clustering
Group: v4.0
Status: Closed
Resolution: Postponed
Priority: 5
Submitted By: proudchief (proudchief)
Assigned to: Nobody/Anonymous (nobody)
Summary: Farm hot deploy of exploded archive fails

Initial Comment:
Copying an exploded WAR to the farm directory causes 
FileNotFoundException if server is up. When server 
restarted, deployment succeeds.

OS: Novell Linux Desktop 9
JDK: Sun 1.4.2_06

Server output attached.

==
===

  JBoss Bootstrap Environment

  JBOSS_HOME: /opt/jboss-4.0.0

  JAVA: /opt/java/j2sdk1.4.2_06/bin/java

  JAVA_OPTS: -server -Xms128m -Xmx128m -
Dprogram.name=run.sh

  CLASSPATH: /opt/jboss-
4.0.0/bin/run.jar:/opt/java/j2sdk1.4.2_06/lib/tools.jar

==
===

12:44:44,516 INFO  [Server] Starting JBoss (MX 
MicroKernel)...
12:44:44,520 INFO  [Server] Release ID: JBoss [Zion] 
4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418)
12:44:44,522 INFO  [Server] Home Dir: /opt/jboss-4.0.0
12:44:44,523 INFO  [Server] Home URL: file:/opt/jboss-
4.0.0/
12:44:44,524 INFO  [Server] Library URL: file:/opt/jboss-
4.0.0/lib/
12:44:44,528 INFO  [Server] Patch URL: null
12:44:44,529 INFO  [Server] Server Name: all
12:44:44,530 INFO  [Server] Server Home 
Dir: /opt/jboss-4.0.0/server/all
12:44:44,531 INFO  [Server] Server Home URL: 
file:/opt/jboss-4.0.0/server/all/
12:44:44,532 INFO  [Server] Server Data Dir: /opt/jboss-
4.0.0/server/all/data
12:44:44,533 INFO  [Server] Server Temp 
Dir: /opt/jboss-4.0.0/server/all/tmp
12:44:44,535 INFO  [Server] Server Config URL: 
file:/opt/jboss-4.0.0/server/all/conf/
12:44:44,536 INFO  [Server] Server Library URL: 
file:/opt/jboss-4.0.0/server/all/lib/
12:44:44,537 INFO  [Server] Root Deployment Filename: 
jboss-service.xml
12:44:44,548 INFO  [Server] Starting General Purpose 
Architecture (GPA)...
12:44:46,859 INFO  [ServerInfo] Java version: 
1.4.2_06,Sun Microsystems Inc.
12:44:46,860 INFO  [ServerInfo] Java VM: Java HotSpot
(TM) Server VM 1.4.2_06-b03,Sun Microsystems Inc.
12:44:46,861 INFO  [ServerInfo] OS-System: Linux 
2.6.5-7.109.5-default,i386

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-04 09:21

Message:
Logged In: YES 
user_id=175228

This is a known limitation. You cannot farm deploy exploded
contents currently.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1078485group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1061111 ] Verifier warning message not found

2004-12-29 Thread SourceForge.net
Bugs item #106, was opened at 2004-11-05 10:08
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=106group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Patrick Murphy (murphyp1)
Assigned to: Thomas Diesler (tdiesler)
Summary: Verifier warning message not found

Initial Comment:
13:05:47,004 WARN  [verifier] EJB spec violation:
Bean   : /d6501/SentinelMonitor
Section: 7.11.1
Warning: No warning message found, please file a Bug 
report.
13:05:47,035 ERROR [MainDeployer] could not create 
deployment: 
file:/C:/home2/jboss/server/aistech/deploy/d6501ws-
ejb.jar
org.jboss.deployment.DeploymentException: Verification 
of Enterprise Beans failed, see above for error messages.
at org.jboss.ejb.EJBDeployer.create
(EJBDeployer.java:553)
at org.jboss.deployment.MainDeployer.create
(MainDeployer.java:898)
at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:754)
at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:718)
at sun.reflect.GeneratedMethodAccessor37.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
at 
org.jboss.mx.interceptor.AbstractInterceptor.invoke
(AbstractInterceptor.java:122)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:74)
at 
org.jboss.mx.interceptor.ModelMBeanOperationIntercepto
r.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:74)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke
(MBeanProxyExt.java:175)
at $Proxy8.deploy(Unknown Source)
at 
org.jboss.deployment.scanner.URLDeploymentScanner.de
ploy(URLDeploymentScanner.java:305)
at 
org.jboss.deployment.scanner.URLDeploymentScanner.sc
an(URLDeploymentScanner.java:463)
at 
org.jboss.deployment.scanner.AbstractDeploymentScann
er$ScannerThread.doScan
(AbstractDeploymentScanner.java:204)
at 
org.jboss.deployment.scanner.AbstractDeploymentScann
er$ScannerThread.loop
(AbstractDeploymentScanner.java:215)
at 
org.jboss.deployment.scanner.AbstractDeploymentScann
er$ScannerThread.run
(AbstractDeploymentScanner.java:194)

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=106group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1070613 ] Redeploy fails when (some) files changed

2004-12-29 Thread SourceForge.net
Bugs item #1070613, was opened at 2004-11-21 13:02
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1070613group_id=22866

Category: JBossWS
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Heiko W.Rupp (pilhuhn)
Assigned to: Nobody/Anonymous (nobody)
Summary: Redeploy fails when (some) files changed

Initial Comment:
When an EJB is running as an EJB2.1 webservices client
and is redeployed with some changes in files that are
referenced in the service-ref element of ejb-jar.xml,
the deploy of the jar will work fine, but as soon as
the service is used, the following Exception will rise:

After restarting the whole jboss server, the problem
goes away. It seems that this is only a problem with
zipped archives (I am not completely sure here).


What I can imagine is the following: something is still
holding a file reference into the old jar. When this is
undeployed, the file reference is still pointing to it
and not to the new deploy unit thus pointing into the
empty.


21:56:55,774 INFO  [STDOUT] Caused by:
java.lang.RuntimeException: Cannot access wsdl from
[jar:file:/D:/jboss4/server/small/deploy/
adb.jar!/META-INF/wsdl/google.wsdl], JAR entry
META-INF/wsdl/google.wsdl not found in
D:\jboss4\server\small\deploy\adb.jar
21:56:55,774 INFO  [STDOUT] at
org.jboss.webservice.WSDLDefinitionFactory$WSDLLocatorImpl.getBaseInputSource(WSDLDefinitionFacto
ry.java:103)
21:56:55,774 INFO  [STDOUT] at
com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
21:56:55,774 INFO  [STDOUT] at
org.jboss.webservice.WSDLDefinitionFactory.parse(WSDLDefinitionFactory.java:71)
21:56:55,774 INFO  [STDOUT] at
org.jboss.webservice.metadata.ServiceRefMetaData.getWsdlDefinition(ServiceRefMetaData.java:180)
21:56:55,774 INFO  [STDOUT] at
org.jboss.webservice.client.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:145)

21:56:55,774 INFO  [STDOUT] at
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
21:56:55,774 INFO  [STDOUT] at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:621)
21:56:55,774 INFO  [STDOUT] ... 58 more




--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Heiko W.Rupp (pilhuhn)
Date: 2004-11-21 13:12

Message:
Logged In: YES 
user_id=217112

The exception also arises when some class files are changed
(which in my build environement can also lead to a newer
version of ejb-jar.xml with same content, but newer timestamp).

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1070613group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1058085 ] AOP launcher: system properties are lost

2004-12-29 Thread SourceForge.net
Bugs item #1058085, was opened at 2004-11-01 03:50
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1058085group_id=22866

Category: JBoss-IDE
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Simon (simongunz)
Assigned to: Nobody/Anonymous (nobody)
Summary: AOP launcher: system properties are lost

Initial Comment:
After launching a JBoss AOP Launcher, previously addes
system properties are deleted and the VM arguments
field is reset to -Djboss.aop.path=

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1058085group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1053237 ] JBoss-4.0.0 uses OLD, BUGGY castor-0.9.3.9-xml.jar

2004-12-29 Thread SourceForge.net
Bugs item #1053237, was opened at 2004-10-24 08:41
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1053237group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: Accepted
Priority: 5
Submitted By: Adrian Price (adrianprice)
Assigned to: Anil Saldhana (osdchicago)
Summary: JBoss-4.0.0 uses OLD, BUGGY castor-0.9.3.9-xml.jar

Initial Comment:
JBoss-4.0.0 deploys a very buggy and out-of-date
castor-0.9.3.9-xml.jar; it was released on December 11,
2001.

3.2.x included a still older version in
server/xxx/deploy/snmp-adaptor.sar but at least then it
was possible to circumvent it by using an EAR-scoped
classloader, whereas 4.0.0 places the castor jar in
server/xxx/lib, which seems to prevent an EAR-scoped
classloader from loading the correct version.

The up-to-date release is Version 0.9.5.3; it has been
available since March 09, 2004.  It would be extremely
helpful if JBoss could upgrade to this version.  Thanks!

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Scott M Stark (starksm)
Date: 2004-10-24 09:00

Message:
Logged In: YES 
user_id=175228

This is due to the jaxr implementation found in the
ebxmlrr-service.sar which cannot be scoped because the
marshalling happens on both the client and server side of
the jaxr invocations. If your not using jaxr throw away this
sar and castor. We are working on cleaning up the jaxr
implementation dependencies on thirdparty components.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1053237group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1058298 ] Creating log4j Logger prevents interceptor

2004-12-29 Thread SourceForge.net
Bugs item #1058298, was opened at 2004-11-01 09:57
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1058298group_id=22866

Category: Aspects
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Simon (simongunz)
Assigned to: Nobody/Anonymous (nobody)
Summary: Creating log4j Logger prevents interceptor

Initial Comment:
I am just after observing a weired behaviour: I add a
simple Interceptor to my hello world class, and method
interception works.

But if I create an arbitrary log4j Logger anywhere in
my hello world program, the interceptor is not called
anymore.

To reproduce the behaviour, please comment the log4j
Logger instantiation in the Main class.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1058298group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1076950 ] TimedObject id persistence fails on restart

2004-12-29 Thread SourceForge.net
Bugs item #1076950, was opened at 2004-12-01 10:03
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1076950group_id=22866

Category: JBossCMP
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Christopher G. Stach II (cstach)
Assigned to: Thomas Diesler (tdiesler)
Summary: TimedObject id persistence fails on restart

Initial Comment:
Upon restarting JBoss, persisted timers throw this SQL 
exception because it seems that the entity bean that 
implements the TimedObject had its primary key (Long) 
converted into a byte array.

java.sql.SQLException: Cannot convert class [B to SQL 
type requested due to java.lang.ClassCastException - 
null
at 
com.mysql.jdbc.PreparedStatement.setObject
(PreparedStatement.java:922)
at 
com.mysql.jdbc.PreparedStatement.setObject
(PreparedStatement.java:944)
at 
org.jboss.resource.adapter.jdbc.WrappedPreparedStatem
ent.setObject(WrappedPreparedStatement.java:615)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCParameterSetter$5.se
tNotNull(JDBCParameterSetter.java:130)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCParameterSetter$JDB
CAbstractParameterSetter.set
(JDBCParameterSetter.java:56)
at 
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFi
eldBridge.setArgumentParameters
(JDBCAbstractCMPFieldBridge.java:354)
at 
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFi
eldBridge.setPrimaryKeyParameters
(JDBCAbstractCMPFieldBridge.java:343)
at 
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.se
tPrimaryKeyParameters(JDBCEntityBridge.java:770)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.e
xecute(JDBCLoadEntityCommand.java:157)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.e
xecute(JDBCLoadEntityCommand.java:72)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEnt
ity(JDBCStoreManager.java:631)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEnt
ity(JDBCStoreManager.java:613)
at 
org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity
(CMPPersistenceManager.java:391)
at 
org.jboss.resource.connectionmanager.CachedConnection
Interceptor.loadEntity
(CachedConnectionInterceptor.java:351)
at 
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.inv
oke(EntitySynchronizationInterceptor.java:232)
at 
org.jboss.resource.connectionmanager.CachedConnection
Interceptor.invoke
(CachedConnectionInterceptor.java:185)
at 
org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke
(EntityReentranceInterceptor.java:111)
at 
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke
(EntityInstanceInterceptor.java:211)
at 
org.jboss.ejb.plugins.EntityLockInterceptor.invoke
(EntityLockInterceptor.java:89)
at 
org.jboss.ejb.plugins.EntityCreationInterceptor.invoke
(EntityCreationInterceptor.java:53)
at 
org.jboss.ejb.plugins.CallValidationInterceptor.invoke
(CallValidationInterceptor.java:48)
at 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext
(AbstractTxInterceptor.java:105)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxInterceptorCMT.java:283)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.invoke
(TxInterceptorCMT.java:149)
at 
org.jboss.ejb.plugins.SecurityInterceptor.invoke
(SecurityInterceptor.java:128)
at org.jboss.ejb.plugins.LogInterceptor.invoke
(LogInterceptor.java:191)
at 
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invok
e(ProxyFactoryFinderInterceptor.java:122)
at org.jboss.ejb.EntityContainer.internalInvoke
(EntityContainer.java:514)
at org.jboss.ejb.Container.invoke
(Container.java:854)
at 
org.jboss.ejb.txtimer.TimedObjectInvokerImpl.callTimeout
(TimedObjectInvokerImpl.java:63)
at 
org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run
(TimerImpl.java:472)
at java.util.TimerThread.mainLoop
(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)



11:44:21,750 ERROR [TimerImpl] Error invoking 
ejbTimeout: javax.ejb.EJBException: Internal error 
setting parameters for field id; CausedByException is:
Cannot convert class [B to SQL type requested 
due to java.lang.ClassCastException - null



11:44:21,750 WARN  [TimerImpl] Timer was not 
registered with Tx, reseting state: [id=1target=
[target=jboss.j2ee:jndiName=ejb/mdf/Campaign,service=E
JB,[EMAIL PROTECTED],remaining=-
59694750,periode=0,in_timeout]



11:44:21,859 ERROR [LogInterceptor] EJBException in 
method: public abstract void 
javax.ejb.TimedObject.ejbTimeout(javax.ejb.Timer), 
causedBy:
java.sql.SQLException: Cannot convert class [B to SQL 
type requested due to java.lang.ClassCastException - 
null
at 
com.mysql.jdbc.PreparedStatement.setObject
(PreparedStatement.java:922)
at 
com.mysql.jdbc.PreparedStatement.setObject
(PreparedStatement.java:944

[JBoss-dev] [ jboss-Bugs-1069954 ] [patch] LongVersionField - info when empty value

2004-12-29 Thread SourceForge.net
Bugs item #1069954, was opened at 2004-11-20 02:34
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1069954group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: taab (taab)
Assigned to: Nobody/Anonymous (nobody)
Summary: [patch] LongVersionField - info when empty value

Initial Comment:
I've created table with version column (and forgot to
put not null on version column). So during update I
receive stack trace:
Caused by: javax.ejb.EJBException: Store failed;
CausedByException is:
null
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreEntityCommand.execute(JDBCStoreEntityCommand.java:144)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.storeEntity(JDBCStoreManager.java:635)

Problem is in the code:

public class JDBCLongVersionFieldBridge extends
JDBCCMP2xVersionFieldBridge
{
   public Object updateVersion(EntityEnterpriseContext ctx)
   {
  long current =
((Long)getInstanceValue(ctx)).longValue();
  Long next = new Long(current + 1);
  setInstanceValue(ctx, next);
  return next;
   }
}

In fact code is ok, but DB content is wrong: version
column is null (I populated table in wrong way -
similar could happen when DB is somehow damaged).
(I suspect second problem here - why is version column
being updated? probably dirty checking doesn't like
null in version column).
I would propose to put better info in this case:
   public Object updateVersion(EntityEnterpriseContext ctx)
   {
  try {
   long current =
((Long)getInstanceValue(ctx)).longValue();
  } catch (Exception e) {
  throw exception here with text: probable
cause:empty value in version column or not-number in
version columnt for primary key: + primary_key value;
  }

This will give direct info of the problem and save a
lot of time in finding db corruption.
Hope it will be helpfull,
taab


--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1069954group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1019633 ] No redeployment possible after unsuccessful first deployment

2004-12-29 Thread SourceForge.net
Bugs item #1019633, was opened at 2004-08-31 05:42
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1019633group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Simon (simongunz)
Assigned to: Thomas Diesler (tdiesler)
Summary: No redeployment possible after unsuccessful first deployment

Initial Comment:
If deployment of ear fails (e.g. because of invalid
deployment descriptors) any further deployment of the
same (valid, since error corrected) archive fails with
the following exception:

org.jboss.deployment.DeploymentException: Error in
accessing application metadata: ; - nested throwable:
(javax.management.InstanceAlreadyExistsException:
jboss.j2ee:service=EARDeployment,url='jpi-jboss-iv.ear'
already registered.)

New deployment only succeeds after restarting JBoss.
Since this is very inconvenient this behaviour should
be changed so that deployment fails completely if there
is a mistake in the deployment descriptor.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1019633group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1068206 ] Incorrect data source used loading relationship field

2004-12-29 Thread SourceForge.net
Bugs item #1068206, was opened at 2004-11-17 11:27
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1068206group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Brad Geddes (bgeddes)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: Incorrect data source used loading relationship field

Initial Comment:
Running Windows 2000, JDK 1.4.2_02, Jboss 3.2.6

I have a relationship between two EJBs associated with
different data sources.  When I update the
relationship, it runs a select statement for the
foreign key column being updated, but it runs it using
the datasource for the related ejb.  This causes an
oracle error (ORA-00942: table or view does not exist),
since the table does not exist in the other schema.

InventoryMapEJB: datasource1
StatusEJB: datasource2

inventoryMapEJB.setStatus(statusEJB);

This runs: SELECT inventory_map_id, status_id FROM
INVENTORY_MAP WHERE (inventory_map_id=?) using datasource2


I believe the problem is in the resolveRelationship
method of the JDBCCMRFieldBridge class.  It checks
hasForeignKey() in order to decide which dataSource to
use, but the foreignKeyFields member variable hasn't
been initialized yet.  This happens later in the
method, during the call to
initializeForeignKeyFields().  The attached file is a
proposed fix to this class.  I just moved dataSource
and table name loading to after where the foreign key
fields are initialized.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1068206group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1047314 ] Exception creating MySQL table using backquoted table name

2004-12-29 Thread SourceForge.net
Bugs item #1047314, was opened at 2004-10-14 13:42
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1047314group_id=22866

Category: JBossCMP
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Joe Simone (jsimone)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: Exception creating MySQL table using backquoted table name

Initial Comment:
According to the mySQL reference:

http://dev.mysql.com/doc/mysql/en/Legal_names.html

It is possible to create tables and columns with reserved 
names by using the backquote character: `.

Using JBoss 4.0.0, JDK 1.5 and mySQL 4.0.21 (the latest 
production version) results in a SQL exception from 
using the following in jbosscmp-jdbc.xml :

entity
   ejb-nameSession/ejb-name
   table-name`SESSION`/table-name
   cmp-field
  field-nameid/field-name
  column-nameID/column-name
   

However, when the backquotes are used for column 
names - NO EXCEPTION occurs.

If I try and issue the SQL commands manually with the 
backquotes this works fine.

It would appear the generated SQL is incorrect when 
reserved words for table names are backquoted.

Below is the exception when trying to create the table 
`SESSION`.

16:29:07,730 ERROR [EntityContainer] Starting failed 
jboss.j2ee:jndiName=local/Comment,service=EJB
org.jboss.deployment.DeploymentException: Error while 
creating table `SESSION`; - nested throwable: 
(java.sql.SQLException: Syntax error or access violation 
message from server: You have an error in your SQL 
syntax.  Check the manual that corresponds to your 
MySQL server version for the right syntax to use 
near 'SESSION` PRIMARY KEY (ID))' at line 1)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.create
Table(JDBCStartCommand.java:540)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.execu
te(JDBCStartCommand.java:196)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startSt
oreManager(JDBCStoreManager.java:484)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start
(JDBCStoreManager.java:381)
at 
org.jboss.ejb.plugins.CMPPersistenceManager.start
(CMPPersistenceManager.java:157)
at org.jboss.ejb.EntityContainer.startService
(EntityContainer.java:340)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStar
t(ServiceMBeanSupport.java:271)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMBeanSupport.java:221)
at 
sun.reflect.GeneratedMethodAccessor82.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:585)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:72)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:642)
at 
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start
(ServiceController.java:416)
at 
sun.reflect.GeneratedMethodAccessor5.invoke(Unknown 
Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:585)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:72)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke
(MBeanProxyExt.java:176)
at $Proxy278.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService
(EjbModule.java:394)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStar
t(ServiceMBeanSupport.java:271)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMBeanSupport.java:221)
at 
sun.reflect.GeneratedMethodAccessor82.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:585)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:72)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:242

[JBoss-dev] [ jboss-Bugs-1081794 ] JDBCEJBQLCompiler: Invalid SQL for Left join read ahead

2004-12-29 Thread SourceForge.net
Bugs item #1081794, was opened at 2004-12-08 17:21
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1081794group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: gunter zeilinger (gunterze)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: JDBCEJBQLCompiler: Invalid SQL for Left join read ahead 

Initial Comment:
JDBCEJBQLCompiler does not take care to put the right
table name in front of the LEFT JOIN phrase:

Extending the GangsterBean by finder:

query
  query-method
method-namefindMembers_leftjoin/method-name
  method-params
method-paramjava.lang.String/method-param
  /method-params
  /query-method
  jboss-ql![CDATA[
SELECT OBJECT(g)
FROM gangster g
WHERE g.organization.name = ?1
]]
  /jboss-ql
  read-ahead
strategyon-find/strategy
page-size4/page-size
eager-load-groupbasic/eager-load-group
left-join cmr-field=hangout
eager-load-group=quick info/
  /read-ahead
/query

results in:

SELECT t0_g.id, t0_g.name, t0_g.nick_name,
t0_g.badness, t1_g_hangout.id, t1_g_hangout.city,
t1_g_hangout.st, t1_g_hangout.zip FROM GANGSTER t0_g,
ORGANIZATION t2_g_organization LEFT OUTER JOIN LOCATION
t1_g_hangout ON t0_g.hangout=t1_g_hangout.id WHERE
(t2_g_organization.name = ? AND
t0_g.organization=t2_g_organization.name)
0

The order of GANGSTER t0_g, ORGANIZATION
t2_g_organization is wrong. HSQL seems to be able to
intepretate the statement anyway, but other DBs (e.g.
PostgreSQL) report a SQL error.

The EJBQLToSQL92Compiler simple ignores the Left join
read ahead configuration for the cmr field:

SELECT t0_g.id, t0_g.name, t0_g.nick_name,
t0_g.badness, t0_g.cell_area, t0_g.cell_exch,
t0_g.cell_ext, t0_g.page_area, t0_g.page_exch,
t0_g.page_ext, t0_g.email, t0_g.organization,
t0_g.hangout FROM GANGSTER t0_g LEFT OUTER JOIN
ORGANIZATION t1_g_organization ON
t0_g.organization=t1_g_organization.name WHERE
t1_g_organization.name = ?

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: gunter zeilinger (gunterze)
Date: 2004-12-09 13:59

Message:
Logged In: YES 
user_id=93547

I am not familiar with the SQL92 spec. I only know, that
PostgreSQL 7.4.6 and DB2 8.1 returns a SQL error:

PostgreSQL:  ERROR: relation t0_g does not exist

DB2: DB2 SQL error: SQLCODE: -338, SQLSTATE: 42972,
SQLERRMC: null
with SQLSTATE: 42972 = An expression in a join-condition or
ON clause of a MERGE statement references columns in more
than one of the operand tables.

if  the left-hand table of the OUT JOIN is not placed
immediately before the OUT JOIN phrase.

--

Comment By: Alexey Loubyansky (loubyansky)
Date: 2004-12-09 01:31

Message:
Logged In: YES 
user_id=543482

EJBQLToSQL92Compiler does not support read-ahead at all. It
always generates SQL equivalent to on-find for the target
entity unless it's an ejbSelect that queries for a CMP field
or function.This is documented on the wiki.

About syntax error. Is this the spec? It seems to be clear
from the statement how joining should be done. I don't see a
reason for a driver to complain unless it's spec.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1081794group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1057118 ] NPE on TableCache while promoting row

2004-12-29 Thread SourceForge.net
Bugs item #1057118, was opened at 2004-10-29 16:59
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1057118group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Ivan Parra (ioparra)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: NPE on TableCache while promoting row

Initial Comment:
JBoss3_2_6
with Cache Invalidition
JDK1.4

The system was under heavy load both from normal 
means and cache invalidation.  

Race condition???

java.lang.NullPointerException
at 
org.jboss.ejb.plugins.cmp.jdbc2.schema.TableCache$Cac
hedRow.access$202(TableCache.java:418)
at 
org.jboss.ejb.plugins.cmp.jdbc2.schema.TableCache.prom
oteRow(TableCache.java:388)
at 
org.jboss.ejb.plugins.cmp.jdbc2.schema.TableCache.getFi
elds(TableCache.java:157)
at 
org.jboss.ejb.plugins.cmp.jdbc2.schema.PartitionedTableC
ache.getFields(PartitionedTableCache.java:152)
at 
org.jboss.ejb.plugins.cmp.jdbc2.schema.EntityTable$View
.getRowByPk(EntityTable.java:868)
at 
org.jboss.ejb.plugins.cmp.jdbc2.schema.EntityTable.loadR
ow(EntityTable.java:444)
at 
org.jboss.ejb.plugins.cmp.jdbc2.JDBCStoreManager2.loadE
ntity(JDBCStoreManager2.java:347)
at 
org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity
(CMPPersistenceManager.java:338)
at 
org.jboss.resource.connectionmanager.CachedConnection
Interceptor.loadEntity
(CachedConnectionInterceptor.java:355)
at 
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.inv
oke(EntitySynchronizationInterceptor.java:246)
at 
org.jboss.resource.connectionmanager.CachedConnection
Interceptor.invoke
(CachedConnectionInterceptor.java:186)
at 
org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke
(EntityReentranceInterceptor.java:116)
at 
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke
(EntityInstanceInterceptor.java:175)
at 
org.jboss.ejb.plugins.EntityCreationInterceptor.invoke
(EntityCreationInterceptor.java:54)
at 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext
(AbstractTxInterceptor.java:84)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxInterceptorCMT.java:315)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
(TxInterceptorCMT.java:148)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke
(SecurityInterceptor.java:111)
at org.jboss.ejb.plugins.LogInterceptor.invoke
(LogInterceptor.java:191)
at 
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invok
e(ProxyFactoryFinderInterceptor.java:122)
at org.jboss.ejb.EntityContainer.internalInvoke
(EntityContainer.java:484)
at org.jboss.ejb.Container.invoke
(Container.java:709)
at 
org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke
(BaseLocalProxyFactory.java:419)
at org.jboss.ejb.plugins.local.EntityProxy.invoke
(EntityProxy.java:44)
at $Proxy1224.getName(Unknown Source)
at 
com.activereasoning.session.infrastructure.DeviceConfigS
essionBean.updateOrCreateNew
(DeviceConfigSessionBean.java:300)
at sun.reflect.GeneratedMethodAccessor164.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at 
org.jboss.ejb.StatelessSessionContainer$ContainerInterce
ptor.invoke(StatelessSessionContainer.java:683)
at 
org.jboss.resource.connectionmanager.CachedConnection
Interceptor.invoke
(CachedConnectionInterceptor.java:186)
at 
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor
.invoke(StatelessSessionInstanceInterceptor.java:72)
at 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext
(AbstractTxInterceptor.java:84)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxInterceptorCMT.java:315)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
(TxInterceptorCMT.java:148)
at org.jboss.ejb.plugins.AbstractInterceptor.invoke
(AbstractInterceptor.java:94)
at 
com.activereasoning.metrics.MetricsInterceptor.invoke
(MetricsInterceptor.java:63)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke
(SecurityInterceptor.java:111)
at org.jboss.ejb.plugins.LogInterceptor.invoke
(LogInterceptor.java:191)
at 
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invok
e(ProxyFactoryFinderInterceptor.java:122)
at 
org.jboss.ejb.StatelessSessionContainer.internalInvoke
(StatelessSessionContainer.java:331)
at org.jboss.ejb.Container.invoke
(Container.java:709)
at 
org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke
(BaseLocalProxyFactory.java:419)
at 
org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke
(StatelessSessionProxy.java:83)
at $Proxy1772.updateOrCreateNew(Unknown 
Source

[JBoss-dev] [ jboss-Bugs-1042923 ] aspectmanager not found error using web-console

2004-12-29 Thread SourceForge.net
Bugs item #1042923, was opened at 2004-10-08 03:13
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1042923group_id=22866

Category: None
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: peter neville (p_nevilleuk)
Assigned to: Nobody/Anonymous (nobody)
Summary: aspectmanager not found error using web-console

Initial Comment:
Get the attached stack trace shown in the console 
when using the web-console (ie. 
http://localhost:8080/web-console).  This only occurs 
when the applet is enabled and is display when the 
applet shows (inited).

It works for me on 3.2.5, but not 4.0.0

Using:
jboss 4.0.0
windows xp  5.1, x86
jre 1.4.2_01
ie 6.0.2800.1106.xpsp2.030422-1633

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1042923group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-996536 ] Wrong deployment state for non deployable files

2004-12-29 Thread SourceForge.net
Bugs item #996536, was opened at 2004-07-23 06:28
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Bernd Zeitler (frito)
Assigned to: Adrian Brock (ejort)
Summary: Wrong deployment state for non deployable files

Initial Comment:
Hi!

When deploying files without any suitable deployer in
jboss (JBoss 3.2.5), the jar deployer is trying to open
this file. This ends up with a ZipException. The
ZipException is cought within the class
SubDeployerSupport (processNestedDeployments) and a
warning is logged. The file is listed within the
deployed list with status: deployed and state: STARTED.
I assume this file should show up within the incomplete
deployment list with state: FAILED.
Instead of logging this warning, a DeploymentException
should be thrown as mentioned there in the source code.
I changed this (attached file) and it works for me.

Greetings,

Bernd


--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Bernd Zeitler (frito)
Date: 2004-09-14 07:33

Message:
Logged In: YES 
user_id=603154

After posting this to the forum, Scott Stark suggested to
reopen the bug.
The files mentioned above should show up in the incomplete
deployment list with state FAILED.

The forum post:
http://www.jboss.org/index.html?module=bbop=viewtopict=54103

--

Comment By: Adrian Brock (ejort)
Date: 2004-08-26 09:51

Message:
Logged In: YES 
user_id=9459

Your change would mean typos are unexpectedly ignored.

You can exclude files using a filter. See conf/jboss-service.xml
!-- The Filter specifies a java.io.FileFilter for scanned
   directories.  Any file not accepted by this
filter will not be
   deployed.  The
org.jboss.deployment.scanner.DeploymentFilter 
   rejects the following patterns:
   #*, %*, ,*, .*, _$*, *#, *$,
*%, *.BAK, 
   *.old, *.orig, *.rej, *.bak, *,v,
*~, .make.state, 
   .nse_depinfo, CVS, CVS.admin, RCS,
RCSLOG, SCCS, 
   TAGS, core, tags
  --
  attribute
name=Filterorg.jboss.deployment.scanner.DeploymentFilter/attribute

--

Comment By: Bernd Zeitler (frito)
Date: 2004-07-23 07:17

Message:
Logged In: YES 
user_id=603154

... better:
don't deploy these files while adding them to the waiting
for deployer list. The jar deployer should not try to deploy it.

Greetings,
Bernd

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=996536group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1055176 ] NPE in HibernateContext.prepareSession

2004-12-29 Thread SourceForge.net
Bugs item #1055176, was opened at 2004-10-27 02:40
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1055176group_id=22866

Category: Hibernate
Group: v4.0
Status: Closed
Resolution: None
Priority: 3
Submitted By: Heiko W.Rupp (pilhuhn)
Assigned to: Nobody/Anonymous (nobody)
Summary: NPE in HibernateContext.prepareSession

Initial Comment:
Hi,
this might be a pilot error ...

When I try to obtain a session like this:

Session =
HibernateContext.getSession(java:/hibernate/SessionFactory);

I get a NPE

Caused by: java.lang.NullPointerException
at
org.jboss.hibernate.session.HibernateContext.prepareSession(HibernateContext.java:171)
at
org.jboss.hibernate.session.HibernateContext.getSession(HibernateContext.java:99)
at
de.bsd.adb_hibernate.server.ServerFacade.beispiel(ServerFacade.java:22)

If I do it the classical way 

InitialContext ic = new InitialContext();
Object o = ic.lookup(java:/hibernate/SessionFactory);
sf = (SessionFactory)o;

Session sess = sf.openSession()

it works as intended.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1055176group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1051955 ] System property jboss.server.lib.url not used

2004-12-29 Thread SourceForge.net
Bugs item #1051955, was opened at 2004-10-21 21:28
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1051955group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Brian Wallis (bwallis42)
Assigned to: Scott M Stark (starksm)
Summary: System property jboss.server.lib.url not used

Initial Comment:
Linux (Gentoo, 2.6.7 kernel, glibc 2.3.3) 
JDK 1.4.2_05 
JBoss 3.2.3 
 
After much struggling to try and move the server library 
directory to another place (and not under 
${jboss.server.home.url}) I have discovered the the 
property jboss.server.lib.url does not seem to be used 
at all. 
 
The correct way to move the server lib directory (or 
add additional lib directories) is by changing or adding 
classpath entries to 
${jboss.server.conf.dir}/jboss-service.xml, ie: 
 
classpath codebase=lib archives=*/ 
could change to  
classpath codebase=file:/a/b/lib archives=*/ 
to load the library files from that new location. 
 
This is documented in jboss-service.xml. 
 
The jboss.server.lib.dir property should be deprecated 
and documented as such in ServerConfig.java (with 
perhaps a warning generated if it is set) to save future 
confusion by others. 
 

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Scott M Stark (starksm)
Date: 2004-10-24 10:12

Message:
Logged In: YES 
user_id=175228

The jboss.server.lib.dir never has been used as the location
for loading classes from as it is controlled by the
conf/jboss-service.xml classpath as you have discovered.
We'll clarify this in the docs.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1051955group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1062429 ] Problem deleting relations

2004-12-29 Thread SourceForge.net
Bugs item #1062429, was opened at 2004-11-08 06:09
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1062429group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Javier Pedrido (javierpedrido)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: Problem deleting relations

Initial Comment:
I have two CMP 2.x entity beans that have a m:n
relationship (ModelEJB and NodeEJB) and a typical model
has thousands of nodes. The problems arrises when I
want to delete all the nodes related to a model, the
class
org.jboss.ejb.plugins.cmp.jdbc.JDBCDeleteRelationsCommand
creates a sql command so large that neither Oracle nor
MS SqlServer can handle it.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Pekka Vainio (pvainio)
Date: 2004-12-15 04:02

Message:
Logged In: YES 
user_id=125350

Here is a quick fix I had to write for this problem for Sybase.

Limit 150 relations per delete statement is hardcoded into
source.  I can write more sophiticated version if needed.

I hope this helps.

--- clip ---

/*
 * JBoss, the OpenSource J2EE webOS
 *
 * Distributable under LGPL license.
 * See terms of license at gnu.org.
 */
package org.jboss.ejb.plugins.cmp.jdbc;

import java.sql.Connection;
import java.sql.PreparedStatement;
import java.util.ArrayList;
import java.util.Collection;
import java.util.Iterator;
import java.util.List;

import javax.ejb.EJBException;
import javax.sql.DataSource;

import org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMPFieldBridge;
import org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge;
import org.jboss.logging.Logger;

/**
 * Deletes relations from a relation table.
 *
 * @author a href=mailto:[EMAIL PROTECTED]Dain
Sundstrom/a
 * @author a href=mailto:[EMAIL PROTECTED]Alex Loubyansky/a
 * @version $Revision: 1.10.2.7 $
 */
public final class JDBCDeleteRelationsCommand
{
   private final Logger log;

   public JDBCDeleteRelationsCommand(JDBCStoreManager manager)
   {
  // Create the Log
  log = Logger.getLogger(
 this.getClass().getName() +
 . +
 manager.getMetaData().getName());
   }

   public void execute(RelationData relationData)
   {
  if(relationData.removedRelations.size() == 0)
  {
 return;
  }

  Connection con = null;
  PreparedStatement ps = null;
  JDBCCMRFieldBridge cmrField =
relationData.getLeftCMRField();
  
  // Get a copy of removed relations
  ArrayList removed = new
ArrayList(relationData.removedRelations);
  try
  {
// get the connection
DataSource dataSource = cmrField.getDataSource();
con = dataSource.getConnection();
while( ! removed.isEmpty()) {
// Sybase allows max 300 parameters
// Remove 150 relations per statement

// Get first 150 relations
List toRemove = null;
if (removed.size()  150) {
toRemove = removed.subList(0,150);
} else {
toRemove = removed;
}
String sql =
createSQL(relationData,toRemove.size());
// create the statement
if(log.isDebugEnabled())
log.debug(Executing SQL:  + sql);
ps = con.prepareStatement(sql);
// set the parameters
setParameters(ps, relationData, toRemove);
// execute statement
int rowsAffected = ps.executeUpdate();
JDBCUtil.safeClose(ps);
// remove deleted from list
toRemove.clear();
ps = null;
if(log.isDebugEnabled())
   log.debug(Rows affected =  + rowsAffected);
 }
  }
  catch(Exception e)
  {
 throw new EJBException(Could not delete relations
from  +
cmrField.getQualifiedTableName(), e);
  }
  finally
  {
 JDBCUtil.safeClose(ps);
 JDBCUtil.safeClose(con);
  }


   }

   private static String createSQL(RelationData
relationData,int removedRelations)
   {
  JDBCCMRFieldBridge left = relationData.getLeftCMRField();
  JDBCCMRFieldBridge right =
relationData.getRightCMRField();

  StringBuffer sql = new StringBuffer(300);
  sql.append(SQLUtil.DELETE_FROM)
 .append(left.getQualifiedTableName())
 .append(SQLUtil.WHERE);

  if(removedRelations  0)
  {
 StringBuffer whereClause = new StringBuffer(20);
 whereClause.append

[JBoss-dev] [ jboss-Bugs-1058660 ] Deployment problem Cannot find setter method setDocBase null

2004-12-29 Thread SourceForge.net
Bugs item #1058660, was opened at 2004-11-02 00:30
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1058660group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Thomas Fromm (tfromm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Deployment problem Cannot find setter method setDocBase null

Initial Comment:
The bug appears exactly like described here: 
http://www.jboss.org/wiki/Wiki.jsp?page=RunJBossWithJ2SDK1.5Beta 
 
But i use sun jdk 1.4.2_05 with jboss+tomcat 3.2.6 release. 
I have no javax.management* stuff inside the deployed ear. 
Inside the .ear is an embedded .war. If i use the .war as 
standalone, everything is fine. If i remove jboss-app.xml from the 
META-INF also everything is fine. 
Seems, that this problem is not only once of the jdk 1.5. 
 
 

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Sean Sullivan (sullis)
Date: 2004-12-04 23:35

Message:
Logged In: YES 
user_id=156581

I posted the EAR file at 
http://openamf.sourceforge.net/jboss1058660/openamf.ear

Download the EAR using Firefox

Drop a copy of the EAR in c:\jboss-4.0.0
\server\default\deploy



--

Comment By: Sean Sullivan (sullis)
Date: 2004-12-04 23:25

Message:
Logged In: YES 
user_id=156581

I am having a similar problem.   I am deploying an EAR in 
JBoss-4.0.0 with J2SE 1.4.2_06

I will attach the EAR file to this bug report. The EAR's 
filename is openamf.ear


2004-12-04 23:22:45,328 ERROR 
[org.jboss.deployment.MainDeployer] could not start 
deployment: file:/C:/jboss-
4.0.0/server/default/deploy/openamf.ear

org.jboss.deployment.DeploymentException: Error during 
deploy; - nested throwable: (ReflectionException: Cannot 
find setter method setDocBase null Cause: 
java.lang.NoSuchMethodException: 
org.apache.commons.modeler.BaseModelMBean.setDocBase
(java.lang.String))

at org.jboss.web.AbstractWebDeployer.start
(AbstractWebDeployer.java:379)

at org.jboss.web.WebModule.startModule
(WebModule.java:62)

at org.jboss.web.WebModule.startService
(WebModule.java:40)

at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart
(ServiceMBeanSupport.java:271)

at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle
(ServiceMBeanSupport.java:221)

at sun.reflect.GeneratedMethodAccessor2.invoke
(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:141)

at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)

at org.jboss.mx.server.Invocation.invoke
(Invocation.java:72)

at org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:242)

at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:642)

at 
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:891)

at $Proxy0.start(Unknown Source)

at org.jboss.system.ServiceController.start
(ServiceController.java:416)

at sun.reflect.GeneratedMethodAccessor6.invoke
(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:141)

at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)

at org.jboss.mx.server.Invocation.invoke
(Invocation.java:72)

at org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:242)

at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:642)

at org.jboss.mx.util.MBeanProxyExt.invoke
(MBeanProxyExt.java:176)

at $Proxy24.start(Unknown Source)

at org.jboss.web.AbstractWebContainer.start
(AbstractWebContainer.java:362)

at org.jboss.deployment.MainDeployer.start
(MainDeployer.java:935)

at org.jboss.deployment.MainDeployer.start
(MainDeployer.java:927)

at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:746)

at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:709)

at sun.reflect.GeneratedMethodAccessor30.invoke
(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25

[JBoss-dev] [ jboss-Bugs-1058402 ] persistance problem

2004-12-29 Thread SourceForge.net
Bugs item #1058402, was opened at 2004-11-01 13:05
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1058402group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: goeboe (boesler)
Assigned to: Nobody/Anonymous (nobody)
Summary: persistance problem

Initial Comment:
Hi,

I developing an project with JBoss AS 3.0 and it was 
running fine (based on the xpetstore project). Now I 
changed in this project to AS 4.0 (Windows XP, JDK 
1.4). This was no problem without one thing:
When a new user logged in, a new account is generated 
for him. This is realized by an create of an Login-Bean.
In my application the ejbCreate and the ejbPostCreate 
Method are called by a session bean in this case (I see 
two times output lbpc after passing on console), but 
then the process does not turn back to the calling 
session bean. I get no further information (black screen, 
no exception), but Timer-Beans are still running. Then 
after a timeout a rollback is initiated. The data, which 
are set in a value-Object as parameter are set in the 
Login-Bean, but not set in the database (sometimes 
values are set, sometimes not. I could not find out a 
systematic). In an other part of my software I use an 
similar mechanism to create beans and there it's always 
fine. I searched now already some days for a difference, 
but I could not find one. Perhaps you have an idear, 
why I have this mysthic error. 



--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: goeboe (boesler)
Date: 2004-11-13 13:19

Message:
Logged In: YES 
user_id=1150522

Hello,

this problem is solved, but I do not understand why???
I use a default entry in database as base for new users with 
an userId = 0 (find by findByPrimaryKey(0)). From the found 
default bean I take the value, fill up all other attributes with 
new data and create an new Bean with it (see attached file). 
When I looked now for the error again I take off this 
mechanism and created the base bean value with new 
LoginValue() directly and set the id = 0 and the other data 
afterwards and created the bean. Then the error does not 
come again. After that I changed back to the origin 
mechanism (same code as before) and the error does not 
come again (i have no idear why the error does not come 
again).

--

Comment By: Scott M Stark (starksm)
Date: 2004-11-07 10:47

Message:
Logged In: YES 
user_id=175228

We need something in the way of an example which illustrates
the problem your seeing.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1058402group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1049907 ] 3.2.6 - empty folders created under /conf

2004-12-29 Thread SourceForge.net
Bugs item #1049907, was opened at 2004-10-19 02:46
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1049907group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Luc Texier (ltexier)
Assigned to: Nobody/Anonymous (nobody)
Summary: 3.2.6 - empty folders created under /conf

Initial Comment:
Windows XP
1.4.2_05-b04

When running default or all configuration, JBoss creates 
the following empty folders under /conf

 - conf
   - jboss.web
  -localhost

Does not seem to impact the behavior of the server so 
far.







--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1049907group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1036416 ] NullPointerException at org.jfree.data.DefaultTableXYDataset

2004-12-29 Thread SourceForge.net
Bugs item #1036416, was opened at 2004-09-28 11:42
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1036416group_id=22866

Category: None
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Bill Coutinho (bcoutinho)
Assigned to: Nobody/Anonymous (nobody)
Summary: NullPointerException at org.jfree.data.DefaultTableXYDataset

Initial Comment:
I got a NullPointerException when a tried to graph a
Dataset generated by a Snapshot monitor.

I´ve created a snapshot monitor for FreeMemory
ServerInfo attribute. Started it and after some time I
stopped it. It generated some 150 lines of data (I can
see with Show Dataset button).

But when I click Graph Dataset, I got the following
exception:

15:21:56,329 ERROR [Engine] StandardWrapperValve[Manage
Snapshot]: Servlet.service() for servlet Manage
Snapshot threw exception
java.lang.NullPointerException
at
org.jfree.data.DefaultTableXYDataset.getDomainRange()Lorg.jfree.data.Range;(DefaultTableXYDataset.java:537)
at
org.jfree.data.DatasetUtilities.getDomainExtent(Lorg.jfree.data.Dataset;)Lorg.jfree.data.Range;(DatasetUtilities.java:162)
at
org.jfree.chart.plot.XYPlot.getDataRange(Lorg.jfree.chart.axis.ValueAxis;)Lorg.jfree.data.Range;(XYPlot.java:2706)
at
org.jfree.chart.axis.NumberAxis.autoAdjustRange()V(NumberAxis.java:350)
at
org.jfree.chart.axis.NumberAxis.configure()V(NumberAxis.java:333)
at
org.jfree.chart.axis.Axis.setPlot(Lorg.jfree.chart.plot.Plot;)V(Axis.java:715)
at
org.jfree.chart.plot.XYPlot.init(Lorg.jfree.data.XYDataset;Lorg.jfree.chart.axis.ValueAxis;Lorg.jfree.chart.axis.ValueAxis;Lorg.jfree.chart.renderer.XYItemRenderer;)V(XYPlot.java:410)
at
org.jfree.chart.ChartFactory.createXYLineChart(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Lorg.jfree.data.XYDataset;Lorg.jfree.chart.plot.PlotOrientation;ZZZ)Lorg.jfree.chart.JFreeChart;(ChartFactory.java:1289)
at
org.jboss.console.plugins.monitor.ManageSnapshotServlet.doit(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ManageSnapshotServlet.java:192)
at
org.jboss.console.plugins.monitor.ManageSnapshotServlet.doPost(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ManageSnapshotServlet.java:42)
at
javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:717)
at
javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ApplicationFilterChain.java:157)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(ReplyHeaderFilter.java:75)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ApplicationFilterChain.java:186)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(Optimized
Method)
at
org.apache.catalina.core.StandardPipeline.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(Lorg.apache.catalina.Wrapper;Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(StandardContextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(Optimized
Method)
at
org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(Optimized
Method)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(Optimized
Method)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke

[JBoss-dev] [ jboss-Bugs-1048919 ] Redeploy UIL2/OIL under java 1.3

2004-12-29 Thread SourceForge.net
Bugs item #1048919, was opened at 2004-10-17 16:54
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1048919group_id=22866

Category: JBossMQ
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to: Nobody/Anonymous (nobody)
Summary: Redeploy UIL2/OIL under java 1.3

Initial Comment:
org.jboss.mq.il.oil.OILServerILService
org.jboss.mq.il.uil2.UILServerILService

Closing the server socket in stopService()
does not interrupt the accept thread under java 1.3
nor does acceptThread.interrupt() if the thread is in
serverSocket.accept()

Does anybody know how to correctly interrupt a
thread that is in serverSocket.accept() under java 1.3
or is this due to crappy VM implementation?

Using SOTimeout isn't really an option since we
would have to make it a reasonable length of time
to stop it spinning.
Which means to allow a redeploy, we would have to
join the acceptThread. 
This potentially means a long wait during a
redeploy or shutdown.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1048919group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1083715 ] EJB container errors

2004-12-29 Thread SourceForge.net
Bugs item #1083715, was opened at 2004-12-11 18:02
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1083715group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Wei Jiang (wei_jiang)
Assigned to: Nobody/Anonymous (nobody)
Summary: EJB container errors

Initial Comment:
Hi,

I report potential three bugs about ejb container.
The third bug is not related with the first two.

Environemnt: Windows XP. Both jboss 3.2.6 and jboss
4.0.0. Configuration: all.

1. Ejb container should never say: 
  java.lang.NoClassDefFoundError: javax/ejb/EJBException

2. the ejb was deployed successfully. The ejb call a
library
which is specified when server starts:
  run -C d:\jboss326\acelet -c all

The error occurred when the ejb is called. 
But it seems the ejb container does not looks for that
classpath (bootstrap classpath).

3. stateful session bean passivation is implemented 
incorrectly: jdbcConnection is not serializable.


d:\jboss400\binrun -C d:\jboss326\acelet -c all
===
.
  JBoss Bootstrap Environment
.
  JBOSS_HOME: d:\jboss400\bin\..
.
  JAVA: d:\j2sdk1.4.2_06\bin\java
.
  JAVA_OPTS:  -Dprogram.name=run.bat -Xms128m -Xmx512m
.
  CLASSPATH:
d:\j2sdk1.4.2_06\lib\tools.jar;d:\jboss400\bin\run.jar
.
===
.
14:59:03,203 INFO  [Server] Starting JBoss (MX
MicroKernel)...
14:59:03,203 INFO  [Server] Release ID: JBoss [Zion]
4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200
418)
14:59:03,203 INFO  [Server] Home Dir: D:\jboss400
14:59:03,203 INFO  [Server] Home URL: file:/D:/jboss400/
14:59:03,203 INFO  [Server] Library URL:
file:/D:/jboss400/lib/
14:59:03,203 INFO  [Server] Patch URL: null
14:59:03,203 INFO  [Server] Server Name: all
14:59:03,203 INFO  [Server] Server Home Dir:
D:\jboss400\server\all
14:59:03,203 INFO  [Server] Server Home URL:
file:/D:/jboss400/server/all/
14:59:03,203 INFO  [Server] Server Data Dir:
D:\jboss400\server\all\data
14:59:03,203 INFO  [Server] Server Temp Dir:
D:\jboss400\server\all\tmp
14:59:03,218 INFO  [Server] Server Config URL:
file:/D:/jboss400/server/all/conf/
14:59:03,218 INFO  [Server] Server Library URL:
file:/D:/jboss400/server/all/lib/
14:59:03,218 INFO  [Server] Root Deployment Filename:
jboss-service.xml
14:59:03,218 INFO  [Server] Starting General Purpose
Architecture (GPA)...
14:59:03,984 INFO  [ServerInfo] Java version:
1.4.2_06,Sun Microsystems Inc.
14:59:03,984 INFO  [ServerInfo] Java VM: Java
HotSpot(TM) Client VM 1.4.2_06-b03,Sun Microsystems In
c.
14:59:03,984 INFO  [ServerInfo] OS-System: Windows XP
5.1,x86
14:59:04,687 INFO  [Server] Core system initialized
14:59:08,687 INFO  [Log4jService$URLWatchTimerTask]
Configuring from URL: resource:log4j.xml
14:59:08,828 INFO  [WebService] Using RMI server
codebase: http://hp2:8083/
14:59:09,140 INFO  [NamingService] Started
jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.
0.0, Client SocketFactory=null, Server
[EMAIL PROTECTED]
3076
14:59:18,750 INFO  [EjbModule] Deploying
ClusteredHTTPSession
14:59:19,000 INFO  [EJBDeployer] Deployed:
file:/D:/jboss400/server/all/deploy/jbossha-httpsession.s
ar/ClusteredHttpSessionEB.jar/
14:59:25,093 INFO  [Embedded] Catalina naming disabled
14:59:25,812 INFO  [Http11Protocol] Initializing Coyote
HTTP/1.1 on http-0.0.0.0-8080
14:59:25,859 INFO  [Catalina] Initialization processed
in 672 ms
14:59:25,859 INFO  [StandardService] Starting service
jboss.web
14:59:25,859 INFO  [StandardEngine] Starting Servlet
Engine: Apache Tomcat/5.0.28
14:59:25,875 INFO  [StandardHost] XML validation disabled
14:59:25,906 INFO  [Catalina] Server startup in 47 ms
14:59:26,062 INFO  [TomcatDeployer] deploy,
ctxPath=/ebxmlrr, warUrl=file:/D:/jboss400/server/all/de
ploy/ebxmlrr-service.sar/ebxmlrr.war/
14:59:26,671 INFO  [STDOUT] Initialized REST
14:59:26,750 INFO  [SAAJServlet] init
14:59:27,234 INFO  [SAAJServlet] init
14:59:27,421 INFO  [TomcatDeployer] deploy,
ctxPath=/invoker, warUrl=file:/D:/jboss400/server/all/de
ploy/http-invoker.sar/invoker.war/
14:59:27,703 INFO  [TomcatDeployer] deploy,
ctxPath=/ws4ee, warUrl=file:/D:/jboss400/server/all/tmp/
deploy/tmp60926jboss-ws4ee-exp.war/
14:59:27,828 INFO  [TomcatDeployer] deploy, ctxPath=/,
warUrl=file:/D:/jboss400/server/all/deploy/jb
ossweb-tomcat50.sar/ROOT.war/
14:59:33,109 INFO  [STDOUT] Loading properties file:
resourceName = '/org/exolab/castor/castor.prope
rties' fileName = 'castor.properties'
14:59:34,546 INFO  [DefaultPartition] Initializing
14:59:35,031 INFO  [STDOUT]
---
GMS: address is 192.168.0.2:1079 (additional data: 16
bytes)
---
14:59:37,062 INFO  [DefaultPartition] Number of cluster
members: 1
14:59:37,062 INFO  [DefaultPartition] Other

[JBoss-dev] [ jboss-Bugs-1041495 ] bad path to included xsd gets built in WSDLFilePublisher

2004-12-29 Thread SourceForge.net
Bugs item #1041495, was opened at 2004-10-06 07:18
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1041495group_id=22866

Category: JBossWeb
Group: v4.0
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: John Mazz (mazzgolf)
Assigned to: Anil Saldhana (osdchicago)
Summary: bad path to included xsd gets built in WSDLFilePublisher

Initial Comment:
Problem when deploying a web service whose WSDL 
imports/includes other WSDL/schemas.

See attached for a simple hello.war that illustrates this 
problem. To replicate, simply place the war file in the 
JBoss deploy directory and start.

I don't think this has anything to do with platforms, but 
just in case - this is on JBoss 4.0, JDK 1.4.2, Windows 
XP SP1.

Description:

My web service WSDL imports another WSDL which in 
turn includes a schema (these are WSRF specification 
files).

It looks like WSDLFilePublisher is not building the path 
correctly to that included schema. It's missing a / in 
one spot and has a double slash // in another spot. 

While debugging in WSDLFilePublisher, line 206 results in 
this as value for resourcePath: 

WEB-INF/wsdl//services/../spec/wsrfWS-
ResourceProperties-1_1.xsd 

Note that there is a / missing between the last 
directory wsrf and the schema filename WS-
ResourceProperties-1_1.xsd. There is also a double 
slash // in there as well.  The double-slash is probably 
OK and most file systems will parse it fine, however, 
obviously the missing slash is going to cause problems 
(which it does on my box).

The value of this.expLocation was WEB-INF/wsdl/ and 
the value of schemaLocation was WS-
ResourceProperties-1_1.xsd. baseURI had a value 
of file:/C:/mazz/jboss/jboss-
4.0.0/server/default/data/wsdl/jboss-
wsdm.war/services/../spec/wsrf/WS-ResourceProperties-
1_1.wsdl. this.di.shortName is jboss-wsdm.war. index 
is 57. All of those values are correct.

The WSDL includes the .xsd like this: 

wsd:typesxsd:schema 
xsd:include schemaLocation=WS-ResourceProperties-
1_1.xsd/ 
... 

The resulting exception is (which is actually thrown in 
line 210): 

16:13:24,774 ERROR [ServiceDeployer] Cannot startup 
webservice for: jboss-wsdm.war 
org.jboss.deployment.DeploymentException: Cannot 
publish wsdl to: C:\mazz\jboss\jboss-4.0.0
\server\default\data\wsdl\jboss-
wsdm.war\services\sensor.wsdl; - nested throwable: 
(java.lang.IllegalArgumentException: Cannot find schema 
import in 
deployment: WEB-INF/wsdl//services/../spec/wsrfWS-
ResourceProperties-1_1.xsd) 
at 
org.jboss.webservice.WSDLFilePublisher.publishWsdlFile
(WSDLFilePublisher.java:106)

If, in my debugger, I fix the resourcePath evaluated on 
line 205 such that the path has the proper slashes, my 
web service deploys fine.

In this example, its as if I made this fix on line 205 of 
WSDLFilePublisher.java

from:

   resourcePath = resourcePath.substring(0, 
resourcePath.lastIndexOf(/));

to:

   resourcePath = resourcePath.substring(1, 
resourcePath.lastIndexOf(/) + 1);

Obviously, it would be best if no assumptions were made 
about the location of / (that is to say, don't assume 
resourcePath has a leading / - I do above and hence 
the 1 in the first argument to substring).  Probably 
would be better if we do something like this for the first 
parameter to that substring:

resourcePath.charAt(0) == / ? 1 : 0

Same holds true with that second argument.  We should 
not do the +1 if we know the schemaLocation is an 
absolute path.  Otherwise, we'd introduce another 
double slash.  So, perhaps, line 205 should be the 
following:

   resourcePath = resourcePath.substring
(resourcePath.chatAt(0) == / ? 1 : 0, 
resourcePath.lastIndexOf(/) + (schemaLocation.charAt
(0) == / ? 0 : 1));

I'll leave it up to the commiter to decide the best course 
of action.

John Mazz

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Anil Saldhana (osdchicago)
Date: 2004-11-16 12:54

Message:
Logged In: YES 
user_id=768753

Fixed in Branch 4.0

--

Comment By: Thomas Diesler (tdiesler)
Date: 2004-11-14 05:22

Message:
Logged In: YES 
user_id=423364

Anil, when you look at this please make sure you run the 
webservices/wsdlImport CTS tests. They already contain 120 
tests that deal with imports and includes in various 
combinations. Currently they all pass.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1041495group_id=22866

[JBoss-dev] [ jboss-Bugs-928024 ] Class Loader Classpath Conflict

2004-12-29 Thread SourceForge.net
Bugs item #928024, was opened at 2004-04-01 21:30
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=928024group_id=22866

Category: JBossSOAP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Jula (julajula)
Assigned to: Scott M Stark (starksm)
Summary: Class Loader Classpath Conflict

Initial Comment:
The JDOM jar which is being used by JBoss is newer to 
what is used in my web service. So I explicitly gave the 
following command to avoid looking at the 3.2.2 servers 
jar. 

jboss-web
   class-loading java2ClassLoadingCompliance=false
  loader-repository
 jboss.test:war=oldxerces.war
 loader-repository-config
java2ParentDelegation=false
 /loader-repository-config
  /loader-repository
   /class-loading
/jboss-web

It solved JDOM error but now I get another error. The 
stack trace is attached here with.

I am simply trying to use FOP to generate a PDF using 
the fop.jar, batik.jar, xalan-2.4.1.jar components in 
addition to using JDOM. These 4 jars are inside my EAR.





--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Andreas (a5sk4s)
Date: 2004-04-05 16:13

Message:
Logged In: YES 
user_id=1006817

I'm facing a similar problem and I'm using

JBoss (MX MicroKernel) [3.2.3 (build: CVSTag=JBoss_3_2_3 
date=200311301445)]

Testcase:

(1) Use polls.war v2.5.1 available from 
http://sourceforge.net/project/showfiles.php?
group_id=61325package_id=57688release_id=214204

(2) Add suitable jboss-web.xml to war file.  I'm using one with 
the following content:

?xml version=1.0 encoding=UTF-8 ? 
!DOCTYPE jboss-app PUBLIC '-//JBoss//DTD Web Application 
2.3V2//EN' 'http://www.jboss.org/j2ee/dtd/jboss-
web_3_2.dtd'
jboss-web
   class-loading java2ClassLoadingCompliance=false
   loader-repository
 org.sf:war=polls2.5.1.war
 loader-repository-
configjava2ParentDelegation=false/loader-repository-
config
   /loader-repository
   /class-loading
/jboss-web
 
For details please see http://www.jboss.org/index.html?
module=bbop=viewtopict=47849

Andreas

--

Comment By: Scott M Stark (starksm)
Date: 2004-04-02 07:37

Message:
Logged In: YES 
user_id=175228

jboss-3.2.2 did not have adequate separation between the web
container deployer and the web application. This was fixed
in 3.2.3 so you have to use that version or simply replace
the jboss version of jdom with your own. If there is still
an issue in 3.2.3 then I need a testcase.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=928024group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1073004 ] Finder with null EQL string reported o wrong entity bean

2004-12-29 Thread SourceForge.net
Bugs item #1073004, was opened at 2004-11-24 23:45
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1073004group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: davout (davout)
Assigned to: Nobody/Anonymous (nobody)
Summary: Finder with null EQL string reported o wrong entity bean

Initial Comment:
I've noticed that if you mistakenly create a 'finder' 
method in a CMP entity bean with an empty EQL string 
then on deployment the application server reports this 
error with the wrong entity bean name and a misleading 
error message.

It seems to use the last entity bean name in the 
deployment list irrespective of where the EQL occurs. 

It also reports the error as...

org.jboss.ejb.plugins.cmp.ejbql.ParseException: FROM 
not found

... which is correct but also misleading.

It ought to report something like

null EQL string






--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1073004group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1048135 ] last CMP entity creates a class cast exception

2004-12-29 Thread SourceForge.net
Bugs item #1048135, was opened at 2004-10-15 17:00
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1048135group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Ivan Parra (ioparra)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: last CMP entity creates a class cast exception

Initial Comment:
JBoss3_2_6
Win2k
JRE1.4_2_05
I noticed that the last entity failed.  To confirm it was 
not our code, I switched the ordering of the last 2 
entities in ejb-jar.xml.  Both times, the last entity failed.

In our environment, we are deploying 169 CMPs.  I 
stripped down the application.xml to only deploy this one 
module(it only deploys cmps, nothing else).  

16:49:48,640 ERROR [EntityContainer] Starting failed 
jboss.j2ee:jndiName=com.activereasoning.persistance.Ap
pLibraryConfigLocal,service=EJB
java.lang.ClassCastException
at 
org.jboss.ejb.plugins.cmp.jdbc2.bridge.JDBCCMRFieldBridg
e2.resolveRelationship(JDBCCMRFieldBridge2.java:118)
at 
org.jboss.ejb.plugins.cmp.jdbc2.bridge.JDBCEntityBridge2.
resolveRelationships(JDBCEntityBridge2.java:99)
at 
org.jboss.ejb.plugins.cmp.jdbc2.JDBCStoreManager2.resol
veRelationships(JDBCStoreManager2.java:421)
at 
org.jboss.ejb.plugins.cmp.jdbc2.JDBCStoreManager2.start
(JDBCStoreManager2.java:173)
at 
org.jboss.ejb.plugins.CMPPersistenceManager.start
(CMPPersistenceManager.java:155)
at org.jboss.ejb.EntityContainer.startService
(EntityContainer.java:337)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart
(ServiceMBeanSupport.java:271)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at 
org.jboss.mx.server.ReflectedDispatcher.dispatch
(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:82)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:473)
at 
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:884)
at $Proxy18.start(Unknown Source)
at org.jboss.system.ServiceController.start
(ServiceController.java:414)
at sun.reflect.GeneratedMethodAccessor6.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at 
org.jboss.mx.server.ReflectedDispatcher.dispatch
(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:82)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke
(MBeanProxyExt.java:176)
at $Proxy94.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService
(EjbModule.java:367)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart
(ServiceMBeanSupport.java:271)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at 
org.jboss.mx.server.ReflectedDispatcher.dispatch
(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke
(Invocation.java:82)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:197)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:473)
at 
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:884)
at $Proxy18.start(Unknown Source)
at org.jboss.system.ServiceController.start
(ServiceController.java:414)
at sun.reflect.GeneratedMethodAccessor6.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324

[JBoss-dev] [ jboss-Bugs-1078390 ] Farm deployment fails to propagate to other servers

2004-12-29 Thread SourceForge.net
Bugs item #1078390, was opened at 2004-12-03 07:29
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1078390group_id=22866

Category: Clustering
Group: v4.0
Status: Closed
Resolution: None
Priority: 8
Submitted By: proudchief (proudchief)
Assigned to: Nobody/Anonymous (nobody)
Summary: Farm deployment fails to propagate to other servers

Initial Comment:
Two-node cluster, identical environments. Deployment of 
simple WAR to farm directory of one fails to deploy to 
the second node, until that node is restarted. No 
console output on second node when deployment occurs 
on first node. The scan period in the farm-service.xml 
file is set to 5000 on both servers.

Operating system: Linux (Novell Linux Desktop 9)
JDK: Sun 1.4.2_06

Output from both server consoles is attached. The 
scenario:

- Each node is started, first one until it's completely up, 
then the second. The second node joins the cluster. 
- A simple WAR file containing one simple servlet is 
copied inot the farm directory of the first server, and 
the deployment message shows in the console output
- No output for the deployment is seen on the second 
server console, no deployment is done.
- To get the WAR deployed on the second server 
requires a restart.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1078390group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1035389 ] permanent File-Lock on JARs in EAR

2004-12-29 Thread SourceForge.net
Bugs item #1035389, was opened at 2004-09-27 04:27
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1035389group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Thomas Krug (tkrug0210)
Assigned to: Scott M Stark (starksm)
Summary: permanent File-Lock on JARs in EAR

Initial Comment:
After deploying an exploded EAR with JARs on EAR level 
even after undeployment through the JMX-Console the 
directory cannot be deleted or the JARs replaced (file-
lock by jboss or the VM)

Putting the JARs in the WAR (WEB-INF\lib) everything 
works fine.

See attached ZIP, after undeployment the 
ThunderbirdUtil.jar can't be deleted or renamed.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1035389group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1031357 ] jaxr service xml security classes broken with jdk 1.4.2_05

2004-12-29 Thread SourceForge.net
Bugs item #1031357, was opened at 2004-09-20 09:36
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1031357group_id=22866

Category: JBossWeb
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Scott M Stark (starksm)
Summary: jaxr service xml security classes broken with jdk 1.4.2_05

Initial Comment:
Stating 4.0.0 with jdk 1.4.2_05 results in the
following exception in the jaxr service. The apache xml
security classes need to be updated.

16:19:14,353 ERROR [Engine]
StandardContext[/ebxmlrr]StandardWrapper.Throwable
java.lang.IllegalAccessError: tried to access field
org.apache.xpath.compiler.FunctionTable.m_functions
from class org.apache.xml.security.Init
at org.apache.xml.security.Init.init(Init.java:233)
at
org.jboss.jaxr.servlet.SAAJServlet.init(SAAJServlet.java:86)
at
javax.servlet.GenericServlet.init(GenericServlet.java:211)
at
org.jboss.jaxr.servlet.SAAJServlet.init(SAAJServlet.java:76)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4013)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4357)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
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:324)

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: ukriegel (ukriegel)
Date: 2004-10-01 02:27

Message:
Logged In: YES 
user_id=1129053

Error does not occur in Java 5

--

Comment By: ukriegel (ukriegel)
Date: 2004-10-01 02:26

Message:
Logged In: YES 
user_id=1129053

Error does not occur in Java 5

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1031357group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1056004 ] batch-cascade-delete problem

2004-12-29 Thread SourceForge.net
Bugs item #1056004, was opened at 2004-10-28 03:42
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1056004group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Vladimir Stefanyuk (kletchatey)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: batch-cascade-delete problem

Initial Comment:
I have 4 entities:

Client
Project
Order
OrderLine

Order has a NOT-NULL foregin key reference to Client.
Order has a NULL-ABLE foreign key reference to Project.
OrderLine has NOT-NULL foreign key reference to Order.

Between Order and Client, Order and Project, OrderLine 
and Order are 1:M relations.

For OrderLine-Order relation cascade-delete/ is 
specified in ejb-jar.xml.
To prevent from UDATING to NULL orderId in OrderLine, 
batch-cascade-delete/ is specified in jbosscmp-
jdbc.xml.

The problem is, that when Order is deleted, an attempt 
is made to UPDATE Order NOT-NULL foreign keys to NULL 
values.
In case if batch-cascade-delete/ is not specified this 
problem doesn't appear, but of course problem with 
updating OrderLine orderId field appear.

Note: This updating is doing only for foreign-keys that 
contains NOT-NULL values.


--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Vitaliy Morarian (vmorarian)
Date: 2004-11-03 04:26

Message:
Logged In: YES 
user_id=1151684

Have the same situation (JBoss 3.2.5)
In what version will be fixed this bug?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1056004group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1025035 ] Warning message not found when deploying WS4EE Web Service

2004-12-29 Thread SourceForge.net
Bugs item #1025035, was opened at 2004-09-09 04:32
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1025035group_id=22866

Category: None
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Davey (davidsalter)
Assigned to: Thomas Diesler (tdiesler)
Summary: Warning message not found when deploying WS4EE Web Service

Initial Comment:
When deploying a WS4EE webservice, a message 
stating no warning message is found is displayed on 
the console when a method in the endpoint interface 
does not implement java.rmi.RemoteException.

In this situation, the JBoss console instructs the 
developer to file a bug report.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1025035group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1072634 ] EJB-QL produces incorrect SQL

2004-12-29 Thread SourceForge.net
Bugs item #1072634, was opened at 2004-11-24 09:44
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1072634group_id=22866

Category: JBossCMP
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Christopher G. Stach II (cstach)
Assigned to: Nobody/Anonymous (nobody)
Summary: EJB-QL produces incorrect SQL

Initial Comment:
It seems that it's forgetting to put in the relation table...

ejb-jar.xml snippets:

 query
description![CDATA[]]/description
query-method
   method-
nameejbSelectRemainingThingCount/method-name
   method-params
  method-paramjava.lang.Long/method-
param
   /method-params
/query-method
ejb-ql![CDATA[SELECT COUNT(DISTINCT c) 
FROM item o, thing c, IN (o.historyList) AS mh WHERE 
o.id = ?1 AND c MEMBER OF o.thingList AND c  
mh.thingInfo.thing]]/ejb-ql
 /query

[...]

  ejb-relation 
 ejb-relation-nameThing-Thing Info/ejb-
relation-name

 ejb-relationship-role 
ejb-relationship-role-namething-info-belongs-
to-thing/ejb-relationship-role-name
multiplicityMany/multiplicity
cascade-delete/
relationship-role-source 
   ejb-nameThingInfo/ejb-name
/relationship-role-source
cmr-field 
   cmr-field-namething/cmr-field-name
/cmr-field
 /ejb-relationship-role

 ejb-relationship-role 
ejb-relationship-role-namething-has-thing-
infos/ejb-relationship-role-name
multiplicityOne/multiplicity
relationship-role-source 
   ejb-nameThing/ejb-name
/relationship-role-source
cmr-field 
   cmr-field-namethingInfoList/cmr-field-
name
   cmr-field-typejava.util.Set/cmr-field-
type
/cmr-field
 /ejb-relationship-role

  /ejb-relation

  ejb-relation 
 ejb-relation-nameThing Info-History/ejb-
relation-name

 ejb-relationship-role 
ejb-relationship-role-namehistory-belongs-to-
thing-info/ejb-relationship-role-name
multiplicityMany/multiplicity
cascade-delete/
relationship-role-source 
   ejb-nameHistory/ejb-name
/relationship-role-source
cmr-field 
   cmr-field-namethingInfo/cmr-field-name
/cmr-field
 /ejb-relationship-role

 ejb-relationship-role 
ejb-relationship-role-namething-info-has-
history/ejb-relationship-role-name
multiplicityOne/multiplicity
relationship-role-source 
   ejb-nameThingInfo/ejb-name
/relationship-role-source
cmr-field 
   cmr-field-namehistoryList/cmr-field-name
   cmr-field-typejava.util.Set/cmr-field-
type
/cmr-field
 /ejb-relationship-role

  /ejb-relation

  ejb-relation 
 ejb-relation-nameItem-Thing/ejb-relation-
name

 ejb-relationship-role 
ejb-relationship-role-namething-belongs-to-
items/ejb-relationship-role-name
multiplicityMany/multiplicity
relationship-role-source 
   ejb-nameThing/ejb-name
/relationship-role-source
cmr-field 
   cmr-field-nameitemList/cmr-field-name
   cmr-field-typejava.util.Set/cmr-field-
type
/cmr-field
 /ejb-relationship-role

 ejb-relationship-role 
ejb-relationship-role-nameitem-has-
things/ejb-relationship-role-name
multiplicityMany/multiplicity
relationship-role-source 
   ejb-nameItem/ejb-name
/relationship-role-source
cmr-field 
   cmr-field-namethingList/cmr-field-name
   cmr-field-typejava.util.Set/cmr-field-
type
/cmr-field
 /ejb-relationship-role

  /ejb-relation

jbosscmp-jdbc.xml:

ejb-relation
  ejb-relation-nameThing-Thing Info/ejb-relation-
name

  ejb-relationship-role
  ejb-relationship-role-namething-info-belongs-
to-thing/ejb-relationship-role-name
  fk-constrainttrue/fk-constraint
  key-fields/

batch-cascade-delete/
  /ejb-relationship-role
  ejb-relationship-role
  ejb-relationship-role-namething-has-thing-
infos/ejb-relationship-role-name
  key-fields
 key-field
   field-nameid/field-name
   column-namething_id/column-name
 /key-field
  /key-fields

  /ejb-relationship-role
/ejb-relation

ejb-relation
  ejb-relation-nameItem-Thing/ejb-relation-name
  relation-table-mapping
table-namething_to_item/table-name
  /relation-table-mapping

  ejb-relationship-role

[JBoss-dev] [ jboss-Bugs-1045277 ] Deployment problem, sar with nested war

2004-12-29 Thread SourceForge.net
Bugs item #1045277, was opened at 2004-10-12 05:17
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1045277group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 7
Submitted By: ycarmel (ycarmel)
Assigned to: Nobody/Anonymous (nobody)
Summary: Deployment problem, sar with nested war

Initial Comment:
I have a sar file with a nested war file. Both are very 
simple, a few utility jars in the sar and only one servlet 
with its corresponding web.xml are in the war. I'm using 
JBoss 3.2.5, JDK 1.4.2_05. on windows 2000 server. 

With my sar in the deploy directory it fails to deploy the 
sar. I get the following error: Code: 
org.jboss.deployment.DeploymentException: Was unable 
to move war to: C:\work\jboss-3.2.5
\server\default\tmp\deploy\tmp56549mysar.sar-
contents\mywar.war.tmp  
 


But it works if I deploy the sar in expanded format with 
the war also in expanded format. 

To reproduce the problem prepare a zipped sar with a 
nested war,put it in the deploy directory and start jboss.



--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: wytten (wytten)
Date: 2004-12-15 11:55

Message:
Logged In: YES 
user_id=1179081

My experience is that this problem exists in 3.2.6, but NOT
in 3.2.3.

--

Comment By: ycarmel (ycarmel)
Date: 2004-10-12 05:51

Message:
Logged In: YES 
user_id=1137666

It also works when i'm redeploying the sar.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1045277group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1064328 ] JBoss 3.2.6 cannot be build using IBM SDK 1.4.2

2004-12-29 Thread SourceForge.net
Bugs item #1064328, was opened at 2004-11-10 21:39
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1064328group_id=22866

Category: Build System
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Ulrich Romahn (diggermaus)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBoss 3.2.6 cannot be build using IBM SDK 1.4.2

Initial Comment:
Whe trying to build JBoss 3.2.6 using IBM's
JDK1.4.2-1.0 on a Linux box, I get the following
exception during the compile of JBoss JMX:
error: IO exception sun.io.MalformedInputException

I get this error exactly three times but no further
message nor a stack trace.

I assume that there are some dependencies to Sun's SDK
in the build system (Ant) because of the sun.io
exception which I should't see using IBM's JDK.

Howver, the precompiled version (with Sun's JDK, I
assume) seems to run flawlessly on IBM's JDK.

I would really like to build JBoss with IBM's JDK
because IBM's javac produces much more optimized code
and performs much faster on Linux with the 2.6 kernel.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Dimitris Andreadis (andd)
Date: 2004-11-11 23:10

Message:
Logged In: YES 
user_id=583305

Cleaning and posting back those files would be great, since 
we rarely use IBM's JDK here!

Thanks

--

Comment By: Ulrich Romahn (diggermaus)
Date: 2004-11-11 18:01

Message:
Logged In: YES 
user_id=579922

Thanks to the comment below, I got past the first error, but 
now IBM's javac reports another compile error:
In class 
org.apache.axis.components.net.SunJSSESocketFactory.java 
it references classes from Sun that obviously cannot be 
resolved. It references classes in the package 
com.sun.net.ssl which are not part of IBM's JDK.

I assume that JBoss has never really been compiled with the 
IBM JDK because otherwise this would have been caught.

I am not sure if anybody at JBoss will tackle this issue or if it 
will be my responsibility to clean these references and then 
feed it back to JBoss.

--

Comment By: Ulrich Romahn (diggermaus)
Date: 2004-11-11 18:00

Message:
Logged In: YES 
user_id=579922

Thanks to the comment below, I got past the first error, but 
now IBM's javac reports another compile error:
In class 
org.apache.axis.components.net.SunJSSESocketFactory.java 
it references classes from Sun that obviously cannot be 
resolved. It references classes in the package 
com.sun.net.ssl which are not part of IBM's JDK.

I assume that JBoss has never really been compiled with the 
IBM JDK because otherwise this would have been caught.

I am not sure if anybody at JBoss will tackle this issue or if it 
will be my responsibility to clean these references and then 
feed it back to JBoss.

--

Comment By: Igor Fedorenko (igorfie)
Date: 2004-11-10 22:20

Message:
Logged In: YES 
user_id=232950

As a guess, try export LANG=en_US before running the
build. I had similar problem building other software on
redhat 9 box. It turned out that sources had non-ascii
characters in comments. IBM I/O libs correctly rejected to
read them using default UTF-8 encoding.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1064328group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-880447 ] Tomcat doesn't call contextDestroyed() on JBoss shutdown

2004-12-29 Thread SourceForge.net
Bugs item #880447, was opened at 2004-01-20 01:06
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=880447group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Sean Clarke (seanclarke04)
Assigned to: Nobody/Anonymous (nobody)
Summary: Tomcat doesn't call contextDestroyed() on JBoss shutdown

Initial Comment:
Hi,  
For some reason when I shut JBoss down (either ^C or 
shutdown script) Tomcat doesn't get a chance to call  
contextDestroyed on my application. I have tried Tomcat 
(standalone) 4.1.24 and 5.x and it works fine.  
  
contextInitialised is called on startup, but contextDestroyed 
remains uncalled.  

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=880447group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1035252 ] build.xml incorrect

2004-12-29 Thread SourceForge.net
Bugs item #1035252, was opened at 2004-09-26 20:20
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1035252group_id=22866

Category: Build System
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Craig Johannsen (cjohan)
Assigned to: Bill Burke (patriot1burke)
Summary: build.xml incorrect

Initial Comment:
For the AOP annotation example, the build.xml file is
incorrect in several ways:
1.) It does not pick up the jboss version of ant.
2.) It does not find the proper jar files.

The effect is that one runs ant and gets messages about
some ant tasks not found.  Then, when that is fixed,
one gets messages about classes not found, due to the
improperly defined classpaths.

What is the intention of this build file?  Where was it
supposed to find the jars?

Here is an example fix that works only after the user
has built the source by running build.sh:

[EMAIL PROTECTED] annotation]$ diff build_orig.xml
build.xml
3a4,8
property name=rel value=jboss-4.0.0 /
property name=jboss.lib
value=../../../../build/output/${rel}/lib /
property name=jboss.all.lib
value=../../../../build/output/${rel}/server/all/lib /
property name=aop.jdk1.5.lib
value=../../../output/lib /
property name=thirdparty
value=../../../../thirdparty /
6c11
  pathelement path=../../../javassist.jar/
---
  pathelement
path=${jboss.all.lib}/javassist.jar/
10c15
  pathelement path=../../../trove.jar/
---
  pathelement
path=${thirdparty}/trove/lib/trove.jar/
14c19
  pathelement path=../../../concurrent.jar/
---
  pathelement
path=${jboss.lib}/concurrent.jar/
18c23
  pathelement path=../../../jboss-common.jar/
---
  pathelement
path=${jboss.lib}/jboss-common.jar/
22c27,28
  pathelement
path=../../../jboss-aop-jdk15.jar/
---
  pathelement
path=${aop.jdk1.5.lib}/jboss-aop-jdk15.jar/
pathelement
path=${aop.jdk1.5.lib}/jboss-aop.jar/
26c32
  pathelement path=../../../qdox.jar/
---
  pathelement path=${thirdparty}/qdox.jar/

Except javassist.jar was missing, so I'm not positive
the above fix is completely correct.  Copying the
javassist.jar from RC1 resulted in a NoClassDefFoundError:
compile:
 [aopc] [debug] jboss.aop.class.path is NULL
 [aopc] [debug] jboss.aop.search.classpath: 'null' true
 [aopc] [debug] jboss.aop.path:
/home/craigj/jboss-4.0.0-src/aop/docs/examples/annotation/jboss-aop.xml
 [aopc] jboss.aop.path[0]:
/home/craigj/jboss-4.0.0-src/aop/docs/examples/annotation/jboss-aop.xml
 [aopc] [deploying]
file:/home/craigj/jboss-4.0.0-src/aop/docs/examples/annotation/jboss-aop.xml
 [aopc] [deploy] bind
file:/home/craigj/jboss-4.0.0-src/aop/docs/examples/annotation/jboss-aop.xml
 [aopc] [deploy] bind
file:/home/craigj/jboss-4.0.0-src/aop/docs/examples/annotation/jboss-aop.xml
 [aopc] [deploy] bind
file:/home/craigj/jboss-4.0.0-src/aop/docs/examples/annotation/jboss-aop.xml
 [aopc] Exception in thread main
java.lang.NoClassDefFoundError:
javassist/bytecode/AnnotationsAttribute
 [aopc] at
org.jboss.aop.AspectManager.translate(AspectManager.java:470)
 [aopc] at
org.jboss.aop.AspectManager.transform(AspectManager.java:404)
 [aopc] at
org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:201)
 [aopc] at
org.jboss.aop.standalone.Compiler.compile(Compiler.java:162)
 [aopc] at
org.jboss.aop.standalone.Compiler.main(Compiler.java:61)




--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Scott M Stark (starksm)
Date: 2004-11-07 10:35

Message:
Logged In: YES 
user_id=175228

Bill, can you take a look at this an reassign it if needed.

--

Comment By: Craig Johannsen (cjohan)
Date: 2004-09-26 20:57

Message:
Logged In: YES 
user_id=47444

Sorry to keep adding comments to my own bug report, but I
keep noticing things I forgot to mention.

NOTE: The attached patch only fixes the classpaths -- it
does not fix the problem of finding the correct Ant instance
nor does it fix the problem of building the jars15 target
automatically, though the latter should be easy to add.

--

Comment By: Craig Johannsen (cjohan)
Date: 2004-09-26 20:52

Message:
Logged In: YES 
user_id=47444

CORRECTION:  javasisist.jar is not missing.  It was moved to
the thirdparty directory.

I neglected above to mention that for the annotation example
to work, one must build the jars15 target at the top

[JBoss-dev] [ jboss-Bugs-937767 ] left-join descriptor is problematic

2004-12-29 Thread SourceForge.net
Bugs item #937767, was opened at 2004-04-19 02:54
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=937767group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Micah Spears (lamarguy)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: left-join descriptor is problematic

Initial Comment:
I applaud the new the left-join read ahead option but
the xml descriptors in jbosscmp-jdbc.xml are difficult
to configure.  reasons for descriptor change are:

1.) for each query I wish to left-join, I have to
specify the cmr fields each time which leads to
redundancy.  grouping the joins is more logical like
load-groups are handled.

2.) writing xdoclet support is non-trivial for the
current left-join descriptors.

so I propose the syntax change from, for example,

read-ahead
  strategyon-find/strategy
  eager-load-groupreport/eager-load-group
  left-join cmr-field=lineItems/
 left-join cmr-field=product
eager-load-group=short/
  /left-join
  left-join cmr-field=customer
eager-load-group=basic/
/read-ahead

to

read-ahead
  strategyon-find/strategy
  eager-load-groupreport/eager-load-group
  left-join-groupgroup_a/left-join-group
/read-ahead

left-join-groups
  left-join-group
 namegroup_a/name
 descriptionexample left join group/description
 left-join
   cmr-fieldlineItems/cmr-field
   left-join
 cmr-fieldproduct/cmr-field
 eager-load-groupshort/eager-load-group
   /left-join
 /left-join
 left-join
   cmr-fieldcustomer/cmr-field
   eager-load-groupbasic/eager-load-group
 /left-join
  /left-join-group
/left-join-groups
 
in addition, maybe left-join should be renamed to
relation-join for clarity.





--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Alexey Loubyansky (loubyansky)
Date: 2004-04-20 09:35

Message:
Logged In: YES 
user_id=543482

This is not a bug. I reposted this to the forums. Let's
discuss it there. Thanks!
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831614

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=937767group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1065491 ] war isolation issue

2004-12-29 Thread SourceForge.net
Bugs item #1065491, was opened at 2004-11-12 14:51
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1065491group_id=22866

Category: JBossMX
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Don Hill (ssswdon)
Assigned to: Scott M Stark (starksm)
Summary: war isolation issue

Initial Comment:
I am trying to get war isolation to work for the
default configuration of jboss-4.0.0, The issue I have
is that there exist a older version of castor in
default/lib folder and I need to use a newer version, I
know I can just remove it but the problem is I am
trying to use war isolation for the classloader or get
the CL to look for a class in the web-inf/lib first
before going to the parent, Here is the jboss-web.xml I
am using
class-loading java2ClassLoadingCompliance='false'
   loader-repository
  test.issue.com:loader=issue.war
  loader-repository-config
 java2ParentDelegaton=false
  /loader-repository-config
   /loader-repository
   /class-loading
I have tried several options and the only way I can get
it to work is by changing the setting in
jboss-service.xml to attribute
name=Java2ClassLoadingCompliancefalse/attribute. I
have attached a war file that will dump some xml after
running through castor that is in the web-inf/lib if
the older castor is in the default/lib it will throw a
NPE, I am not sure but I think this will also be the
case in the server/all config.



--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Scott M Stark (starksm)
Date: 2004-11-23 18:54

Message:
Logged In: YES 
user_id=175228

The default isolation is being removed. 4.0.1RC1 uses the
same flat class loading model by default that 3.2 does and
this will read the web level class loader configuration. The
default flat class loading model has been a feature of jboss
since 3.0.x.

--

Comment By: Dan Small (dsmall0)
Date: 2004-11-23 18:51

Message:
Logged In: YES 
user_id=1104154

OK, thanks.

But what about this difference between 4.0.0 and 
4.0.1rc1?   

That is I would like to know, if possible, what 
direction jboss is going in before I update our install 
doc.  

Also, is this 'un-encapsulation' of dom4j and jaxen 
usage a feature?


--

Comment By: Scott M Stark (starksm)
Date: 2004-11-23 18:09

Message:
Logged In: YES 
user_id=175228

The oberon war fails due to default configuration of the
tomcat container which does not read the
WEB-INF/jboss-web.xml class loader config. The
jboss-4.0.0/server/default config runs more like standalone
tomcat but it not using the servlet 2.3 class loading model
by default. Edit the
jbossweb-tomcat50.sar/META-INF/jboss-service.xml and either set:
attribute name=Java2ClassLoadingCompliancefalse/attribute

or enable the parsing of the jboss-web.xml class loading
settings by setting:

attribute name=UseJBossWebLoadertrue/attribute


--

Comment By: Scott M Stark (starksm)
Date: 2004-11-23 07:28

Message:
Logged In: YES 
user_id=175228

Correct. So can you provide the servlet which demonstrates
how castor is being used as requested?


--

Comment By: Don Hill (ssswdon)
Date: 2004-11-23 06:09

Message:
Logged In: YES 
user_id=1158015

I want to be able to deploy a war in the default and all
config without having to modify the server configs, I
thought that I was able to add the class loading entry in
the jboss-web, jbos-app ... and get the behavior that I
needed, what I need is for the classloader of the war to
load classes from the web container e.g,
/web-inf/classes/lib before looking for the classes in the
parent CL.

hth

--

Comment By: Dan Small (dsmall0)
Date: 2004-11-22 15:32

Message:
Logged In: YES 
user_id=1104154

We are having a similar pbm.  Only in our case clash 
is over versions of jaxen and dom4j.

Btw we have a .war that works with 3.2.5 through 3.2.
7rc1, and works with 4.0.1rc1.  It does _not_ however
work with 4.0.0.

In a couple of hours from now you will be able to 
download the war from

http://orbeon.sourceforge.
net/unstable-blds/presentation-server/

When it doesn't work you get a ClassCastException.

When it does you will see something similar to
this :
http://www.orbeon.com/ois/
.

Btw, shouldn't the fact that jboss exposes these
implementation details ( dom4j version

[JBoss-dev] [ jboss-Bugs-1056747 ] Catalina ContextConfig memoryleak @ undeployment scoped app

2004-12-29 Thread SourceForge.net
Bugs item #1056747, was opened at 2004-10-29 05:27
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1056747group_id=22866

Category: JBossWeb
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Wonne Keysers (wonnekeysers)
Assigned to: Nobody/Anonymous (nobody)
Summary: Catalina ContextConfig memoryleak @ undeployment scoped app

Initial Comment:
See also bug 576913 - OutOfMemory after redeploys

I attached an export of the jProfiler view containing the 
GC path to our scoped ear's UCL after it had been 
updeployed.  There are 3 static Catalina variables which 
are not cleaned up upon undeployment. All related to 
the Digester that parses web.xml and context.xml...

JDK 1.4.2,
JBoss 3.2.7RC1 (from cvs)



ps: Sorry for starting a new bug, but I could not upload 
the image...

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1056747group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1073564 ] CachedConnectionManager - inUseConnections not correct

2004-12-29 Thread SourceForge.net
Bugs item #1073564, was opened at 2004-11-25 22:39
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1073564group_id=22866

Category: JBossCX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Purush Rudrakshala (prudrakshala)
Assigned to: Adrian Brock (ejort)
Summary: CachedConnectionManager - inUseConnections not correct

Initial Comment:
Environment: Windows XP SP2, JDK 1.4.2_05, JBoss 3.2.6

For CachedConnectionManager service debug option is
enabled to monitor connections.

!-- Enable connection close debug monitoring --
attribute name=Debugtrue/attribute

Using jmx-console, if we look at the inUseCount
property. The number displayed is not consitent with
the underlying connection pool. listInUseConnections
shows stack traces for connections that have been
closed long back.  It take a long time for the
inUseCount to drop down, but never drops to 0 even
after the connection pools correctly show inUseCount as 0.


--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-05 17:19

Message:
Logged In: YES 
user_id=175228

This is being tracked via the following jira issue:
http://jira.jboss.com/jira/browse/JBAS-31

--

Comment By: Purush Rudrakshala (prudrakshala)
Date: 2004-12-02 18:25

Message:
Logged In: YES 
user_id=1150762

I am attaching test.jsp that reproduces this problem. After
running the test.jsp few times, please look at CCM
inUseConnections count and run listInUseConnections
operation. In my tests, I see as follows:

[EMAIL PROTECTED]:
STACKTRACE
at
org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:319)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:525)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:887)
at
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:102)
at org.apache.jsp.test_jsp._jspService(test_jsp.java:58)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:158)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118

[JBoss-dev] [ jboss-Bugs-1056478 ] jdbc2 cmp container assumes tx exists

2004-12-29 Thread SourceForge.net
Bugs item #1056478, was opened at 2004-10-28 17:38
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1056478group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Ivan Parra (ioparra)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: jdbc2 cmp container assumes tx exists

Initial Comment:
Schema:22 can get NullPointer
on multi-row finder.  

Session Facade is doing call with supports
the finder is marked as supports.

It worked in 3.2.5, but now null pointers.  

I, personally, don't think supports should be allowed, 
especially for local collections.  Perhaps a more logical 
exception would work?


java.lang.NullPointerException
at 
org.jboss.ejb.plugins.cmp.jdbc2.schema.Schema$1.initialV
alue(Schema.java:42)
at org.jboss.tm.TransactionLocal.get
(TransactionLocal.java:145)
at org.jboss.tm.TransactionLocal.get
(TransactionLocal.java:128)
at 
org.jboss.ejb.plugins.cmp.jdbc2.schema.Schema.flush
(Schema.java:122)
at 
org.jboss.ejb.plugins.cmp.jdbc2.AbstractQueryCommand.f
etchCollection(AbstractQueryCommand.java:101)
at 
org.jboss.ejb.plugins.cmp.jdbc2.JDBCStoreManager2.findE
ntities(JDBCStoreManager2.java:335)
at 
org.jboss.ejb.plugins.CMPPersistenceManager.findEntities
(CMPPersistenceManager.java:278)
at 
org.jboss.resource.connectionmanager.CachedConnection
Interceptor.findEntities(CachedConnectionInterceptor.jav
at org.jboss.ejb.EntityContainer.findLocal
(EntityContainer.java:613)
at sun.reflect.GeneratedMethodAccessor112.invoke
(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at 
org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke
Home(EntityContainer.java:1070)
at 
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome
(AbstractInterceptor.java:88)
at 
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome
(AbstractInterceptor.java:88)
at 
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.inv
okeHome(EntitySynchronizationInterceptor.java:204)
at 
org.jboss.resource.connectionmanager.CachedConnection
Interceptor.invokeHome
(CachedConnectionInterceptor.java:
at 
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome
(AbstractInterceptor.java:88)
at 
org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHo
me(EntityInstanceInterceptor.java:90)
at 
org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHom
e(EntityCreationInterceptor.java:28)
at 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext
(AbstractTxInterceptor.java:88)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxInterceptorCMT.java:341)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome
(TxInterceptorCMT.java:128)
at 
org.jboss.ejb.plugins.SecurityInterceptor.invokeHome
(SecurityInterceptor.java:85)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome
(LogInterceptor.java:120)
at 
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invok
eHome(ProxyFactoryFinderInterceptor.java:93)
at org.jboss.ejb.EntityContainer.internalInvokeHome
(EntityContainer.java:478)
at org.jboss.ejb.Container.invoke
(Container.java:729)
at 
org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeH
ome(BaseLocalProxyFactory.java:347)
at 
org.jboss.ejb.plugins.local.LocalHomeProxy.invoke
(LocalHomeProxy.java:110)
at $Proxy487.findAll(Unknown Source)
at 

TRANSACTION=SUPPORTS
com.activereasoning.session.company.OrgOperationBean.
getAllOrgs(OrgOperationBean.java:142)
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:324)
at 
org.jboss.ejb.StatelessSessionContainer$ContainerInterce
ptor.invoke(StatelessSessionContainer.java:683)
at 
org.jboss.resource.connectionmanager.CachedConnection
Interceptor.invoke
(CachedConnectionInterceptor.java:186)
at 
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor
.invoke(StatelessSessionInstanceInterceptor.java:72)
at 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext
(AbstractTxInterceptor.java:84)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxInterceptorCMT.java:341)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
(TxInterceptorCMT.java:148)
at org.jboss.ejb.plugins.AbstractInterceptor.invoke
(AbstractInterceptor.java:94)
at 
com.activereasoning.metrics.MetricsInterceptor.invoke
(MetricsInterceptor.java:63

[JBoss-dev] [ jboss-Bugs-1048143 ] 3.2.6: Optimist Version Lock not assigneable

2004-12-29 Thread SourceForge.net
Bugs item #1048143, was opened at 2004-10-15 17:23
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1048143group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Ivan Parra (ioparra)
Assigned to: Alexey Loubyansky (loubyansky)
Summary: 3.2.6: Optimist Version Lock not assigneable

Initial Comment:
When defined in jbosscmp-jdbc.xml

optimistic-locking
version-column/
column-nameOCA/column-name
jdbc-typeINTEGER/jdbc-type
sql-typeINTEGER/sql-type
/optimistic-locking

We recieve deployment error saying version_lock does 
not exist.  

This descriptor worked in 3.2.5 and was introduce 
somewhere on the way.

3.2.6
jdk1.4.2_05
win2000



--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Alexey Loubyansky (loubyansky)
Date: 2004-10-19 00:31

Message:
Logged In: YES 
user_id=543482

Till the end of the year I don't have plans to add new
features to CMP unless paying customers ask for this.
I am not an XDoclet committer. Doesn't this work for you?
 * @jboss.optimistic-locking
 *version-column=true
 *field-name=version
 *column-name=VERSION


--

Comment By: Ivan Parra (ioparra)
Date: 2004-10-18 11:43

Message:
Logged In: YES 
user_id=812998

3.2.5 jdbc(1).pm(ie Fake or hidden OCA field).

Are you planning to support both in jdbc2?  If you don't, are 
you planning to update xdoclet so a tag can be exposed to 
support the field-name column?

-Ivan


--

Comment By: Alexey Loubyansky (loubyansky)
Date: 2004-10-16 00:51

Message:
Logged In: YES 
user_id=543482

For which persistence manager it worked in 3.2.5?
Standard persistence manager allows you to have fake fields
in optimistic locking.
jdbc2 pm needs a real field. For example:
 optimistic-locking
version-column/
field-namenextNumber/field-name
 /optimistic-locking

where nextNumber is a real CMP field.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1048143group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-971010 ] 3.2.4 and 4DR4 can not handle spaces in dir names

2004-12-29 Thread SourceForge.net
Bugs item #971010, was opened at 2004-06-11 02:51
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=971010group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: ulf gohde (gohde)
Assigned to: Scott M Stark (starksm)
Summary: 3.2.4 and 4DR4 can not handle spaces in dir names

Initial Comment:
An MBean loads a configuration file from the jboss start 
directory. In our case this directory contains spaces 
whicj is not a problem in JBoss 3.2.2. However, 3.2.4 
and 4DR4 seem to have problems with spaces in 
directory names.

see attached log

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: ulf gohde (gohde)
Date: 2004-08-25 10:12

Message:
Logged In: YES 
user_id=1022717

hehe, as i already stated in my comment from 2004-06-23

--

Comment By: DoctorPizza (doctorpizza)
Date: 2004-08-25 09:49

Message:
Logged In: YES 
user_id=1034988

I concur, it looks like the new XML libraries are causing issues.

--

Comment By: ulf gohde (gohde)
Date: 2004-08-25 09:46

Message:
Logged In: YES 
user_id=1022717

My point exactly. after replacing the xercesimpl.jar and xml-
apis.jar with the versions used in JBoss 3.2.2 it works fine.

--

Comment By: DoctorPizza (doctorpizza)
Date: 2004-08-25 08:25

Message:
Logged In: YES 
user_id=1034988

It may or may not be related, but moving from 3.2.3 to 3.2.5 
broke some XML handling for us, due to space-in-filename-
related issues.

The code was this:
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser saxParser = factory.newSAXParser();
saxParser.parse(myFile, this); // 'this' extends DefaultHandler
where myFile referred to an file with a space in its path.



--

Comment By: ulf gohde (gohde)
Date: 2004-08-03 07:38

Message:
Logged In: YES 
user_id=1022717

Your example does not reflect the described problem at all. As 
i stated in my example the filename does NOT contain path 
information, which means the working directory is autmatically 
used and if that contains spaces you get the error. If you 
pass the whole path it works fine, which means the logic that 
is adding the working directory to the path is buggy.

--

Comment By: Scott M Stark (starksm)
Date: 2004-08-01 07:19

Message:
Logged In: YES 
user_id=175228

This little program does not show a problem using the 3.2.5
parsers.

package xml;

import org.apache.xerces.parsers.DOMParser;
import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
import org.w3c.dom.Node;
import org.w3c.dom.Element;

public class TestFilenameSpaces
{
   public static void main(String[] args) throws Exception
   {
  String filename = /tmp/java/xml/Space Here/ejb-jar.xml;
  DOMParser parser = new DOMParser();
  parser.parse(filename);
  Document doc = parser.getDocument();
  NodeList sessions = doc.getElementsByTagName(session);
  for(int n = 0; n  sessions.getLength(); n ++)
  {
 Element ejb = (Element) sessions.item(n);
 Node name =
ejb.getElementsByTagName(ejb-name).item(0);

System.out.println(name.getFirstChild().getNodeValue());
  }
   }
}


--

Comment By: ulf gohde (gohde)
Date: 2004-06-23 01:11

Message:
Logged In: YES 
user_id=1022717

The code is actually quite simple. The passed filename is just 
the filename w/o any path information. After looking at the 
code it was clear that JBoss is not the problem. I replaced 
the xercesimpl.jar and xml-apis.jar with the versions used in 
JBoss 3.2.2 and after that it is working fine.



public Configuration(String strFilename) throws 
CaseWareException
{
m_strFilename = strFilename;

try
{
DOMParser parser = new DOMParser();

parser.parse(m_strFilename);

m_document = parser.getDocument();

// build hashtable with section name as key and 
corresponding handler name
extractSections();

// build hashtable with section name as key and 
corresponding handler instance
extractNameValuePairs();
}
catch(Exception e)
{
if( Debug.isOnFor(FULL_CLASS

[JBoss-dev] [ jboss-Bugs-1030770 ] Need more tolerant web-console initialization

2004-12-29 Thread SourceForge.net
Bugs item #1030770, was opened at 2004-09-19 10:54
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1030770group_id=22866

Category: Tools
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Need more tolerant web-console initialization

Initial Comment:
If you startup the 4.0 server without the aspect
manager deployed, the web-console is throwing an error
because the AspectManager cannot be found. The web
console is usable, it just does not have the AOP
section. The web console plugin framework should be
tolerant of plugin failures due to missing dependencies
and just display a place holder that indicates the
plugin is not available. 

10:39:47,093 ERROR [Engine] - Root Cause -
java.lang.NoClassDefFoundError: org/jboss/aop/AspectManager
at
java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
at java.lang.Class.getConstructor0(Class.java:1930)
at java.lang.Class.newInstance0(Class.java:278)
at java.lang.Class.newInstance(Class.java:261)
at
org.jboss.console.plugins.helpers.ServletPluginHelper.createPluginWra
pper(ServletPluginHelper.java:90)
at
org.jboss.console.plugins.helpers.ServletPluginHelper.init(ServletPlu
ginHelper.java:60)


--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: David Dossot (ddossot)
Date: 2004-09-23 01:30

Message:
Logged In: YES 
user_id=751436

Unfortunately, the web console is not really usable because
every time it requests something from the missing Aspect
Manager, the tree view is reset, all the leafs are closed...

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1030770group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1036143 ] Missing EJB verifier message

2004-12-29 Thread SourceForge.net
Bugs item #1036143, was opened at 2004-09-28 05:41
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1036143group_id=22866

Category: JBossServer
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Igor Fedorenko (igorfie)
Assigned to: Thomas Diesler (tdiesler)
Summary: Missing EJB verifier message

Initial Comment:
I had service-endpoint/ element specified in my
ejb-jar.xml file, but forgot to package service
endpoint interface. Here is the error message that I
got from JBoss:

quote
08:27:49,290 WARN  [verifier] EJB spec violation: 
Bean   : test/wiki/ejb/Explorer
Method : public abstract EJBHome getEJBHome() throws
RemoteException
Section: 7.11.9
Warning: No warning message found, please file a Bug
report.
/quote




--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1036143group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-995279 ] wsdl generation problem when inheritance

2004-12-29 Thread SourceForge.net
Bugs item #995279, was opened at 2004-07-21 07:40
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=995279group_id=22866

Category: JBossSOAP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: arnaud (arn44fr)
Assigned to: Nobody/Anonymous (nobody)
Summary: wsdl generation problem when inheritance

Initial Comment:
I have a problem when I use jboss EJBProvider. It work's 
fine with axis EJBProvider.

I write a class (Ejb1SessionBean) which implements 
SessionBean. This class contain one method 
named test1

I write a class (Ejb2SessionBean) which extends 
Ejb1SessionBean. This class contain one method 
named test2

In the file web-service.xml
when i use
parameter name=handlerClass 
value=org.jboss.net.axis.server.EJBProvider/
I see one web service (test1) in WSDL

when i use
parameter name=handlerClass 
value=org.apache.axis.providers.java.EJBProvider/
I see two web service (test1 and test2) in WSDL

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: arnaud (arn44fr)
Date: 2004-07-21 08:03

Message:
Logged In: YES 
user_id=1088353

my config
OS: Windows XP SP1
JRE: J2SDK 1.4.2_04 (Sun)
JBoss: 3.2.5

--

Comment By: arnaud (arn44fr)
Date: 2004-07-21 07:46

Message:
Logged In: YES 
user_id=1088353

This problem does not exist in 3.0.6.

--

Comment By: arnaud (arn44fr)
Date: 2004-07-21 07:45

Message:
Logged In: YES 
user_id=1088353

This problem does not exist in 3.0.6.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=995279group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1007192 ] JSF files don't compile when opened in a browser

2004-12-29 Thread SourceForge.net
Bugs item #1007192, was opened at 2004-08-11 04:34
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1007192group_id=22866

Category: JBossWeb
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: kaitken (kaitken)
Assigned to: Nobody/Anonymous (nobody)
Summary: JSF files don't compile when opened in a browser

Initial Comment:
I am using JBoss 3.2.5 (build: CVSTag=JBoss_3_2_5
date=200406251954).
I edited this JSF file (selectLanguage2.jsp) and then
deployed it in JBoss:
==
Code:
%@ taglib uri=http://java.sun.com/jsf/html; prefix=h %
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
html
head
titleSelect Language/title
/head
body
h2Please select your language/h2
f:view
h:form id=selectLanguage
brLanguage:
h:selectOneMenu
f:selectItem itemValue=en itemLabel=English/
f:selectItem itemValue=de itemLabel=German/
/h:selectOneMenu
br
h:commandButton type=submit
value=Submit action=success/
/h:form
/f:view
/body
/html

==
When I call it in the browser, the attached errors
occur in the JBoss log, which I can only fix by
restarting JBoss and repeatedly redeploying the JSF
project until it starts working again.
The first error is:
==
2004-08-06 09:21:42,629 ERROR
[org.jboss.web.localhost.Engine]
StandardWrapperValve[Faces Servlet]: Servlet.service()
for servlet Faces Servlet threw exception
org.apache.jasper.JasperException: Unable to compile
class for JSP

== 
Operating System and version: Windows XP SP1
JDK version: 1.4.2_05


--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1007192group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-1041622 ] invalid schemaLocation generated for imported schema

2004-12-29 Thread SourceForge.net
Bugs item #1041622, was opened at 2004-10-06 10:32
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1041622group_id=22866

Category: None
Group: v4.0
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: John Mazz (mazzgolf)
Assigned to: Anil Saldhana (osdchicago)
Summary: invalid schemaLocation generated for imported schema

Initial Comment:
Somewhat related to 1041495 - see that issue for the 
hello.war attachment - the same war used to replicate 
the problem in that issue is the same war that can be 
used to replicate the problem for this issue.  Same 
platforms as well were used to replicate.

JBoss performs the cool feature of auto-modifying a web 
service's WSDLs (including its imported/included WSDLs 
and schemas).

However, in one instance that modification produces a 
URL that does not point to the resource - I get a HTTP 
500 instead.

Deploy the hello.war (rather than duplicate 
attachments, see issue 1041495 for the attachment 
there).  This assumes issue 1041495 has been corrected 
or worked around (I worked around it by fixing issue 
1041495 inside a JPDA session and continuing).

Once the web service is deployed, look at the hello 
service's WSDL.  You will see an import of another WSDL 
(this is correct):

wsdl:import location=/hello/hello/?
wsdlresource=../spec/wsrf/WS-ResourceProperties-
1_1.wsdl ...

If you point your browser to that location, you can see 
that WS-ResourceProperties-1_1.wsdl file.  Looking at 
that WSDL, you will notice that it, itself, imports 
another file - this time a .xsd schema inside its 
wsdl:types/wsd:schema element:

wsdl:import namespace=... 
schemaLocation=/hello/hello?
wsdlresource=../../wsa/WS-Addressing-2003_03.xsd

That schemaLocation is incorrect - if you point your 
browser to that URL, you will get a HTTP 500 and the 
JBoss logs tells me cannot obtain wsdl resource from: 
WEB-INF/wsdl/wsa/WS-Addressing-2003_03.xsd.

Notice the .. appears twice - I _think_ that is 
incorrect.  I think it only needs to go up to the 
immediate parent directory only - it should not have 
gone up twice to its grandparent directory.  This wsa 
directory is located as a peer directory to wsmf (under 
the spec parent - just like the WS-ResouceProperties-
1_1.wsdl is under wsrf which is under spec).

I think it should be:

schemaLocation=/hello/hello?wsdlresource=../wsa/WS-
Addressing-2003_03.xsd

However, when I put that URL in my browser, I still did 
not get the .xsd served up - I again got a 500.  Funny 
thing is that the JBoss error log says it was still looking 
for WEB-INF/wsdl/wsa/WS-Addressing-2003_03.xsd - 
the same relative path it told me when I used the ../.. 
form.  Using just ../ to go up one level instead of two 
didn't change the relative path JBoss was looking for.

I did not have a chance to debug this to find out how to 
fix this - I just noticed that I was unable to get to 
that .xsd file from my browser (so, therefore, I assume 
any client of this web service will not be able to 
successfully parse its WSDL due to the inability to have 
the server serve up this schema).



--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Anil Saldhana (osdchicago)
Date: 2004-11-16 12:38

Message:
Logged In: YES 
user_id=768753

John, thanks for the directions.

I have fixed this issue in the 4.0 branch.

The fix is in
src/main/org/jboss/webservice/server/InvokerProvider.java

From:
String newResourcePath = orgLocation;
if (resourcePath != null  resourcePath.indexOf(/)  0  )
   newResourcePath =
resourcePath.substring(0,resourcePath.indexOf(/) + 1) +
orgLocation;
String newLocation = requestURI + ?wsdlresource= +
newResourcePath;


To:

String newResourcePath = orgLocation;
 //Bug Fix: [ 1041622 ] invalid schemaLocation generated for
imported schema
//Added the new check!orgLocation.startsWith(../)
 if (resourcePath != null  resourcePath.indexOf(/)  0
  !orgLocation.startsWith(../) )
  newResourcePath = resourcePath.substring(0,
resourcePath.indexOf(/) + 1) + orgLocation;
  
   String newLocation = requestURI + ?wsdlresource= +
newResourcePath; 

--

Comment By: John Mazz (mazzgolf)
Date: 2004-11-16 07:39

Message:
Logged In: YES 
user_id=1134120

Go to the web service's WSDL 
(http://localhost:8080/hello/hello?wsdl).  From there, look at 
the imports - you'll see the import for WS-ResouceProperties-
1_1.wsdl).  Bring your browser to that location (the import 
location will tell you what URL to go

[JBoss-dev] [ jboss-Bugs-717680 ] Make *-service.xml 'validable'

2004-12-29 Thread SourceForge.net
Bugs item #717680, was opened at 2003-04-08 11:24
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=717680group_id=22866

Category: None
Group: v4.0
Status: Closed
Resolution: None
Priority: 5
Submitted By: Han Ming ONG (hanming)
Assigned to: Nobody/Anonymous (nobody)
Summary: Make *-service.xml 'validable'

Initial Comment:
A little while back, I reported this bug:

https://sourceforge.net/tracker/?func=detailamp;atid=376685amp;aid=715680amp;group_id=22866

It brought jboss-service_3_2.dtd closer to what David
Jencks has in mind:

quot;we do not have a dtd for *-service files because
attributes can have xml
 element values.  AFAIK the only way to cater to this
is with namespaces and
 xml schema.  We may need to do this for jboss 4.

 basically...
 lt;depends optional-attribute-name=quot;fooquot;gt;[object name or
another mbean
 dd]lt;/dependsgt;

 and

 lt;depends-list optional-attribute-name=quot;barquot;gt;
   lt;depends-list-elementgt;[o-n or mbean
dd]lt;/depends-list-elementgt;
   lt;depends-list-elementgt;[o-n or mbean
dd]lt;/depends-list-elementgt;
 ...
 lt;/depends-listgt;quot;

jboss-service_3_2.dtd is as good a DTD as in reflecting
what David has in mind but it has a major problem: it
can never be used to validate any *-service.xml file.
This is because XML 1.0 can never have this kind of
construct (represented here as using DTD language, as
opposed to Schema because it cannot be represented
using the latter):

lt;!ELEMENT depends (#PCDATA | mbean)gt;

The closest that one can come up with is

lt;!ELEMENT depends (#PCDATA | mbean)*gt;

This is how XML 1.0 (may XML 1.1 changes it, I don't
know) deal with a class of SGML problem known as the
'pernicious mixed contentquot;. Search Google for more details.

http://www.w3.org/TR/REC-xml#sec-mixed-content

Summary:
---

I know it's too late to change anything for 3.2 but I
have suggestions for 4.0

1. Don't use mixed content, if possible. It's easy to
get it wrong in different level: API, parsing and
writing of DTDs/Schemas.

2. The easiest local workaround for the element
lt;dependsgt; is to use Element wrapper pattern, e.g:

lt;!ELEMENT depends-content (#PCDATA)gt;
lt;!ELEMENT depends (depends-content | mbean)gt;

But that might not be a good overall solution.

3. Bear in mind that XML Schema in designed to work
with XML 1.0, hence the closest one can use Schema to
constraint lt;dependsgt; is:

  lt;xs:element name=quot;dependsquot;gt;
lt;xs:complexType mixed=quot;truequot;gt;
  lt;xs:choicegt;
lt;xs:element ref=quot;mbeanquot;/gt;
  lt;/xs:choicegt;
  lt;xs:attribute name=quot;optional-attribute-namequot;
type=quot;xs:stringquot;/gt;
lt;/xs:complexTypegt;
  lt;/xs:elementgt;

which is not really what David's original intention is.

Thank you, Han Ming



--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:51

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: Han Ming ONG (hanming)
Date: 2003-04-08 12:03

Message:
Logged In: YES 
user_id=741972


1. What you have in mind is a choice contraint: either you
want string content or you want Elements content. In
general, to represent this kind of constraints in
DTD/Schema, one would refer to in the XML lingo as quot;mixed
contentquot;. It is a term that is used to refer to the
potential mixing of String/Element. Whether it is actually
mingled or not does not affect the semantics of the
technical term quot;mixed contentquot;. Hope that is clear.

The point is: it is not possible to contraint what you have
in mind, using XML 1.0's DTD or XML Schema. Which makes the
XML file not validable.

2. There is of course another problem that is clear to
everyone, which is why I didn't bring it up: the use of
quot;ANYquot;. In this case, using CDATA would not solve the problem
because CDATA just means string content that is not parsed
(thus able to contain stuff like 'lt;' etc). The parser and
validator usually just takes the data and spits it back to
higher level.

This problem has to be solved eventually. This bug is not
about it and I don't have a solution.

Cheers.

--

Comment By: David Jencks (d_jencks)
Date: 2003-04-08 11:41

Message:
Logged In: YES 
user_id=60525

I don't understand the problem you describe.  There is no mixed content in the 
depends or depends-list-element elements that I can see.  depends can have one 
object name or one embedded mbean config, and so can depends-list-element.

If I misunderstand please give a concrete example of the mixed content.

The problem I was originally referring

[JBoss-dev] [ jboss-Bugs-1029606 ] jdbc.WrapperDataSource.getConnection is slow

2004-12-29 Thread SourceForge.net
Bugs item #1029606, was opened at 2004-09-16 19:02
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1029606group_id=22866

Category: JBossCX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Elias Ross (genman)
Assigned to: Nobody/Anonymous (nobody)
Summary: jdbc.WrapperDataSource.getConnection is slow

Initial Comment:

I've been profiling JMS code.  When a JMS message is
added to the server, the persistence manager locates an
appropriate DataSource.

Out of the time spent in
org.jboss.mq.Connection.sendToServer, about 28% of the
time is getting the database connection through 
jdbc.WrapperDataSource.getConnection to do its work. 
This is after the pool has been initialized, etc.  (40%
is actual persistence, though most of it is the message
serialization.)

I suspect a lot of the work is calculating a hashCode
on the javax.security.auth.Subject.  SubjectCriKey and
SubjectKey should have this value cached.  Ideally,
when one is accessing the local DB, none of this auth
stuff should have to take place.  Looking at the source
for Subject.java, the hash code is not kept.

BaseConnectionManager2.allocateConnection %CPU=27.949
%Time=27.963 calls=411

Allocations I've seen:

JBossManagedConnectionPool$SubjectActions
is created 3284 times (for 411 getConnection calls)
java.util.Properties (1642 times)

(Disclaimer:  This was done through JBoss profiler,
which may or may not create real numbers.  It does
look, though, that CX is pretty slow for some operations.)

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=1029606group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-973234 ] Cache Invalidation fails when redeploy CMP beans

2004-12-29 Thread SourceForge.net
Bugs item #973234, was opened at 2004-06-15 06:10
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=973234group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Mark Frost (coneheed)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cache Invalidation fails when redeploy CMP beans

Initial Comment:
Java version: 1.4.2_04,Sun Microsystems Inc.
Java VM: Java HotSpot(TM) Client VM 1.4.2_04-b05
,Sun Microsystems Inc.
OS-System: Windows 2000 5.0,x86

We have in place a clustering architecture as described 
in the JBoss clustering book. 

It currently consists of 3 nodes. 2 read-only nodes 
whose CMP entity beans have read-only accessor 
methods and a read-write node where the entity beans 
have read-write accessor methods. 

We use the cache invalidation architecture (based on 
JGroups) to link the read-only and read-write beans 
together. Changes to the RW beans cause invalidation in 
the RO beans and the data remains consistent. 

This all appears to work fine until we redeploy our 
application jar files. The system continues to function 
but we get out of date data in our RO beans. Basically 
the RO beans are not asked to ejbLoad and hence re-
read the data from the DB. 

Bounce all 3 nodes and the system works fine again. 

Redeplying to the RW node is OK but redeploying to the 
RO node breaks the cache invalidation.

Forum article:
http://www.jboss.org/index.html?
module=bbop=viewtopict=50823

Regards

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=973234group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-957704 ] Jaxen-based Applications no longer working wth JBoss =3.2.4

2004-12-29 Thread SourceForge.net
Bugs item #957704, was opened at 2004-05-20 15:07
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=957704group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Sascha-Matthias Kulawik (skulawik)
Assigned to: Scott M Stark (starksm)
Summary: Jaxen-based Applications no longer working wth JBoss =3.2.4

Initial Comment:
Hello,

I have a lot of applications based on XPath, which uses
Jaxen for XPath processing. Through JBoss deliveres
within JBoss 3.2.4 and 4.0 JDom as library, also Jaxen
will be delivered in an incompatible version to the
Jaxen-Final. Also the delivered Jaxen version is not
complete, so generic XPath is no longer working because
of the classloader as well - Im currently using the
lib element in the applications.xml of my ear.

Here is a short snipped which will no longer work with
this versions:
import org.jaxen.BaseXPath;
import org.jaxen.dom.DOMXPath;
public static Iterator findNodes(Node node, String
xpathquery) {
Iterator it = null;
try {
BaseXPath expression = new DOMXPath(xpathquery);
it = expression.selectNodes(node).iterator();
} catch(Exception exe) { }
if(it==null) {
it = new Vector().iterator();
}
return it;
}

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: David Budworth (dbudworth)
Date: 2004-07-21 12:06

Message:
Logged In: YES 
user_id=343354

Added solution to original topic: 
http://jboss.org/index.html?module=bbop=viewtopict=51255

Basic jist is, current dom4j-1.5-rc1 does not seem to expose this conflict.  
It may not be a 100% proper solution, but it does allow someone to move 
from  3.2.4 to 3.2.4 + without getting the nosuchmethod exceptions


--

Comment By: David Budworth (dbudworth)
Date: 2004-07-21 09:01

Message:
Logged In: YES 
user_id=343354

Here is a simple EAR file (source packaged inside) that
shows the conflict with the versions of Jaxen in jdom and
jboss 3.2.4+
(I don't see an attach check box, I'm just hoping that it
will show up after I submit this)


--

Comment By: Sascha-Matthias Kulawik (skulawik)
Date: 2004-05-25 12:57

Message:
Logged In: YES 
user_id=362237

Page not created yet?
Do you have the right URL?

--

Comment By: Scott M Stark (starksm)
Date: 2004-05-21 10:44

Message:
Logged In: YES 
user_id=175228

3.2.4 does not ship with jdom, it ships with dom4j, which is
what includes jaxen. You will have to configure your
application to override the jboss classes using scoped class
loading as described here:
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration

If this does not work create an ear which demonstrates the
problem.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=957704group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-995821 ] Virtual host problem

2004-12-29 Thread SourceForge.net
Bugs item #995821, was opened at 2004-07-22 03:09
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=995821group_id=22866

Category: JBossWeb
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Mr.Sea (mrsea)
Assigned to: Nobody/Anonymous (nobody)
Summary: Virtual host problem

Initial Comment:
   I downloaded and installed JBoss version 3.2.5 without 
any problem.
   When I started JBoss it works fine. No errors in logs.

I have an web application (war) which already running 
on a standalone Tomcat 5.0.26 (different machine).

I copied this web app to Jboss deploy folder 
as mywebapp.war. After copy application initialized and 
deployed automatically without any problem.

But I must use this web app under different host. So I 
configured this web application to JBoss with a different 
host configuration.

I added a virtual host configuration and a context for 
this web app. like this;

 Host name=mrsea.test.com
   Aliasmrsea/Alias
   Valve 
className=org.apache.catalina.valves.AccessLogValve 
prefix=mrsea.test.com_access_log. 
suffix=.txt pattern=common 
directory=${jboss.server.home.dir}/log/
   Logger 
className=org.apache.catalina.logger.FileLogger 
prefix=mrsea.test.com_log. suffix=.txt
directory=${jboss.server.home.dir}/log 
timestamp=true/
   Valve 
className=org.jboss.web.tomcat.security.SecurityAssoc
iationValve/
   !-- Default context parameters --
   DefaultContext cookies=true 
crossContext=true override=true/

   Context path=/mywebapp 
docBase=E:/Java/Projects/WebApplications/MyWebappPr
oject/webroot/doc/rootwebapp 
debug=0 reloadable=true cookies=false
   /Context
 /Host


After restart I saw following messages ;

2004-07-09 09:55:03,831 INFO  
[org.apache.catalina.core.StandardEngine] Starting 
Servlet Engine: Apache Tomcat/5.0.26
2004-07-09 09:55:03,841 INFO  
[org.apache.catalina.core.StandardHost] XML validation 
disabled
2004-07-09 09:55:03,871 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] Starting 
tomcat.mrsea.test.com./mywebapp.Context
2004-07-09 09:55:03,871 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] 
Registering 
j2eeType=WebModule,name=//mrsea.test.com/mywebapp
,J2EEApplication=none,J2EEServer=none for null
2004-07-09 09:55:03,881 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] 
Configuring default Resources
2004-07-09 09:55:03,951 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] No realm 
for this host 
jboss.web:type=Host,host=mrsea.test.com,path=/myweb
app
2004-07-09 09:55:03,951 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] 
Configuring non-privileged default Loader
2004-07-09 09:55:04,142 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] Processing 
standard container startup
2004-07-09 09:55:04,182 INFO  
[org.apache.catalina.loader.WebappLoader] Dual 
registration of jndi stream handler: factory already 
defined
2004-07-09 09:55:04,622 INFO  
[org.apache.catalina.startup.ContextConfig] No default 
web.xml
2004-07-09 09:55:04,652 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] Setting 
deployment descriptor public ID to '-//Sun Microsystems, 
Inc.//DTD Web Application 2.3//EN'
2004-07-09 09:55:04,752 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] Posting 
standard context attributes
2004-07-09 09:55:04,752 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] 
Configuring application event listeners
2004-07-09 09:55:04,752 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context]  
Configuring event listener 
class 'mywebapp.DTServletContextListener'
2004-07-09 09:55:04,802 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] Sending 
application start events
2004-07-09 09:55:05,544 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] Starting 
filters
2004-07-09 09:55:05,574 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] Starting 
completed
2004-07-09 09:55:05,574 DEBUG 
[tomcat.mrsea.test.com./mywebapp.Context] Checking 
for 
jboss.web:j2eeType=WebModule,name=//mrsea.test.com
/mywebapp,J2EEApplication=none,J2EEServer=none
2004-07-09 09:55:05,634 INFO  
[org.apache.catalina.core.StandardHost] Create Host 
deployer for direct deployment ( non-jmx ) 
2004-07-09 09:55:05,644 INFO  
[org.apache.catalina.core.StandardHost] XML validation 
disabled
2004-07-09 09:55:05,654 INFO  
[org.apache.catalina.startup.Catalina] Server startup in 
1833 ms


There is a message like;

2004-07-09 09:55:04,622 INFO  
[org.apache.catalina.startup.ContextConfig] No default 
web.xml

So I think tomcat could not find default web.xml file if 
you define a different host other than localhost.
Default web.xml is 
under ..\server\default\deploy\jbossweb-tomcat50.sar 
folder.

I copied this file in to ..\server\default\conf folder and 
added an attribute to my context tag like this;

defaultWebXml=${jboss.server.home.dir}/conf/web.xml

After restart

[JBoss-dev] [ jboss-Bugs-974735 ] Slow performance of JaasSecurityManager

2004-12-29 Thread SourceForge.net
Bugs item #974735, was opened at 2004-06-17 06:32
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=974735group_id=22866

Category: JBossSX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: iprigg (iprigg)
Assigned to: Nobody/Anonymous (nobody)
Summary: Slow performance of JaasSecurityManager

Initial Comment:
I am operating Jboss 3.2.3 on an Athlon XP 1400+ 
machine with 512 MB of RAM running Windows 2000 
server. I am using JDK 1.4.1.I would like to report a bug 
in the jbossSX framework. In fact I don't know if it is 
actually a bug or just an implementation approach, that 
restricts the performance of the framework. I think it is 
the second, but I would like to know, whether it has 
been noticed and If there are plans for changing it.So 
lets continue with the description of the problem:
What I have tried lately to do was to perform some 
benchmark testing of a service access control data 
model I have created. In order to do that I decided to 
use the jbossSX framework for performing access control 
on 200 stateless EJBs. The security data was stored in 
an LDAP server, so I have created 3 login modules that 
perform specific searches in it, retrieving roles and 
assigning them to users. All Login modules were specified 
as required.The benchmark involved thousand of 
invocations of these EJBs (they all belong in the same 
security domain), within a few minutes, through a 
stateless client EJB, using 
the org.jboss.security.ClientLoginModule in order to 
pass the security credentials (username and password) 
to the server. The ldap server contains the credentials 
of 1000 users. So in practice I had 1000 users randomly 
performing calls on the methods provided by 200 
stateless EJBs. Each EJB contained 5 methods, each 
secured with a different role. Generation of invocation 
requests was extremely fast (about 3000 requests in a 3 
minutes period).
What I noticed, straight from the begining was that the 
whole process was extremely slow. For example 3000 
invocations of the secured EJBs (notice that the 
business logic included in the EJB is minimal, just printing 
a string), consumes the following time:
1) if JAAS cache is disabled 50 minutes
2) if JAAS cache is enabled 15 minutes (notice however 
that we have at maximum 1000 security checks the 
same with the total number of users)
Finally I have performed the same invocations without 
specifying a security domain for the EJBs and the testing 
was completed almost with the post of the final request 
(3 minutes).At first I suspected that the delay was due 
to the searches and the actual processing that takes 
place inside the Login Modules. However by measuring 
the actual time of each operation, I found out that less 
than 1% percent of the total execution time is spent 
there.After several tests, I found out that the actual 
problem was imposed by 
the JAASSecurityManager.class and speciffically its 
boolean method isValid(Principal principal, Object 
credential, Subject activeSubject), which is defined as 
synchronized. This results to all execution threads 
freezing upon accessing the method and ceasing their 
execution for very large periods of time. The more the 
threads accessing the class the more the experienced 
delay.
Is that something that would be taken care in the 
future? or it just needs to be done on this way, so no 
possible solution is foreseen?

--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

Comment By: iprigg (iprigg)
Date: 2004-06-18 09:31

Message:
Logged In: YES 
user_id=1065443

Indeed, I have tested the case you mention, removing the 
synchronized keyword. Of course, as you mention the 
functionality is not correct as, different threads are accessing 
different security contexts, resulting to a hell of exceptions.
Here is my report:
1) Time for serving all requests is not significantly improved: a 
few minutes only, though this may be due to the random way 
requests are generated.  

2) However, what has been significantly improved is the 
serving time as experienced by the service itself (service 
time=the period from the time the invocation of the EJB is 
performed until the result is returned)
To be more specific when the synchronized keyword is 
present, and while requests are kept coming to the jboss 
system, each new request waits on the JaasSecurityManager, 
for a continuously increasing period. This wait is so long that 
after a certain period of high load (about 10 minutes), existing 
transactions start to rollback, (there is a default transaction 
timeout period

[JBoss-dev] [ jboss-Bugs-990882 ] destroying context with tomcat5 happens too late

2004-12-29 Thread SourceForge.net
Bugs item #990882, was opened at 2004-07-14 07:10
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=990882group_id=22866

Category: JBossWeb
Group: v3.2
Status: Open
Resolution: None
Priority: 7
Submitted By: ittay dror (ittay)
Assigned to: Nobody/Anonymous (nobody)
Summary: destroying context with tomcat5 happens too late

Initial Comment:
Hi,

When I stop my JBoss (3.2.5), it first undeployes all beans and only 
then stops the web service. This causes two wrong behaviors:

1. if some client tries to load a page (or send any request to a 
servlet), after some beans are undeployed, and before the service is 
stopped, the servlet will start to work but because the beans were 
undeployed, will get strange errors (NPE etc.)

2. if i want to hook into the contextDestroyed, to perform some 
cleanup, it is too late, since beans have already been undeployed.




--

Comment By: Scott M Stark (starksm)
Date: 2004-12-29 12:52

Message:
Logged In: YES 
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=990882group_id=22866


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


  1   2   3   4   5   6   7   8   9   10   >